Bug 499294

Summary:	Plasma crashes trying to open menu
Product:	[Plasma] plasmashell	Reporter:	jackmcslay
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 In:
Sentry Crash Report:
Attachments:	New crash information added by DrKonqi

Description jackmcslay 2025-01-29 23:15:46 UTC

Application: plasmashell (5.27.5)

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

-- Information about the crash:
At random, plasma crashes trying to open the app launcher, always crashing brave browser along with it.

The crash can be reproduced sometimes.

-- Backtrace (Reduced):
#4  0x00007f2b758d8598 in QXcbIntegration::createPlatformOpenGLContext(QOpenGLContext*) const () at /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#5  0x00007f2b7af8258d in QOpenGLContext::create() () at /lib/x86_64-linux-gnu/libQt5Gui.so.5
[...]
#10 0x00007f2b7a6a81c4 in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:442
#11 0x00007f2b7a72885c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81
#5  __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=11, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44


The reporter indicates this bug may be a duplicate of or related to bug 498482, bug 498620, bug 499162, bug 499254.

Reported using DrKonqi

Comment 1 jackmcslay 2025-01-29 23:15:47 UTC

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

DrKonqi auto-attaching complete backtrace.

Comment 2 Bug Janitor Service 2025-01-29 23:33:37 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!