Application: kwin (4.7.2 (4.7.2) "release 5") KDE Platform Version: 4.7.2 (4.7.2) "release 5" Qt Version: 4.7.4 Operating System: Linux 3.1.0-1.2-desktop x86_64 Distribution: "openSUSE 12.1 (x86_64)" -- Information about the crash: kwin crashed when i open a youtube video on 720p 2 times in the same video -- Backtrace: Application: KWin (kwin), signal: Segmentation fault [Current thread is 1 (Thread 0x7f0dc56b0780 (LWP 2449))] Thread 2 (Thread 0x7f0dac86f700 (LWP 2562)): #0 0x00007f0dc0f52e6c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007f0dc3d0e852 in QTWTF::TCMalloc_PageHeap::scavengerThread (this=0x7f0dc4006e80) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2359 #2 0x00007f0dc3d0e889 in QTWTF::TCMalloc_PageHeap::runScavengerThread (context=<optimized out>) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1464 #3 0x00007f0dc0f4ef05 in start_thread () from /lib64/libpthread.so.0 #4 0x00007f0dc4eea53d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f0dc56b0780 (LWP 2449)): [KCrash Handler] #6 QProcess::setProcessState (this=0xf449d0, state=QProcess::NotRunning) at io/qprocess.cpp:1753 #7 0x00007f0dc12656df in QProcessPrivate::cleanup (this=<optimized out>) at io/qprocess.cpp:781 #8 0x00007f0dc126a2d9 in QProcessPrivate::_q_processDied (this=0xda6a00) at io/qprocess.cpp:1041 #9 0x00007f0dc126a919 in QProcess::qt_metacall (this=0xce6680, _c=QMetaObject::InvokeMetaMethod, _id=13, _a=0x7fff6c5f8f40) at .moc/release-shared/moc_qprocess.cpp:115 #10 0x00007f0dc12d859a in QMetaObject::activate (sender=0xf23370, m=<optimized out>, local_signal_index=<optimized out>, argv=0x7fff6c5f8f40) at kernel/qobject.cpp:3287 #11 0x00007f0dc132216e in QSocketNotifier::activated (this=<optimized out>, _t1=23) at .moc/release-shared/moc_qsocketnotifier.cpp:89 #12 0x00007f0dc12e024b in QSocketNotifier::event (this=0xf23370, e=0x7fff6c5f95b0) at kernel/qsocketnotifier.cpp:317 #13 0x00007f0dc0477c34 in notify_helper (e=0x7fff6c5f95b0, receiver=0xf23370, this=0x647860) at kernel/qapplication.cpp:4481 #14 QApplicationPrivate::notify_helper (this=0x647860, receiver=0xf23370, e=0x7fff6c5f95b0) at kernel/qapplication.cpp:4453 #15 0x00007f0dc047cac1 in QApplication::notify (this=0x7fff6c5f9af0, receiver=0xf23370, e=0x7fff6c5f95b0) at kernel/qapplication.cpp:4360 #16 0x00007f0dc49dee36 in KApplication::notify (this=0x7fff6c5f9af0, receiver=0xf23370, event=0x7fff6c5f95b0) at /usr/src/debug/kdelibs-4.7.2/kdeui/kernel/kapplication.cpp:311 #17 0x00007f0dc12c581c in QCoreApplication::notifyInternal (this=0x7fff6c5f9af0, receiver=0xf23370, event=0x7fff6c5f95b0) at kernel/qcoreapplication.cpp:787 #18 0x00007f0dc12f180b in sendEvent (event=0x7fff6c5f95b0, receiver=<optimized out>) at kernel/qcoreapplication.h:215 #19 QEventDispatcherUNIX::activateSocketNotifiers (this=<optimized out>) at kernel/qeventdispatcher_unix.cpp:891 #20 0x00007f0dc12f3082 in QEventDispatcherUNIXPrivate::doSelect (this=0x647a70, flags=) at kernel/qeventdispatcher_unix.cpp:305 #21 0x00007f0dc12f3443 in QEventDispatcherUNIX::processEvents (this=0x607280, flags=...) at kernel/qeventdispatcher_unix.cpp:933 #22 0x00007f0dc051bde8 in QEventDispatcherX11::processEvents (this=0x607280, flags=...) at kernel/qeventdispatcher_x11.cpp:152 #23 0x00007f0dc12c4a22 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149 #24 0x00007f0dc12c4c1f in QEventLoop::exec (this=0x7fff6c5f9a30, flags=...) at kernel/qeventloop.cpp:201 #25 0x00007f0dc12c8de7 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1064 #26 0x00007f0dc51fe5f6 in kdemain (argc=<optimized out>, argv=<optimized out>) at /usr/src/debug/kde-workspace-4.7.2/kwin/main.cpp:517 #27 0x00007f0dc4e3223d in __libc_start_main () from /lib64/libc.so.6 #28 0x0000000000400681 in _start () at ../sysdeps/x86_64/elf/start.S:113 Possible duplicates by query: bug 289316, bug 277190, bug 276367, bug 264657, bug 256708. Reported using DrKonqi
no, actually you were trying to kill sth. and killed kwin (or rather the "kill hanging application" dialog) instead *** This bug has been marked as a duplicate of bug 196350 ***