Description of problem: Version-Release number of selected component: imsettings-1.8.3-2.fc36 Additional info: reporter: libreport-2.17.1 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/session-8.scope cmdline: /usr/libexec/imsettings-check --check-dbus crash_function: __memmove_sse2_unaligned_erms executable: /usr/libexec/imsettings-check journald_cursor: s=0325f794070a4f0cbc4530c1f3e0ce87;i=20c51;b=b81031ec0c0a4f658013367757b620ac;m=59a36bb73;t=5e0402d681c0a;x=54d794e43c0fd92d kernel: 5.17.11-300.fc36.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 __memmove_sse2_unaligned_erms at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:575 #1 memmove at /usr/include/bits/string_fortified.h:36 #2 g_bsearch_array_grow at ../glib/gbsearcharray.h:214 #3 g_bsearch_array_insert at ../glib/gbsearcharray.h:238 #4 g_signal_newv at ../gobject/gsignal.c:1790 #5 g_signal_new_valist at ../gobject/gsignal.c:1983 #6 g_signal_new at ../gobject/gsignal.c:1512 #7 g_dbus_auth_observer_class_init at ../gio/gdbusauthobserver.c:197 #8 g_dbus_auth_observer_class_intern_init at ../gio/gdbusauthobserver.c:149 #9 type_class_init_Wm at ../gobject/gtype.c:2297
Created attachment 1885279 [details] File: backtrace
Created attachment 1885280 [details] File: core_backtrace
Created attachment 1885281 [details] File: cpuinfo
Created attachment 1885282 [details] File: dso_list
Created attachment 1885283 [details] File: environ
Created attachment 1885284 [details] File: exploitable
Created attachment 1885285 [details] File: limits
Created attachment 1885286 [details] File: maps
Created attachment 1885287 [details] File: mountinfo
Created attachment 1885288 [details] File: open_fds
Created attachment 1885289 [details] File: proc_pid_status
Does this still happen? The code itself is very simple and this is most likely a bug in glib since it just calls g_bus_get_sync().
This message is a reminder that Fedora Linux 36 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '36'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 36 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16. Fedora Linux 36 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.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days