Created attachment 110580 [details] crash.log Distribution: Arch Linux (amd64) Plasma: 5.12 KDE Applications: 17.12 Very often if I am using the ctrl+c / ctrl+v (first I thought it has been on ctrl+v, but now it seems already been triggered on ctrl+v) on Chrome the kwin session crashes. I also seen that crash on ctrl+c on krusader, so it is not Chrome only related. Mostly the screen goes blank and I cannot go to another VT anymore. It reacts on the power button and on shut down it seems that the display session (SDDM) cannot be terminated anymore (the systemd 1:30 default termination times out). Sometimes I am back on SDDM and can relogin to the Plasma (Wayland) session. I attached the "journal" log. There is a stack trace. If I can provide additional information (I am pretty sure there are a lot one missing), please give me some advice.
We need the backtrace of KWin crashing.
I switched recently from Gentoo to Arch Linux. Need to check how to add debug symbols... I assume this one does not help ;) === [root@thor ~]# coredumpctl gdb /usr/bin/kwin_wayland 2972 PID: 2972 (kwin_wayland) UID: 1000 (maggu2810) GID: 1000 (maggu2810) Signal: 11 (SEGV) Timestamp: Mon 2018-02-12 23:18:34 CET (8h ago) Command Line: /usr/bin/kwin_wayland --xwayland --libinput --exit-with-session=/usr/lib/startplasma Executable: /usr/bin/kwin_wayland Control Group: /user.slice/user-1000.slice/session-c5.scope Unit: session-c5.scope Slice: user-1000.slice Session: c5 Owner UID: 1000 (maggu2810) Boot ID: e319dcda790549d093b368cfbb7613ef Machine ID: fcda77640fc5493b8a9638645326e281 Hostname: thor Storage: /var/lib/systemd/coredump/core.kwin_wayland.1000.e319dcda790549d093b368cfbb7613ef.2972.1518473914000000.lz4 (truncated) Message: Process 2972 (kwin_wayland) of user 1000 dumped core. Stack trace of thread 2972: #0 0x00007f8768a69e63 n/a (n/a) 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"... Reading symbols from /usr/bin/kwin_wayland...(no debugging symbols found)...done. BFD: warning: /var/tmp/coredump-dEYyaJ is truncated: expected core file size >= 2446155776, found: 2147483648 [New LWP 2972] [New LWP 2975] [New LWP 2997] [New LWP 3003] [New LWP 2976] Cannot access memory at address 0x7f87723530c8 Cannot access memory at address 0x7f87723530c0 Failed to read a valid object file image from memory. Core was generated by `/usr/bin/kwin_wayland --xwayland --libinput --exit-with-session=/usr/lib/startp'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x00007f8768a69e63 in ?? () [Current thread is 1 (LWP 2972)] (gdb) (gdb) bt #0 0x00007f8768a69e63 in ?? () Backtrace stopped: Cannot access memory at address 0x7ffdef2e3cc8 (gdb) thread apply all bt Thread 5 (LWP 2976): #0 0x00007f876eeff97b in ?? () Backtrace stopped: Cannot access memory at address 0x7f875618bbe0 Thread 4 (LWP 3003): #0 0x00007f8770bd23bd in ?? () Backtrace stopped: Cannot access memory at address 0x7f873c888cf0 Thread 3 (LWP 2997): #0 0x00007f876eeff97b in ?? () Backtrace stopped: Cannot access memory at address 0x7f873fffebc0 Thread 2 (LWP 2975): #0 0x00007f876eeff97b in ?? () Backtrace stopped: Cannot access memory at address 0x7f875698cbe0 Thread 1 (LWP 2972): #0 0x00007f8768a69e63 in ?? () Backtrace stopped: Cannot access memory at address 0x7ffdef2e3cc8
I will attach gdb to the runnin kwin process from now on. Will post a bt as soon as it crashs again.
Created attachment 110662 [details] bt.txt Added a backtrace
Unfortunately the backtrace is lacking debug symbols, but from what I see it is possible that it is the same as 389221.
It seems Arch Linux does not provide debug symbols for their packages (only a very few one). I could try to build the packages containing "/usr/lib/libKF5WaylandServer.so.5" and "at /usr/lib/libwayland-server.so.0" myself to get debug symbols. Would this help? Other files, too?
If you want to build I would suggest to try the patch from https://phabricator.kde.org/D10142 to see whether it's truly the same. And if not, then we would have a backtrace. And yes KWaylandServer should be fully sufficient.
I have build kwayland 5.43.0 with the patch "D10142" applied and debug symbols. If the error will be raised again, I will post the information. If the error cannot be reproduced anymore, should I build kwayland with debug symbols but without the patch? So we get a better backtrace and "knows" that D10142 will fix the issue?
no, we just assume then it's the same.
As long as I cannot reproduce this bug (after applying the referenced patch), I think we could mark it as a duplicate of the mentioned bug. @Martin Thank you for your support. *** This bug has been marked as a duplicate of bug 389221 ***
Great! I'm glad to hear that it looks like the same issue.
Today Wayland session crashed on my Arch Linux when I pressed ctrl+x in dolphin. I hope kwin 5.12.2 will include the fix to this problem.
It seems the problem still exits. The last days my KDE Wayland session crashes very often, if I try to copy text from the Chrome Browser (so XWayland is part of the game, too). I will attach a stacktrace that hopefully contains the necessary information. KDE Frameworks: 5.44.0 KDE Plasma: 5.12.4 Qt: 5.10.1
Created attachment 111806 [details] stacktrace-2018-04-03.txt
wayland session crashed right now on my neon dev unstable after I copy an url in address bar of Opera browser.
The problem with the Chrome Browser did not occur the last weeks anymore. Something has been changed. I don't know what has been changed, but at least I cannot reproduce.
I think this bug is not really fixed. After I read comment 16 here, Wayland session crashed on my Neon dev unstable when I pressed ctrl+c to copy files in Dolphin file manager.