Bug 396928 - kwin_x11 crashes on switching virtual desktops
Summary: kwin_x11 crashes on switching virtual desktops
Status: RESOLVED WORKSFORME
Alias: None
Product: kwin
Classification: Plasma
Component: platform-x11-standalone (show other bugs)
Version: 5.13.3
Platform: Manjaro Linux
: NOR crash
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2018-07-28 13:24 UTC by Andrew
Modified: 2018-10-29 02:20 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew 2018-07-28 13:24:51 UTC
I'm not sure when exactly this happening, I feel like it happens when switching virtual desktops, happens with both cube and slide animations. I'm using two monitors and two main windows: Google Chrome and Intellij Idea. All window titlebars are disappearing, I can't switch between windows, change focus, close app etc. Can be fixed with command kwin_x11 --replace. Here is logs from journalctl when it happened last time:

Jul 28 16:17:04 andy-lt kwin_x11[984]: The X11 connection broke: No error (code 0)
Jul 28 16:17:04 andy-lt kwin_x11[984]: QObject::~QObject: Timers cannot be stopped from another thread
Jul 28 16:17:04 andy-lt kwin_x11[984]: QThread::wait: Thread tried to wait on itself
Jul 28 16:17:04 andy-lt kwin_x11[984]: QtDBus: cannot relay signals from parent QObject(0x55fd62d4bbe0 "") unless they are emitted in the object's thread QThread(0x55fd62ca0e60 ""). Current thread is QSGRenderThread(0x55fd632fcfa0 "").
Comment 1 Martin Flöser 2018-07-28 13:38:53 UTC
Please provide a backtrace of the crash.
Comment 2 Andrew 2018-07-28 14:00:07 UTC
(In reply to Martin Flöser from comment #1)
> Please provide a backtrace of the crash.

Prompt me please how to do it. Thank you!
Comment 3 trmdi 2018-07-28 14:52:11 UTC
(In reply to Andrew from comment #2)
> (In reply to Martin Flöser from comment #1)
> > Please provide a backtrace of the crash.
> 
> Prompt me please how to do it. Thank you!

https://community.kde.org/KWin/Debugging#Debug_.26_log_KWin_.28or_any_process.29_via_gdb
Comment 4 Andrew 2018-07-28 18:14:02 UTC
(In reply to Martin Flöser from comment #1)
> Please provide a backtrace of the crash.

Here is everything I could get from gdb:

_andy@andy-lt:~\[01;32m[andy@andy-lt[01;37m ~[01;32m]$[00m gdb --pid `pidof kwin_x11` 2>&1 | tee kwin.gdb && continue[K[K[K[K[K[K[K[K[K[K[K[K
GNU gdb (GDB) 8.1
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word".
Attaching to process 2189
[New LWP 2190]
[New LWP 2191]
[New LWP 2193]
[New LWP 2197]
[New LWP 2469]
[New LWP 2478]
[New LWP 2479]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
0x00007f55a79fefa6 in ppoll () from /usr/lib/libc.so.6
(gdb) continue
Continuing.
[New Thread 0x7f54db46c700 (LWP 2639)]
[Thread 0x7f5586af4700 (LWP 2478) exited]
[Thread 0x7f5573598700 (LWP 2479) exited]
[Thread 0x7f558795b700 (LWP 2191) exited]
[Thread 0x7f556bdff700 (LWP 2469) exited]
[Thread 0x7f54db46c700 (LWP 2639) exited]
[Thread 0x7f557cad0700 (LWP 2193) exited]
[Thread 0x7f558dfdc700 (LWP 2190) exited]
[Thread 0x7f55a80826c0 (LWP 2189) exited]
[Inferior 1 (process 2189) exited with code 01]
(gdb) bt
No stack.
(gdb) quit
Comment 5 Andrew Crouthamel 2018-09-28 03:33:32 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 6 Andrew Crouthamel 2018-10-29 02:20:54 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!