Version-Release number of selected component: gnome-software-3.30.0-1.fc29 Additional info: reporter: libreport-2.9.5 backtrace_rating: 4 cmdline: /usr/bin/gnome-software --gapplication-service crash_function: gs_progress_button_set_progress executable: /usr/bin/gnome-software journald_cursor: s=4dec4b710ffe422db274aec8447aa717;i=d434;b=9b7c1b5646244da89fc2b2efefe1b228;m=d2860c5;t=5768a68ff51de;x=91a101150dfe5ad3 kernel: 4.18.9-300.fc29.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (1 frames) #0 gs_progress_button_set_progress at ../src/gs-progress-button.c:46
Created attachment 1486210 [details] File: backtrace
Created attachment 1486211 [details] File: cgroup
Created attachment 1486212 [details] File: core_backtrace
Created attachment 1486213 [details] File: cpuinfo
Created attachment 1486214 [details] File: dso_list
Created attachment 1486215 [details] File: environ
Created attachment 1486216 [details] File: exploitable
Created attachment 1486217 [details] File: limits
Created attachment 1486218 [details] File: maps
Created attachment 1486219 [details] File: mountinfo
Created attachment 1486220 [details] File: open_fds
Created attachment 1486221 [details] File: proc_pid_status
Created attachment 1486222 [details] File: var_log_messages
Similar problem has been detected: Crash of GNOME Software while doing dnf update. Probably some race, can't reproduce now. gnome-software-3.30.0-1.fc29.x86_64 dnf-3.5.1-1.fc29.noarch reporter: libreport-2.9.5 backtrace_rating: 4 cmdline: /usr/bin/gnome-software --gapplication-service crash_function: gs_progress_button_set_progress executable: /usr/bin/gnome-software journald_cursor: s=4ca6e09ab8d944ba98161b85003cd8a0;i=7322;b=fb7b05c9629f4272a4fe214647add1fe;m=12f2b1a5cf;t=5765db97434f6;x=4a89514f337cae61 kernel: 4.18.7-300.fc29.x86_64 package: gnome-software-3.30.0-1.fc29 reason: gnome-software killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Should be fixed by https://gitlab.gnome.org/GNOME/gnome-software/merge_requests/88
This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-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 Fedora 'version' of '29'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 29 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 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 please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.