Version: unknown (using 4.1.80 (KDE 4.1.80 (KDE 4.2 Beta1)), Gentoo) Compiler: i686-pc-linux-gnu-gcc OS: Linux (i686) release 2.6.28-rc5 when a kopete or copy/move/delete notification appears if i left click on notification's title my plasma crash. i run plasma from command line and i took the following last messages plasma(10070) Plasma_WiFi_Signal_Strength::paintAntenna: "off" KCrash: Application 'plasma' crashing... sock_file=/home/cephalon/.kde4/socket-tablet/kdeinit4__0 Object::connect: No such signal OrgKdeKephalConfigurationsInterface::statusChanged() QLayout: Attempting to add QLayout "" to QWidget "", which already has a layout Object::connect: No such slot Kickoff::FavoritesModel::sortFavoritesAscending() Object::connect: No such slot Kickoff::FavoritesModel::sortFavoritesDescending()
Could you also include a backtrace? See http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports
I think to reproduce you have to do the following. Drag a kopete or kmail notification to the desktop, wait some time, drop it. Move it again on the desktop, if plasma did not crash yet. Anwendung: Plasma-Arbeitsfläche (plasma), Signal SIGSEGV [?1034h[Thread debugging using libthread_db enabled] 0x00007f629c291261 in nanosleep () from /lib64/libc.so.6 [Current thread is 0 (LWP 19127)] Thread 3 (Thread 0x425d4950 (LWP 19128)): #0 0x00007f629cccbdd9 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007f629cf3cfd9 in QWaitCondition::wait (this=0xb04740, mutex=0xb04738, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:82 #2 0x00007f62a08267bc in QHostInfoAgent::run (this=0xb04720) at kernel/qhostinfo.cpp:241 #3 0x00007f629cf3c022 in QThreadPrivate::start (arg=0xb04720) at thread/qthread_unix.cpp:185 #4 0x00007f629ccc8040 in start_thread () from /lib64/libpthread.so.0 #5 0x00007f629c2c20cd in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x418c0950 (LWP 19129)): #0 0x00007f629cccbdd9 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007f629cf3cfd9 in QWaitCondition::wait (this=0x8ef020, mutex=0x8ef018, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:82 #2 0x00007f6284581ea8 in RenderThread::run (this=0x8ef008) at /home/kde-devel/kde/src/KDE/kdebase/workspace/plasma/wallpapers/image/renderthread.cpp:90 #3 0x00007f629cf3c022 in QThreadPrivate::start (arg=0x8ef008) at thread/qthread_unix.cpp:185 #4 0x00007f629ccc8040 in start_thread () from /lib64/libpthread.so.0 #5 0x00007f629c2c20cd in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f62a1be6740 (LWP 19127)): [KCrash Handler] #5 Plasma::ExtenderItem::mouseReleaseEvent (this=0xd95bd0, event=0x7fffa9d2ce20) at /home/kde-devel/kde/src/KDE/kdelibs/plasma/extenderitem.cpp:772 #6 0x00007f629de6e08e in QGraphicsItem::sceneEvent (this=0xd95bd0, event=0x7f629c311f50) at graphicsview/qgraphicsitem.cpp:4001 #7 0x00007f629de8dab2 in QGraphicsScenePrivate::sendMouseEvent (this=0x6e9140, mouseEvent=0x7fffa9d2ce20) at graphicsview/qgraphicsscene.cpp:1101 #8 0x00007f629de95081 in QGraphicsScene::mouseReleaseEvent (this=<value optimized out>, mouseEvent=0x7fffa9d2ce20) at graphicsview/qgraphicsscene.cpp:3597 #9 0x00007f629de953f0 in QGraphicsScene::event (this=0x715aa0, event=0x7fffa9d2ce20) at graphicsview/qgraphicsscene.cpp:2966 #10 0x00007f629d95217d in QApplicationPrivate::notify_helper (this=0x656160, receiver=0x715aa0, e=0x7fffa9d2ce20) at kernel/qapplication.cpp:3803 #11 0x00007f629d959f2a in QApplication::notify (this=0x6340a0, receiver=0x715aa0, e=0x7fffa9d2ce20) at kernel/qapplication.cpp:3768 #12 0x00007f62a01a450b in KApplication::notify (this=0x6340a0, receiver=0x715aa0, event=0x7fffa9d2ce20) at /home/kde-devel/kde/src/KDE/kdelibs/kdeui/kernel/kapplication.cpp:307 #13 0x00007f629d024e81 in QCoreApplication::notifyInternal (this=0x6340a0, receiver=0x715aa0, event=0x7fffa9d2ce20) at kernel/qcoreapplication.cpp:587 #14 0x00007f629dea500b in QGraphicsView::mouseReleaseEvent (this=0xa98990, event=0x7fffa9d2d680) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:209 #15 0x00007f629d9a4999 in QWidget::event (this=0xd95bd0, event=0x7fffa9d2d680) at kernel/qwidget.cpp:7163 #16 0x00007f629dea2f7b in QGraphicsView::viewportEvent (this=0xa98990, event=0x7fffa9d2d680) at graphicsview/qgraphicsview.cpp:2337 #17 0x00007f629d024148 in QCoreApplicationPrivate::sendThroughObjectEventFilters (this=<value optimized out>, receiver=0xae2c60, event=0x7fffa9d2d680) at kernel/qcoreapplication.cpp:694 #18 0x00007f629d95214c in QApplicationPrivate::notify_helper (this=0x656160, receiver=0xae2c60, e=0x7fffa9d2d680) at kernel/qapplication.cpp:3799 #19 0x00007f629d95a79a in QApplication::notify (this=<value optimized out>, receiver=0xae2c60, e=0x7fffa9d2d680) at kernel/qapplication.cpp:3528 #20 0x00007f62a01a450b in KApplication::notify (this=0x6340a0, receiver=0xae2c60, event=0x7fffa9d2d680) at /home/kde-devel/kde/src/KDE/kdelibs/kdeui/kernel/kapplication.cpp:307 #21 0x00007f629d024e81 in QCoreApplication::notifyInternal (this=0x6340a0, receiver=0xae2c60, event=0x7fffa9d2d680) at kernel/qcoreapplication.cpp:587 #22 0x00007f629d959b38 in QApplicationPrivate::sendMouseEvent (receiver=0xae2c60, event=0x7fffa9d2d680, alienWidget=0xae2c60, nativeWidget=0xa70800, buttonDown=<value optimized out>, lastMouseReceiver=@0x7f629e2cf760) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:212 #23 0x00007f629d9be259 in QETWidget::translateMouseEvent (this=0xa70800, event=<value optimized out>) at kernel/qapplication_x11.cpp:4040 #24 0x00007f629d9bcc77 in QApplication::x11ProcessEvent (this=0x1a6, event=0x7fffa9d2e100) at kernel/qapplication_x11.cpp:3158 #25 0x00007f629d9e355c in x11EventSourceDispatch (s=0x659680, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:142 #26 0x00007f62996f393a in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #27 0x00007f62996f7040 in ?? () from /usr/lib64/libglib-2.0.so.0 #28 0x00007f62996f71dc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #29 0x00007f629d04d3af in QEventDispatcherGlib::processEvents (this=0x652a90, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:319 #30 0x00007f629d9e2ccf in QGuiEventDispatcherGlib::processEvents (this=0xd95bd0, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:198 #31 0x00007f629d023782 in QEventLoop::processEvents (this=<value optimized out>, flags={i = -1445796880}) at kernel/qeventloop.cpp:143 #32 0x00007f629d02390d in QEventLoop::exec (this=0x7fffa9d2e430, flags={i = -1445796800}) at kernel/qeventloop.cpp:194 #33 0x00007f629d025dfd in QCoreApplication::exec () at kernel/qcoreapplication.cpp:845 #34 0x00007f62a18cf033 in kdemain (argc=1, argv=0x7fffa9d2e7a8) at /home/kde-devel/kde/src/KDE/kdebase/workspace/plasma/shells/desktop/main.cpp:58 #35 0x00007f629c20d436 in __libc_start_main () from /lib64/libc.so.6 #36 0x00000000004007f9 in _start ()
Fixed in trunk.
Could you give me a revision? I updated kdelibs to Revision: 891703 and kdebase to Revision: 891713 after you closed the bug and it is not fixed.
The crash on click got solved with r890249, I think the crash you experienced of which you posted the backtrace (on drop after detach) is actually separate issue. I can't reproduce that crash, so I expect a difference in Qt version. Which revision of qt-copy do you use?
I use the opensuse Qt packages, i.e. 4.4.3. Do you know which patch from qt-copy solves this, so I could check whether it is not yet included in the packages?
I was just about to report the same bug. It definitely is not closed yet :-) Here are the different revisions I use: kdelibs: 892135 kdebase: 892120 kdenetwork: 892102 Here a description of how to reproduce it: Someone sends you a message on kopete::icq/msn. A notification box pops up, you click on it, the chat window opens, _and_ plasma crashes. But it immediately reloads. Please see my attachement for details.
Created attachment 29019 [details] Plasma crash backtrace
Sorry I forgot... I use qt-4.4.2 from gentoo. Guess it could very well be that. I'll install qt-copy just to be sure, and keep you updated.
Well herewith I confirm that the crashes I've been experiencing were really due to my qt version. Using qt-copy, there is no more such crash :-).
@Georges: thanks for the confirmation; btw, when you post backtraces, please include them in the comment rather than uploading as an attachment. that way we can use bugzilla's search feature to find similar crashes =)
@Aaron: right, will do so next time!
Hi All, I've still got this bug in rev 901580. I've tested it with both qt-copy and Mandriva 2009.0's Qt 4.4.3. It occurs almost whenever notify window disappears, whether that's by timeout or by clicking a button on there. Sometimes it doesn't repro on timeout (may depend on the type on notification???) but always repros when clicking view/ignore from kopete message notifications. Here's a backtrace from a timeout on login to msn with lots of user notifications. Cheers, Alan. Application: Plasma Workspace (plasma), signal SIGABRT 0x00007fc5fa96d771 in nanosleep () from /lib64/libc.so.6 [Current thread is 1 (Thread 0x7fc60040a700 (LWP 7485))] Thread 2 (Thread 0x422cc950 (LWP 7565)): #0 0x00007fc5fb3dbf59 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007fc5fb653c49 in QWaitCondition::wait () from /usr/lib64/libQtCore.so.4 #2 0x00007fc5e5dc3b60 in RenderThread::run (this=0x217f9b8) at /storage/kde/trunk/KDE/kdebase/workspace/plasma/wallpapers/image/renderthread.cpp:91 #3 0x00007fc5fb652c62 in ?? () from /usr/lib64/libQtCore.so.4 #4 0x00007fc5fb3d82a3 in start_thread () from /lib64/libpthread.so.0 #5 0x00007fc5fa9aa03d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7fc60040a700 (LWP 7485)): [KCrash Handler] #5 0x00007fc5fa8fe975 in raise () from /lib64/libc.so.6 #6 0x00007fc5fa9001a3 in abort () from /lib64/libc.so.6 #7 0x00007fc5fb18d744 in __gnu_cxx::__verbose_terminate_handler () from /usr/lib64/libstdc++.so.6 #8 0x00007fc5fb18bb46 in ?? () from /usr/lib64/libstdc++.so.6 #9 0x00007fc5fb18bb73 in std::terminate () from /usr/lib64/libstdc++.so.6 #10 0x00007fc5fb18c41f in __cxa_pure_virtual () from /usr/lib64/libstdc++.so.6 #11 0x00007fc5fc5a8ea1 in QGraphicsItem::sceneBoundingRect () from /usr/lib64/libQtGui.so.4 #12 0x00007fc5fc5cad1a in ?? () from /usr/lib64/libQtGui.so.4 #13 0x00007fc5fc5dd99c in ?? () from /usr/lib64/libQtGui.so.4 #14 0x00007fc5fc5de393 in QGraphicsView::items () from /usr/lib64/libQtGui.so.4 #15 0x00007fc5fc5de422 in QGraphicsView::itemAt () from /usr/lib64/libQtGui.so.4 #16 0x00007fc5fc5b1d0b in QGraphicsItem::unsetCursor () from /usr/lib64/libQtGui.so.4 #17 0x00007fc5fc5f688b in ?? () from /usr/lib64/libQtGui.so.4 #18 0x00007fc5fc5f6edb in QGraphicsProxyWidget::~QGraphicsProxyWidget () from /usr/lib64/libQtGui.so.4 #19 0x00007fc5ffcf1f81 in ~PushButton (this=0x4c12db0) at /storage/kde/trunk/KDE/kdelibs/plasma/widgets/pushbutton.cpp:161 #20 0x00007fc5fc5ae587 in QGraphicsItem::~QGraphicsItem () from /usr/lib64/libQtGui.so.4 #21 0x00007fc5fc5e7135 in QGraphicsWidget::~QGraphicsWidget () from /usr/lib64/libQtGui.so.4 #22 0x00007fc5e2a79594 in NotificationWidgetPrivate::completeDetach (this=0x4af4130) at /storage/kde/trunk/KDE/kdebase/workspace/plasma/applets/systemtray/ui/notificationwidget.cpp:148 #23 0x00007fc5e2a7965e in NotificationWidgetPrivate::destroy (this=0x4af4130) at /storage/kde/trunk/KDE/kdebase/workspace/plasma/applets/systemtray/ui/notificationwidget.cpp:219 #24 0x00007fc5e2a796d5 in NotificationWidget::qt_metacall (this=0x4983d90, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=<value optimized out>) at /home/alan/kde/build/KDE/kdebase/workspace/plasma/applets/systemtray/notificationwidget.moc:68 #25 0x00007fc5fb74fc34 in QMetaObject::activate () from /usr/lib64/libQtCore.so.4 #26 0x00007fc5e2a5fec7 in SystemTray::Notification::destroyed (this=0x1d3d, _t1=0x4dfd790) at /home/alan/kde/build/KDE/kdebase/workspace/plasma/applets/systemtray/notification.moc:96 #27 0x00007fc5e2a604ab in ~Notification (this=0x1d3d) at /storage/kde/trunk/KDE/kdebase/workspace/plasma/applets/systemtray/core/notification.cpp:62 #28 0x00007fc5e2a6d0b1 in ~DBusNotification (this=0x4dfd790) at /storage/kde/trunk/KDE/kdebase/workspace/plasma/applets/systemtray/protocols/notifications/dbusnotification.cpp:38 #29 0x00007fc5fb74a8c5 in QObject::event () from /usr/lib64/libQtCore.so.4 #30 0x00007fc5fc08da2d in QApplicationPrivate::notify_helper () from /usr/lib64/libQtGui.so.4 #31 0x00007fc5fc0957ba in QApplication::notify () from /usr/lib64/libQtGui.so.4 #32 0x00007fc5fe8cfd7b in KApplication::notify (this=0x202d210, receiver=0x4dfd790, event=0x4b8b080) at /storage/kde/trunk/KDE/kdelibs/kdeui/kernel/kapplication.cpp:307 #33 0x00007fc5fb73b85f in QCoreApplication::notifyInternal () from /usr/lib64/libQtCore.so.4 #34 0x00007fc5fb73c4fa in QCoreApplicationPrivate::sendPostedEvents () from /usr/lib64/libQtCore.so.4 #35 0x00007fc5fb763f73 in ?? () from /usr/lib64/libQtCore.so.4 #36 0x00007fc5f7d918d2 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #37 0x00007fc5f7d9505d in ?? () from /usr/lib64/libglib-2.0.so.0 #38 0x00007fc5f7d9521b in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #39 0x00007fc5fb763bff in QEventDispatcherGlib::processEvents () from /usr/lib64/libQtCore.so.4 #40 0x00007fc5fc11e72f in ?? () from /usr/lib64/libQtGui.so.4 #41 0x00007fc5fb73a182 in QEventLoop::processEvents () from /usr/lib64/libQtCore.so.4 #42 0x00007fc5fb73a30d in QEventLoop::exec () from /usr/lib64/libQtCore.so.4 #43 0x00007fc5fb73c7bd in QCoreApplication::exec () from /usr/lib64/libQtCore.so.4 #44 0x00007fc5fffec45b in kdemain (argc=1, argv=0x7fff08447678) at /storage/kde/trunk/KDE/kdebase/workspace/plasma/shells/desktop/main.cpp:54 #45 0x00007fc5fa8eb316 in __libc_start_main () from /lib64/libc.so.6 #46 0x0000000000400789 in _start ()
#12 0x00007fc5fc5cad1a in ?? () from /usr/lib64/libQtGui.so.4 #13 0x00007fc5fc5dd99c in ?? () from /usr/lib64/libQtGui.so.4 #14 0x00007fc5fc5de393 in QGraphicsView::items () from /usr/lib64/libQtGui.so.4 #15 0x00007fc5fc5de422 in QGraphicsView::itemAt () from /usr/lib64/libQtGui.so.4 #16 0x00007fc5fc5b1d0b in QGraphicsItem::unsetCursor () from /usr/lib64/libQtGui.so.4 #17 0x00007fc5fc5f688b in ?? () from /usr/lib64/libQtGui.so.4 #18 0x00007fc5fc5f6edb in QGraphicsProxyWidget::~QGraphicsProxyWidget () from /usr/lib64/libQtGui.so.4 that is from Qt. it is a bug in Qt. they have provided a patch for it. the patch is ostensibly in qt-copy (in the patches dir, you need to run apply-patches if you haven't). this is not a problem in plasma. it is a problem in Qt. the Qt engineers discovered the cause for the problem. they said it's a problelm in Qt. they wrote the patch. not sure how much clearer i can make it or how many different ways i can say it. i do wish people would stop re-opening bugs like this, though.
Hi Aaron, My apologies for this. In my defence it was never mention in this bug that qt-copy needed patches applied. The only docs I found on installing qt-copy were here http://techbase.kde.org/User:Dhaumann/Compiling_KDE4#.7E.2Fkde.2Fbuild-qt-copy.sh and that makes no mention of patching. Nor was it mentioned that there is no release of Qt out which contains a fix for this - only that qt-copy should be used. Which I did. There was no explicit statement that you could not expect a released version of Qt to work properly. The fix message here just says "Fixed in trunk" and the resolution was set to fixed - I notice this time you set it to resolved upstream which helps remove ambiguity. Combined with no documentation to say that qt-copy should have patches applied (what's the point of having an svn copy if you don't apply the patches btw? may as well just store the patches). Also go through the #kde-devel irc log I asked there if there was likely to be any difference between Mandriva 2009.0 qt 4.4.3 and qt-copy and received no response. Some people do put the effort in not to overload you with unnecessary bug reports. In those cases you should see why it happened and what would prevent it happening in future. In this case proper documentation would have stopped this from happening and me to unjustifiably receive the aggressive tone you put in your reply. Attacking those who are trying to help is not the best way to ensure they assist in future and I am disappointed you felt it was appropriate. Cheers, Alan.
@Alan: my bad, I should have marked this one as upstream instead of fixed. Also forgive Aaron his tone, but it quite easy to get a bit impatient when going through bug reports: you don't want to know how often this specific crash (the qt one) has got opened and reopened, in quite a lot of different bug reports. The amount of bug reports we receive daily is just insane, which is good on the one hand, but more then half of them (well, I haven't got exact figures, but it feels that way) are duplicates, allready fixed in trunk, or generally worthless because of the lack of useful backtraces/instructions on how to reproduce. It's a bit unfortunate that you used some 'unofficial' instructions on how to build from techbase (how did you get at those?). If you follow http://techbase.kde.org/Getting_Started/Build/KDE4 http://techbase.kde.org/Getting_Started/Build/KDE4/Prerequisites the patches part is mentioned. Your testing is appreciated, and I hope this doesn't stop you from reporting bugs in the future. Also, feel free to ping me on irc about bugs in notifications/jobs/extenders you encounter... my nick is pinda.
*** Bug 176235 has been marked as a duplicate of this bug. ***
*** Bug 167533 has been marked as a duplicate of this bug. ***
*** Bug 172956 has been marked as a duplicate of this bug. ***
*** Bug 178497 has been marked as a duplicate of this bug. ***
*** Bug 178127 has been marked as a duplicate of this bug. ***
*** Bug 167831 has been marked as a duplicate of this bug. ***
Sorry, for the duplicate post, I posted on the duplicate instead of this So,could you point me to the right patch in order to include that in the next revbump of qt-gui on Gentoo Linux? I am not sure which one is on this page http://websvn.kde.org/branches/qt/4.4/patches/ Thanks
@Markos: It's 0254-fix-qgraphicsproxywidget-deletion-crash.diff, though it's generally advised to apply all the qt-copy patches, since that's what kde is mainly tested against.
Yes we are planning a new revision of our qt-gui package with many of qt-copy patches