Description of problem: Just like the summary, plasma crashed when boot into kde and unable to restart automatically. The part of 3D destop still works, but nothing left on the desktop. Version-Release number of selected component (if applicable): 4.8.0 How reproducible: Steps to Reproduce: 1. Boot into KDE 2. Then it happened. 3.
Created attachment 1562 [details] The crash log auto generated by the system. I had installed most debug packages to debug, so I believe it may help.
I confirm the same behavior on my cauldron/x86_64 after having updated today (last update was one week ago) Get as error message : plasma-desktop[8524]: segfault at 0 ip ae23235a sp bfd6af50 error 6 in sip.so[ae226000+16000] (sorry, I have no debug packages)
CC: (none) => linux.briet
Ping? After the update the bug still holds.
Sorry for the late answer. Assigned to the package maintainer. (Please set the status to 'assigned' if you are working on it)
Keywords: (none) => TriagedCC: (none) => lmenutAssignee: bugsquad => balcaen.johnSource RPM: (none) => kdebase4
Personally, the problem came from a third-party plasmoid : veromix. I built-up my KDE4 environment from scratch (after removing ~/.kde4 directory) and the problem reappears when I try to place this plasmoid. Steps to Reproduce: 1. Boot into KDE 2. Download veromix plasmoid 3. Add it to desktop Note : veromix was functional before last update of KDE4.8
@Michel, feel free to add a bug upstream (if there is none) http://code.google.com/p/veromix-plasmoid/issues/list @Chih Wei Yao, same for you ?
Severity: critical => major
Yes, I had installed veromix to substitute kmix in the task bar. So I guess I just need to use plasmapkg to remove it?
Created attachment 1631 [details] Crashlog after remove veromix using plasmapkg --remove veromix-plasmoid I had used the command as following: plasmapkg --remove veromix-plasmoid to remove the plasmoid, but still no help. Attachment is the new crashlog
[kira@Kira ~]$ plasma-desktop QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. QDBusObjectPath: invalid path "" QDBusObjectPath: invalid path "" QGraphicsLinearLayout::insertItem: cannot insert null item QGraphicsLinearLayout::insertItem: cannot insert null item plasma-desktop(22844)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result in instability plasma-desktop(22844)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result in instability plasma-desktop(22844)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result in instability QGraphicsLinearLayout::insertItem: cannot insert null item QGraphicsLinearLayout::insertItem: cannot insert null item plasma-desktop(22844)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result in instability KCrash: Attempting to start /usr/bin/plasma-desktop from kdeinit sock_file=/home/kira/.kde4/socket-Kira.AEDLab/kdeinit4__0 plasma-desktop(22843): Communication problem with "plasma-desktop" , it probably crashed. Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Message did not receive a reply (timeout by message bus)" " [kira@Kira ~]$ KCrash: Application 'plasma-desktop' crashing... KCrash: Attempting to start /usr/lib64/kde4/libexec/drkonqi from kdeinit sock_file=/home/kira/.kde4/socket-Kira.AEDLab/kdeinit4__0 Another error message if I re-execute the plasma-desktop from the command line.
I found another plasmoid that would cause the same problem: clockwallpaper. Using brute force , i.e. remove the whole folder containing the plasmoid, solves the problem.
Keywords: (none) => UPSTREAMSummary: Plasma crashed when boot into KDE and unable to restart automatically => Plasma crashed (thirty part: veromix, clockwallpaper)
From the backtrace available in comment #1 the crash seems to be related to python sip. So maybe someone (Luc ? :p ) can try to rebuild python-kde4 because i'm wondering if someone did not update python (or python-qt4) without rebuilding python-kde4.
CC: (none) => balcaen.john
Indeed, python-kde4 was not rebuilt after python-qt4 4.9.1 and python-sip 4.13.2 updates. I just rebuilt it. It should be soon available on mirrors.
(In reply to comment #12) > Indeed, python-kde4 was not rebuilt after python-qt4 4.9.1 and python-sip > 4.13.2 updates. That explain only the crash of plasmapkg, I'am right ? :)
(In reply to comment #12) > Indeed, python-kde4 was not rebuilt after python-qt4 4.9.1 and python-sip > 4.13.2 updates. > > I just rebuilt it. It should be soon available on mirrors. Maybe we should drop a note in python-qt4 & python-sip spec so fwang can rebuild pykde4 when it's upgrading thoses packages since he's the de facto maintainer for thoses (how long as i remember he's the more active on thoses package). The other (but more ugly) solution is to add some version-release dependency during build time (In reply to comment #13) > (In reply to comment #12) > > Indeed, python-kde4 was not rebuilt after python-qt4 4.9.1 and python-sip > > 4.13.2 updates. > > That explain only the crash of plasmapkg, I'am right ? :) It's also explain the crash of plasma-desktop too since it was trying to load a python related applet. Here it would have been possible to « narrow » the culprit plasmoid using plasmoidviewer to load the plasma applet (i wrote it here so our QA team can use it later to get more info for us :p).
Veromix plasmoid is now OK with last python-kde4 !
Ok so closing.
Keywords: UPSTREAM => (none)Status: NEW => RESOLVEDResolution: (none) => FIXED