While trying to move a window to another virtual desktop by "Right-Click on window title bar > Move to Desktop > Left-Click onto Entry No. 16" the window manager KWin crashed an restarted. The following bug report which had to be stored in a file because I repeatedly got an error message (No. 410 of http I think) from the kde bug reporting assistant that submission isn't possible due to not being logged in (bugzilla). But I'm sure I was logged in -- got possible duplicates of my error report after typing my user name and password that I use here on the web interface, too. Here the bug report: Application: kwin (4.11.9) KDE Platform Version: 4.11.5 Qt Version: 4.8.5 Operating System: Linux 3.11.10-17-desktop x86_64 Distribution: "openSUSE 13.1 (Bottle) (x86_64)" -- Information about the crash: - What I was doing when the application crashed: Right-Click on window title bar > Move to Desktop > Left-Click onto Entry No. 16 => KWin crashes (only sometimes, but particularly when doing the described action) The crash can be reproduced sometimes. -- Backtrace: Application: KWin (kwin), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fdf61d91880 (LWP 1181))] Thread 4 (Thread 0x7fdf2e54b700 (LWP 1205)): #0 0x00007fdf5b5960af in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007fdf3b1884cb in ?? () from /usr/lib64/dri/r600_dri.so #2 0x00007fdf5b5920db in start_thread () from /lib64/libpthread.so.0 #3 0x00007fdf6158e90d in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7fdf2bfee700 (LWP 1207)): #0 0x00007fdf5b5960af in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007fdf6078a8cb in QTWTF::TCMalloc_PageHeap::scavengerThread (this=0x7fdf60a88f00 <QTWTF::pageheap_memory>) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2359 #2 0x00007fdf6078a909 in QTWTF::TCMalloc_PageHeap::runScavengerThread (context=<optimized out>) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1464 #3 0x00007fdf5b5920db in start_thread () from /lib64/libpthread.so.0 #4 0x00007fdf6158e90d in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7fdf43e25700 (LWP 23474)): #0 QTimerInfoList::timerWait (this=this@entry=0x7fdf3c016d08, tm=...) at kernel/qeventdispatcher_unix.cpp:459 #1 0x00007fdf5b959884 in QEventDispatcherUNIX::processEvents (this=0x7fdf3c0008f0, flags=...) at kernel/qeventdispatcher_unix.cpp:938 #2 0x00007fdf5b927d0f in QEventLoop::processEvents (this=this@entry=0x7fdf43e24d20, flags=...) at kernel/qeventloop.cpp:149 #3 0x00007fdf5b928005 in QEventLoop::exec (this=this@entry=0x7fdf43e24d20, flags=...) at kernel/qeventloop.cpp:204 #4 0x00007fdf5b826fef in QThread::exec (this=this@entry=0x318c890) at thread/qthread.cpp:536 #5 0x00007fdf5b909513 in QInotifyFileSystemWatcherEngine::run (this=0x318c890) at io/qfilesystemwatcher_inotify.cpp:256 #6 0x00007fdf5b82968f in QThreadPrivate::start (arg=0x318c890) at thread/qthread_unix.cpp:338 #7 0x00007fdf5b5920db in start_thread () from /lib64/libpthread.so.0 #8 0x00007fdf6158e90d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7fdf61d91880 (LWP 1181)): [KCrash Handler] #5 begin (this=0x1c5) at ../../src/corelib/tools/qlist.h:101 #6 contains (t=@0x7fff09e23578: 0x3dca810, this=0x1c5) at ../../src/corelib/tools/qlist.h:882 #7 QActionGroup::addAction (this=0x28080c0, a=0x3dca810) at kernel/qactiongroup.cpp:180 #8 0x00007fdf618fb70c in ?? () from /usr/lib64/libkdeinit4_kwin.so #9 0x00007fdf5b93cd68 in QMetaObject::activate (sender=sender@entry=0x3fee110, m=m@entry=0x7fdf5b559c80 <QMenu::staticMetaObject>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at kernel/qobject.cpp:3556 #10 0x00007fdf5aecce20 in QMenu::aboutToShow (this=this@entry=0x3fee110) at .moc/release-shared/moc_qmenu.cpp:164 #11 0x00007fdf5aecfd1d in QMenu::popup (this=0x3fee110, p=..., atAction=atAction@entry=0x0) at widgets/qmenu.cpp:1844 #12 0x00007fdf5aed135b in QMenu::internalDelayedPopup (this=this@entry=0x37459f0) at widgets/qmenu.cpp:3057 #13 0x00007fdf5aed2dd4 in QMenu::timerEvent (this=0x37459f0, e=<optimized out>) at widgets/qmenu.cpp:2917 #14 0x00007fdf5b940f31 in QObject::event (this=this@entry=0x37459f0, e=e@entry=0x7fff09e23e90) at kernel/qobject.cpp:1165 #15 0x00007fdf5aaf7e4b in QWidget::event (this=this@entry=0x37459f0, event=event@entry=0x7fff09e23e90) at kernel/qwidget.cpp:8846 #16 0x00007fdf5aed53eb in QMenu::event (this=0x37459f0, e=0x7fff09e23e90) at widgets/qmenu.cpp:2481 #17 0x00007fdf5aaa88ac in QApplicationPrivate::notify_helper (this=this@entry=0x1ae9020, receiver=receiver@entry=0x37459f0, e=e@entry=0x7fff09e23e90) at kernel/qapplication.cpp:4562 #18 0x00007fdf5aaaee70 in QApplication::notify (this=0x7fff09e24f20, receiver=0x37459f0, e=0x7fff09e23e90) at kernel/qapplication.cpp:4348 #19 0x00007fdf601dc18a in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5 #20 0x00007fdf5b9290ad in QCoreApplication::notifyInternal (this=0x7fff09e24f20, receiver=0x37459f0, event=0x7fff09e23e90) at kernel/qcoreapplication.cpp:949 #21 0x00007fdf5b95883c in sendEvent (event=<optimized out>, receiver=<optimized out>) at kernel/qcoreapplication.h:231 #22 QTimerInfoList::activateTimers (this=0x1ae9a88) at kernel/qeventdispatcher_unix.cpp:636 #23 0x00007fdf5b958ef0 in QEventDispatcherUNIX::activateTimers (this=this@entry=0x1a72a70) at kernel/qeventdispatcher_unix.cpp:893 #24 0x00007fdf5b959860 in QEventDispatcherUNIX::processEvents (this=this@entry=0x1a72a70, flags=...) at kernel/qeventdispatcher_unix.cpp:955 #25 0x00007fdf5ab46256 in QEventDispatcherX11::processEvents (this=0x1a72a70, flags=...) at kernel/qeventdispatcher_x11.cpp:152 #26 0x00007fdf5b927d0f in QEventLoop::processEvents (this=this@entry=0x7fff09e241e0, flags=...) at kernel/qeventloop.cpp:149 #27 0x00007fdf5b928005 in QEventLoop::exec (this=this@entry=0x7fff09e241e0, flags=...) at kernel/qeventloop.cpp:204 #28 0x00007fdf5aed41e7 in QMenu::exec (this=0x37459f0, p=..., action=0x0) at widgets/qmenu.cpp:2125 #29 0x00007fdf618f7ffa in ?? () from /usr/lib64/libkdeinit4_kwin.so #30 0x00007fdf618f80bb in ?? () from /usr/lib64/libkdeinit4_kwin.so #31 0x00007fdf618f883a in ?? () from /usr/lib64/libkdeinit4_kwin.so #32 0x00007fdf618dd4d5 in ?? () from /usr/lib64/libkdeinit4_kwin.so #33 0x00007fdf618e046a in ?? () from /usr/lib64/libkdeinit4_kwin.so #34 0x00007fdf4341ad28 in ?? () from /usr/lib64/kde4/kwin3_keramik.so #35 0x00007fdf5b929216 in QCoreApplicationPrivate::sendThroughObjectEventFilters (this=this@entry=0x1ae9020, receiver=receiver@entry=0x386d4b0, event=event@entry=0x7fff09e247b0) at kernel/qcoreapplication.cpp:1059 #36 0x00007fdf5aaa888c in QApplicationPrivate::notify_helper (this=this@entry=0x1ae9020, receiver=receiver@entry=0x386d4b0, e=e@entry=0x7fff09e247b0) at kernel/qapplication.cpp:4558 #37 0x00007fdf5aaaefad in QApplication::notify (this=<optimized out>, receiver=0x386d4b0, e=0x7fff09e247b0) at kernel/qapplication.cpp:4105 #38 0x00007fdf601dc18a in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5 #39 0x00007fdf5b9290ad in QCoreApplication::notifyInternal (this=0x7fff09e24f20, receiver=receiver@entry=0x386d4b0, event=event@entry=0x7fff09e247b0) at kernel/qcoreapplication.cpp:949 #40 0x00007fdf5aaae763 in sendEvent (event=<optimized out>, receiver=<optimized out>) at ../../src/corelib/kernel/qcoreapplication.h:231 #41 QApplicationPrivate::sendMouseEvent (receiver=receiver@entry=0x386d4b0, event=event@entry=0x7fff09e247b0, alienWidget=alienWidget@entry=0x0, nativeWidget=nativeWidget@entry=0x386d4b0, buttonDown=buttonDown@entry=0x7fdf5b586278 <qt_button_down>, lastMouseReceiver=..., spontaneous=spontaneous@entry=true) at kernel/qapplication.cpp:3173 #42 0x00007fdf5ab1ff7b in QETWidget::translateMouseEvent (this=this@entry=0x386d4b0, event=event@entry=0x7fff09e24b30) at kernel/qapplication_x11.cpp:4528 #43 0x00007fdf5ab1e9ec in QApplication::x11ProcessEvent (this=0x7fff09e24f20, event=event@entry=0x7fff09e24b30) at kernel/qapplication_x11.cpp:3651 #44 0x00007fdf5ab461f0 in QEventDispatcherX11::processEvents (this=0x1a72a70, flags=...) at kernel/qeventdispatcher_x11.cpp:132 #45 0x00007fdf5b927d0f in QEventLoop::processEvents (this=this@entry=0x7fff09e24d90, flags=...) at kernel/qeventloop.cpp:149 #46 0x00007fdf5b928005 in QEventLoop::exec (this=this@entry=0x7fff09e24d90, flags=...) at kernel/qeventloop.cpp:204 #47 0x00007fdf5b92d13b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1221 #48 0x00007fdf618d5186 in kdemain () from /usr/lib64/libkdeinit4_kwin.so #49 0x00007fdf614c8be5 in __libc_start_main () from /lib64/libc.so.6 #50 0x0000000000400761 in _start () Possible duplicates by query: bug 337159, bug 337084, bug 336757, bug 336006, bug 335955. An https://bugs.kde.org/ berichten Reproducible: Sometimes Steps to Reproduce: None
*** This bug has been marked as a duplicate of bug 334152 ***
How can I see recognize that "my bug" is a duplicate of an already filed one *before* I file the bug? Particularly the action on which the crash happened (see my summary) is completely different to bug 334152. I think "my crash" happened under other circumstances. So, why is it a duplicate?
The condition is exactly the same - you're opening the context menu (and because the amount of activities changed at some point, you get a crash in return) Therefore it's also the the exact same backtrace. Bugzilla should have suggested similar bugs based upon the backtrace (before you finally submitted the bug), but there's some recent issue in bugzilla (see bug #337742, I have no further knowlege in that area, sorry) which lead to the 410 error and broke the DrKonqui bug submission. The bug is a dupe for sure - you may just trust me on this ;-)
Hi Thomas, Am 10.09.2014 19:59, schrieb Thomas Lübking : > https://bugs.kde.org/show_bug.cgi?id=338984 > > --- Comment #3 from Thomas Lübking <thomas.luebking@gmail.com> --- > The condition is exactly the same - you're opening the context menu I agree so far. > (and because the amount of activities changed at some point, I never changed the "amount of activities" consciously. Are there conditions for changing this automatically without knowledge of the user? > you get a crash in return) Therefore it's also the the exact same > backtrace. Could there be other, may be unwanted reasons to reach the same code position and therefore getting exactly the same backtrace (under similar but not the same conditions)? > Bugzilla should have suggested similar bugs based upon the backtrace > (before you finally submitted the bug), It did, but it's really hard to recognize this. Visually there seemed to be some similarities but they looked not like identical traces. And: be aware that normal users don't have any clue how they should handle stuff like backtraces and duplicate bug messages. Thus I consider the benefit of comparison backtraces doubtful if reporting the error is the main issue respectively the real goal. > but there's some recent > issue in bugzilla (see bug #337742, I have no further knowlege in > that area, sorry) which lead to the 410 error and broke the DrKonqui > bug submission. Ok, let's hope for a soon resolution. > The bug is a dupe for sure - you may just trust me on this ;-) I willingly trust you as the expert of course :-) But the condition that lead to the bug seems to be partially another one. Happy fixing! Tom
(In reply to Thomas Michalka from comment #4) > I never changed the "amount of activities" consciously. Are there > conditions for changing this automatically without knowledge of the user? Since it's more about "running" activities than "all" activities - "potentially" (read: "I frankly don't know, but could be - yes") > Could there be other, may be unwanted reasons to reach the same code > position and therefore getting exactly the same backtrace (under similar > but not the same conditions)? "Unlikely" - the menu action gets deleted, but not NULLed, what's (afaics) because it's deleted by moc what happens when its parent is deleted what happens when the activity submenu gets removed because there's only one activity left. That does however not matter, because the patch catches whatever deletes the menuaction with a guarded pointer. > Happy fixing! It is fixed since 4.11.10