Description of problem: Happens whenever attaching a usb drive or network share Version-Release number of selected component: gnome-software-42.0-1.fc36 Additional info: reporter: libreport-2.17.1 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-gnome-org.gnome.Software-1843.scope cmdline: /usr/bin/gnome-software --gapplication-service crash_function: dnf_context_invalidate_full executable: /usr/bin/gnome-software journald_cursor: s=becda3bc6c78441488c64598e6283142;i=d06d;b=58688555da7f40228ff05ced01a44476;m=db4514c;t=5dbc729f4625b;x=8c3c2083553017fc kernel: 5.17.1-300.fc36.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 dnf_context_invalidate_full at /usr/src/debug/libdnf-0.66.0-1.fc36.x86_64/libdnf/dnf-context.cpp:2746 #2 signal_emit_unlocked_R.isra.0 at ../gobject/gsignal.c:3743 #5 g_cclosure_marshal_VOID__OBJECTv at ../gobject/gmarshal.c:1910 #6 _g_closure_invoke_va at ../gobject/gclosure.c:893 #9 mount_added at ../client/gdaemonvolumemonitor.c:162 #12 signal_emit_unlocked_R.isra.0 at ../gobject/gsignal.c:3743 #15 mounted_cb at ../common/gmounttracker.c:473 #16 ffi_call_unix64 at ../src/x86/unix64.S:105 #17 ffi_call_int at ../src/x86/ffi64.c:672 #18 g_cclosure_marshal_generic at ../gobject/gclosure.c:1534
Created attachment 1870580 [details] File: backtrace
Created attachment 1870581 [details] File: core_backtrace
Created attachment 1870582 [details] File: cpuinfo
Created attachment 1870583 [details] File: dso_list
Created attachment 1870584 [details] File: environ
Created attachment 1870585 [details] File: exploitable
Created attachment 1870586 [details] File: limits
Created attachment 1870587 [details] File: maps
Created attachment 1870588 [details] File: mountinfo
Created attachment 1870589 [details] File: open_fds
Created attachment 1870590 [details] File: proc_pid_status
Created attachment 1870591 [details] File: var_log_messages
Thanks for a bug report. This particular one had been reported already, thus I'm marking it as a duplicate. *** This bug has been marked as a duplicate of bug 2070153 ***
*** Bug 2121857 has been marked as a duplicate of this bug. ***