Application: kwin (4.7.3 (4.7.3)) KDE Platform Version: 4.7.3 (4.7.3) (Compiled from sources) Qt Version: 4.7.2 Operating System: Linux 3.1.0.custom x86_64 Distribution (Platform): Gentoo Packages -- Information about the crash: - What I was doing when the application crashed: Using firefox, nothing special, then system crashed.. but I didn't lose any data, kwin respawned just fine.. -- Backtrace: Application: KWin (kwin), signal: Aborted [Current thread is 1 (Thread 0x7f0eba12c7a0 (LWP 25008))] Thread 2 (Thread 0x7f0e9b69f700 (LWP 25014)): #0 0x00007f0eb58ac5ac in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007f0eb878bcb4 in ?? () from /usr/lib64/qt4/libQtScript.so.4 #2 0x00007f0eb878bce9 in ?? () from /usr/lib64/qt4/libQtScript.so.4 #3 0x00007f0eb718225a in ?? () from /usr/lib64/opengl/nvidia/lib/libGL.so.1 #4 0x00007fffa06805c8 in ?? () #5 0x0000000100000000 in ?? () #6 0x0000000000000000 in ?? () Thread 1 (Thread 0x7f0eba12c7a0 (LWP 25008)): [KCrash Handler] #6 0x00007f0eb98f9455 in raise () from /lib64/libc.so.6 #7 0x00007f0eb98fa870 in abort () from /lib64/libc.so.6 #8 0x00007f0eb49d3d0d in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/gcc/x86_64-pc-linux-gnu/4.5.3/libstdc++.so.6 #9 0x00007f0eb49d1f26 in ?? () from /usr/lib/gcc/x86_64-pc-linux-gnu/4.5.3/libstdc++.so.6 #10 0x00007f0eb49d1f53 in std::terminate() () from /usr/lib/gcc/x86_64-pc-linux-gnu/4.5.3/libstdc++.so.6 #11 0x00007f0eb49d20a6 in __cxa_rethrow () from /usr/lib/gcc/x86_64-pc-linux-gnu/4.5.3/libstdc++.so.6 #12 0x00007f0eb5c2b73d in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4 #13 0x00007f0eb5c2f69b in QCoreApplication::exec() () from /usr/lib64/qt4/libQtCore.so.4 #14 0x00007f0eb9c8ac5d in kdemain () from /usr/lib64/libkdeinit4_kwin.so #15 0x00007f0eb98e5d2d in __libc_start_main () from /lib64/libc.so.6 #16 0x0000000000400789 in _start () Possible duplicates by query: bug 286292, bug 286237, bug 286234, bug 286221, bug 286144. Reported using DrKonqi
rethrow bug, means likely a memory corruption (exception thrown by the "new" operator) if this happens on a regular base, check bug #241163 for an explanation on how to obtain a _real_ backtrace - otherwise there's nothing we could do about this.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!