Bug 356322

Summary:	Black screen after login, mouse pointer visible
Product:	[Plasma] kwin	Reporter:	Juraj <jura.som>
Component:	general	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED UNMAINTAINED
Severity:	crash	CC:	mrmazda
Priority:	NOR	Keywords:	drkonqi
Version:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
See Also:	https://bugs.kde.org/show_bug.cgi?id=328718 https://bugs.kde.org/show_bug.cgi?id=349219
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Juraj 2015-12-05 21:09:31 UTC

Application: kwin (4.11.20)
KDE Platform Version: 4.14.9
Qt Version: 4.8.6
Operating System: Linux 3.16.7-24-desktop x86_64
Distribution: "openSUSE 13.2 (Harlequin) (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
Normal system boot.
- Unusual behavior I noticed:
After login there was just a black screen. The mouse pointer was visible but there was nothing to click on.

The crash can be reproduced sometimes.

-- Backtrace:
Application: KWin (kwin), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f5a2d269800 (LWP 1739))]

Thread 2 (Thread 0x7f5a0d802700 (LWP 1743)):
#0  0x00007f5a26a6805f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0
#1  0x00007f5a2bc958cb in  () at /usr/lib64/libQtScript.so.4
#2  0x00007f5a2bc95909 in  () at /usr/lib64/libQtScript.so.4
#3  0x00007f5a26a640a4 in start_thread () at /lib64/libpthread.so.0
#4  0x00007f5a2ca9408d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f5a2d269800 (LWP 1739)):
[KCrash Handler]
#5  0x00007f5a2c9e4187 in raise () at /lib64/libc.so.6
#6  0x00007f5a2c9e5538 in abort () at /lib64/libc.so.6
#7  0x00007f5a2c9dd126 in __assert_fail_base () at /lib64/libc.so.6
#8  0x00007f5a2c9dd1d2 in  () at /lib64/libc.so.6
#9  0x00007f5a2a892a39 in  () at /usr/lib64/libX11.so.6
#10 0x00007f5a2a892acc in  () at /usr/lib64/libX11.so.6
#11 0x00007f5a2a892d9d in _XEventsQueued () at /usr/lib64/libX11.so.6
#12 0x00007f5a2a895a45 in _XGetRequest () at /usr/lib64/libX11.so.6
#13 0x00007f5a278e56ce in  () at /usr/lib64/libGL.so.1
#14 0x00007f5a27b4c9d4 in KWin::checkGLError(char const*) () at /usr/lib64/libkwinglutils.so.1
#15 0x00007f5a2ce35a73 in  () at /usr/lib64/libkdeinit4_kwin.so
#16 0x00007f5a2ce35d07 in  () at /usr/lib64/libkdeinit4_kwin.so
#17 0x00007f5a2ce1a843 in  () at /usr/lib64/libkdeinit4_kwin.so
#18 0x00007f5a26e143b1 in QObject::event(QEvent*) () at /usr/lib64/libQtCore.so.4
#19 0x00007f5a25f7876c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQtGui.so.4
#20 0x00007f5a25f7ecad in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQtGui.so.4
#21 0x00007f5a2b6e8e0a in KApplication::notify(QObject*, QEvent*) () at /usr/lib64/libkdeui.so.5
#22 0x00007f5a26dfc2ad in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib64/libQtCore.so.4
#23 0x00007f5a26e2bcbc in  () at /usr/lib64/libQtCore.so.4
#24 0x00007f5a26e2cd18 in QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4
#25 0x00007f5a26015f96 in  () at /usr/lib64/libQtGui.so.4
#26 0x00007f5a26dfae6f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4
#27 0x00007f5a26dfb165 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4
#28 0x00007f5a26e005b9 in QCoreApplication::exec() () at /usr/lib64/libQtCore.so.4
#29 0x00007f5a2cdd47a3 in kdemain () at /usr/lib64/libkdeinit4_kwin.so
#30 0x00007f5a2c9d0b05 in __libc_start_main () at /lib64/libc.so.6
#31 0x000000000040075e in _start ()

Reported using DrKonqi

Comment 1 Thomas Lübking 2015-12-05 21:54:23 UTC

lacks debug symbols, but looks quite like bug #328718 or bug #349219
=> Please attach the output of "glxinfo" and (when running, composited) the output of "qdbus org.kde.KWin /KWin supportInformation"

Though, KWin crash does not explain "black empty screen", sounds as if plasma-desktop crashes as well.

Comment 2 Martin Flöser 2016-08-29 07:49:30 UTC

The crash is reported against KWin 4.11. This version is by now unmaintained. Too much code changed to assume that this crash is still valid for KWin 5. If you are still able to reproduce this crash with KWin 5 please report a new bug with a new backtrace. Thank you.