SUMMARY That's pretty much it. It probably is a bug in xwayland, but I was wondering because systemmonitor should be a wayland app, right? *** STEPS TO REPRODUCE 1. Start system, log in 2. start a few programs from the taskbar (icons only) 3. start system monitor from the taskbar (I have kontact, firefox, dolphin and system monitor fixed to my panel). OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 Kernel Version: 6.2.0-33-generic (64-bit) Graphics Platform: Wayland Processors: 6 × AMD Ryzen 5 4500U with Radeon Graphics Memory: 15,0 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: Acer Product Name: Aspire A515-44G System Version: V1.12 ADDITIONAL INFORMATION
>It probably is a bug in xwayland, yeah, a crash in xwayland is always an xwayland ug >but I was wondering because systemmonitor should be a wayland app, right? It should. Can you run WAYLAND_DEBUG=1 plasma-systemmonitor and see if you get loads of output or none at all
Created attachment 161746 [details] konsole output when starting system monitor Here's the output when starting system monitor from konsole:
ok, that's definitely running in wayland. Did xwayland crash when you ran it that time?
Yes, every time (just did it again twice).
Anything I could do to give more info?
We also need a symbolicated backtrace of the crash. Can you supply one?
Created attachment 161769 [details] attachment-1261488-0.html How? sent from my Android phone Nate Graham <bugzilla_noreply@kde.org> schrieb am Mi., 20. Sept. 2023, 21:31: > https://bugs.kde.org/show_bug.cgi?id=474728 > > Nate Graham <nate@kde.org> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > CC| |nate@kde.org > Status|REPORTED |NEEDSINFO > Resolution|--- |BACKTRACE > > --- Comment #6 from Nate Graham <nate@kde.org> --- > We also need a symbolicated backtrace of the crash. Can you supply one? > > -- > You are receiving this mail because: > You reported the bug.
Well, Google is your friend, so I found how to attach gdb to the running Xwayland process. But when having gdb attached, Xwayland does not crash when starting system monitor. I tried it from the panel and also from konsole. But after detaching gdb from Xwayland, it crashed immediately. Then, when starting system monitor while gdb isn't attached, it will crash again. I looked whether I could somehow create a backtrace after Xwayland crashed, and found coredumpctl, so I tried this. I will attach the output of both a direct crash after launching system monitor and also the crash after detaching gdb.
Created attachment 161770 [details] crash after opening system monitor
Created attachment 161771 [details] crash after detaching gdb
Created attachment 161772 [details] Crash after opening system monitor (with debug symbols installed) I didn't have debug symbols installed, sorry. Here with symbols.
Thank you very much!
Unfortunately I don't really see how we can reproduce this, so I'm going to close this as an upstream bug. If it still happens with Plasma 6, you're probably better off filing a bug with XWayland.