Language Selection

English French German Italian Portuguese Spanish

Software Review: The KDE 4.6 Desktop Environment

Filed under
KDE

It’s been three years, and it’s still hard to put the KDE 4.0 debacle behind me. I was running KDE 3.5 on Debian stable happy as a clam, and then one fine day in January of 2008 the KDE folks dumped their brand-new, completely re-vamped desktop environment into our laps. I couldn’t get it for Debian so I installed another distro just to check it out… and used it for less than 24 hours. I could see what they were trying to do, and there were some good ideas there, but the implementation was so unbelievably bad that I missed out on the next two releases altogether. I didn’t try KDE 4.x again until January of last year, when I installed Debian testing with the KDE 4.3 desktop. It was great! Since then KDE has gone from strength to strength. KDE 4.4 was mature and stable, and KDE 4.5 added polish and finesse. KDE 4.6, released a little over a week ago, ups the ante once again.

Hidden Treasure:

A lot of the improvements in 4.6 are behind-the-scenes stuff that the casual user will never really notice. Most important is the move to upower and udev for back-end support, replacing the deprecated Hal. After installing KDE 4.6 I was able to uninstall Hal altogether. Additionally, the move to Akonadi, which will keep all your PIM information in a nice neat database, is finally coming to fruition, although the implementation has been delayed because the 4.6 edition of the KDEPIM suite wasn’t quite ready yet. It’s supposed to ship with KDE 4.6.1, which will be out later this month.

rest here




More in Tux Machines

Black Hat 2014: Open Source Could Solve Medical Device Security

On the topic of source code liability, Greer suggests that eventually software developers, including medical device development companies, will be responsible for the trouble their software causes (or fails to prevent). I think it’s fair to say that it is impossible to guarantee a totally secure system. You cannot prove a negative statement after all. Given enough time, most systems can be breached. So where does this potential liability end? What if my company has sloppy coding standards, no code reviews, or I use a third-party software library that has a vulnerability? Should hacking be considered foreseeable misuse? Read more

Does government finally grok open source?

Yes, the government -- one U.S. federal government employee told me that government IT tends to be "stove-piped," with people "even working within the same building" not having much of a clue what their peers are doing, which is not exactly the open source way. That's changing. One way to see this shift is in government policies. For the U.S. federal government, there is now a "default to open," a dramatic reversal on long-standing practices of spending heavily with a core of proprietary technology vendors. Read more

The OS LinuX Desktop

Reader Oliver wanted to make his Linux Mint desktop look as much like a Mac as possible so others would find it easy to use. Given some of our previous Linux featured desktops, we know it wasn't tough, but the end-result still looks great. Here's how it's all set up. Read more

A Linux Desktop Designed for You

Desktop environments for Linux are not released ready-made. Behind each is a set of assumptions about what a desktop should be, and how users should interact with them. Increasingly, too, each environment has a history -- some of which are many years old. As you shop around for a desktop, these assumptions are worth taking note of. Often, they can reveal tendencies that you might not discover without several days of probing and working with the desktop. Read more