KDE 4.1.4 and 4.2 Release Candidate Available Now

The KDE community has made available two new releases of the KDE desktop and applications today. KDE 4.1.4 is the latest update for the KDE 4.1 series. It contains many bugfixes, mainly in the e-mail and PIM suite Kontact and the document viewer Okular. KDE 4.2 RC is the release candidate of KDE 4.2, also bringing new features and thousands of bug fixes to the KDE desktop and applications. KDE 4.1.4 is the last planned update to the KDE 4.1 series and stabilises the 4.1 platform further. It is a recommended update for everyone running KDE 4.1.3 or earlier.

KDE 4.2.0 will be released on January 27th and is considered a significant improvement over the KDE 4.1 series. The beta announcements have all the details. Enjoy our releases, and don't have your head explode when choosing which version to upgrade to.

Dot Categories: 

Comments

by Beat Wolf (not verified)

You should consider using a newer nvidia driver, they are waaay faster for kde4.

For that cashew bug, please make a bugreport with screenshot.

by wanthalf (not verified)

Unfortunately, there is no newer driver for my card, as far as I know. Even this one is still a "beta". Drivers from the 177 and 180 series do not support chips older than GeForce 6. Or did I miss something?

by wanthalf (not verified)

Actually the Desktop Cube works very well, so I don't know, what is the problem with the Sphere, Cylinder and Blur effects.

by wanthalf (not verified)

Oops, the "bloody cashew" is probably innocent in this case. Gkrellm still "jumps away" even though the cashew is sitting in the other corner. Then I have no more idea.

by Anon (not verified)

Probably the desktop layout algorithm, then - I know that's caused me some annoyance before.

by Beat Wolf (not verified)

you should still submit a bug with screenshot, if it's a bug in kde4 it can be fixed, if not, the bugreport will be closed and you can submit it in the Gkrellm bugtracker

by SR (not verified)

We were all waiting for a usable (read "ok, 3.5 can be dropped") version? 4.2 will be what we were waiting for. For those like me who are weekly compiling from svn since the days 4.0 was at his beginning (almost 2 years ago), it's absolutely clear the amount and the quality of work done by all the developers. Now, if I want a crash (with my desktop usage), I really have to go hunt it.

There are show-stoppers for someone (dual monitor, I guess is an example), but I think the vast majority of the things reported here are quite "normal bugs" that don't make KDE4 usage *impossible*. Maybe "harder", but not impossible. Looks weird here and there? Ok, but this won't stop you (or me) from using it *daily*. I agree for example with the amount of space often wasted blank, but ok, I can live with it.

Seeing the development quality and pace, I'm confident that great things will be done. But.

My but is about (like pointed from others in this thread) not in KDE as a whole, but on single apps. For example, single plasmoids. A dumb example is the disk usage plasmoid: its minimum size contraints are definitely too big (I have 6/10 fs mounted) to be left on the screen. Or the annotation plugin, way too "rough edge" to be for common usage.

Another example, invest in integrating Nepomuk/Strigi in each every app KDE base ships (have users understood the value of Nepomuk/Strigi?) so that its potential comes out.

Now that KDE4.2 is such a beautiful thing, please invest on it before stepping into 4.3 (that means, take more care of what exist before creating). Please, forward patches to trunk instead of backporting to branch (I you know what I mean).

The build fails on some boost issues;

[ 67%] Building CXX object poxml/CMakeFiles/swappo.dir/swappo_automoc.o
In file included from /usr/src/kdesdk-4.1.96/umbrello/umbrello/activitywidget.h:16,
from /usr/src/kdesdk-4.1.96/umbrello/umbrello/dialogs/activitydialog.cpp:17:
/opt/lunar/qt/4/include/Qt3Support/q3canvas.h:551: warning: 'virtual void Q3CanvasPolygonalItem::draw(QPainter&)' was hid
/usr/src/kdesdk-4.1.96/umbrello/umbrello/umlwidget.h:231: warning: by 'virtual void UMLWidget::draw(QPainter&, int, int
[ 67%] [ 67%] Building CXX object umbrello/umbrello/CMakeFiles/umbrello.dir/dialogs/activitypage.o
Building CXX object poxml/CMakeFiles/swappo.dir/GettextLexer.o
[ 67%] Building CXX object kompare/komparepart/CMakeFiles/komparepart.dir/komparesplitter.o
[ 67%] Building CXX object poxml/CMakeFiles/swappo.dir/GettextParser.o

