Bug 295920 - kde freezed
Summary: kde freezed
Status: RESOLVED DUPLICATE of bug 196350
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-13 13:14 UTC by Pavel
Modified: 2012-03-13 15:21 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Pavel 2012-03-13 13:14:44 UTC
Application: kwin (4.6.5 (4.6.5))
KDE Platform Version: 4.6.5 (4.6.5)
Qt Version: 4.7.2
Operating System: Linux 2.6.38-13-generic-pae i686
Distribution: Ubuntu 11.04

-- Information about the crash:
- What I was doing when the application crashed:
Clicked on "offline" menu item on skype menu of quick launch panel -> no result -> "quit" menu item -> screen is freezed -> swiched tty5 -> kill skype process -> no result -> kill -9 skype process
- Unusual behavior I noticed:

-- Backtrace:
Application: KWin (kwin), signal: Segmentation fault
[Current thread is 1 (Thread 0xb28ed720 (LWP 1932))]

Thread 3 (Thread 0xad24db70 (LWP 2422)):
#0  0xb779a424 in __kernel_vsyscall ()
#1  0xb75cf681 in select () from /lib/i386-linux-gnu/libc.so.6
#2  0xb659438b in qt_safe_select (nfds=17, fdread=0x9d4ef68, fdwrite=0x9d4f17c, fdexcept=0x9d4f390, orig_timeout=0x0) at kernel/qcore_unix.cpp:82
#3  0xb65986e9 in QEventDispatcherUNIX::select (this=0x9fc2308, nfds=17, readfds=0x9d4ef68, writefds=0x9d4f17c, exceptfds=0x9d4f390, timeout=0x0) at kernel/qeventdispatcher_unix.cpp:632
#4  0xb659966b in QEventDispatcherUNIXPrivate::doSelect (this=0x9d4ee70, flags=..., timeout=0x0) at kernel/qeventdispatcher_unix.cpp:219
#5  0xb659a326 in QEventDispatcherUNIX::processEvents (this=0x9fc2308, flags=...) at kernel/qeventdispatcher_unix.cpp:919
#6  0xb6569289 in QEventLoop::processEvents (this=0xad24d280, flags=...) at kernel/qeventloop.cpp:149
#7  0xb6569522 in QEventLoop::exec (this=0xad24d280, flags=...) at kernel/qeventloop.cpp:201
#8  0xb64732a0 in QThread::exec (this=0x9dd93c0) at thread/qthread.cpp:492
#9  0xb654afdb in QInotifyFileSystemWatcherEngine::run (this=0x9dd93c0) at io/qfilesystemwatcher_inotify.cpp:248
#10 0xb6475da2 in QThreadPrivate::start (arg=0x9dd93c0) at thread/qthread_unix.cpp:320
#11 0xb3906e99 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#12 0xb75d673e in clone () from /lib/i386-linux-gnu/libc.so.6

Thread 2 (Thread 0xaca4cb70 (LWP 2423)):
#0  0xb779a424 in __kernel_vsyscall ()
#1  0xb390b48c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i386-linux-gnu/libpthread.so.0
#2  0xb75e43fd in pthread_cond_wait () from /lib/i386-linux-gnu/libc.so.6
#3  0xb6d61817 in QTWTF::TCMalloc_PageHeap::scavengerThread (this=0xb6e751c0) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2359
#4  0xb6d61851 in QTWTF::TCMalloc_PageHeap::runScavengerThread (context=0xb6e751c0) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1464
#5  0xb3906e99 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#6  0xb75d673e in clone () from /lib/i386-linux-gnu/libc.so.6

