Version-Release number of selected component: gnome-software-44.3-1.fc38 Additional info: reporter: libreport-2.17.11 type: CCpp reason: gnome-software killed by SIGSEGV journald_cursor: s=516f546cdd1b4e6cb3b42a61c687ad9f;i=1f6957;b=02e0247fbadc48d89061bd9102d0cbe6;m=3a992f7;t=6001cbdda4d21;x=a53b55712944a150 executable: /usr/bin/gnome-software cmdline: /usr/bin/gnome-software --gapplication-service cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-gnome-org.gnome.Software-4173.scope rootdir: / uid: 1000 kernel: 6.3.11-200.fc38.x86_64 package: gnome-software-44.3-1.fc38 runlevel: N 5 backtrace_rating: 4 crash_function: g_type_check_instance Truncated backtrace: Thread no. 1 (9 frames) #0 g_type_check_instance at ../gobject/gtype.c:4272 #3 signal_emit_unlocked_R.isra.0 at ../gobject/gsignal.c:3812 #6 on_signal_received at ../gio/gdbusproxy.c:890 #7 emit_signal_instance_in_idle_cb at ../gio/gdbusconnection.c:3802 #11 g_main_context_iterate.isra.0 at ../glib/gmain.c:4276 #12 g_main_context_iteration at ../glib/gmain.c:4343 #13 thread_cb at ../lib/gs-worker-thread.c:175 #14 g_thread_proxy at ../glib/gthread.c:831 #16 clone3 at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81
Created attachment 1974926 [details] File: proc_pid_status
Created attachment 1974927 [details] File: maps
Created attachment 1974928 [details] File: limits
Created attachment 1974929 [details] File: environ
Created attachment 1974930 [details] File: open_fds
Created attachment 1974931 [details] File: mountinfo
Created attachment 1974932 [details] File: os_info
Created attachment 1974933 [details] File: cpuinfo
Created attachment 1974934 [details] File: core_backtrace
Created attachment 1974935 [details] File: exploitable
Created attachment 1974936 [details] File: dso_list
Created attachment 1974937 [details] File: backtrace
Thanks for a bug report. Unfortunately, the backtrace doesn't give much idea what could go wrong, neither where or why. It looks like some sort of memory corruption, possibly some code accessing already freed memory, effectively overwriting whatever is newly stored in that part of the memory, but it's only a guess. By any chance, are you able to reproduce this anyhow, please? Do you remember what you've been doing in the gnome-software before the crash happened, if anything (it could happen in the background too).