xwayland crashing for more than 2 months now
Hi there, KDE on Wayland is unusable in my AMD based desktop for more than 12 month. I am sure it is something related to AMD (CPU or GPU) since my intel laptop is running KDE/Wayland without problems. Also, I do not experience any problems in a X11 session. That is I am doing in the last 2 months: using the X11. I can't say how it behaves on gnome/wayland. Currently I am at 20231012. It has to do with chrome that crash after a few minutes of usage. When it does, it crashes the graphical stack somehow, since I had to close and start a new login session to use it again. I can trigger an immediate crash just by running opera-103.0.4928.16-1.1.x86_64 or brave-browser-1.59.117-1.x86_64. I suppose here it is not the place to get the problem fixed, so what is the proper channel/forum/bugzilla to address this problem as it involves gpu amd, a third part app (chrome/brave/opera) and kde ? Oct 14 09:57:50 mastodon kwin_wayland_wrapper[1841]: (EE) 0: /usr/bin/Xwayland (0x55c2603c5000+0x16d30e) [0x55c26053230e] Oct 14 09:57:50 mastodon kwin_wayland_wrapper[1841]: (EE) 1: /usr/bin/Xwayland (0x55c2603c5000+0x16d410) [0x55c260532410] Oct 14 09:57:50 mastodon kwin_wayland_wrapper[1841]: (EE) 3: /usr/bin/Xwayland (0x55c2603c5000+0x4c699) [0x55c260411699] Oct 14 09:57:50 mastodon kwin_wayland_wrapper[1841]: (EE) 4: /usr/bin/Xwayland (0x55c2603c5000+0x4cd5c) [0x55c260411d5c] Oct 14 09:57:50 mastodon kwin_wayland_wrapper[1841]: (EE) 5: /usr/bin/Xwayland (0x55c2603c5000+0x16f2d5) [0x55c2605342d5] Oct 14 09:57:50 mastodon kwin_wayland_wrapper[1841]: (EE) 6: /usr/bin/Xwayland (0x55c2603c5000+0xadc38) [0x55c260472c38] Oct 14 09:57:50 mastodon kwin_wayland_wrapper[1841]: (EE) 7: /usr/bin/Xwayland (0x55c2603c5000+0x36b6f) [0x55c2603fbb6f] Oct 14 09:57:50 mastodon kwin_wayland_wrapper[1841]: (EE) 10: /usr/bin/Xwayland (0x55c2603c5000+0x38335) [0x55c2603fd335] Oct 14 09:57:50 mastodon systemd-coredump[4659]: Process 1841 (Xwayland) of user 1000 dumped core. #3 0x000055c2605345fc n/a (Xwayland + 0x16f5fc) #4 0x000055c26053d2ec n/a (Xwayland + 0x1782ec) #5 0x000055c26053246a n/a (Xwayland + 0x16d46a) #7 0x000055c260411699 n/a (Xwayland + 0x4c699) #8 0x000055c260411d5c n/a (Xwayland + 0x4cd5c) #9 0x000055c2605342d5 n/a (Xwayland + 0x16f2d5) #10 0x000055c260472c38 n/a (Xwayland + 0xadc38) #11 0x000055c2603fbb6f n/a (Xwayland + 0x36b6f) #14 0x000055c2603fd335 n/a (Xwayland + 0x38335) Oct 14 09:57:50 mastodon kwin_wayland[1756]: kwin_xwl: Xwayland process crashed
On Sat, 14 Oct 2023 13:11:39 -0000, "Miguel Rozsas" <miguel@rozsas.eng.br> wrote:
KDE on Wayland is unusable in my AMD based desktop for more than 12 month. [...] I suppose here it is not the place to get the problem fixed, so what is the proper channel/forum/bugzilla to address this problem as it involves gpu amd, a third part app (chrome/brave/opera) and kde ?
List: support@lists.opensuse.org or https://bugzilla.opensuse.org/ -- Robert Webb
On 14. 10. 23, 15:11, Miguel Rozsas wrote:
Hi there,
KDE on Wayland is unusable in my AMD based desktop for more than 12 month. I am sure it is something related to AMD (CPU or GPU) since my intel laptop is running KDE/Wayland without problems. Also, I do not experience any problems in a X11 session. That is I am doing in the last 2 months: using the X11. I can't say how it behaves on gnome/wayland.
Currently I am at 20231012.
It has to do with chrome that crash after a few minutes of usage. When it does, it crashes the graphical stack somehow, since I had to close and start a new login session to use it again.
I can trigger an immediate crash just by running opera-103.0.4928.16-1.1.x86_64 or brave-browser-1.59.117-1.x86_64.
I suppose here it is not the place to get the problem fixed, so what is the proper channel/forum/bugzilla to address this problem as it involves gpu amd, a third part app (chrome/brave/opera) and kde ?
Oct 14 09:57:50 mastodon kwin_wayland_wrapper[1841]: (EE) 0: /usr/bin/Xwayland (0x55c2603c5000+0x16d30e) [0x55c26053230e] Oct 14 09:57:50 mastodon kwin_wayland_wrapper[1841]: (EE) 1: /usr/bin/Xwayland (0x55c2603c5000+0x16d410) [0x55c260532410] Oct 14 09:57:50 mastodon kwin_wayland_wrapper[1841]: (EE) 3: /usr/bin/Xwayland (0x55c2603c5000+0x4c699) [0x55c260411699] Oct 14 09:57:50 mastodon kwin_wayland_wrapper[1841]: (EE) 4: /usr/bin/Xwayland (0x55c2603c5000+0x4cd5c) [0x55c260411d5c] Oct 14 09:57:50 mastodon kwin_wayland_wrapper[1841]: (EE) 5: /usr/bin/Xwayland (0x55c2603c5000+0x16f2d5) [0x55c2605342d5] Oct 14 09:57:50 mastodon kwin_wayland_wrapper[1841]: (EE) 6: /usr/bin/Xwayland (0x55c2603c5000+0xadc38) [0x55c260472c38] Oct 14 09:57:50 mastodon kwin_wayland_wrapper[1841]: (EE) 7: /usr/bin/Xwayland (0x55c2603c5000+0x36b6f) [0x55c2603fbb6f] Oct 14 09:57:50 mastodon kwin_wayland_wrapper[1841]: (EE) 10: /usr/bin/Xwayland (0x55c2603c5000+0x38335) [0x55c2603fd335]
Oct 14 09:57:50 mastodon systemd-coredump[4659]: Process 1841 (Xwayland) of user 1000 dumped core.
In that case ^^^, install debuginfo packages and run: coredumpctl dump That will help a lot as it is decoded dump of the above cryptic one. Attach that to a bug. regards, -- js suse labs
There is 2 debuginfo packages: libwaylandpp1-debuginfo and waylandpp-debuginfo. I expected to see a xwayland-debuginfo but not.... Do you know which one I should install ?
participants (3)
-
Jiri Slaby -
Miguel Rozsas -
Robert Webb