Language Selection

English French German Italian Portuguese Spanish

KDE 4.2 Progress Report

Filed under

Well, I’ve been a few days with KDE 4.2 and thought I’d give a little insight of my experience and why I made the decision to go back to KDE 3.5.10.


I had 2 crashes with KDE 4.2, not surprisingly related to the Plasma portion of the desktop. Once while changing themes, and another while changing the height of a second panel.

The Pros:

Speed. The desktop seemed to be quite a bit faster, thanks to the implementation of QT 4.

KWin Composite engine is very nice. However, I do with I could use mouse gestures or change the keyboard keys to my liking.

It works. I contemplated putting this as a pro, but then I considered my negative experience with previous versions of KDE 4 (including KDE 4.1).

Sub-pixel hinting enabled by default

The Cons:

Leaking Plasma Everywhere!

bushweed.blogspot: KDE 4.2 is out and a lot of people are calling it the the KDE 4 release that is desktop ready. Honestly, i've been using "UNSTABLE" branch for a while, and there is a definite improvement between KDE 4.1 and 4.2. Plasma has been a somewhat controversial part of KDE 4, however given time, most people agree that it is the way forward. The technology and ideas in behind Plasma are very progressive and have resulted in the most extensibly beautiful desktop currently available on any form of hardware capable of running KDE 4 ( this sentence took a long time to work out, purely because saying "on the pc" excludes the large variety of platforms that modern desktop Linux supports ). So, having a new pc that can handle some decent Inkscape and Gimp work, i thought i should have a shot at some Plasma theming.

rest here

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

NATS Messaging Project Joins Cloud Native Computing Foundation

The Cloud Native Computing Foundation (CNCF) voted on March 14 to accept the NATS messaging project as its newest hosted effort. The NATS project is an open-source distributed messaging technology that got its start seven years ago and has already been deployed by multiple organizations including Ericsson, Comcast, Samsung and General Electric (GE). "NATS has room to grow as cloud native adds more use cases and grows adoption, driven by Kubernetes and containers," Alexis Richardson, Chair of the Technical Oversight Committee (TOC) at the CNCF told eWEEK. "CNCF provides a way to scale community and education so that adopters can engage faster and at all levels." Read more

The 'New' (and 'Improved') Microsoft

lkml: remove eight obsolete architectures

In the end, it seems that while the eight architectures are extremely different, they all suffered the same fate: There was one company in charge of an SoC line, a CPU microarchitecture and a software ecosystem, which was more costly than licensing newer off-the-shelf CPU cores from a third party (typically ARM, MIPS, or RISC-V). It seems that all the SoC product lines are still around, but have not used the custom CPU architectures for several years at this point. Read more

If you hitch a ride with a scorpion… (Coverity)

I haven’t seen a blog post or notice about this, but according to the Twitters, Coverity has stopped supporting online scanning for open source projects. Is anybody shocked by this? Anybody? [...] Not sure what the story is with Coverity, but it probably has something to do with 1) they haven’t been able to monetize the service the way they hoped, or 2) they’ve been able to monetize the service and don’t fancy spending the money anymore or 3) they’ve pivoted entirely and just aren’t doing the scanning thing. Not sure which, don’t really care — the end result is the same. Open source projects that have come to depend on this now have to scramble to replace the service. [...] I’m not going to go all RMS, but the only way to prevent this is to have open tools and services. And pay for them. Read more