Version-Release number of selected component: xsettingsd-1.0.2-5.fc38 Additional info: reporter: libreport-2.17.9 cmdline: /usr/bin/xsettingsd executable: /usr/bin/xsettingsd runlevel: N 5 reason: xsettingsd killed by SIGABRT package: xsettingsd-1.0.2-5.fc38 kernel: 6.2.12-300.fc38.x86_64 backtrace_rating: 4 uid: 1333 type: CCpp xsession_errors: rootdir: / journald_cursor: s=3eaf5c0ea56c46bd84b2e24c2ddb5222;i=56fdc;b=bc33351dd71c48b481165fac3330f28c;m=baf9d8f03;t=5fa6374ed0201;x=bda8e532db4a75f6 cgroup: 0::/user.slice/user-1333.slice/user/session.slice/plasma-kded.service crash_function: __select Truncated backtrace: Thread no. 1 (2 frames) #0 __select at ../sysdeps/unix/sysv/linux/select.c:69 #1 xsettingsd::SettingsManager::RunEventLoop at /usr/src/debug/xsettingsd-1.0.2-5.fc38.x86_64/settings_manager.cc:145
Created attachment 1961463 [details] File: proc_pid_status
Created attachment 1961464 [details] File: var_log_messages
Created attachment 1961465 [details] File: maps
Created attachment 1961466 [details] File: mountinfo
Created attachment 1961467 [details] File: backtrace
Created attachment 1961468 [details] File: limits
Created attachment 1961469 [details] File: dso_list
Created attachment 1961470 [details] File: open_fds
Created attachment 1961471 [details] File: environ
Created attachment 1961472 [details] File: core_backtrace
Created attachment 1961473 [details] File: os_info
Created attachment 1961474 [details] File: cpuinfo
Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21. Fedora Linux 38 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.