Bug 493123 - Plasma crashed when right click the steam icon in the tray and hover over to different options
Summary: Plasma crashed when right click the steam icon in the tray and hover over to ...
Status: RESOLVED NOT A BUG
Alias: None
Product: plasmashell
Classification: Plasma
Component: generic-crash (other bugs)
Version First Reported In: 6.1.5
Platform: Arch Linux Linux
: NOR crash
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2024-09-14 13:46 UTC by zhuoyin
Modified: 2024-09-14 21:04 UTC (History)
1 user (show)

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


Attachments
New crash information added by DrKonqi (88.65 KB, text/plain)
2024-09-14 13:46 UTC, zhuoyin
Details

Note You need to log in before you can comment on or make changes to this bug.
Description zhuoyin 2024-09-14 13:46:35 UTC
Application: plasmashell (6.1.5)

Qt Version: 6.7.2
Frameworks Version: 6.5.0
Operating System: Linux 6.10.9-arch1-2 x86_64
Windowing System: Wayland
Distribution: "Arch Linux"
DrKonqi: 6.1.5 [CoredumpBackend]

-- Information about the crash:
Normally freshly booted plasma will work, but normally after 1 min usage, plasma crashes very frequently in different ways and generated similar backtrace, below are the observations of how it triggers crashes:

- If I press alt+tab to switch 
- If I right click the steam icon in the tray and hover over to different options
- If I just move around my mouse

I thought it might be nvidia driver issue, but I switched between proprietary driver and open source driver (560.35), the crashing issue persisted

The crashes happened way more often in wayland compare to x11, and sometimes the plasmashell reopen is not even triggered and I need maintain a terminal to start the plasmashell if I need to

The crash can be reproduced sometimes.

-- Backtrace (Reduced):
#5  __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
#6  0x00007d34daca5463 in __pthread_kill_internal (threadid=<optimized out>, signo=6) at pthread_kill.c:78
#7  0x00007d34dac4c120 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
#8  0x00007d34dac334c3 in __GI_abort () at abort.c:79
#9  0x00007d34dd254734 in wl_abort (fmt=fmt@entry=0x7d34dd2597f0 "Tried to add event to destroyed queue\n") at ../wayland-1.23.1/src/wayland-util.c:476


Reported using DrKonqi
Comment 1 zhuoyin 2024-09-14 13:46:37 UTC
Created attachment 173658 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.
Comment 2 cwo 2024-09-14 14:13:07 UTC
Thank you for the bug report. The backtrace looks very similar to cases caused by enabling the QtQuick Vulkan backend, which is not supported.

Please run `kcmshell6 kcm_qtquicksettings` and make sure that Rendering backend is set to Automatic.
Comment 3 zhuoyin 2024-09-14 21:04:24 UTC
Thanks for the advice, I think it's solved, I changed to automatic as you suggested, then log off and log in again, so far no crashes.

Really appreciated