Created attachment 2019069 [details]
File: proc_pid_status

Created attachment 2019070 [details]
File: maps

Created attachment 2019071 [details]
File: limits

Created attachment 2019072 [details]
File: environ

Created attachment 2019073 [details]
File: open_fds

Created attachment 2019074 [details]
File: mountinfo

Created attachment 2019075 [details]
File: os_info

Created attachment 2019076 [details]
File: cpuinfo

Created attachment 2019077 [details]
File: core_backtrace

Created attachment 2019078 [details]
File: backtrace

This bug appears to have been reported against 'rawhide' during the Fedora Linux 42 development cycle.
Changing version to 42.

I launched KDE connect, and got this crash.


reporter:       libreport-2.17.15
type:           CCpp
reason:         systemsettings killed by SIGSEGV
journald_cursor: s=7aa6f2ba6c2243efbe4a980197e532ec;i=2a011a;b=3e16f19c70b74bfea2cbceb02063dfac;m=c38edcf2b;t=63b7c07b41e46;x=12bcbf60c8e8ca37
executable:     /usr/bin/systemsettings
cmdline:        /usr/bin/systemsettings kcm_kdeconnect
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/app-systemsettings
rootdir:        /
uid:            1000
kernel:         6.15.8-200.fc42.x86_64
package:        plasma-systemsettings-6.4.3-1.fc42
runlevel:       N 5
dso_list:       /usr/bin/systemsettings plasma-systemsettings-6.4.3-1.fc42.x86_64 (Fedora Project) 1752732306
backtrace_rating: 4
crash_function: KCrash::defaultCrashHandler
comment:        I launched KDE connect, and got this crash.

whenever i open system setings it crashed if i click any sub menu


reporter:       libreport-2.17.15
backtrace_rating: 4
runlevel:       N 5
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/app-org.kde.konsole
uid:            1000
type:           CCpp
executable:     /usr/bin/systemsettings
cmdline:        systemsettings
rootdir:        /
package:        plasma-systemsettings-6.4.4-1.fc42
crash_function: KCrash::defaultCrashHandler
journald_cursor: s=52b072e215cc476b81fa4bbf69a7edee;i=23bc8;b=55080ec5cbac4f088a20fd49366d23bf;m=c8f5c15;t=63e4a20d434bd;x=e57e13f32a667346
dso_list:       /usr/bin/systemsettings plasma-systemsettings-6.4.4-1.fc42.x86_64 (Fedora Project) 1757273012
comment:        whenever i open system setings it crashed if i click any sub menu
reason:         systemsettings killed by SIGSEGV
kernel:         6.16.5-cachyos1.fc42.x86_64

it is happened when i open system settings


reporter:       libreport-2.17.15
backtrace_rating: 4
runlevel:       N 5
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/app-systemsettings
uid:            1000
type:           CCpp
executable:     /usr/bin/systemsettings
cmdline:        /usr/bin/systemsettings kcm_lookandfeel
rootdir:        /
package:        plasma-systemsettings-6.4.4-1.fc42
crash_function: KCrash::defaultCrashHandler
journald_cursor: s=52b072e215cc476b81fa4bbf69a7edee;i=1cc04;b=38d6d61eedf440f78c40edbe6f388915;m=d3f231a1;t=63e49e5e7cf10;x=b38e7df8359246be
dso_list:       /usr/bin/systemsettings plasma-systemsettings-6.4.4-1.fc42.x86_64 (Fedora Project) 1757273012
comment:        it is happened when i open system settings
reason:         systemsettings killed by SIGSEGV
kernel:         6.16.5-cachyos1.fc42.x86_64

There are two ways of triggering this crash and observing it easily. It is 95% consistent on my machine, though there are individual cases where it hasn't crashed.

1. Open systemsettings with gdb
2. Close the program using the window decoration close button (or anything that causes a normal, clean exit)
3. Observe the crash
or
1. Open systemsettings
2. Switch KCMs using the sidebar
3. Observe the crash

My hypothesis, feel free to ignore:
These steps cause the KCM view (Quick Settings landing page at the time) to get deallocated, which in turn somehow causes the program to access bad memory (perhaps a null pointer?). And I suppose the cases where it doesn't crash point to some kind of race condition?

I have attempted basic reinstallation (dnf reinstall) of plasma-systemsettings, and clearing of ~/.cache/systemsettings to no avail.

My system is slightly modified from Fedora 42 Stable:
Operating System: Fedora Linux 42
KDE Plasma Version: 6.4.4
KDE Frameworks Version: 6.17.0
Qt Version: 6.9.2
Kernel Version: 6.16.7-cachyos1.fc42.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 16 Ã AMD Ryzen 7 7800X3D 8-Core Processor
Memory: 32 GiB of RAM (30.5 GiB usable)
Graphics Processor: NVIDIA GeForce RTX 4080
(rawhide akmod-nvidia drivers)


reporter:       libreport-2.17.15
type:           CCpp
reason:         systemsettings killed by SIGSEGV
journald_cursor: s=167eac5e3ca146089dcc0686e4d87d0b;i=3c4ae0;b=b41068ceb51c4004a55171864d0431c0;m=8e64e72af;t=63e3ef4fd1c08;x=ea0fcf5a66703bae
executable:     /usr/bin/systemsettings
cmdline:        /usr/bin/systemsettings
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/app-systemsettings
rootdir:        /
uid:            1000
kernel:         6.16.5-cachyos1.fc42.x86_64
package:        plasma-systemsettings-6.4.4-1.fc42
runlevel:       N 5
backtrace_rating: 4
crash_function: KCrash::defaultCrashHandler

Created attachment 2107067 [details]
Backtrace for my crash

The backtrace for my crash is very different from OP's, different KDE version notwithstanding. I find it likely to be a different bug altogether.

Okay, my crash is resolved.

It's because I use the Better Blur COPR, which ships an outdated kf6-kirigami-oxygen package, and I assume there's some kind of ABI incompatibility there.
https://copr.fedorainfracloud.org/coprs/hazel-bunny/ricing/packages/

As per the maintainer's recommendation here, running `sudo dnf swap kf6-kirigami-oxygen kf6-kirigami --refresh` fixes it.
https://discuss.kde.org/t/i-cant-use-the-system-settings-anymore/39514/14