Bug 515287

Summary:	Distorted hamburger submenus
Product:	[Plasma] plasmashell	Reporter:	meso5 <meso5>
Component:	general	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	kde
Priority:	NOR
Version First Reported In:	6.3.6
Target Milestone:	1.0
Platform:	Debian stable
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	menu screenshot

Description meso5 2026-01-30 02:06:13 UTC

Created attachment 189050 [details]
menu screenshot

Some hamburger submenus appear distorted like in my menu screenshot. It happens every time I open the menu, but it’s not always the same submenus. The problem fixes itself if I move to another submenu and back. After a problem submenu has been drawn correctly once, it will always be drawn correctly until I close and re-open the hamburger menu.  

Others and I reported this here: https://bugs.kde.org/show_bug.cgi?id=495073

Operating System: Debian GNU/Linux 13
KDE Plasma Version: 6.3.6
KDE Frameworks Version: 6.13.0
Qt Version: 6.8.2
Kernel Version: 6.12.63+deb13-amd64 (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i7-5600U CPU @ 2.60GHz
Memory: 8 GiB of RAM (7.6 GiB usable)
Graphics Processor: Mesa Intel® HD Graphics 5500

Comment 1 Bug Janitor Service 2026-01-30 02:33:41 UTC

Thank you for the bug report!

Debian advises users to not submit bugs upstream (https://www.debian.org/Bugs/Reporting), and Plasma 6.3.6 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!

Comment 2 meso5 2026-01-30 11:40:44 UTC

After spending some time trying to report this to the Debian maintainers and reportbug losing my report, I gave up. It's just too much. Hopefully, one day the bug will be fixed. I see others, including one on Fedora, reported the same bug here: https://bugs.kde.org/show_bug.cgi?id=495073 (not the resolved part)