Bug 398494 - KDE either freezes/crashes after launching Steam
Summary: KDE either freezes/crashes after launching Steam
Status: RESOLVED FIXED
Alias: None
Product: kwin
Classification: Plasma
Component: wayland-generic (show other bugs)
Version: 5.13.90
Platform: Arch Linux Linux
: NOR crash
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-09-11 12:47 UTC by Sandeep
Modified: 2020-10-19 13:25 UTC (History)
4 users (show)

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


Attachments
journalctl (106.84 KB, text/plain)
2018-10-06 11:00 UTC, Bedis Nbiba
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Sandeep 2018-09-11 12:47:45 UTC
I use Plasma on Wayland.

Whenever I launch the latest versions of "Steam (Runtime)" - the latest version with the UI refresh, the chat window always pops up. It always fails to login.

If I close Steam's chat window while it's still in the process of logging in, when the login operation fails, the chat window automatically pops up again, showing that it's failed to login.

At this point, one of the following happens:

1. The whole desktop freezes and I cannot switch to a TTY either, but I can Ctrl + Alt + PrtScr + REISUB to reboot the machine
2. Plasma crashes and the display manager's login screen is shown again

This only happens on Plasma on Wayland. I tested, and it does not happen on Plasma on X11, or GNOME on Wayland.
Comment 1 Alexander Mentyu 2018-09-11 13:25:52 UTC
Please attach a backtrace of the crash
Comment 2 Sandeep 2018-09-11 14:52:48 UTC
Since the desktop as a whole crashes or freezes, I am not able to obtain a backtrace through Plasma's normal crash reporting mechanism. Is there a log file or other place where kwin/Plasma writes the crash backtrace to?
Comment 3 David Edmundson 2018-09-11 15:05:24 UTC
It's a pain to get wtih kwin wayland, but going to a TTY running
sudo gdb --pid `pidof kwin_wayland` 
typing continue

then reproducing the crash is a good way. Then back from the tty you can type
"set logging on" "bt" to save a crash report.
Comment 4 Sandeep 2018-09-11 15:21:03 UTC
Thanks! I will try it out when it crashes again.
Comment 5 Sandeep 2018-09-20 20:53:44 UTC
I was able to reproduce kwin freezing up as mentioned below - obtained the backtrace by ssh'ing from another system - so the kernel and other low level software are fine, but Plasma/KWin is frozen.

#0  0x00007f1cc1ea0bb1 in poll () at /usr/lib/libc.so.6
#1  0x00007f1cc210f180 in  () at /usr/lib/libxcb.so.1
#2  0x00007f1cc2110b3f in  () at /usr/lib/libxcb.so.1
#3  0x00007f1cc2110c51 in xcb_wait_for_reply () at /usr/lib/libxcb.so.1
#4  0x00007f1cc34f2cb0 in KWin::Shadow::readX11ShadowProperty(unsigned int) () at /usr/lib/libkwin.so.5
#5  0x00007f1cc34f4ed8 in KWin::Shadow::createShadowFromX11(KWin::Toplevel*) () at /usr/lib/libkwin.so.5
#6  0x00007f1cc34f5b69 in KWin::Shadow::createShadow(KWin::Toplevel*) () at /usr/lib/libkwin.so.5
#7  0x00007f1cc35418b6 in KWin::Toplevel::getShadow() () at /usr/lib/libkwin.so.5
#8  0x00007f1cc25ca0c0 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/libQt5Core.so.5
#9  0x00007f1cc303329b in KWayland::Server::SurfaceInterface::Private::swapStates(KWayland::Server::SurfaceInterface::Private::State*, KWayland::Server::SurfaceInterface::Private::State*, bool) () at /usr/lib/libKF5WaylandServer.so.5
#10 0x00007f1cc303375c in KWayland::Server::SurfaceInterface::Private::commit() () at /usr/lib/libKF5WaylandServer.so.5
#11 0x00007f1cbae641c8 in ffi_call_unix64 () at /usr/lib/libffi.so.6
#12 0x00007f1cbae63c2a in ffi_call () at /usr/lib/libffi.so.6
#13 0x00007f1cbe1156ff in  () at /usr/lib/libwayland-server.so.0
#14 0x00007f1cbe1120a3 in  () at /usr/lib/libwayland-server.so.0
#15 0x00007f1cbe113702 in wl_event_loop_dispatch () at /usr/lib/libwayland-server.so.0
#16 0x00007f1cc300132f in KWayland::Server::Display::Private::dispatch() () at /usr/lib/libKF5WaylandServer.so.5
#17 0x0000556497efc687 in  ()
#18 0x0000556497efa305 in  ()
#19 0x00007f1cc1dd4223 in __libc_start_main () at /usr/lib/libc.so.6
#20 0x0000556497efb19e in _start ()
Comment 6 Sandeep 2018-09-20 21:03:22 UTC
I was able to reproduce the crash a few times, but gdb doesn't show a backtrace of any sort - the only output I can see is about threads getting destroyed.
Comment 7 Bedis Nbiba 2018-10-06 11:00:21 UTC
Created attachment 115438 [details]
journalctl
Comment 8 Bedis Nbiba 2018-10-06 11:03:05 UTC
Hi, same issue, looks it happens when steam use vulkan driver query, I have an optimus laptop with intel ivy bridge.
Comment 9 Martin Flöser 2018-10-06 12:02:25 UTC
From the backtrace it looks like XWayland crashes and KWin freezes when trying to access the no longer living X.
Comment 10 Bedis Nbiba 2018-10-06 12:20:19 UTC
At second look, It might not be the same issue, I tested more steam seems to work fine for a while but crashes randomly sometimes. I'll just file a different bug when I'm able to pinpoint something.
Comment 11 Vlad Zahorodnii 2020-10-19 13:25:49 UTC
(In reply to Martin Flöser from comment #9)
> From the backtrace it looks like XWayland crashes and KWin freezes when
> trying to access the no longer living X.

Yep.

Marking as FIXED because kwin handles xwayland crashes in 5.20. Please re-open this bug report if kwin still crashes.