Bug 484413

Summary: Plasmashell crash after entering taskbar edit mode
Product: [Plasma] plasmashell Reporter: Merlot <blu.merlot>
Component: generic-crashAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash CC: akselmo, nate
Priority: NOR Keywords: drkonqi
Version: 6.0.2   
Target Milestone: 1.0   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: New crash information added by DrKonqi

Description Merlot 2024-03-24 20:41:19 UTC
Application: plasmashell (6.0.2)

Qt Version: 6.6.2
Frameworks Version: 6.0.0
Operating System: Linux 6.8.1-arch1-1 x86_64
Windowing System: Wayland
Distribution: Arch Linux
DrKonqi: 6.0.2 [CoredumpBackend]

-- Information about the crash:
When entering edit mode of Taskbar edit entire plasmashell crashes

KWin  Script: KWin Rectangle
	Disabled it, rebooted, no effect
Global Theme: Apple.BigSur.Dark.P6
	Changed to Dark Breeze, rebooted, no effect
Application Theme: Breeze
Plasma Theme: AppleDark-ALL
	Changed to Dark Breeze, rebooted, no effect

The crash can be reproduced every time.

-- 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  0x00007562b7eab393 in __pthread_kill_internal (signo=6, threadid=<optimized out>) at pthread_kill.c:78
#7  0x00007562b7e5a6c8 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
#8  0x00007562b7e424b8 in __GI_abort () at abort.c:79
#9  0x00007562b99854f2 in wl_abort (fmt=fmt@entry=0x7562b998a6d8 "Tried to add event to destroyed queue\n") at ../wayland-1.22.0/src/wayland-util.c:462


Reported using DrKonqi
Comment 1 Merlot 2024-03-24 20:41:20 UTC
Created attachment 167715 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.
Comment 2 Akseli Lahtinen 2024-06-14 12:25:03 UTC
I can't spot any obvious KDE libraries from the backtrace, it looks like the crash was in QtWayland?
Comment 3 Nate Graham 2024-07-30 21:30:57 UTC

*** This bug has been marked as a duplicate of bug 482754 ***