Description of problem: This gnome-software bug report is reported after a successfull upgrade to F38. I am not sure when it failed in the process. Version-Release number of selected component: gnome-software-44.0-3.fc38 Additional info: reporter: libreport-2.17.9 crash_function: XB_IS_SILO executable: /usr/bin/gnome-software package: gnome-software-44.0-3.fc38 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-gnome-org.gnome.Software-10572.scope kernel: 6.2.11-300.fc38.x86_64 uid: 1000 cmdline: /usr/bin/gnome-software --gapplication-service runlevel: N 5 backtrace_rating: 4 reason: gnome-software killed by SIGSEGV rootdir: / journald_cursor: s=b8caca0bb7de4f00832ab80694aa8f8f;i=48613;b=502dc0d80a6b4d2dae06f35c7a074159;m=51984687;t=5f9f7fba5d8d9;x=8c170700ea4036ab type: CCpp Truncated backtrace: Thread no. 1 (14 frames) #0 XB_IS_SILO at ../src/xb-silo.h:18 #1 silo_query_with_root at ../src/xb-silo-query.c:294 #2 xb_silo_query_with_root at ../src/xb-silo-query.c:408 #3 xb_node_query_first at ../src/xb-node-query.c:204 #4 gs_appstream_refine_app at ../lib/gs-appstream.c:1102 #5 gs_appstream_create_app at ../lib/gs-appstream.c:32 #6 gs_flatpak_refine_wildcard at ../plugins/flatpak/gs-flatpak.c:3667 #7 refine_thread_cb at ../plugins/flatpak/gs-plugin-flatpak.c:724 #8 work_run_cb at ../lib/gs-worker-thread.c:236 #12 g_main_context_iterate.isra.0 at ../glib/gmain.c:4276 #13 g_main_context_iteration at ../glib/gmain.c:4343 #14 thread_cb at ../lib/gs-worker-thread.c:175 #15 g_thread_proxy at ../glib/gthread.c:831 #17 clone3 at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81
Created attachment 1959291 [details] File: open_fds
Created attachment 1959292 [details] File: dso_list
Created attachment 1959293 [details] File: proc_pid_status
Created attachment 1959294 [details] File: cpuinfo
Created attachment 1959295 [details] File: mountinfo
Created attachment 1959296 [details] File: maps
Created attachment 1959297 [details] File: os_info
Created attachment 1959298 [details] File: environ
Created attachment 1959299 [details] File: core_backtrace
Created attachment 1959300 [details] File: backtrace
Created attachment 1959301 [details] File: var_log_messages
Created attachment 1959302 [details] File: exploitable
Created attachment 1959303 [details] File: limits
Thanks for a bug report, It looks like there happened some sort of memory corruption, maybe accessing an already freed memory or some such thing, but the backtrace only shows when the crash happened (or when the problem had been detected), rather than the place where the memory broke. By any chance, are you able to reproduce this, please? I'm afraid not on will, because these things are usually quite hard to reproduce.
At the moment, the installed flatpaks are updated. The following packages are updated md.obsidian.Obsidian.Locale org.freedesktop.Platform.openh264 us.zoom.Zoom md.obsidian.Obsidian com.google.Chrome org.gnome.Platform.Locale org.gnome.Platform com.github.tchx84.Flatseal reporter: libreport-2.17.11 type: CCpp reason: gnome-software killed by SIGSEGV journald_cursor: s=a0a22de9bf71489abe7c00588dc5f0f5;i=365096;b=21c5027fb8734a2db4df3c88920a46ac;m=2c8cd79f5;t=601dbcb97d2f7;x=8309754fdd4cabfa 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-2482.scope rootdir: / uid: 1000 kernel: 6.3.12-200.fc38.x86_64 package: gnome-software-44.3-1.fc38 runlevel: N 5 backtrace_rating: 4 crash_function: XB_IS_SILO
*** Bug 2253878 has been marked as a duplicate of this bug. ***
Not sure if that's connected, but probably it is: I was installing updated flatpaks from CLI with "flatpak update" command. reporter: libreport-2.17.11 comment: Not sure if that's connected, but probably it is: I was installing updated flatpaks from CLI with "flatpak update" command. uid: 1000 backtrace_rating: 4 reason: gnome-software killed by SIGSEGV crash_function: XB_IS_SILO type: CCpp cmdline: /usr/bin/gnome-software --gapplication-service executable: /usr/bin/gnome-software package: gnome-software-45.2-1.fc39 rootdir: / kernel: 6.6.8-200.fc39.x86_64 journald_cursor: s=25ccb7f1084142848b27e266f3c07260;i=87c980;b=8c419ca0df094155a794ad94ac3cc73c;m=2bcab478;t=60e2e234f1426;x=f6d82c83e2613444 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-gnome-org.gnome.Software-5254.scope runlevel: N 5
Unknown. It failed without being viewed. reporter: libreport-2.17.11 type: CCpp reason: gnome-software killed by SIGSEGV journald_cursor: s=f3cce9eb70c543bc932b07415b31aeaa;i=108b0c;b=4d552e4617364251a13fc46b834e8add;m=35dd0e96;t=60efc10c416ad;x=b0e316f0dc1b5dfd 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-2479.scope rootdir: / uid: 1000 kernel: 6.6.9-200.fc39.x86_64 package: gnome-software-45.3-1.fc39 runlevel: N 5 backtrace_rating: 4 crash_function: XB_IS_SILO comment: Unknown. It failed without being viewed.
This message is a reminder that Fedora Linux 39 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 39 on 2024-11-26. 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 '39'. 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 39 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 39 entered end-of-life (EOL) status on 2024-11-26. Fedora Linux 39 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.