Bug 472475 - Crash after changing icon theme
Summary: Crash after changing icon theme
Status: RESOLVED DUPLICATE of bug 463276
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (show other bugs)
Version: 5.27.6
Platform: openSUSE Linux
: NOR crash
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2023-07-21 18:05 UTC by Edan Osborne
Modified: 2023-07-23 14:35 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
New crash information added by DrKonqi (70.53 KB, text/plain)
2023-07-21 18:05 UTC, Edan Osborne 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Edan Osborne 2023-07-21 18:05:48 UTC 
Application: plasmashell (5.27.6)

Qt Version: 5.15.10
Frameworks Version: 5.108.0
Operating System: Linux 6.4.3-1-default x86_64
Windowing System: Wayland
Distribution: "openSUSE Tumbleweed"
DrKonqi: 5.27.6 [CoredumpBackend]

-- Information about the crash:
I had Qmmp open, and I went into the system settings to change my icon theme from Newaita to Breeze. As soon as I clicked "Apply", Plasma crashed.

The reporter is unsure if this crash is reproducible.

-- Backtrace (Reduced):
#5  0x00007f3c55162458 in KConfig::reparseConfiguration() () from /lib64/libKF5ConfigCore.so.5
#6  0x00007f3c55182a61 in KCoreConfigSkeleton::load() () from /lib64/libKF5ConfigCore.so.5
[...]
#8  0x00007f3c5515cb17 in KConfigWatcher::configChanged(KConfigGroup const&, QList<QByteArray> const&) () from /lib64/libKF5ConfigCore.so.5
[...]
#10 0x00007f3c55167483 in KConfigWatcher::qt_metacall(QMetaObject::Call, int, void**) () from /lib64/libKF5ConfigCore.so.5
[...]
#12 0x00007f3c53d192b0 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5


Reported using DrKonqi
Comment 1 Edan Osborne 2023-07-21 18:05:49 UTC 
Created attachment 160432 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.
Comment 2 Nicolas Fella 2023-07-23 14:35:28 UTC 

*** This bug has been marked as a duplicate of bug 463276 ***