Created attachment 1945483 [details] journal Description of problem: Do a fresh installation with Fedora-Workstation-Live-x86_64-38-20230214.n.1.iso,open gnome-software,click "Download" and then click "Restart&update",crash happens immediately Version-Release number of selected component (if applicable): gnome-software-44~beta-1.fc38.x86_64 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Created attachment 1945484 [details] screencast
Thanks for a bug report. Did ABRT not catch the crash, please? It provides much better backtraces, it shows also line numbers, which helps significantly to recognize where exactly the problem is. The backtraces in the journal file point to a function only. Nonetheless, I believe the crash you face had been fixed recently, by [1]. It landed after the 44.beta release, thus it'll be fixed in 44.rc upcoming release. [1] https://gitlab.gnome.org/GNOME/gnome-software/-/merge_requests/1626
> Did ABRT not catch the crash, please? It did catch the crash,but it seems there is some problem with ABRT,the backtrace is not unlikely usable.
Created attachment 1945658 [details] backtrace
Created attachment 1945659 [details] core_backtrace
Thanks for the update. You are right about the backtrace, it doesn't show anything, just a timeout on the gdb side, possibly caused by slow debuginfod response/download. The core_backtrace is better. I believe it is fixed by the change I referenced earlier.
1200 is actually an internal timeout set by ABRT. We could easily increase it, if needed. However, the log looks suspicious: ``` [New LWP 3259] Downloading 0.03 MB separate debug info for /home/lnie/.cache/debuginfod_client/59155548f7e6864dd0717af8fc44ac03a23ce193/debuginfo... Downloading 0.02 MB separate debug info for /home/lnie/.cache/debuginfod_client/a8929fc4c0381bd78ffe2bd5df1d130b0451dd5d/debuginfo... Downloading 0.01 MB separate debug info for /home/lnie/.cache/debuginfod_client/946f9bf0d5c46765d191279cdc74a211fcb18829/debuginfo... Downloading 0.04 MB separate debug info for /home/lnie/.cache/debuginfod_client/368d02eb34b7f50e227fd065e1cb9f087b235e8e/debuginfo... Downloading 0.02 MB separate debug info for /lib64/libgmodule-2.0.so.0... Downloading 0.01 MB separate debug info for /home/lnie/.cache/debuginfod_client/e59e03abf23b02bd8e49b679dac7f8080587ff28/debuginfo... Downloading 0.02 MB separate debug info for /home/lnie/.cache/debuginfod_client/b1edf9d5bc791e26db0350eb0302e716e65ff98e/debuginfo... Downloading 0.02 MB separate debug info for /home/lnie/.cache/debuginfod_client/7419ad7c8c98499846e9487357898a4e142a8af1/debuginfo... Timeout exceeded: 1200 seconds, killing /usr/libexec/gdb. ``` It seems like the download was super-slow. Would it be possible to retry (if you know that your internet connection is good)?
*** Bug 2173118 has been marked as a duplicate of this bug. ***
> It seems like the download was super-slow. Would it be possible to retry (if you know that your internet connection is good)? The bug #2173118 is the one, which had been reported. It worked the next time, it seems.
Gnome Software crashed after I tried to install the updates reporter: libreport-2.17.7 type: CCpp reason: gnome-software killed by SIGSEGV journald_cursor: s=12a6bc07fdc8418294ff1e22dc533e1a;i=bda;b=67ec19ecbb324156bd716ffe80d914d1;m=13f4e85f;t=5f785141f9eb9;x=95af6816f15fcaff executable: /usr/bin/gnome-software cmdline: /usr/bin/gnome-software --gapplication-service cgroup: 0::/user.slice/user-1000.slice/user/app.slice/dbus-:1.2-org.gnome.Software rootdir: / uid: 1000 kernel: 6.2.2-301.fc38.x86_64 package: gnome-software-44~beta-2.fc38 runlevel: N 5 dso_list: /usr/bin/gnome-software gnome-software-44~beta-2.fc38.x86_64 (Fedora Project) 1678230751 backtrace_rating: 4 crash_function: update_app_unlock_cb comment: Gnome Software crashed after I tried to install the updates
Created attachment 1952962 [details] File: backtrace
tried to update software after initial install. secure boot dbx seemed to be the initial stumbling block, but then the problem reporting app began misfiring while attempting to retrieve the backtrace, which started what would have been, without user intervention, a recursive loop of bug reporting instance creation. reporter: libreport-2.17.7 type: CCpp reason: gnome-software killed by SIGSEGV journald_cursor: s=fc42c76f245247babda59ad142081aef;i=cd2;b=088e46124dde49629c32b0e0e5fd99c0;m=c79c77d5;t=5f7c23fa10b40;x=3b5f4bc2bee35ef4 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-3220.scope rootdir: / uid: 1000 kernel: 6.2.2-301.fc38.x86_64 package: gnome-software-44~beta-2.fc38 runlevel: N 5 backtrace_rating: 4 crash_function: update_app_unlock_cb comment: tried to update software after initial install. secure boot dbx seemed to be the initial stumbling block, but then the problem reporting app began misfiring while attempting to retrieve the backtrace, which started what would have been, without user intervention, a recursive loop of bug reporting instance creation.
Created attachment 1953659 [details] File: backtrace
tried to update software after initial install. secure boot dbx seemed to be the initial stumbling block, but then the problem reporting app began misfiring while attempting to retrieve the backtrace, which started what would have been, without user intervention, a recursive loop of bug reporting instance creation. reporter: libreport-2.17.7 type: CCpp reason: gnome-software killed by SIGSEGV journald_cursor: s=fc42c76f245247babda59ad142081aef;i=cd2;b=088e46124dde49629c32b0e0e5fd99c0;m=c79c77d5;t=5f7c23fa10b40;x=3b5f4bc2bee35ef4 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-3220.scope rootdir: / uid: 1000 kernel: 6.2.2-301.fc38.x86_64 package: gnome-software-44~beta-2.fc38 runlevel: N 5 comment: tried to update software after initial install. secure boot dbx seemed to be the initial stumbling block, but then the problem reporting app began misfiring while attempting to retrieve the backtrace, which started what would have been, without user intervention, a recursive loop of bug reporting instance creation. backtrace_rating: 4 crash_function: update_app_unlock_cb
Created attachment 1953660 [details] File: backtrace