Thread 1 (Thread 0xb28ed720 (LWP 1932)):
[KCrash Handler]
#7  QProcess::setProcessState (this=0xa9ba880, state=QProcess::NotRunning) at io/qprocess.cpp:1753
#8  0xb6504829 in QProcessPrivate::cleanup (this=0xa6d7a48) at io/qprocess.cpp:781
#9  0xb6509be8 in QProcessPrivate::_q_processDied (this=0xa6d7a48) at io/qprocess.cpp:1041
#10 0xb6509d0e in QProcess::qt_metacall (this=0xaa91930, _c=QMetaObject::InvokeMetaMethod, _id=13, _a=0xbfadb298) at .moc/release-shared/moc_qprocess.cpp:115
#11 0xb65706ba in QMetaObject::metacall (object=0xaa91930, cl=QMetaObject::InvokeMetaMethod, idx=21, argv=0xbfadb298) at kernel/qmetaobject.cpp:237
#12 0xb65804ff in QMetaObject::activate (sender=0xa24b8c0, m=0xb66a5550, local_signal_index=0, argv=0xbfadb298) at kernel/qobject.cpp:3287
#13 0xb65cd183 in QSocketNotifier::activated (this=0xa24b8c0, _t1=27) at .moc/release-shared/moc_qsocketnotifier.cpp:89
#14 0xb6585fb7 in QSocketNotifier::event (this=0xa24b8c0, e=0xbfadb744) at kernel/qsocketnotifier.cpp:317
#15 0xb5ac1d24 in QApplicationPrivate::notify_helper (this=0x98e87d0, receiver=0xa24b8c0, e=0xbfadb744) at kernel/qapplication.cpp:4462
#16 0xb5ac68ce in QApplication::notify (this=0xbfadbb64, receiver=0xa24b8c0, e=0xbfadb744) at kernel/qapplication.cpp:3862
#17 0xb733c32a in KApplication::notify (this=0xbfadbb64, receiver=0xa24b8c0, event=0xbfadb744) at ../../kdeui/kernel/kapplication.cpp:311
#18 0xb76cd9ef in KWin::Application::notify (this=0xbfadbb64, o=0xa24b8c0, e=0xbfadb744) at ../../kwin/main.cpp:376
#19 0xb656a0bb in QCoreApplication::notifyInternal (this=0xbfadbb64, receiver=0xa24b8c0, event=0xbfadb744) at kernel/qcoreapplication.cpp:731
#20 0xb6598a68 in sendEvent (this=0x98a8aa8) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#21 QEventDispatcherUNIX::activateSocketNotifiers (this=0x98a8aa8) at kernel/qeventdispatcher_unix.cpp:877
#22 0xb6599807 in QEventDispatcherUNIXPrivate::doSelect (this=0x98eaa50, flags=..., timeout=0xbfadb8b4) at kernel/qeventdispatcher_unix.cpp:305
#23 0xb659a326 in QEventDispatcherUNIX::processEvents (this=0x98a8aa8, flags=...) at kernel/qeventdispatcher_unix.cpp:919
#24 0xb5b7925a in QEventDispatcherX11::processEvents (this=0x98a8aa8, flags=...) at kernel/qeventdispatcher_x11.cpp:152
#25 0xb6569289 in QEventLoop::processEvents (this=0xbfadbaa4, flags=...) at kernel/qeventloop.cpp:149
#26 0xb6569522 in QEventLoop::exec (this=0xbfadbaa4, flags=...) at kernel/qeventloop.cpp:201
#27 0xb656decc in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1008
#28 0xb5abf8e7 in QApplication::exec () at kernel/qapplication.cpp:3736
#29 0xb76d04e2 in kdemain (argc=3, argv=0xbfadbde4) at ../../kwin/main.cpp:542
#30 0x080485bb in main (argc=3, argv=0xbfadbde4) at kwin_dummy.cpp:3

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

Possible duplicates by query: bug 290711, bug 289316, bug 277190, bug 276367.

Reported using DrKonqi
Comment 1 Thomas Lübking 2012-03-13 15:21:28 UTC
the skype freeze is a skype bug.

> kill skype process -> no result -> kill -9 skype process
with one of the kills you accidentally killed the kwin process (you killed the kill helper, being a subprocess) what also means the compositor (thus the kwin event loop) didn't lock, but skype was actually frozen.

-> "screen is freezed" 
sure that anything but plasma-dektop (ie. the panel) froze?


Dev note:
we should get the kill helper out of process for 4.9, so killing it won't affect kwin

*** This bug has been marked as a duplicate of bug 196350 ***