Summary: | System Settings crashes when opening "Applications" module | ||
---|---|---|---|
Product: | [Applications] systemsettings | Reporter: | Jason Cox <dev> |
Component: | general | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | alex.merry, alexander.lohnau, nate |
Priority: | NOR | Keywords: | drkonqi |
Version: | 5.19.0 | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | https://invent.kde.org/plasma/plasma-desktop/commit/74753128180a36c9fba154914b3a2384025c4893 | Version Fixed In: | 5.19.3 |
Sentry Crash Report: | |||
Attachments: | New crash information added by DrKonqi |
Description
Jason Cox
2020-06-11 14:30:03 UTC
Created attachment 129719 [details]
New crash information added by DrKonqi
systemsettings5 (5.19.2) using Qt 5.15.0
- What I was doing when the application crashed:
There are two ways I can trigger this crash: opening the "Default Applications" module directly from KRunner, or opening System Settings and navigating to "Default Applications".
I currently have Firefox installed. I also had elinks installed originally, but even after uninstalling elinks, the crash still happens.
I recompiled kservice and plasma-desktop from sources (using the same build scripts as the distribution's packages) in order to get useful backtrace information. The crash happened both before and after this, in an identical manner.
-- Backtrace (Reduced):
#4 0x00007f1112fd94b4 in KService::storageId() const () from /usr/lib/libKF5Service.so.5
#5 0x00007f10e404caa6 in CfgFileManager::load (this=0x555ad80cd430) at /usr/include/qt/QtCore/qshareddata.h:161
#6 0x00007f10e404aacb in ComponentChooser::load (this=0x555ad80b8a20) at /usr/src/debug/plasma-desktop-5.19.2/kcms/componentchooser/componentchooser.cpp:130
#7 0x00007f1111daf0b2 in QObject::event(QEvent*) () from /usr/lib/libQt5Core.so.5
#8 0x00007f11128d8702 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5
Wait, I messed up the debug package installation. Here's a better version of the stop of the backtrace: [KCrash Handler] #4 0x00007f72a27774b4 in KService::d_func (this=<optimized out>) at /usr/src/debug/kservice-5.71.0/src/services/kservice.cpp:823 #5 KService::storageId (this=0x0) at /usr/src/debug/kservice-5.71.0/src/services/kservice.cpp:824 #6 0x00007f728402aaa6 in CfgFileManager::load (this=0x55cae1734d90) at /usr/include/qt/QtCore/qshareddata.h:161 #7 0x00007f7284028acb in ComponentChooser::load (this=0x55cae17203a0) at /usr/src/debug/plasma-desktop-5.19.2/kcms/componentchooser/componentchooser.cpp:130 #8 0x00007f72a154d0b2 in QObject::event(QEvent*) () from /usr/lib/libQt5Core.so.5 What file managers do you have installed? None - I've been looking through the code and come to the conclusion that was the cause. The fix is trivial - I'll submit a patch shortly. A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/49 I also have no file manager installed, so it's likely the same cause for me. Git commit 74753128180a36c9fba154914b3a2384025c4893 by Alex Merry. Committed on 27/06/2020 at 12:18. Pushed by alexmerry into branch 'Plasma/5.19'. Fix a KCM crash when no file manager is installed If no file manager is installed, the componentchooser KCM would attempt to dereference a null pointer. FIXED-IN: 5.19.3 M +1 -1 kcms/componentchooser/componentchooserfilemanager.cpp https://invent.kde.org/plasma/plasma-desktop/commit/74753128180a36c9fba154914b3a2384025c4893 |