Bug 502649

Summary:	Plasma crashed unexpectedly while using MilkyTracker
Product:	[Plasma] plasmashell	Reporter:	fambu336
Component:	general	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED UNMAINTAINED
Severity:	crash	CC:	kde, kdedev
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 fambu336 2025-04-10 16:35:13 UTC

Application: plasmashell (5.27.5)

Qt Version: 5.15.8
Frameworks Version: 5.103.0
Operating System: Linux 6.12.20+rpt-rpi-2712 aarch64
Windowing System: Wayland
Distribution: Debian GNU/Linux 12 (bookworm)
DrKonqi: 5.27.5 [CoredumpBackend]

-- Information about the crash:
Plasma crashed and I noticed because the TaskBar on my Raspberry Pi dissapeared then Dr. Konqi appeared

The crash does not seem to be reproducible.

-- Backtrace (Reduced):
#4  0x00007fff6ec99ca0 in QSGNode::markDirty(QFlags<QSGNode::DirtyStateBit>) () at /lib/aarch64-linux-gnu/libQt5Quick.so.5
#5  0x00007fff6e87afc4 in QAbstractAnimationJob::setCurrentTime(int) () at /lib/aarch64-linux-gnu/libQt5Qml.so.5
#6  0x00007fff6e87b190 in QQmlAnimationTimer::updateAnimationsTime(long long) () at /lib/aarch64-linux-gnu/libQt5Qml.so.5
#7  0x00007fff6cd90078 in QUnifiedTimer::updateAnimationTimers(long long) () at /lib/aarch64-linux-gnu/libQt5Core.so.5
#8  0x00007fff6cd922b0 in QAnimationDriver::advanceAnimation(long long) () at /lib/aarch64-linux-gnu/libQt5Core.so.5


Reported using DrKonqi

Comment 1 fambu336 2025-04-10 16:35:14 UTC

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

DrKonqi auto-attaching complete backtrace.

Comment 2 TraceyC 2025-04-10 17:11:15 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!