Bug 511474

Summary:	Occasinal crash after hitting the Win-key to launch the Start menu
Product:	[Plasma] plasmashell	Reporter:	tbgunoi
Component:	general	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED UNMAINTAINED
Severity:	crash	CC:	kde
Priority:	NOR	Keywords:	drkonqi
Version First Reported In:	5.27.5
Target Milestone:	1.0
Platform:	Debian stable
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	New crash information added by DrKonqi

Description tbgunoi 2025-11-01 16:46:18 UTC

Application: plasmashell (5.27.5)

Qt Version: 5.15.8
Frameworks Version: 5.103.0
Operating System: Linux 6.1.0-40-amd64 x86_64
Windowing System: X11
Distribution: Debian GNU/Linux 12 (bookworm)
DrKonqi: 5.27.5 [CoredumpBackend]

-- Information about the crash:
I tried to start the Start menu by pressing the Win-key on my swiss keyboard. Usually, this works very fine.
This time, instead of launching the menu, Plasma crashed.

The reporter is unsure if this crash is reproducible.

-- Backtrace (Reduced):
#4  __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=6, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44
#5  0x00007f232faa8f4f in __pthread_kill_internal (signo=6, threadid=<optimized out>) at ./nptl/pthread_kill.c:78
#6  0x00007f232fa59fb2 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
#7  0x00007f232fa44472 in __GI_abort () at ./stdlib/abort.c:79
[...]
#9  0x00007f232fab286a in malloc_printerr (str=str@entry=0x7f232fbbb6c8 "malloc(): unaligned tcache chunk detected") at ./malloc/malloc.c:5660


Reported using DrKonqi

Comment 1 tbgunoi 2025-11-01 16:46:19 UTC

Created attachment 186392 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.

Comment 2 Bug Janitor Service 2025-11-01 17:33:43 UTC

Thank you for the bug report!

Debian advises users to not submit bugs upstream (https://www.debian.org/Bugs/Reporting), and Plasma 5.27.5 is no longer eligible for support or maintenance from KDE. It's possible that the issue exists only in Debian at this point.

Could you report the bug to Debian using the report bug utility (https://packages.debian.org/stable/utils/reportbug)? If necessary, the maintainer of the package will forward the bug upstream.
Thanks for understanding!

Thanks again!