KDE Ships First Beta of Next Generation Plasma Workspace

rohangarg (1966752) writes "KDE announced the beta of its next generation of its plasma workspace today. Built ontop of Qt5 and KDE Frameworks 5, with this transition, all QML-based UIs — which Plasma is built exclusively with — will make use of a new scenegraph and scripting engine, resulting in huge performance wins as well as architectural benefits, such as being able to render using available graphics hardware." There are experimental packages for some distros, and a Live CD (ISO download) available if you want to try it out.

Comments

KDE 3

[Atomic Fro]

Anyone else remember the awesomeness that was the KDE 3 series?

Re:KDE 3

[iggymanz]

no, squatting and pinching off one plasmoid in the punch bowl pretty much means everyone forgets whatever good time they had at the party up to that point

Re:KDE 3

[Anonymous Coward]

Anyone else remember the awesomeness that was the KDE 3 series?

Ah, yes. Life before the f(*&#ing useless cashew. Good times.

Re: KDE 3

[Vyse of Arcadia]

Yeah, but I've gotta say, KDE4 is even more awesome. I've looked into other desktops, and nothing, not even Trinity (fork of KDE3,) can do everything that I use daily in KDE4.

Re:KDE 3

[Anonymous Coward]

Yes I remember, and i miss it.
It seems to me the general motto between the two versions was:
3.x : "Make it work, Make it robust, Make it solid"
4.x: "Make it pretty, Make it poofy, Make it; ohh shiny things!"

I fully understand the stated need for the change: "These old frameworks were a mess, and we need to change just to improve the spagetti we are stuck with."

What I don't understand is why it was instead used to concentrate on flashy widgets that don't really help.

They wanted the codebase to be portable, so that it can be used across a wide span of devices, but what they forgot is that people won't WANT to run it as it is everywhere.
Same mistake Windows and Gnome made: There is no "One interface to Rule them all"

Re: KDE 3

[iggymanz]

more awesome at what, eye candy?

Re:KDE 3

[Sun]

KDE 4, when it first came out, was horrid. I delayed upgrade as long as I could.

Today, however, I don't think that's still true. If your hardware doesn't have 3D you might think otherwise, but I find current KDE 4 useful and functional. I even enable some of the actual effects. There are a few of them (highlight active window, magic lamp minimize) actually contribute to my intuition of what's going on.

Not everything is perfect, but the only feature I still miss from KDE 3 is the different color for the active window's title bar. It is possible, but not worth the trouble, to achieve that effect on KDE 4, but it's not the same. Turns out you can make do without (but, as I said, it's better with).

Shachar

Re: KDE 3

[Anonymous Coward]

At everything. Stability, speed, functions, and yes, eye candy as well.

You criticisms may have been valid up until about 4.4, but since then KDE 4 has been far and away the best desktop environment (much better than 3/series too)

Re: KDE 3

[Anonymous Coward]

Well, yes, KDE4 definitely looks better. It is also more flexible and, in some cases, runs faster than KDE3. Widgets can be quite useful in some situations and KDE can run multiple layouts at the same time, letting users switch between workflows and desktop/mobile styles.

Re:KDE 3

[Anonymous Coward]

Sure.
I still recall those VT100s and the sunny green 80x25 characters and just a keyboard.
1 MB RAM was all I was looking for. Now I gave 16GB and they seem to be inadequate.
Whatever I have now, that ol' stuff was way better, indeed.

Re:KDE 3

[JabberWokky]

I love KDE4. I use it every day. I can, however, see one issue. My biggest fault with KDE4 was that DCOP in KDE3 was a joy to use from a script (bash script, etc). DBUS is a pain in the butt. It's not only much saltier (in terms of syntactical salt) but it also tends to change much more often. Calls that work in one version don't work after an update. DCOP was more simple, had a great interface, and -- most importantly -- the app interfaces tended to stay stable.

I'm really hoping that the Qt5 and QML combo makes up for this, allowing easy scripting and simple use of internals. I used to say that KDE was like the *nix command line, only GUI: a bunch of small apps that exposed a ton of tiny options that you could link together. KDE4 clearly continued that philosophy with DBUS, but I think it was far less successful in that aspect.

Re: KDE 3

[Vyse of Arcadia]

I can configure the desktop to be more useful than just being there. For example, I work with a lot of LaTeX documents, in particular folders containing tests and assignments for the classes I teach. So I have a desktop with a set of folder view plasmoids pointing at this folder full of assignments. One view is filtered to show only .tex files, and the other view is filtered to show only .pdfs. Super convenient, better than popping open Konqueror (or Dolphin) and navigating the folder, even more convenient than popping open a terminal. Way nicer than the garbage dump of "maybe I'll need it later" files that desktops usually are.

Similarly I have a desktop full of folder views and other plasmoids that are useful for my research, a desktop full of folder views and plasmoids useful for coding, et cetera.

This is something I can't do with any other desktop environment, and I've looked. (Well, actually there's a couple of proprietary Windows 7 add-ons that give similar functionality, if I felt like forking over the dough. And using Windows 7.) And other than the desktop itself, the auxillary applications (the ones I use, at least) are all at least as good as they were in KDE3.

Also, KRunner (Alt+F2) with nepomuk is awesome. File search and program launching, yeah, every desktop is decent at those nowadays. But there's a lot of useful KRunner plugins too. Calculator, dictionary, spell-check, search wikipedia, mini command-line shell; it even has a task manager so if a process is misbehaving I don't even have to open a terminal and use htop (unless I'm in the mood to use htop.)

Give it a try, man; it's actually pretty great. And as far as eye-candy and bloat go, I do all this on a four year old netbook. I didn't even disable any of the eye-candy. What bloat?

Re: KDE 3

[Anonymous Coward]

At using up resources on stuff that is, at best, of secondary importance? At insisting to be the star of the show, rather than silently and diligently do what you want?

Re:KDE 3

[flyingfsck]

Yup. I think most people who moan about KDE, never even used it. In my experience, KDE is fast, stable and runs on anything - even little netbooks.

Re:KDE 3

[efitton]

I think we used it for a while. I tried at least KDE 4.0, 4.1, 4.2 and 4.3. When Sergio insisted to SVN that KDE 4.1 was better than 3.X it was the beginning of the end for me. It might be better now, it might be worse. I do know that it was far worse for me for years after KDE 4 came out and at some point you stop looking. And none of that changes that I miss KDE 3 and thought it was a wonderful desktop.

Re:KDE 3

[Sun]

Had I not been able to postpone the migration for as long as I have, I would probably have agreed with you. I tried at least two of the versions you mentioned, and reached conclusions substantially similar to yours. None the less, modern KDE 4 is okay (after some getting used to).

Shachar

Re:KDE 3

[Bill, Shooter of Bul]

No, you're forgetting the beauty of the backend. KDE 4 was all about plasma. In Plasma worskpaces nothing is special. Everything is a plasmoid widget. Nothing is special about the dock, the desktop, or an icon. They all have the same back end object, and can be placed and dealt with in the same way. It was seen as a way to increase the flexibility and configuration of the desktop.

That was job #1, converting everything to plasma. Job #2 was making it pretty, then everything else.

4.0 was poorly explained that it *wasn't* really ready they just called it a .0 to get people to beta test it. I know that makes no sense at all. It was really stupid. KDE was ready for distros and actual end users right around 4.4.

It looks like they've learned their lesson by calling this the beta that it is. Hopefully, distros will be a bit more pragmatic in upgrading this time.

Re:KDE 3

[warrax_666]

Try it again. Seriously.

Re:KDE 3

[morgauxo]

Sure do. Thought about switching to Trinity (KDE3 fork) but it's dependance on QT3 conflicted with newer application's dependancies on QT4.

Re: KDE 3

[morgauxo]

KRunner? Ugggh!

I used to use Alt-F2 that all the time, back when all it did was run applications or open urls. Now it's searching so much junk it's slow. Also, before where I would just type an executable name and hit enter, now it wants to give me a list of possibly similar things and make me click one.

I have the same problem with windows. I'm still used to hitting the windows button, the 'r' key and then typing what I want to open. Now it takes forever to do that and it comes up with all sorts of search results I didn't want.

Re: KDE 3

[Anonymous Coward]

Do you know you can turn unnecessary searches (krunner plugins) off

Re:KDE 3

[HiThere]

KDE4 is now tolerable, especially when I look at the competition. But Gnome2 was better than it has yet become (presuming that it's still improving) and Gnome2 was clearly inferior to KDE3.

The odd thing is that I had no technical problems with the early KDE4 versions. My problems were entirely with the intentional design. Recently, however, technical problems have started to appear. So far it's merely an occasional random lockup, or the icons being spread all across the top menubar after a restart rather than collected together as I specified (and as they often are). Well, this may be due to running Debian testing (actually Jessie, as I don't want to auto upgrade once the release happens). But it's worrisome, especially as they're ramping up an entirely new version of KDE. Perhaps I'll check out QtRazor or some such. Always good to have your options open.

Re:KDE 3

[efitton]

I might, but it honestly isn't easy. I think of it like a restaurant. Your favorite restaurant changes owners. They then change from serving the food you like to trying to provide a "dining experience." You still go a handful of times but you get food poisoning twice and bad service a third time. You stop going, complain about losing your favorite place and start eating at the food truck that just isn't the same but at least you don't get sick. Now the owner doesn't "owe" you anything but you still get the feeling of regret and resentment every time you drive past.

The other issue is that Kasbar was by far my favorite piece of KDE 3 and it isn't back in KDE 4. I kind of wonder, what's the point without that?

Re:KDE 3

[Barsteward]

"4.0 was poorly explained that it *wasn't* really ready they just called it a .0 to get people to beta test it."

No it wasn't bad explained, it was the stupid idiots who couldn't read or comprehend that it was not for users (and those stupid idiots includes the distros).

Re: KDE 3

[Anonymous Coward]

That must be the US customary "forever", defined as 0.73311 metric seconds; ie. not really a significant delay. Besides, if you use windows key + r it only searches %PATH% so that should be almost instantaneous.

Re:KDE 3

[Tough Love]

Right, when kmail worked. Now after a years long running email fiasco, all hope of saving kmail2 and Akonadi must be abandoned, and never again make the mistake of thinking that a database backend works as well just just doing what needs to be done with ordinary filesystem operations.

Re: KDE 3

[phorm]

nepomuk is not something I'd consider a friend. It's always "fun" to be in the middle of something when the system gets sluggish and the CPU fan starts cranking up, only to find that nepomuk decided to go on an indexing rampage and consume 100% of a core or more.

Thankfully, though, it can be disabled. Which generally makes my KDE system quite usable (even with KDE4).

Re: KDE 3

[jma05]

> more awesome at what

Everything. But if I had to pick one feature, I would say Activities.
Apparently, they are not still that widely used. But they are the defining feature of KDE 4 and are quite impressive once you understand to exploit them (docs could be better).

> eye candy?

KDE 4 does not look good, out of the box (Gnome 3, Cinnamon, Pantheon are what I consider to be good looking DEs, out of the box). With a little tweaking though, it looks as good or better than all my (also tweaked) desktops.

Right now, I feel that KDE 4 is a potentially great looking desktop, that is the most functional and the most configurable of the lot - just like KDE 3 was in its day.

The earlier KDE 4 releases were not good. The recent KDE editions are excellent.

Re: KDE 3

[richlv]

kde3 had one area in which it was way, way better - stability/quality. 3.5.10 was extremely stable and without any noticeable bugs.
4.11.5 - despite being nice and very usable - still has some longstanding bugs.

Re:KDE 3

[Anonymous Coward]

Kubuntu at least will be staying with 4.x for the october release - but it will be releasing an alternate ISO specifically for testing 5.

Re:KDE 3

[blackpaw]

Disagree, I've been using kmail2 with gmail & a rackspace imap server for some time now, its been flawless. Also using the google resource to integrate my contacts and calender, reliably synced between gmail and my android phone - something kmail1 was never able to do.

And with baloo replacing nepomuk, email search finally works - far faster than kmail1 ever was, I have over a 100,000 msgs which it can full text search in seconds.

Re: KDE 3

[iggymanz]

point is that used to work without the bloat-delay

Re:KDE 3

[Tough Love]

Nice to hear your positive report, however it conflicts with my own experience where kmail2+akonadi failed in multiple ways so that it is unusable. Recent. Switched to trojita - features are missing, but it works.

Re:KDE 3

[Tough Love]

Maybe kmail2 works tolerably well if you use it very lightly. It certainly does not work for me. Gets stuck all the time, duplicates mails, can't move mails between folders, etc etc.

Re:KDE 3

[Bill, Shooter of Bul]

If you don't want confusion, you do things people expect in a way they expect.

If you have a giant red button that says STOP on a piece of machinery, but it actually speeds things up ( by stopping the speed restrictor from working) that will cause issues, regardless if there is a label above it saying "speed restrictor".

That's essentially what KDE did with a 4.0 release that they never inteded for wider distribution.

Re:KDE 3

[Anonymous Coward]

Gnome gave '3' a bad name

Re:KDE 3

[rdnetto]

And with baloo replacing nepomuk, email search finally works - far faster than kmail1 ever was, I have over a 100,000 msgs which it can full text search in seconds.

If you're using 4.13.0 (the first version with baloo), or about to upgrade, here are two things I learnt the hard way:

• When KNotes asks if you want to migrate your notes, say no. The migration process wipes them, and recovering them is non-trivial.
• If you have any virtual machines, make sure you've got limits.conf set to prevent baloo from eating all your RAM

Such is life on the bleeding edge...
But apart from that, Kmail/Kontact works great for me (especially with Kolab).

Idiots at Ubuntu?

[Anonymous Coward]

Are you reading? "Ready for testing, not production"!
Please, don't repeat the KDE4 fiasco!!!

Re:Idiots at Ubuntu?

[Anonymous Coward]

No worries. Canonical doesn't even do Kubuntu anymore; it's supported by people who care about KDE.

Re:Idiots at Ubuntu?

[Anonymous Coward]

Nope. Kubuntu doens't have its own repos. They draw from Canonical's.
My underpants are already shaking now!

Re:Idiots at Ubuntu?

[ChunderDownunder]

kubuntu is just a series of packages contributed to the Ubuntu repositories, yes. Canonical doesn't invest time in packaging and testing KDE though, this is handled by the community.

Though the Kubuntu maintainers face a split in the next year or so as to whether they adopt XMir or switch to a shiny new Wayland-based experience...

So perhaps we'll see porting efforts directed more to creating a nice ISO for upstream debian, respun as KDEbian? :)

I really hope they'll upgrade the look

[Anonymous Coward]

Although it's just a theme, KDE needs a design refresh IMHO. The look of the default themes is very 10 years ago.

Say what you will about Gnome, but their design in gnome 3, much flatter and cleaner, conveys a much more modern and stylish experience.

Re:I really hope they'll upgrade the look

[Hognoxious]

The look of the default themes is very 10 years ago.

Might give it a go. Because it seems that "now" is either dark grey text on black except for the radioactive pink bits or "invisible controls until you click them" a la gmail.

Are you one of UX dribbletards?

Re:I really hope they'll upgrade the look

[Anonymous Coward]

nope, just an ex-user of KDE

Re:I really hope they'll upgrade the look

[AvitarX]

I really like the look of the default theme, and it doesn't look particularly old to me. I think they went smooth gray before Apple even (Apple having slowly been removing their original candy look with every release).

I generally add some spacer between the close and other buttons, and add an always on top button, but otherwise, I think it's great.

It doesn't look that different

[Roxoff]

I thought when you updated your Open Source desktop environment project to a new release version, you were supposed to take all the really useful tools, features and usability models that had been refined for years and chuck them all in the bin leaving you with a horrible monstrosity that was near impossible to use (and then have it remain that way for at least four years).

Surely, KDE have got this badly wrong.

Re:It doesn't look that different

[bill_mcgonigle]

Surely, KDE have got this badly wrong.

:) Even KDE developers can learn a lesson?

qt5 is very nice, but doing the whole thing in QML is going to be the major win (made feasible by qt5, naturally). I'd estimate it opens up the potential hacker pool by two orders of magnitude. Expect an explosion in community-driven KDE fixes and enhancements once the distros adopt this version.

I stopped using GNOME back when they caught mono, but between Unity and the direction of KDE, the endgame for heavy DE's on Open Source desktops is looking very clear. The mono thing was just an example of a flawed decision making process on that project, which has extended forward to today, with predictable results.

P.S. Slashdot - you've managed to break Plain Old Text mode after 15 years. I've got a manual BR after the quote above to fix rendering.

Re:It doesn't look that different

[efitton]

But will I ever get Kasbar back?

Re:It doesn't look that different

[Arkh89]

Not sure if limited only to Open Source Desktop Environment...

Re:It doesn't look that different

[dcooper_db9]

From the press release:

Plasma Next is intended for end users, but will not provide feature parity with the latest 4.x release, which will come in follow-up releases.

Stability is not yet up to the level where the developers want Plasma Next. With a substantial new toolkit stack below come exciting new crashes and problems that need time to be shaken out.

Performance...will be hampered by various shortcomings. These can and will be addressed, however, much is dependent on components like Qt, Mesa and hardware drivers lower in the stack.

Re:It doesn't look that different

[Barsteward]

well duh, it explains what a BETA is because there are too many idiots out there who can't comprehend

Re:It doesn't look that different

[dcooper_db9]

No, this isn't about beta status. The components are being rewritten and some will not be ready for the release in July. Other components will not have feature parity with the current versions. Again, from the press release:

Plasma Next builds on top of Qt 5. With this transition, all QML-based UIs—which Plasma is built exclusively with—will make use of a new scenegraph and scripting engine, resulting in huge performance wins as well as architectural benefits, such as being able to render using available graphics hardware. Plasma Next is the first complex codebase to transition to KDE Frameworks 5, which is a modular evolution of the KDE development platform into leaner, less interdependent libraries.

Re:It doesn't look that different

[Phil Urich]

But will I ever get Kasbar back?

A lot of the features of Kasbar are built in to the default or alternative taskbars; considering how easy QML is to work with, you might even want to look at hacking away at it yourself.

Personally I'm 100% satisfied with the options currently available, and all the quintessentially awesome KDE stuff I missed during the initial port---Filelight, Yakuake, etc---all made it back in by around 4.4. I honestly never used Kasbar much myself, so I only have dim recollections of it alongside basic descriptions on old websites, but again, people have done some crazy things with Plasma and it's getting easier as things shift towards QML (you can already code mode things in QML in Plasma-Current, AFAIK, but the Plasma-Next development has made this all easier and they've run into the edge cases and lack of features that they've then had to implement to shift towards pure QML themselves, so there should be fewer 'gotchas').

Re:It doesn't look that different

[efitton]

Kasbar was... amazing. I'm guessing the window preview part is back (and the first time I ever saw that was Kasbar on KDE but KDE 4 had to throw the baby out with the bath water). But I also miss being able to change window behavior / decoration with a right click on the task. Want to full screen an application? Right click on the task in taskbar and make it full screen. Right click again (because you could throw your mouse in the corner and get it kasbar back on top) and turn it off. Right click and that window is always on top. Right click and pin it across desktops. Right click and remove window decorations. Fucking powerful, fucking easy, fucking intuitive.

As a teacher with a 1 year old trying to fix up a foreclosure, my desire to have to resurrect something that worked just fine four years ago is... well screw it, I'll just use Windows 7 which sucks but less painful than using KDE 4.

Also: fuck beta. Soylnet News is shaping up ok.

Re:It doesn't look that different

[Roxoff]

Good point. I understand that commercial OS vendors are equally as capable of f*cking up their DEs as the Open Source experts. However, I don't care about the commercial offerings. I -do- care about the DEs I actually use.

All but another GNOME3, please

[Anonymous Coward]

I don't need another d*mn thing that fails to fire up unless you have a $$$ video card with super-duper-extra shiny 3-4-5d crap.

Re:All but another GNOME3, please

[Anonymous Coward]

There is no major graphics chip (Intel, AMD, NVIDIA) that won't run it on hardware (even dirt cheap/integrated) from at least the past 5 years. All you need is OpenGL 2+ compatibility. Hell, you can pick up a GT610 for like 30 bucks. Kind of disappointed at the level of trolls now at /., I expect so much better.

Re:All but another GNOME3, please

[HiThere]

It won't run on my computer, or it wouldn't a year or so ago. And more recent computers don't offer enough improvement over my current machine for me to want to change. (They've basically stopped even making multi-cpu desktops.)

Re:All but another GNOME3, please

[rdnetto]

I'm not sure about Plasma-next, but I could comfortably run KDE 4.10 (or thereabouts) on a tiny little Tegra 2 clocked at 1 GHz with 1 GB of RAM and no hardware acceleration. Chrome ate more RAM than KDE ever did. I've also used KDE quite comfortable on a Pentium 4.

So if KDE doesn't run on your desktop, then I'll wager one of the following is the case:
-you have horribly broken graphics drivers. Try changing the compositing mode, graphic driver, etc.
-your PC is over a decade old
-you have stumbled across an extremely rare and specific bug in KDE

Re:All but another GNOME3, please

[HiThere]

It's Gnome3 that won't run on my computer. And it's not speed, or RAM, it's video card requirements that are the problem.

KDE4 is actually what I'm currently running. It's not as good as KDE3, but it's slightly better than xfce.

Am I the only one who wants 1.x back?

[pecosdave]

Seriously, 1.x compiled against modern libraries for the most part so everything works, but 1.x 1.x was great, fast, light weight, great file browser, easy to customize, no bullshit indexers and what have you insisting upon running in the background, it was a nice setup. Everything since has just sort of bloated.

Misleading title

[Kurast]

I read ship and plasma in the title, and the first thing that came to my mind was some kind of science fiction movie named KDE.

Looks like...

[djdanlib]

That first screenshot... I thought I was looking at a slightly less polished MacOS/X for a minute there. The resemblance is strong.

This sentence should be more common

[hackertourist]

in the release notes of new software:

Plasma Next keeps existing workflows intact...

(Are you listening, Mozilla?)

[AustralisSucks]

Re:This sentence should be more common

[efitton]

If they bring back my KDE 3 workflow I would be interested.

Looks good

[ichthus]

I've teetered between MATE and KDE for the last couple of years -- they're both great, but I like KDE's interface and look/feel a bit more. Also, Dolphin is, IMHO the best file manager for Linux.

But, the thing that still pisses me off about KDE is the handling of cifs mounting (a la smb://). In MATE (or Cinnamon or Gnome2), if I mount a share with smb:// in the file manager (Nautilus, or the newer ones), I get an actual cifs mount. Now, if I open a file on that mount with a photo viewer, or a media player (like VLC), the file manager throws a locally-mounted and accessible file path to the application.

Not so with KDE. Doing the same thing from Dolphin throws the URL of the file (smb://server/share/file.ext) to the application, and the application usually has no effing idea what to do with this. So, I end up either copying the file to my local hdd and opening it from there, or adding an entry to fstab to get a real mount (which is not practical if mounting a new share on someone else's server.) The gvfs way is better than the KIO way.

Re:Looks good

[Anonymous Coward]

> Doing the same thing from Dolphin throws the URL of the file (smb://server/share/file.ext) to the application,
> and the application usually has no effing idea what to do with this

KDE apps know how to handle these just fine; perhaps this tech could be ported to Gnome to make it work there as well, rather than a mounted share.

Re:Looks good

[StormReaver]

The gvfs way is better than the KIO way.

I started with GNOME way back when, but then switched to KDE at version 1.44.

I have a love/hate relationship with KIO. My biggest complaint is that KIO isn't a virtual file system, but rather is just a file copy mechanism. It works great for many uses, but completely falls flat when trying to perform an open/read/close sequence. It copies the entire file to a temporary location, then opens that temporary copy. This is asinine, and is the single largest failing of the IO Slave mechanism.

Even Windows' UNC handles remote files better in this regard, which is saying something since most of Windows networking is a painful joke.

Re:Looks good

[ichthus]

That's great, if you're only using KDE apps. What about apps that are neither KDE/Qt or Gnome? VLC is the first that comes to mind. xmms2 is another. Or, what if I want to use WinAmp through Wine? All of this just works in MATE/Gnome/Cinnamon with gvfs.

The media playing apps should be file system agnostic -- they shouldn't have to know about URLs or network protocols.

Re:Looks good

[ichthus]

This is asinine, and is the single largest failing of the IO Slave mechanism.

Exactly! This is especially idiotic when opening a 1.4 gig (or 4.1 gig or larger!) video file. On my laptop with an SSD, where my /tmp is a tmpfs ramdisk, this is going to fail miserably.

Re:Looks good

[rdnetto]

That's great, if you're only using KDE apps. What about apps that are neither KDE/Qt or Gnome? VLC is the first that comes to mind. xmms2 is another. Or, what if I want to use WinAmp through Wine? All of this just works in MATE/Gnome/Cinnamon with gvfs.
The media playing apps should be file system agnostic -- they shouldn't have to know about URLs or network protocols.

I just tested this with FTP and Audacity, and the files are copied to temporary directories before being opened in non-KDE apps. (Actually, they're copied for both, but to different directories for some reason...)
I'm using Sabayon with KDE 4.13.0 - you're either using an older, buggy version, or there's something wrong with your setup.

32 bit version

[Hognoxious]

Would it be a stupid question to ask if there's a 32 bit version? I have an old stinkpad T40 for experimenting on.

non-PAE please, kthnxbye.

Re:32 bit version

[Anonymous Coward]

Err open source software... 32 bit version... compile one?

Re:32 bit version

[Hognoxious]

I wonder what the odds of that working are.

Just being open source doesn't make it platform independent, if some silly bugger has hardcoded the length of $deity-knows-what.

And this is KDE, remember - not near the top of the list for being a silly bugger free zone.

P.S. Do you actually know what a T40 is?

Re:32 bit version

[ChunderDownunder]

KDE 4 works acceptably on a 32 bit CPU.

What FUD are you spreading that version 5 will be 64bit only?

Re:32 bit version

[rdnetto]

KDE worked fine on 32-bit ARM, last I checked. If they're going through the effort to support a completely different architecture, I'm pretty sure they'll still support 32-bit x86.
Also, I'm not sure that PAE-support should even make a difference to anything running in userspace...

Interesting story

[Anonymous Coward]

Can't wait to learn more about this....

Nepomuk still takes 100% CPU?

[Torp]

Subject says it all...

Re:Nepomuk still takes 100% CPU?

[Anonymous Coward]

Nepomuk has been retired in favor of Baloo. If Baloo is taking 100% CPU for a significant amount of time either hop on the KDE IRC channel or file a bug report. The maintainer has been fixing all of the performance related problems almost as quickly as they pop up.

Re:Nepomuk still takes 100% CPU?

[blackpaw]

Baloo is amazing, it actually delivers what nepomuk promised. I actually use ti regularly day to day - file, email & contact searching.

Notifications

[jones_supa]

I hope the notifications system gets an improvement. It's horribly cluttered in KDE4.

The worst case is when you start a system upgrade: you get a good bunch of weird progress bars and gauges in the notifications area, with a text saying "Waiting for service to start..." That label never disappears, and no progress is ever shown either. Still the updates install fine. Seriously! Does anyone test these systems?

When new updates are available, it shows the number of them but tries to also shove a long list of package names in a small box.

When you copy files, after the process has completed it shows only the name of the last file copied, giving an impression that only that file was copied.

Not very elegant. I'm getting that "open source feeling" again, with my hand trying to reach the anti-depressant bottle.

Re:Notifications

[Anonymous Coward]

use a better distro, the one you currently are using is either broken or misconfigured.

Re:Notifications

[Anonymous Coward]

Complain to your distro - the update notifications don't originate from KDE (obviously, as it is only a DE).

Re:Notifications

[jones_supa]

I see. Just for the record, it's the Fedora 20 KDE spin.

BSD?

[Anonymous Coward]

Will we have good support for the BSDs?

One question

[fnj]

All I want to know is one thing. Will we FINALLY get a resolution-independent UI? One that you don't have to screw with when the dpi departs far from 96? All the style elements; icon sizes, title height, widgets, etc., should be in % of screen size, not pixels. All you should have to set is ONE variable to scale everything to taste.

I can't believe this is such a difficult thing to implement. There is a crying need for it; to hell with the eye candy crap.

Re:One question

[Phil Urich]

See https://community.kde.org/KDE/High-dpi_issues. In fairness, most (in fact, the overwhelming majority) of elements within KDE are resolution independent (hell, KDE has been using SVG icons since well before the KDE4 days), and basically every element can be changed and tweaked as desired, it's just that it takes a shit ton of annoying manual tweaking.

You're right though, it Isn't There Yet (tm). But it is in fact a focus of much of the development; this is generally on the minds of KDE devs, and is being worked towards for Plasma Next, as well as for specific applications; for example, the Yakuake developer is changing the theming engine specifically with resolution-independence and high-DPI screens in mind. So upcoming versions of KDE will be, at very least, closer to supporting high DPI and resolution independence, and I wouldn't be surprised at all if a version or two into Frameworks 5 we get a nice centralized control for scaling the UI.

Re:One question

[Anonymous Coward]

All I want to know is one thing. Will we FINALLY get a resolution-independent UI? One that you don't have to screw with when the dpi departs far from 96? All the style elements; icon sizes, title height, widgets, etc., should be in % of screen size, not pixels. All you should have to set is ONE variable to scale everything to taste.

I can't believe this is such a difficult thing to implement. There is a crying need for it; to hell with the eye candy crap.

you will never get it. programmers can't read and they can't program. the world would be a better place if programmers killed themselves. they suck.
  Tips for developers
        Do not use QFont setPixelSize but use setPointSize, and better, avoid setting a custom size at all. Try to stick with the possibilities from KGlobalSettings (KGlobalSettings::generalFont(), KGlobalSettings::largeFont() etc.)
        Do not use a fixed QSize with images (QPixmap, QIcon...)
        Do not use KIconLoader::StdSizes. Even though it would sound like a good idea to use it, it suffers from the same issue: Hardcoded pixel sizes.
        To get a user's configured icon size, include and use the IconSize function (note: this is not a member function): IconSize(KIconLoader::Small). However, be aware that the user might be able to mess up your apps look by setting some insane values here.
        If you use svg images for icons (for example in plasma) get the standard sizes from some theme elements (e.g. buttons, fonts) and scale your images accordingly. (Don't do this when using pixel based images)
        If you do attempt to program, don't be a dick.

Re:One question

[Anonymous Coward]

In fairness though! How long has it been that we've had displays of widely varying sizes? Smartphones for 10 years now, netbooks for 7 years, tablets for 5. I remember portrait displays from Portrait Display Labs 20 years ago for goodness' sakes!

A lot of these desktop manager upgrades seem to be driven by internal issues. Yet something that many users would immediately benefit from and it's maybe one major revision away, or maybe more, and it's not really on the priority list, is it?

Yes, and who is using Trinity?

[antdude]

https://www.trinitydesktop.org... for KDE3's design?

Notifications have improved greatly recently

[Phil Urich]

I'm using Kubuntu and have seen the notifications look+feel improve greatly lately, and have never seen the issues you describe. So, not to jump on the "you're using the wrong distro" bandwagon (which is probably used as an excuse more than it deserves to be, and often deflects from real issues), but . . . yeah, I'm going to say you should try another distro and see if there's a difference for you.

KDE Devs the Only Stable UI guys on Earth

[thinuspollard]

Am I the only one who thinks that the KDE devs are (almost) the only UI team that has its head screwed on right?

Re:KDE Devs the Only Stable UI guys on Earth

[efitton]

You might be. I thought they were the first to lose their minds.