Do these types of bugs get filed at http://bugs.kde.org ?

by panzi (not verified)

I'm using http://rdieter.fedorapeople.org/torrents/trash/f10-kde-4.1.96-2.torrent to evaluate KDE 4.2 in VirtualBox. Plasma keeps crashing. Sometimes some kind of grey plasma window covers almost the whole desktop, preventing me to click anything on the desktop. And it never remembers which widgets I removed from the desktop. So every time I relogin I get all the widgets I ever added. Urgh. Thats still really buggy. Almost unusable. Gah, I don't want to switch to a buggy system, but Fedora does not provide security patches to Fedora 8 anymore!

by Anonymous bastard (not verified)

Have they fixed the start menu so that it at last starts fitting the rest of the theme? That blocker level bug has been around from the earliest 4.x development versions :(

by Cyril (not verified)

The menue changes it's appearance with the theme.

Funny, I never payed attention to that. Everybody seems to have his own little blocker. ;-)

by Nadav Kavalerchik (not verified)

KDE 4.2 is my home now !

by Clifford (not verified)

I know that long debates have happened as a result of what has become known as the cashew. I'm one user who thinks its rather ugly. Will there ever be an option to remove this from the desktop or do I have to live with it? It is one of the visual aspects of KDE4.X that I absolutely loathe. I just want it off my desktop.

by Evan "JabberWok... (not verified)

As Tom Patzig writes in http://bugs.kde.org/show_bug.cgi?id=172267 :

"After a hard last week, I released kdebluetooth4-0.3 today.

"This version is no feature release. Kdebluetooth4 provides now full bluez4 support. Therefore a lot of work and api change had to be done in solid-bluetooth.

"Means: kdebluetooth4-0.3 needs the latest solid-bluetooth (kdebase4-workspace) stuff to compile and run. I've patched the openSUSE kdebase4-workspace packages from KDE4.1 and KDE4.2 to support the latest solid-bluetooth changes. If someone needs these patches for other distro packages, let me know. Kdebluetooth4-0.3 also needs the latest bluez and obex-data-server package."

by Evan "JabberWok... (not verified)

(And that'll teach *me* to browse the dot with more than one tab... obviously this reply wasn't intended on this thread. My fault entirely).

by Kolla (not verified)

Two questions that affect professional users:

Does the multimonitor bug yield to those who plug external monitor or projector into the external VGA port, or is it just multi-gfxcard systems that are affected?

And, does KDE4 crypto (SSL/TLS) support CRLs or OCSP yet? It's very annoying that KDE apps happily continue to put up SSL connections to fraudent services that use revoked certificates. It's in fact a major security flaw in KDE.

by Alex (not verified)

Well, progress is quite impressive but I have no hope that 4.2 release will be really usable as 3.5. Developers are eager to make visual effects but real bugs not fixed for eons. For example, I often can not make my notebook go to suspend because stupid button in this dialogue works strange way.

by Rioting_pacifist (not verified)

suspend/resume is usually handled by the OS not the desktop

by Bluez (not verified)

Proper Bluetooth-Support ist essential. Please make it bluez4-compatible. KDE4.2 without it would unfortunately be a No-Go for me.

http://bugs.kde.org/show_bug.cgi?id=172267

by Evan "JabberWok... (not verified)

As Tom Patzig writes in http://bugs.kde.org/show_bug.cgi?id=172267 :

"After a hard last week, I released kdebluetooth4-0.3 today.

"This version is no feature release. Kdebluetooth4 provides now full bluez4 support. Therefore a lot of work and api change had to be done in solid-bluetooth.

"Means: kdebluetooth4-0.3 needs the latest solid-bluetooth (kdebase4-workspace) stuff to compile and run. I've patched the openSUSE kdebase4-workspace packages from KDE4.1 and KDE4.2 to support the latest solid-bluetooth changes. If someone needs these patches for other distro packages, let me know. Kdebluetooth4-0.3 also needs the latest bluez and obex-data-server package."