Seems that KDE 4.10.0 and QT (64bit) are causing problems for some users on different distros
The dilfridge blog - Friday, February 8, 2013KDE 4.10.0 plasma-desktop crashes and qt frustrations
While on my machine KDE 4.10.0 runs perfectly fine, unfortunately a lot of Gentoo users see immediate crashes of plasma-desktop - which makes the graphical desktop environment completely unuseable. We know more or less what happened in the meantime, just not how to properly fix it...
plasma-desktop uses a new code path in 4.10, which triggers a Qt bug leading to immediate SIGSEGV.
The Qt bug only becomes fatal for some compiler options, and only on 64bit systems (amd64).
The Qt bug may be a fundamental architectural problem that needs proper thought.
The bugfixing situation:
Reverting the commit to plasma-workspace that introduced the problem makes the crash go away, but plasma-desktop starts hogging 100% CPU after a while. (This is done in plasma-workspace-4.10.0-r1 as a stopgap measure.) Kinda makes sense since the commit was there to fix a problem - now we hit the original problem.
The bug seems not to occur if Qt is compiled with CFLAGS="-Os". Cause unknown.
David E. Narváez aka dmaggot wrote a patch for Qt that fixes this particular codepath but likely does not solve the global problem.
So far comments from Qt upstream indicate that this is in their opinion not the right way to fix the problem.
Our Gentoo Qt team understandably only wants to apply a patch if it has been accepted upstream.
Right now, the only option we (as Gentoo KDE team) have is wait for someone to pick up the phone. Either from KDE (to properly use the old codepath or provide some alternative), or from Qt (to fix the bug or apply a workaround)...http://dilfridge.blogspot.co.uk/2013/02/kde-4100-plasma-desktop-crashes-and-qt.html