Bug 404166

Summary:	KWin crashed after waking up from sleep
Product:	[Plasma] kwin	Reporter:	techxgames
Component:	general	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	crash	Keywords:	drkonqi
Priority:	NOR
Version:	5.14.5
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	KWin qdbus output

Description techxgames 2019-02-10 08:34:22 UTC

Application: kwin_x11 (5.14.5)

Qt Version: 5.11.1
Frameworks Version: 5.52.0
Operating System: Linux 4.18.0-15-generic x86_64
Distribution: Ubuntu 18.10

-- Information about the crash:
- What I was doing when the application crashed:
Woke up my PC from sleep, switched to a different activity and exited Steam

-- Backtrace:
Application: KWin (kwin_x11), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fa34f380840 (LWP 9257))]

Thread 6 (Thread 0x7fa3323d3700 (LWP 6159)):
#0  0x00007fa35998e7d6 in __GI_ppoll (fds=0x559580a68578, nfds=1, timeout=<optimized out>, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39
#1  0x00007fa358523141 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x00007fa3585245b9 in QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x00007fa3584d416b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x00007fa3583230b6 in QThread::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x00007fa35832cc87 in  () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x00007fa359861164 in start_thread (arg=<optimized out>) at pthread_create.c:486
#7  0x00007fa35999adef in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 5 (Thread 0x7fa29e194700 (LWP 1180)):
#0  0x00007fa3598672eb in futex_wait_cancelable (private=<optimized out>, expected=0, futex_word=0x559581060104) at ../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x00007fa3598672eb in __pthread_cond_wait_common (abstime=0x0, mutex=0x5595810600b0, cond=0x5595810600d8) at pthread_cond_wait.c:502
#2  0x00007fa3598672eb in __pthread_cond_wait (cond=0x5595810600d8, mutex=0x5595810600b0) at pthread_cond_wait.c:655
#3  0x00007fa35832d43b in QWaitCondition::wait(QMutex*, unsigned long) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x00007fa356cad279 in  () at /lib/x86_64-linux-gnu/libQt5Quick.so.5
#5  0x00007fa356cad4da in  () at /lib/x86_64-linux-gnu/libQt5Quick.so.5
#6  0x00007fa35832cc87 in  () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x00007fa359861164 in start_thread (arg=<optimized out>) at pthread_create.c:486
#8  0x00007fa35999adef in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 4 (Thread 0x7fa330bfe700 (LWP 9583)):
#0  0x00007fa3598672eb in futex_wait_cancelable (private=<optimized out>, expected=0, futex_word=0x7fa357f13fb8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x00007fa3598672eb in __pthread_cond_wait_common (abstime=0x0, mutex=0x7fa357f13f68, cond=0x7fa357f13f90) at pthread_cond_wait.c:502
#2  0x00007fa3598672eb in __pthread_cond_wait (cond=0x7fa357f13f90, mutex=0x7fa357f13f68) at pthread_cond_wait.c:655
#3  0x00007fa357e1ce2a in  () at /lib/x86_64-linux-gnu/libQt5Script.so.5
#4  0x00007fa357e1ce49 in  () at /lib/x86_64-linux-gnu/libQt5Script.so.5
#5  0x00007fa359861164 in start_thread (arg=<optimized out>) at pthread_create.c:486
#6  0x00007fa35999adef in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 3 (Thread 0x7fa3477fe700 (LWP 9478)):
#0  0x00007fa35998e7d6 in __GI_ppoll (fds=0x7fa334000d28, nfds=1, timeout=<optimized out>, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39
#1  0x00007fa358523141 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x00007fa3585245b9 in QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x00007fa3584d416b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x00007fa3583230b6 in QThread::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x00007fa3569781f5 in  () at /lib/x86_64-linux-gnu/libQt5Qml.so.5
#6  0x00007fa35832cc87 in  () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x00007fa359861164 in start_thread (arg=<optimized out>) at pthread_create.c:486
#8  0x00007fa35999adef in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 2 (Thread 0x7fa34d110700 (LWP 9407)):
#0  0x00007fa35998e7d6 in __GI_ppoll (fds=0x7fa34000ef08, nfds=1, timeout=<optimized out>, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39
#1  0x00007fa358523141 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x00007fa3585245b9 in QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x00007fa3584d416b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x00007fa3583230b6 in QThread::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x00007fa356453545 in  () at /lib/x86_64-linux-gnu/libQt5DBus.so.5
#6  0x00007fa35832cc87 in  () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x00007fa359861164 in start_thread (arg=<optimized out>) at pthread_create.c:486
#8  0x00007fa35999adef in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 1 (Thread 0x7fa34f380840 (LWP 9257)):
[KCrash Handler]
#6  0x00007fa3598c1077 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#7  0x00007fa3598a2535 in __GI_abort () at abort.c:79
#8  0x00007fa3598a240f in __assert_fail_base (fmt=0x7fa359a2e858 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=0x7fa3597beb4c "delete_refcount == 0", file=0x7fa3597beb98 "/build/kwin-1VaUe5/kwin-5.14.5/deleted.cpp", line=56, function=<optimized out>) at assert.c:92
#9  0x00007fa3598b2142 in __GI___assert_fail (assertion=0x7fa3597beb4c "delete_refcount == 0", file=0x7fa3597beb98 "/build/kwin-1VaUe5/kwin-5.14.5/deleted.cpp", line=56, function=0x7fa3597bec40 "virtual KWin::Deleted::~Deleted()") at assert.c:101
#10 0x00007fa3596d9db2 in KWin::Deleted::~Deleted() () at /lib/x86_64-linux-gnu/libkwin.so.5
#11 0x00007fa3596d9f29 in KWin::Deleted::~Deleted() () at /lib/x86_64-linux-gnu/libkwin.so.5
#12 0x00007fa3584fefb0 in QObject::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x00007fa358e944a1 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#14 0x00007fa358e9bae0 in QApplication::notify(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#15 0x00007fa3584d5499 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x00007fa3584d848b in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x00007fa35852442b in QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x00007fa34e93b0ed in  () at /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#19 0x00007fa3584d416b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x00007fa3584dc2e2 in QCoreApplication::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x00007fa359a7447b in kdemain () at /lib/x86_64-linux-gnu/libkdeinit5_kwin_x11.so
#22 0x00007fa3598a409b in __libc_start_main (main=0x55957ff29050, argc=1, argv=0x7ffc34c9f0a8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffc34c9f098) at ../csu/libc-start.c:308
#23 0x000055957ff2908a in _start ()
[Inferior 1 (process 9257) detached]

