Application: plasma-desktop (0.4) KDE Platform Version: 4.7.2 (4.7.2) "release 5" Qt Version: 4.7.4 Operating System: Linux 3.1.0-1.2-desktop x86_64 Distribution: "openSUSE 12.1 (x86_64)" -- Information about the crash: I had set up Firefox and Thunderbird to start up automatically upon login. I booted the machine with dual monitors attached and as soon as I logged in I adjusted the external monitor's position and waited for Firefox and Thunderbird to finish loading. Soon afterwards something in KDE broke. -- Backtrace: Application: Plasma Desktop Shell (kdeinit4), signal: Segmentation fault [Current thread is 1 (Thread 0x7f03194c5760 (LWP 2703))] Thread 2 (Thread 0x7f02f39d3700 (LWP 2706)): #0 0x00007f0316b39423 in poll () from /lib64/libc.so.6 #1 0x00007f031392ea98 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x00007f031392ef59 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x00007f031814b576 in QEventDispatcherGlib::processEvents (this=0x106ee10, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:424 #4 0x00007f031811fa22 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149 #5 0x00007f031811fc1f in QEventLoop::exec (this=0x7f02f39d2df0, flags=...) at kernel/qeventloop.cpp:201 #6 0x00007f03180375df in QThread::exec (this=<optimized out>) at thread/qthread.cpp:498 #7 0x00007f0318102aef in QInotifyFileSystemWatcherEngine::run (this=0x1112120) at io/qfilesystemwatcher_inotify.cpp:248 #8 0x00007f031803a025 in QThreadPrivate::start (arg=0x1112120) at thread/qthread_unix.cpp:331 #9 0x00007f0317da9f05 in start_thread () from /lib64/libpthread.so.0 #10 0x00007f0316b4253d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f03194c5760 (LWP 2703)): [KCrash Handler] #6 ref (this=0x4043000000000000) at /usr/include/QtCore/qatomic_x86_64.h:121 #7 QString (other=..., this=0x7fffc4f20f80) at /usr/include/QtCore/qstring.h:729 #8 udi (this=0x1ff5d80) at /usr/src/debug/kdelibs-4.7.2/solid/solid/device_p.h:42 #9 Solid::Device::udi (this=0x30c3de8) at /usr/src/debug/kdelibs-4.7.2/solid/solid/device.cpp:104 #10 0x00007f0305ca803d in KFilePlacesItem::device (this=0x30c3db0) at /usr/src/debug/kdelibs-4.7.2/kfile/kfileplacesitem.cpp:107 #11 0x00007f0305caa1e3 in KFilePlacesModel::deviceForIndex (this=<optimized out>, index=<optimized out>) at /usr/src/debug/kdelibs-4.7.2/kfile/kfileplacesmodel.cpp:244 #12 0x00007f02fe3054d5 in Kickoff::SystemModel::refreshNextUsageInfo() () from /usr/lib64/libkickoff.so #13 0x00007f02fe3069fc in Kickoff::SystemModel::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libkickoff.so #14 0x00007f031813714a in QObject::event (this=0x36149e0, e=<optimized out>) at kernel/qobject.cpp:1226 #15 0x00007f03172d2be4 in notify_helper (e=0x22c89b0, receiver=0x36149e0, this=0x6f9010) at kernel/qapplication.cpp:4481 #16 QApplicationPrivate::notify_helper (this=0x6f9010, receiver=0x36149e0, e=0x22c89b0) at kernel/qapplication.cpp:4453 #17 0x00007f03172d7a71 in QApplication::notify (this=0x6e5890, receiver=0x36149e0, e=0x22c89b0) at kernel/qapplication.cpp:4360 #18 0x00007f0318eb2e36 in KApplication::notify (this=0x6e5890, receiver=0x36149e0, event=0x22c89b0) at /usr/src/debug/kdelibs-4.7.2/kdeui/kernel/kapplication.cpp:311 #19 0x00007f031812081c in QCoreApplication::notifyInternal (this=0x6e5890, receiver=0x36149e0, event=0x22c89b0) at kernel/qcoreapplication.cpp:787 #20 0x00007f0318123bf8 in sendEvent (event=0x22c89b0, receiver=0x36149e0) at kernel/qcoreapplication.h:215 #21 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x615f10) at kernel/qcoreapplication.cpp:1428 #22 0x00007f031814b0b3 in sendPostedEvents () at kernel/qcoreapplication.h:220 #23 postEventSourceDispatch (s=<optimized out>) at kernel/qeventdispatcher_glib.cpp:277 #24 0x00007f031392e58d in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #25 0x00007f031392ed88 in ?? () from /usr/lib64/libglib-2.0.so.0 #26 0x00007f031392ef59 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #27 0x00007f031814b50f in QEventDispatcherGlib::processEvents (this=0x6faf90, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:422 #28 0x00007f0317375f2e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=<optimized out>) at kernel/qguieventdispatcher_glib.cpp:204 #29 0x00007f031811fa22 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149 #30 0x00007f031811fc1f in QEventLoop::exec (this=0x7fffc4f21b10, flags=...) at kernel/qeventloop.cpp:201 #31 0x00007f0318123de7 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1064 #32 0x00007f0306c79773 in kdemain () from /usr/lib64/libkdeinit4_plasma-desktop.so #33 0x0000000000408897 in _start () Possible duplicates by query: bug 275554, bug 226911. Reported using DrKonqi
*** Bug 290544 has been marked as a duplicate of this bug. ***
*** Bug 290562 has been marked as a duplicate of this bug. ***
Created attachment 69800 [details] New crash information added by DrKonqi plasma-desktop (0.4) on KDE Platform 4.7.2 (4.7.2) "release 5" using Qt 4.7.4 - What I was doing when the application crashed: Soon after I logged in with multiple applications set to automatically start (Firefox, Thunderbird, Pidgin, ...) I corrected my dual display's position on my laptop. I then wanted to launch another application and plasma crashed. -- Backtrace (Reduced): #7 QString (other=..., this=0x7fff50cfb410) at /usr/include/QtCore/qstring.h:729 #8 udi (this=0x1a54a30) at /usr/src/debug/kdelibs-4.7.2/solid/solid/device_p.h:42 #9 Solid::Device::udi (this=0x2beeea8) at /usr/src/debug/kdelibs-4.7.2/solid/solid/device.cpp:104 #10 0x00007f13b82d103d in KFilePlacesItem::device (this=0x2beee70) at /usr/src/debug/kdelibs-4.7.2/kfile/kfileplacesitem.cpp:107 #11 0x00007f13b82d31e3 in KFilePlacesModel::deviceForIndex (this=<optimized out>, index=<optimized out>) at /usr/src/debug/kdelibs-4.7.2/kfile/kfileplacesmodel.cpp:244
Created attachment 70101 [details] New crash information added by DrKonqi plasma-desktop (0.4) on KDE Platform 4.7.2 (4.7.2) "release 5" using Qt 4.8.0 - What I was doing when the application crashed: Had multiple applications set to automatically set to launch on startup. Hovered mouse over plasma menu before they finished loading. The apps launched and stole focus and when the plasma menu automatically hid again it crashed. -- Backtrace (Reduced): #7 QString (other=..., this=0x7fff2ed2df40) at /usr/include/QtCore/qstring.h:729 #8 udi (this=0x3720790) at /usr/src/debug/kdelibs-4.7.2/solid/solid/device_p.h:42 #9 Solid::Device::udi (this=0x2983d58) at /usr/src/debug/kdelibs-4.7.2/solid/solid/device.cpp:104 #10 0x00007f01d6c5303d in KFilePlacesItem::device (this=0x2983d20) at /usr/src/debug/kdelibs-4.7.2/kfile/kfileplacesitem.cpp:107 #11 0x00007f01d6c551e3 in KFilePlacesModel::deviceForIndex (this=<optimized out>, index=<optimized out>) at /usr/src/debug/kdelibs-4.7.2/kfile/kfileplacesmodel.cpp:244
*** Bug 311670 has been marked as a duplicate of this bug. ***
Created attachment 76913 [details] BruceWolfe plasma-desktop crash trace
I think tracing plasma-desktop is a better way of tracking down the issue. After upgrading to Kubuntu 12.10, I started experience plasma-desktop crashing. The crash assistant though states there is no useful information. So, I now get plasma-desktop to start through the shell using 'plasma-desktop'. In my case, there seems to be a D-bus issue going on plus some issue with device-notifier plasmoid both of which are not triggered by any other plasmoid or script. I've attached an example showing it crashing at the bottom. (In reply to comment #6) > Created attachment 76913 [details] > BruceWolfe plasma-desktop crash trace
Bruce, comment #6 is not the backtrace of the crash, but only the debug output. For more information about backtrace generation, please read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports
(In reply to comment #8) > Bruce, comment #6 is not the backtrace of the crash, but only the debug > output. For more information about backtrace generation, please read > http://techbase.kde.org/Development/Tutorials/Debugging/ > How_to_create_useful_crash_reports I gotta say for the complete package that is the requirement for actual use as a GUI for an entire distribution, KDE is failing miserably. I am all for helping out but to let this kind of situation hang for so long (as per the forum/bug reports), helping developers by creating a backtrace being this hard is a huge showstopper. I am adept at the command line and debugging but this entire process for creating a backtrace for Plasma-Desktop is totally broken and offers absolutely no recourse for the new user or even the IT manager trying to migrate an entire office of staffers we are so trying to build trust from AND convert Mac and Win. So now what? I decided to meticulously follow the building-a-backtrace instructions you noted as if I was someone new to Kubuntu. It stops cold when trying to install plasma-desktop-dbgsym, as follows: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ brucew@HINGE11:/var/crash$ apt-cache policy plasma-desktop plasma-desktop: Installed: 4:4.10.0-0ubuntu1~ubuntu12.10~ppa1 Candidate: 4:4.10.0-0ubuntu1~ubuntu12.10~ppa1 Version table: *** 4:4.10.0-0ubuntu1~ubuntu12.10~ppa1 0 500 http://ppa.launchpad.net/kubuntu-ppa/backports/ubuntu/ quantal/main amd64 Packages 100 /var/lib/dpkg/status 4:4.9.4-0ubuntu0.2 0 500 http://archive.ubuntu.com/ubuntu/ quantal-updates/universe amd64 Packages 4:4.9.2-0ubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ quantal/universe amd64 Packages brucew@HINGE11:/var/crash$ sudo apt-get install plasma-desktop-dbgsym Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: plasma-desktop-dbgsym : Depends: plasma-desktop (= 4:4.9.4-0ubuntu0.2) but 4:4.10.0-0ubuntu1~ubuntu12.10~ppa1 is to be installed E: Unable to correct problems, you have held broken packages. brucew@HINGE11:/var/crash$ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Bruce, please ask in an Ubuntu forum how to install the debug symbols. It looks like you are mixing repositories with different KDE versions (4.9.4 and 4.10).
Bruce, can you reproduce this every time?if so, can you provide: solid-hardware list Also, do you have a cd in the cd drive? can you reproduce this without it? Thanks and sorry for the problems getting the debug symbols :/
Thanks for checking in, Alex. Well, using GDB I cannot get a backtrace. Just comes up blank when running: (gdb) thread apply all backtrace Also, under GDB, if I run as 'plasma-desktop --nofork', it starts up solidly and stays stable first time. Then exiting GBD and running it again with the --nofork switch, it crashes again. I do notice in the process list on login that two instances of plasma-desktop appear. I've attached a hardware list using lspci. If you want something more, let me know.
Created attachment 78079 [details] Bruce's hardware list
Can you try executing it with valgrind?
Created attachment 78189 [details] Bruce Wolfe's plasma-desktop backtrace using Valgrind Here is the backtrace using Valgrind as requested. This was performed with it crashing then plasma-desktop tries to restart again which resulted it finally did successfully. Hopefully you can see both tries. Thanks for looking into this.
Created attachment 78280 [details] 3/21/2013 backtrace Several more here if you please.
Created attachment 78281 [details] 3/21/2013 #2 backtrace
Created attachment 78282 [details] 3/21/2013 #3 backtrace
Created attachment 80475 [details] New crash information added by DrKonqi dolphin (2.2) on KDE Platform 4.10.3 "release 1" using Qt 4.8.4 - What I was doing when the application crashed: I was using KDE Partition Manager to resize a partition on an SD. -- Backtrace (Reduced): #7 QString (other=..., this=0x7fff305dd740) at /usr/include/QtCore/qstring.h:726 #8 udi (this=0x20d29c0) at /usr/src/debug/kdelibs-4.10.3/solid/solid/device_p.h:42 #9 Solid::Device::udi (this=0x21c3ab8) at /usr/src/debug/kdelibs-4.10.3/solid/solid/device.cpp:104 #10 0x00007f88cf4571ef in KFilePlacesItem::device (this=this@entry=0x21c3a80) at /usr/src/debug/kdelibs-4.10.3/kfile/kfileplacesitem.cpp:114 #11 0x00007f88cf457459 in KFilePlacesItem::deviceData (this=0x21c3a80, role=110940459) at /usr/src/debug/kdelibs-4.10.3/kfile/kfileplacesitem.cpp:175
Hello! Sorry to be the bearer of bad news, but this project has been unmaintained for many years so I am closing this bug. Please try again with the latest version and submit a new bug to frameworks-solid if your issue persists. Thank you!