Bug 465568 - System settings crashes when opening a submenu
Summary: System settings crashes when opening a submenu
Status: RESOLVED DUPLICATE of bug 465543
Alias: None
Product: systemsettings
Classification: Applications
Component: general (show other bugs)
Version: 5.26.5
Platform: Neon Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-02-11 02:55 UTC by Alek Evans
Modified: 2023-02-11 09:55 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Display and Monitor systemsettings crash (2.43 KB, text/vnd.kde.kcrash-report)
2023-02-11 02:55 UTC, Alek Evans
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alek Evans 2023-02-11 02:55:26 UTC
Created attachment 156139 [details]
Display and Monitor systemsettings crash

SUMMARY
When trying to open various submenus in systemsettings, many menus will cause the systemsettings application to crash with a segfault.

Attached is a crash report from opening the Display and Monitor menu.

STEPS TO REPRODUCE
1. Open systemsettings
2. Select a submenu that causes it to crash (see list in ADDITIONAL INFORMATION)

OBSERVED RESULT
Systemsettings will immediately crash with a segfault.

EXPECTED RESULT
The submenu should open as expected.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: KDE neon 5.26
(available in About System)
KDE Plasma Version: 5.26.5
KDE Frameworks Version:  5.102.0
Qt Version: 5.15.8

ADDITIONAL INFORMATION

Submenus that cause a crash:
- Appearance
  - Plasma Style
  - Colors
  - Window Decorations
  - Fonts
  - Cursors
- Workspace Behavior
  - Virtual Desktops
- Startup and Shutdown
  - Background Services
- Search
  - Initial menu (can't explore further)
- Users
- Applications
  - Default Applications
- Firewall (if plasma-firewall is installed)
- Display and Monitor
  - Initial menu (can't explore further)
- Audio
- Software Update
Comment 1 Antonio Rojas 2023-02-11 09:55:20 UTC
*** This bug has been marked as a duplicate of bug 465543 ***