Application that crashed: plasma-desktop Version of the application: 0.3 KDE Version: 4.3.1 (KDE 4.3.1) Qt Version: 4.5.3 Operating System: Linux 2.6.31-gentoo-r6 x86_64 What I was doing when the application crashed: Well I will be doing my thing -- usen the KDE and then, poof! out of the blue the task panel bottom and another one on the right side disappear and krash dialog appears and then the panel restart again and will be continuing on my way. This happens regualrly and randomly -- I haven't been able to establish conditions or possible cause TJ -- Backtrace: Application: Plasma Workspace (kdeinit4), signal: Segmentation fault [Current thread is 0 (LWP 6742)] Thread 2 (Thread 0x7f66d1598950 (LWP 6745)): #0 0x00007f66f072dda9 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #1 0x00007f66f09997f7 in QWaitCondition::wait () from /usr/lib64/qt4/libQtCore.so.4 #2 0x00007f66ef62ca1d in ?? () from /usr/lib64/qt4/libQtNetwork.so.4 #3 0x00007f66f0998afc in ?? () from /usr/lib64/qt4/libQtCore.so.4 #4 0x00007f66f0729ff7 in start_thread () from /lib/libpthread.so.0 #5 0x00007f66ed48848d in clone () from /lib/libc.so.6 #6 0x0000000000000000 in ?? () Thread 1 (Thread 0x7f66f0f04750 (LWP 6742)): [KCrash Handler] #5 0x00007f66ee4d7b76 in QGraphicsItem::parentItem () from /usr/lib64/qt4/libQtGui.so.4 #6 0x00007f66ee5186c0 in ?? () from /usr/lib64/qt4/libQtGui.so.4 #7 0x00007f66ee52ee80 in QGraphicsGridLayout::addItem () from /usr/lib64/qt4/libQtGui.so.4 #8 0x00007f66d422e3b9 in ?? () from /usr/lib64/kde4/plasma_applet_tasks.so #9 0x00007f66d4235479 in ?? () from /usr/lib64/kde4/plasma_applet_tasks.so #10 0x00007f66d4239bba in ?? () from /usr/lib64/kde4/plasma_applet_tasks.so #11 0x00007f66f0a694cb in QMetaObject::activate () from /usr/lib64/qt4/libQtCore.so.4 #12 0x00007f66d42291f4 in ?? () from /usr/lib64/kde4/plasma_applet_tasks.so #13 0x00007f66d4229561 in ?? () from /usr/lib64/kde4/plasma_applet_tasks.so #14 0x00007f66e8ad5184 in Plasma::Applet::flushPendingConstraintsEvents () from /usr/lib64/libplasma.so.3 #15 0x00007f66e8ad5749 in Plasma::Applet::timerEvent () from /usr/lib64/libplasma.so.3 #16 0x00007f66f0a6640c in QObject::event () from /usr/lib64/qt4/libQtCore.so.4 #17 0x00007f66ee51d64a in QGraphicsWidget::event () from /usr/lib64/qt4/libQtGui.so.4 #18 0x00007f66ee0433f7 in QApplicationPrivate::notify_helper () from /usr/lib64/qt4/libQtGui.so.4 #19 0x00007f66ee04a592 in QApplication::notify () from /usr/lib64/qt4/libQtGui.so.4 #20 0x00007f66eefa0dec in KApplication::notify () from /usr/lib64/libkdeui.so.5 #21 0x00007f66f0a595b6 in QCoreApplication::notifyInternal () from /usr/lib64/qt4/libQtCore.so.4 #22 0x00007f66f0a7d600 in ?? () from /usr/lib64/qt4/libQtCore.so.4 #23 0x00007f66f0a7a594 in ?? () from /usr/lib64/qt4/libQtCore.so.4 #24 0x00007f66ecaf18e3 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #25 0x00007f66ecaf483c in ?? () from /usr/lib/libglib-2.0.so.0 #26 0x00007f66ecaf49be in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #27 0x00007f66f0a7a513 in QEventDispatcherGlib::processEvents () from /usr/lib64/qt4/libQtCore.so.4 #28 0x00007f66ee0bbec6 in ?? () from /usr/lib64/qt4/libQtGui.so.4 #29 0x00007f66f0a58324 in QEventLoop::processEvents () from /usr/lib64/qt4/libQtCore.so.4 #30 0x00007f66f0a584ab in QEventLoop::exec () from /usr/lib64/qt4/libQtCore.so.4 #31 0x00007f66f0a59ff4 in QCoreApplication::exec () from /usr/lib64/qt4/libQtCore.so.4 #32 0x00007f66e529b257 in kdemain () from /usr/lib64/libkdeinit4_plasma-desktop.so #33 0x0000000000407365 in _start () This bug may be a duplicate of or related to bug 215915 Reported using DrKonqi
The crash is related to the taskbar widgets which had some "common" issues in the recent versions. A full backtrace would be useful... (also testing on KDE SC 4.3.3... as the situation should have improved a bit). Regards
Dario, my man, please tell me how to turn on full backtrace. I dunno how long before 4.3.3 is markt stable in the portage, but I can do some backtraces for you on 4.3.1 if your interested
The backtrace may be useful, too bad it is not 100% reproducible... Check this guide: http://www.gentoo.org/proj/en/qa/backtraces.xml you need to setup the "nostrip" FEATURE and recompile kdebase/workspace with debug symbols Regards
Dario, OK my brother, I have 2 packages in the portage: kde-base/libkworkspace and kde-base/plasma-workspace. I recompiled both with "nostrip" FEATURE and also added "-ggdb" to CFLAGS and CXXFLAGS. I will try to make it krash and letcha know how goes it. If those are not the right packages, holler at me. TJ
Created attachment 38681 [details] Backtrace Backtrace of the first time the plasma desktop crashed and DrKonqi popped up. The Dr told me the backtrace was useful. I hope so too.
Dario, my computer went berserk this morning -- plasma started crashing non-stop! I thought I was running Winblows 95 or something ;) OK, here is what I was doing: I was in thunderbird. I copied (Ctrl+C) some text with foreign characters that got mangled. The text that I copied was: ц╝ц│ц■ц│ц▄ц≤ц▒ ц╜ц│ц▄ц┴ц▌ц▐ц≈ц⌠ц▀ц│ц▒ (yeah that's right -- a buncha gibberish -- it was supposed to be a name in russian letters -- I was gonna save it in different encodings and see if I can un-gibberish it) I pressed Alt-F2 and typed in kwrite, as soon as kwrite opened, the plasma crashed! DrKonqi poped up and helped me generate backtrace. It's attached in comment 5 above. Then I opened 2nd copy of kwrite the same way (Alt-F2, kwrite) -- beum, it crashed again! I started experimenting and did it a few more times. It did not always crash. I tried copying english characters and then the above characters, but did not see any relation. But it was not crashing consistently. Then one time after I opened 2nd copy of kwrite, the taskbar at the bottom went bozo. The app buttons got all squashed and it said I had 3 instances of kwrite open, when in fact it was only 2. (Screenshot called fubar.png will be attached below.) I did screen capture and opened kolourpaint. Beum -- the plasma crashed again! I saved the image (fubar.png) and closed kolourpaint. Opened it again and the plasma crashed again. I figured it wasn't the kwrite causing the plasma to crash, as it was now doing the same thing with kolourpaint. I opened up terminal and did pstree and captured it -- I dunno if it might be of any use. It's attached below. Next weird thing started happening. I only had 1 instance of konsole open, but there were 2 buttons for it in the taskbar. When you click either one, it brought up/minimized the same bash window. I captured that -- see below (extra_button.png). After I closed the konsole, one of the buttons went away and the other remained and there is no way of closing it. This is also captured (extra_button_left.png). I actually see this quite often and it might be a disrelated bug, but I am mentioning it just in case. OK my friend, hopefully this is some useful info. Please let me know what else I can do to help. D
Created attachment 38683 [details] Taskbar going bozo App buttons are squashed and it says I have 3 instances of kwrite runnen, when it's only 2 actually runnen
Created attachment 38684 [details] Double button Taskbar shows 2 buttons for konsole, but only 1 instance is runnen and both buttons control the same instance
Created attachment 38685 [details] Leftover button After konsole was closed, one of the buttons went away and the other remained and I can't get rid of it. Have to log out and back in
Dario, KDE 4.3.3 was marked as stable in gentoo portage and I upgraded last night hoping it would fix my problem. I have not experienced crashes yet, but the extra buttons in taskbar are still there. For example, I opened firefox and it showed that I have 2 instances open, but I didn't. Clicking on either button would bring up/minimize the same window. Moreover, when I closed one of the Dolphin windows, it turned into 3rd firefox button on the taskbar!!! :) I closed firefox and I now I have 2 extra firefox buttons that don't do nothing and cannot be closed. Should I file a separate bug for this or should we continue here? TJ
The crashes you were experiencing were bug 199325. The problems with the double buttons of unexistant tasks are being tracked at bug 202199. You can track both issues if you want. Merging this report with bug 199325 Thanks *** This bug has been marked as a duplicate of bug 199325 ***
Thank you very much for the detailed explanations and files :)