Possible duplicates by query: bug 401491, bug 400358, bug 400170, bug 399644, bug 399344.

Reported using DrKonqi

Comment 1 Vlad Zahorodnii 2019-02-10 12:40:58 UTC

Hmm, interesting... Could you please post output of
    qdbus org.kde.KWin /KWin supportInformation

Comment 2 techxgames 2019-02-11 05:39:24 UTC

Created attachment 117977 [details]
KWin qdbus output

Comment 3 techxgames 2019-02-11 05:39:35 UTC

I have attached it

Comment 4 Vlad Zahorodnii 2019-02-11 08:32:12 UTC

The Scale and the Glide effect usually don't go along quite well. Could you please disable either one of them and see if KWin still crashes?

Comment 5 Vlad Zahorodnii 2019-02-15 10:07:29 UTC

comment 4

Comment 6 techxgames 2019-02-15 10:42:57 UTC

(In reply to Vlad Zagorodniy from comment #4)
> The Scale and the Glide effect usually don't go along quite well. Could you
> please disable either one of them and see if KWin still crashes?

Sometimes, I'm getting this notification after waking up: "Desktop effects were restarted due to a graphics reset"

Comment 7 techxgames 2019-02-15 10:43:14 UTC

Sorry I forgot to reply

Comment 8 Vlad Zahorodnii 2019-02-15 10:52:32 UTC

Graphics reset is unrelated. Wait, so KWin crashes even after disabling either Glide or Scale effect? Does the backtrace look the same?

Comment 9 techxgames 2019-02-15 15:35:01 UTC

(In reply to Vlad Zagorodniy from comment #8)
> Graphics reset is unrelated. Wait, so KWin crashes even after disabling
> either Glide or Scale effect? Does the backtrace look the same?

Actually, KWin doesn't crash, or at the very least, no KCrash no Apport notification popped up when the graphics reset happened.

Comment 10 Vlad Zahorodnii 2019-02-15 15:43:02 UTC

Well, okay then. Seems like glide and scale effect didn't go along quite well. If you use 5.14 make sure that only one of them is enabled. In 5.15, it's not possible to enable both of them.

If the crash still happens in 5.15, please file a new bug report. :-)

Comment 11 techxgames 2019-02-15 17:07:34 UTC

(In reply to Vlad Zagorodniy from comment #10)
> Well, okay then. Seems like glide and scale effect didn't go along quite
> well. If you use 5.14 make sure that only one of them is enabled. In 5.15,
> it's not possible to enable both of them.
> 
> If the crash still happens in 5.15, please file a new bug report. :-)

Oh thank God! I was actually planning on submitting a wishlist that will prevent or warn users not to enable both effects.

Just gonna wait for it to land on Kubuntu.  Thanks!  I'll keep in touch