Bug 501954

Summary:	crash after applying a new global theme
Product:	[Plasma] plasmashell	Reporter:	erik <erikderonde>
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 erik 2025-03-24 19:57:11 UTC

Application: plasmashell (5.27.5)

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

-- Information about the crash:
i deleted 2 global themes, then directly afterwards applied a newly downloaded global theme (Reactionary). then crash

The reporter is unsure if this crash is reproducible.

-- Backtrace (Reduced):
#5  0x00007fb333c47342 in QQuickItemPrivate::addToDirtyList() () from /lib/x86_64-linux-gnu/libQt5Quick.so.5
#6  0x00007fb333c4bb4e in QQuickItemPrivate::dirty(QQuickItemPrivate::DirtyType) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5
#7  0x00007fb333c4d5e2 in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5
#8  0x00007fb333c4d651 in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5
#9  0x00007fb333c4d783 in QQuickItemPrivate::setVisible(bool) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5


Reported using DrKonqi

Comment 1 erik 2025-03-24 19:57:11 UTC

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

DrKonqi auto-attaching complete backtrace.

Comment 2 Bug Janitor Service 2025-03-24 20:33:38 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!