Bug 504729

Summary: using the web browser zen browser monkeytyping
Product: [Plasma] plasmashell Reporter: Harshit <harshitsinghkalsi>
Component: generalAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED UNMAINTAINED    
Severity: crash CC: john.kizer, kde
Priority: NOR Keywords: drkonqi
Version First Reported In: 5.27.5   
Target Milestone: 1.0   
Platform: Mint (Debian based)   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: New crash information added by DrKonqi

Description Harshit 2025-05-24 11:58:35 UTC 
Application: plasmashell (5.27.5)

Qt Version: 5.15.8
Frameworks Version: 5.103.0
Operating System: Linux 6.1.0-37-amd64 x86_64
Windowing System: X11
Distribution: LMDE 6 (faye)
DrKonqi: 5.27.5 [CoredumpBackend]

-- Information about the crash:
built in display went black for a short while I was typing

The reporter is unsure if this crash is reproducible.

-- Backtrace (Reduced):
#5  0x00007f870c1dc628 in KCoreConfigSkeleton::load() () from /lib/x86_64-linux-gnu/libKF5ConfigCore.so.5
[...]
#7  0x00007f870c1b48e7 in KConfigWatcher::configChanged(KConfigGroup const&, QList<QByteArray> const&) () from /lib/x86_64-linux-gnu/libKF5ConfigCore.so.5
#8  0x00007f870c1ee4b9 in KConfigWatcher::onConfigChangeNotification(QHash<QString, QList<QByteArray> > const&) () from /lib/x86_64-linux-gnu/libKF5ConfigCore.so.5
#9  0x00007f870c1b4c52 in KConfigWatcher::qt_metacall(QMetaObject::Call, int, void**) () from /lib/x86_64-linux-gnu/libKF5ConfigCore.so.5
[...]
#11 0x00007f870a2dd730 in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5


Reported using DrKonqi
Comment 1 Harshit 2025-05-24 11:58:36 UTC 
Created attachment 181703 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.
Comment 2 John Kizer 2025-05-27 19:00:19 UTC 
Thank you for your bug report!

Debian advises users to not submit bugs upstream (https://www.debian.org/Bugs/Reporting), as this version of the KDE software is out of support from KDE, and so it's possible that the bug 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!