Description of problem: Using GNOME Software, installed Flatpak DISCORD, pushed the "open" button and it crashed. Version-Release number of selected component: gnome-software-46~beta-1.fc40 Additional info: reporter: libreport-2.17.14 rootdir: / kernel: 6.8.0-0.rc5.41.fc40.x86_64 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-gnome-org.gnome.Software-2984.scope package: gnome-software-46~beta-1.fc40 cmdline: /usr/bin/gnome-software --gapplication-service runlevel: N 5 backtrace_rating: 4 uid: 1000 crash_function: g_object_notify_queue_thaw journald_cursor: s=73cc89bcdf8f4125bcb5d17e9f88ea04;i=262d;b=017ed243d1614783a42406f1ff7c6560;m=43c31df2;t=611ed72d6589d;x=eaa225d12fdbba78 type: CCpp reason: gnome-software killed by SIGSEGV executable: /usr/bin/gnome-software comment: Using GNOME Software, installed Flatpak DISCORD, pushed the "open" button and it crashed. Truncated backtrace: Thread no. 1 (6 frames) #0 g_object_notify_queue_thaw at ../gobject/gobject.c:363 #1 app_thaw_notify_idle at ../lib/gs-plugin-job-refine.c:712 #4 g_main_context_dispatch_unlocked at ../glib/gmain.c:4152 #5 g_main_context_iterate_unlocked.isra.0 at ../glib/gmain.c:4217 #6 g_main_context_iteration at ../glib/gmain.c:4282 #7 g_application_run at ../gio/gapplication.c:2613
Created attachment 2018069 [details] File: core_backtrace
Created attachment 2018070 [details] File: backtrace
Created attachment 2018071 [details] File: mountinfo
Created attachment 2018072 [details] File: open_fds
Created attachment 2018073 [details] File: proc_pid_status
Created attachment 2018074 [details] File: os_info
Created attachment 2018075 [details] File: environ
Created attachment 2018076 [details] File: cpuinfo
Created attachment 2018077 [details] File: limits
Created attachment 2018078 [details] File: exploitable
Created attachment 2018079 [details] File: maps
Created attachment 2018080 [details] File: var_log_messages
Created attachment 2018081 [details] File: dso_list
I also got a crashed when pushing Open for Gimp (Flatpak from Fedora)
Thanks for a bug report. I believe this is caused by a similar reason as in bug #2265304, thus I mark this as a duplicate of it. *** This bug has been marked as a duplicate of bug 2265304 ***