Bug 301516

Summary: kwin crashed on killing a frozen application
Product: [Plasma] kwin Reporter: g111
Component: generalAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: crash    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Debian unstable   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description g111 2012-06-09 16:22:57 UTC
Application: kwin (4.7.4 (4.7.4))
KDE Platform Version: 4.7.4 (4.7.4)
Qt Version: 4.8.1
Operating System: Linux 3.4-1.slh.2-aptosid-amd64 x86_64
Distribution: Debian GNU/Linux unstable (sid)

-- Information about the crash:
- What I was doing when the application crashed:

An application (RockboxUtility) did not respond anymore. I tried to close it. kwin showed up the dialog that the app is not responding anymore and asked me if kwin should terminate the app. I decided to let kwin kill the app. But it did not work.

Some seconds later I again tried to close the window. The kwin dialog for termination did show up again. I kept it open and decided to "kill -9" the application in konsole. On pressing enter on this command kwin did freeze. Nothing moved anymore, only the mouse cursor could still be dragged. Approx. half a minute later kwin did a restart and showed up the bug reporting assistant.

-- Backtrace:
Application: KWin (kwin), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f96089cc780 (LWP 4314))]

Thread 2 (Thread 0x7f95fed64700 (LWP 4409)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x00007f961aed7437 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#2  0x00007f961aed7469 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#3  0x00007f9612347b50 in start_thread (arg=<optimized out>) at pthread_create.c:304
#4  0x00007f961c0d16dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#5  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f96089cc780 (LWP 4314)):
[KCrash Handler]
#6  QProcess::setProcessState (this=0x1882790, state=state@entry=QProcess::NotRunning) at io/qprocess.cpp:1770
#7  0x00007f961839cc4f in QProcessPrivate::cleanup (this=this@entry=0x1cf0ad0) at io/qprocess.cpp:799
#8  0x00007f96183a0c53 in QProcessPrivate::_q_processDied (this=0x1cf0ad0) at io/qprocess.cpp:1058
#9  0x00007f96183a0d0e in qt_static_metacall (_a=<optimized out>, _id=<optimized out>, _o=<optimized out>, _c=<optimized out>) at .moc/release-shared/moc_qprocess.cpp:92
#10 QProcess::qt_static_metacall (_o=<optimized out>, _c=<optimized out>, _id=<optimized out>, _a=<optimized out>) at .moc/release-shared/moc_qprocess.cpp:69
#11 0x00007f961841aa9f in QMetaObject::activate (sender=0x1b21810, m=<optimized out>, local_signal_index=<optimized out>, argv=0x7fff9be467c0) at kernel/qobject.cpp:3547
#12 0x00007f961846511e in QSocketNotifier::activated (this=<optimized out>, _t1=26) at .moc/release-shared/moc_qsocketnotifier.cpp:103
#13 0x00007f96184223bb in QSocketNotifier::event (this=0x1b21810, e=0x7fff9be46df0) at kernel/qsocketnotifier.cpp:317
#14 0x00007f96177b07dc in QApplicationPrivate::notify_helper (this=this@entry=0xd3e5f0, receiver=receiver@entry=0x1b21810, e=e@entry=0x7fff9be46df0) at kernel/qapplication.cpp:4559
#15 0x00007f96177b4d0a in QApplication::notify (this=0x7fff9be474f0, receiver=0x1b21810, e=0x7fff9be46df0) at kernel/qapplication.cpp:4420
#16 0x00007f961bbbfad6 in KApplication::notify (this=0x7fff9be474f0, receiver=0x1b21810, event=0x7fff9be46df0) at ../../kdeui/kernel/kapplication.cpp:311
#17 0x00007f961840514e in QCoreApplication::notifyInternal (this=0x7fff9be474f0, receiver=0x1b21810, event=0x7fff9be46df0) at kernel/qcoreapplication.cpp:876
#18 0x00007f9618434805 in sendEvent (event=0x7fff9be46df0, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#19 QEventDispatcherUNIX::activateSocketNotifiers (this=this@entry=0xd38580) at kernel/qeventdispatcher_unix.cpp:884
#20 0x00007f9618435570 in QEventDispatcherUNIXPrivate::doSelect (this=0xfffffffffffffe48, this@entry=0xd3e910, flags=..., timeout=0x7fff9be46f90) at kernel/qeventdispatcher_unix.cpp:309
#21 0x00007f9618436042 in QEventDispatcherUNIX::processEvents (this=0xd38580, flags=...) at kernel/qeventdispatcher_unix.cpp:926
#22 0x00007f961785273f in QEventDispatcherX11::processEvents (this=0xd38580, flags=...) at kernel/qeventdispatcher_x11.cpp:152
#23 0x00007f961840414f in QEventLoop::processEvents (this=this@entry=0x7fff9be47270, flags=...) at kernel/qeventloop.cpp:149
#24 0x00007f96184043d8 in QEventLoop::exec (this=0x7fff9be47270, flags=...) at kernel/qeventloop.cpp:204
#25 0x00007f96184092d8 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1148
#26 0x00007f961c3dd0fa in kdemain (argc=3, argv=0x7fff9be47678) at ../../kwin/main.cpp:517
#27 0x00007f961c017ead in __libc_start_main (main=<optimized out>, argc=<optimized out>, ubp_av=<optimized out>, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff9be47668) at libc-start.c:228
#28 0x0000000000400761 in _start ()

This bug may be a duplicate of or related to bug 196350.

Possible duplicates by query: bug 300955, bug 295920, bug 290711, bug 289316, bug 277190.

Reported using DrKonqi
Comment 1 Thomas Lübking 2012-06-09 16:48:21 UTC
you killed the killhelper instead of or next to the hanging process, taking down the parenting kwin process as well

kwin 4.9 will detach itself from the kill helper (cause you're not the only one who managed this ;-) but you still killed the wrong process.

*** This bug has been marked as a duplicate of bug 196350 ***
Comment 2 g111 2012-06-09 16:54:19 UTC
Oops, you are right. It is still in the konsole scroll buffer. (I did only notice the "rockbox" string in command parameters)

Sorry,
Gert