Version-Release number of selected component: gdb-headless-13.2-3.fc38 Additional info: reporter: libreport-2.17.11 type: CCpp reason: gdb killed by SIGSEGV journald_cursor: s=2f3fccf0f95a46a2ae56257e384bbc36;i=4ed99;b=89d06b2ceb684f258684b0a85ce25d64;m=2e8d368c3;t=604eefa2b0384;x=27bfe3f405eb64d5 executable: /usr/libexec/gdb cmdline: /usr/libexec/gdb -batch -ex $'set debuginfod enabled on' "" -ex $'file /usr/bin/gnome-control-center' -ex $'core-file ./coredump' -ex $'thread apply all -ascending backtrace full 1024' -ex $'info sharedlib' -ex $'print (char*)__abort_msg' -ex $'print (char*)__glib_assert_msg' -ex $'info all-registers' -ex disassemble cgroup: 0::/user.slice/user-1000.slice/user/app.slice/dbus-:1.2-org.freedesktop.problems.applet rootdir: / uid: 1000 kernel: 6.4.13-200.fc38.x86_64 package: gdb-headless-13.2-3.fc38 runlevel: N 5 backtrace_rating: 4 crash_function: internal_vproblem(internal_problem *, const char *, int, const char *, typedef __va_list_tag __va_list_tag *) Truncated backtrace: Thread no. 1 (1 frames) #511 internal_vproblem(internal_problem *, const char *, int, const char *, typedef __va_list_tag __va_list_tag *) at ../../gdb/utils.c:352
Created attachment 1987897 [details] File: proc_pid_status
Created attachment 1987898 [details] File: maps
Created attachment 1987899 [details] File: limits
Created attachment 1987900 [details] File: environ
Created attachment 1987901 [details] File: open_fds
Created attachment 1987902 [details] File: mountinfo
Created attachment 1987903 [details] File: os_info
Created attachment 1987904 [details] File: cpuinfo
Created attachment 1987905 [details] File: core_backtrace
Created attachment 1987906 [details] File: exploitable
Created attachment 1987907 [details] File: dso_list
Created attachment 1987908 [details] File: backtrace
Do you still have the core file from /usr/bin/gnome-control-center ? If so, could you upload/attach it to this bug?
(In reply to Kevin Buettner from comment #13) > Do you still have the core file from /usr/bin/gnome-control-center ? If so, > could you upload/attach it to this bug?
This is an old bug I haven't seen since then. You can probably close out this ticket.