Bug 510005 - System Settings crashes whenever selecting anything from the sidebar
Summary: System Settings crashes whenever selecting anything from the sidebar
Status: RESOLVED DUPLICATE of bug 509183
Alias: None
Product: systemsettings
Classification: Applications
Component: generic-crash (other bugs)
Version First Reported In: 6.4.5
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2025-09-27 17:30 UTC by Techokami
Modified: 2025-09-27 19:35 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report: https://crash-reports.kde.org/organizations/kde/issues/262374/events/ccf3f152913d4d1880dc584da78834fb/


Attachments
New crash information added by DrKonqi (112.36 KB, text/plain)
2025-09-27 17:30 UTC, Techokami
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Techokami 2025-09-27 17:30:08 UTC
Application: systemsettings (6.4.5)

ApplicationNotResponding [ANR]: false
Qt Version: 6.9.2
Frameworks Version: 6.18.0
Operating System: Linux 6.16.8-200.fc42.x86_64 x86_64
Windowing System: Wayland
Distribution: "Fedora release 42 (Adams)"
DrKonqi: 6.4.5 [CoredumpBackend]

-- Information about the crash:
100% of the time, when selecting any category on the sidebar of the System Settings application, it crashes. This has started happening a few weeks ago with a system software update from the official Fedora repos. I did not alter any settings regarding this application, it just started crashing like this. It will also crash if the program is exited out by clicking the close window button in the title bar.

I have NO IDEA why this is happening. I have sent countless automatic crash reports for this via the Crash Handler application, but nothing has been fixed. I know the Fedora developers have been busy with Fedora 43, and there have been conventions that have taken up people's time, but crashes like this should be setting off alarms if crash reports actually do get delivered to the developers.

The crash can be reproduced every time.

-- Backtrace (Reduced):
#5  QQuickWindow::maybeUpdate (this=0x560b395dc210) at /usr/src/debug/qt6-qtdeclarative-6.9.2-1.fc42.x86_64/src/quick/items/qquickwindow.cpp:2349
#6  0x00007fb2a49724c6 in QQuickWindowPrivate::cleanup (this=<optimized out>, n=<optimized out>) at /usr/src/debug/qt6-qtdeclarative-6.9.2-1.fc42.x86_64/src/quick/items/qquickwindow.cpp:903
#7  0x00007fb2a48a9a6c in QQuickItemPrivate::derefWindow (this=this@entry=0x560b396d2300) at /usr/src/debug/qt6-qtdeclarative-6.9.2-1.fc42.x86_64/src/quick/items/qquickitem.cpp:3144
#8  0x00007fb2a48ad6ef in QQuickItem::setParentItem (this=0x560b396eaa80, parentItem=parentItem@entry=0x0) at /usr/src/debug/qt6-qtdeclarative-6.9.2-1.fc42.x86_64/src/quick/items/qquickitem.cpp:2810
#9  0x00007fb2a48b020f in QQuickItem::~QQuickItem (this=this@entry=0x560b395f7d60) at /usr/src/debug/qt6-qtdeclarative-6.9.2-1.fc42.x86_64/src/quick/items/qquickitem.cpp:2394
#10 0x00007fb28d83ec59 in QQuickControl::~QQuickControl (this=this@entry=0x560b395f7d60) at /usr/src/debug/qt6-qtdeclarative-6.9.2-1.fc42.x86_64/src/quicktemplates/qquickcontrol.cpp:955
#11 0x00007fb28d86a6f0 in QQuickPane::~QQuickPane (this=this@entry=0x560b395f7d60) at /usr/src/debug/qt6-qtdeclarative-6.9.2-1.fc42.x86_64/src/quicktemplates/qquickpane.cpp:270
#12 0x00007fb28d8673a3 in QQuickPage::~QQuickPage (this=this@entry=0x560b395f7d60) at /usr/src/debug/qt6-qtdeclarative-6.9.2-1.fc42.x86_64/src/quicktemplates/qquickpage.cpp:225
#13 0x00007fb28d8deba1 in QQmlPrivate::QQmlElement<QQuickPage>::~QQmlElement (this=0x560b395f7d60) at /usr/src/debug/qt6-qtdeclarative-6.9.2-1.fc42.x86_64/src/qml/qml/qqmlprivate.h:104
#14 QQmlPrivate::QQmlElement<QQuickPage>::~QQmlElement (this=0x560b395f7d60) at /usr/src/debug/qt6-qtdeclarative-6.9.2-1.fc42.x86_64/src/qml/qml/qqmlprivate.h:104
#15 0x00007fb2a46d0c5b in KQuickConfigModule::~KQuickConfigModule (this=this@entry=0x560b39483680, this=<optimized out>) at /usr/src/debug/kf6-kcmutils-6.18.0-1.fc42.x86_64/src/quick/kquickconfigmodule.cpp:78
#16 0x00007fb2a46d13dd in KQuickManagedConfigModule::~KQuickManagedConfigModule (this=this@entry=0x560b39483680, this=<optimized out>) at /usr/src/debug/kf6-kcmutils-6.18.0-1.fc42.x86_64/src/quick/kquickmanagedconfigmodule.cpp:34
#17 0x00007fb27002f03f in KCMLandingPage::~KCMLandingPage (this=0x560b39483680, this=<optimized out>) at /usr/src/debug/plasma-desktop-6.4.5-1.fc42.x86_64/kcms/landingpage/landingpage.h:82
#18 KCMLandingPage::~KCMLandingPage (this=0x560b39483680, this=<optimized out>) at /usr/src/debug/plasma-desktop-6.4.5-1.fc42.x86_64/kcms/landingpage/landingpage.h:82
#19 0x00007fb2a1d5d1c2 in QObjectPrivate::deleteChildren (this=this@entry=0x560b3946d3d0) at /usr/src/debug/qt6-qtbase-6.9.2-1.fc42.x86_64/src/corelib/kernel/qobject.cpp:2226
#20 0x00007fb2a30a13e8 in QWidget::~QWidget (this=0x560b397f43a0) at /usr/src/debug/qt6-qtbase-6.9.2-1.fc42.x86_64/src/widgets/kernel/qwidget.cpp:1569


Reported using DrKonqi
Comment 1 Techokami 2025-09-27 17:30:10 UTC
Created attachment 185324 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.
Comment 2 Antonio Rojas 2025-09-27 18:33:44 UTC

*** This bug has been marked as a duplicate of bug 509183 ***
Comment 3 Techokami 2025-09-27 19:35:34 UTC
Oh, I didn't know about those bug reports, nor the KDE Discuss thread which has an actual solution, which was to run `sudo dnf swap kf6-kirigami-oxygen kf6-kirigami --refresh` and things now work correctly. Sorry about that!