Created attachment 2111896 [details]
File: proc_pid_status

Created attachment 2111897 [details]
File: maps

Created attachment 2111898 [details]
File: limits

Created attachment 2111899 [details]
File: environ

Created attachment 2111900 [details]
File: open_fds

Created attachment 2111901 [details]
File: mountinfo

Created attachment 2111902 [details]
File: os_info

Created attachment 2111903 [details]
File: cpuinfo

Created attachment 2111904 [details]
File: core_backtrace

Created attachment 2111905 [details]
File: dso_list

Created attachment 2111906 [details]
File: var_log_messages

Created attachment 2111907 [details]
File: backtrace

Last boot, I updated https://github.com/luisbocanegra/plasma-smart-video-wallpaper-reborn, acquired via plasma-discover-6.5.5-1.fc43.x86_64. Upon successful `qdbus-qt6 org.kde.LogoutPrompt /LogoutPrompt promptReboot`, when SDDM was automatically bypassed, as I've configured its KCM to do, I observed that PlasmaShell was not visible. Invoking it via BaSH didn't remediate this. To demonstrate, `time strace -Ttr qdbus-qt6 org.kde.plasmashell /PlasmaShell org.kde.PlasmaShell.activateLauncherMenu` fails, and returns:

> ~~~
> 00:49:27 (+     0.000027) futex(0x560ff83d3ad8, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 0, NULL, FUTEX_BITSET_MATCH_ANY) = 0 <24.986885>
> 00:49:52 (+    24.986928) futex(0x560ff83d3a90, FUTEX_WAKE_PRIVATE, 1) = 0 <0.000010>
> 00:49:52 (+     0.000042) fstat(1, {st_mode=S_IFCHR|0600, st_rdev=makedev(0x88, 0x2), ...}) = 0 <0.000011>
> 00:49:52 (+     0.000045) write(1, "Error: org.freedesktop.DBus.Erro"..., 42Error: org.freedesktop.DBus.Error.NoReply
> ) = 42 <0.000013>
> 00:49:52 (+     0.000035) write(1, "Did not receive a reply. Possibl"..., 211Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
> ) = 211 <0.000010>
> 00:49:52 (+     0.000034) write(4, "\1\0\0\0\0\0\0\0", 8) = 8 <0.000009>
> 00:49:52 (+     0.000028) futex(0x7ffc29885570, FUTEX_WAIT_PRIVATE, 0, NULL) = 0 <0.000019>
> 00:49:52 (+     0.000050) write(4, "\1\0\0\0\0\0\0\0", 8) = 8 <0.000008>
> 00:49:52 (+     0.000026) futex(0x560ff83d0648, FUTEX_WAKE_PRIVATE, 1) = 1 <0.000008>
> 00:49:52 (+     0.000025) futex(0x7f12543ff990, FUTEX_WAIT_BITSET, 20630, NULL, FUTEX_BITSET_MATCH_ANY) = 0 <0.000032>
> 00:49:52 (+     0.000151) exit_group(2) = ?
> 00:49:52 (+     0.000488) +++ exited with 2 +++
> 
> real    0m49.541s
> user    0m0.005s
> sys     0m0.009s
> ~~~

Consequently, I attempted to change wallapers, via the relevant KCM. However, doing so reproducibly causes this ANR.

Additional diagnostic information may be available at https://retrace.fedoraproject.org/faf/reports/bthash/72e5ea886c5df548bcd4c356fedde6fdf75ae6d5, until https://forge.fedoraproject.org/workstation/tickets/issues/503#issue-67773, or P6M elapse.


reporter:       libreport-2.17.15
type:           CCpp
reason:         systemsettings killed by SIGABRT
journald_cursor: s=c1f108f1ef4e48808a377c0a73f168fc;i=13e4dd4;b=344f5bd31c364beb94d90b86a9a69ac2;m=1799d502;t=64ae60b5ba713;x=a9a212c15eba1f11
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.18.9-200.fc43.x86_64
package:        plasma-systemsettings-6.5.5-1.fc43
runlevel:       /bin/sh: line 1: runlevel: command not found
backtrace_rating: 4
crash_function: KCrash::defaultCrashHandler

(In reply to Mr. Beedell, Roke Julian Lockhart (RJLB) from comment #13)

I have reported this, upstream, at https://bugs.kde.org/show_bug.cgi?id=516065#c0.