Bug 289995

Summary: Kwin crash
Product: [Plasma] kwin Reporter: Giuseppe Mameli <mamelig>
Component: generalAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED WORKSFORME    
Severity: crash Keywords: investigated, triaged
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Giuseppe Mameli 2011-12-28 10:33:06 UTC 
Application: kwin (4.7.3 (4.7.3))
KDE Platform Version: 4.7.3 (4.7.3)
Qt Version: 4.7.4
Operating System: Linux 3.0.0-14-generic x86_64
Distribution: Ubuntu 11.10

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

I was reading a Wikipedia article on firefox. I neither wasn't moving the mouse nor typing on the keyboard. The programs that were active at time of fault: dolphin, firefox, kcalc, Kmail, muon, Okular, Virtualbox (with only one win7 machine active in background) and folding@home smp client.

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

Thread 3 (Thread 0x7f6c70b80700 (LWP 1898)):
#0  0x00007f6c91616913 in select () at ../sysdeps/unix/syscall-template.S:82
#1  0x00007f6c8da1dbc6 in qt_safe_select (nfds=16, fdread=0x1081590, fdwrite=0x1081828, fdexcept=0x1081ac0, orig_timeout=<optimized out>) at kernel/qcore_unix.cpp:82
#2  0x00007f6c8da23330 in QEventDispatcherUNIXPrivate::doSelect (this=0x10813d0, flags=..., timeout=0x0) at kernel/qeventdispatcher_unix.cpp:219
#3  0x00007f6c8da23833 in QEventDispatcherUNIX::processEvents (this=0x10c9d40, flags=...) at kernel/qeventdispatcher_unix.cpp:918
#4  0x00007f6c8d9f4cf2 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007f6c8d9f4ef7 in QEventLoop::exec (this=0x7f6c70b7fdb0, flags=...) at kernel/qeventloop.cpp:201
#6  0x00007f6c8d90c27f in QThread::exec (this=<optimized out>) at thread/qthread.cpp:498
#7  0x00007f6c8d9d7cbf in QInotifyFileSystemWatcherEngine::run (this=0x10801f0) at io/qfilesystemwatcher_inotify.cpp:248
#8  0x00007f6c8d90ed05 in QThreadPrivate::start (arg=0x10801f0) at thread/qthread_unix.cpp:331
#9  0x00007f6c87b74efc in start_thread (arg=0x7f6c70b80700) at pthread_create.c:304
#10 0x00007f6c9161d89d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#11 0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7f6c7037f700 (LWP 1899)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x00007f6c90477fe2 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#2  0x00007f6c90478019 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#3  0x00007f6c87b74efc in start_thread (arg=0x7f6c7037f700) at pthread_create.c:304
#4  0x00007f6c9161d89d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#5  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f6c91de47a0 (LWP 1825)):
[KCrash Handler]
#6  0x00007f6c8f34462f in _XDeq () from /usr/lib/x86_64-linux-gnu/libX11.so.6
#7  0x00007f6c8f330b94 in XNextEvent () from /usr/lib/x86_64-linux-gnu/libX11.so.6
#8  0x00007f6c8ce4ef18 in QEventDispatcherX11::processEvents (this=0xac8f40, flags=...) at kernel/qeventdispatcher_x11.cpp:88
#9  0x00007f6c8d9f4cf2 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#10 0x00007f6c8d9f4ef7 in QEventLoop::exec (this=0x7fff1aae01a0, flags=...) at kernel/qeventloop.cpp:201
#11 0x00007f6c8d9f9789 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1064
#12 0x00007f6c91936ca6 in kdemain () from /usr/lib/kde4/libkdeinit/libkdeinit4_kwin.so
#13 0x00007f6c9155d30d in __libc_start_main (main=0x400640, argc=3, ubp_av=0x7fff1aae08c8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff1aae08b8) at libc-start.c:226
#14 0x0000000000400671 in _start ()

Reported using DrKonqi
Comment 1 Martin Flöser 2012-01-19 21:04:38 UTC 
nothing in the backtrace from KWin. Looks very strange. I'm setting to backtrace as debugging symbols for kwin are missing and maybe, maybe something useful is filtered (though I doubt it)
Comment 2 Thomas Lübking 2012-01-19 21:50:30 UTC 
i'd bet for sth. related to this one:
https://bugs.launchpad.net/xorg-server/+bug/257659

(qelt being NULL or dangeling is about the only chance for _XDeq to crash - the other one would be an invalid dpy*)

Ubuntu has possibly applied that semi-sane workaround ;-)

*See:
http://cgit.freedesktop.org/xorg/lib/libX11/tree/src/NextEvent.c
and
http://cgit.freedesktop.org/xorg/lib/libX11/tree/src/XlibInt.c
Comment 3 Andrew Crouthamel 2018-09-22 02:04:01 UTC 
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!
Comment 4 Andrew Crouthamel 2018-10-27 02:09:50 UTC 
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!