Bug 2221572

Summary: [abrt] gnome-software: g_type_check_instance(): gnome-software killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Michael <michael.scheiffler>
Component: gnome-softwareAssignee: Milan Crha <mcrha>
Status: NEW --- QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 38CC: gnome-sig, mcrha, michael.scheiffler, rhughes
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/c9effa4a89e3cd4550d8d54db17a15443dde3f8
Whiteboard: abrt_hash:98bed8457d20a0eaec47d4c1644aff257a4d3298;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: proc_pid_status
none
File: maps
none
File: limits
none
File: environ
none
File: open_fds
none
File: mountinfo
none
File: os_info
none
File: cpuinfo
none
File: core_backtrace
none
File: exploitable
none
File: dso_list
none
File: backtrace none

Description Michael 2023-07-10 07:20:41 UTC 
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
Comment 1 Michael 2023-07-10 07:20:43 UTC 
Created attachment 1974926 [details]
File: proc_pid_status
Comment 2 Michael 2023-07-10 07:20:45 UTC 
Created attachment 1974927 [details]
File: maps
Comment 3 Michael 2023-07-10 07:20:46 UTC 
Created attachment 1974928 [details]
File: limits
Comment 4 Michael 2023-07-10 07:20:48 UTC 
Created attachment 1974929 [details]
File: environ
Comment 5 Michael 2023-07-10 07:20:49 UTC 
Created attachment 1974930 [details]
File: open_fds
Comment 6 Michael 2023-07-10 07:20:51 UTC 
Created attachment 1974931 [details]
File: mountinfo
Comment 7 Michael 2023-07-10 07:20:52 UTC 
Created attachment 1974932 [details]
File: os_info
Comment 8 Michael 2023-07-10 07:20:53 UTC 
Created attachment 1974933 [details]
File: cpuinfo
Comment 9 Michael 2023-07-10 07:20:55 UTC 
Created attachment 1974934 [details]
File: core_backtrace
Comment 10 Michael 2023-07-10 07:20:56 UTC 
Created attachment 1974935 [details]
File: exploitable
Comment 11 Michael 2023-07-10 07:20:58 UTC 
Created attachment 1974936 [details]
File: dso_list
Comment 12 Michael 2023-07-10 07:20:59 UTC 
Created attachment 1974937 [details]
File: backtrace
Comment 13 Milan Crha 2023-07-10 07:48:56 UTC 
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).