Description of problem: Restarting gnome-software after aborting looking for updates Version-Release number of selected component: gnome-software-3.28.0-5.fc28 Additional info: reporter: libreport-2.9.4 backtrace_rating: 3 cmdline: /usr/bin/gnome-software --gapplication-service crash_function: gtk_stack_set_visible_child_name executable: /usr/bin/gnome-software journald_cursor: s=a226d9fefa8f4c028739e4f3cf84f391;i=45881;b=7d5af5c9982a440b9b8c4215ba888258;m=6aa9507;t=569652f398f5b;x=6419e48e6bc6e17f kernel: 4.16.0-0.rc7.git0.1.fc28.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (7 frames) #0 gtk_stack_set_visible_child_name at gtkstack.c:1839 #1 get_installed_updates_cb at ../src/gs-update-dialog.c:231 #2 g_task_return_now at gtask.c:1148 #3 complete_in_idle_cb at gtask.c:1162 #8 g_main_context_iteration at gmain.c:3964 #9 g_application_run at gapplication.c:2482 #12 _start Potential duplicate: bug 1513568
Created attachment 1419136 [details] File: backtrace
Created attachment 1419137 [details] File: cgroup
Created attachment 1419138 [details] File: core_backtrace
Created attachment 1419139 [details] File: cpuinfo
Created attachment 1419140 [details] File: dso_list
Created attachment 1419141 [details] File: environ
Created attachment 1419142 [details] File: exploitable
Created attachment 1419143 [details] File: limits
Created attachment 1419144 [details] File: maps
Created attachment 1419145 [details] File: mountinfo
Created attachment 1419146 [details] File: open_fds
Created attachment 1419147 [details] File: proc_pid_status
Created attachment 1419148 [details] File: var_log_messages
*** Bug 1583141 has been marked as a duplicate of this bug. ***
*** Bug 1588188 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Gnome software crashed right after a window with done updates was shown (after restart I clicked on notification about installed updates). reporter: libreport-2.9.5 backtrace_rating: 4 cmdline: /usr/bin/gnome-software --gapplication-service crash_function: gtk_stack_set_visible_child_name executable: /usr/bin/gnome-software journald_cursor: s=61c2c27b756b44b0b65c0b2fae382149;i=c619;b=27c075cf0a4440239f4e9a168e79f753;m=4a91198;t=575cfa9eb24f6;x=c5aaaecae1996bd0 kernel: 4.18.7-200.fc28.x86_64 package: gnome-software-3.28.2-2.fc28 reason: gnome-software killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Created attachment 1483206 [details] File: backtrace
Similar problem has been detected: I clicked on an post-update notification and it started showing me the window etc. It was so slow, I also switched to the window, when it was shown in dash-to-dock. reporter: libreport-2.9.5 backtrace_rating: 4 cmdline: /usr/bin/gnome-software --gapplication-service crash_function: gtk_stack_set_visible_child_name executable: /usr/bin/gnome-software journald_cursor: s=5fac00b9d279434a8b3bbf77921eb9fa;i=1599e;b=2e22c45688144bd0b98a7a37db6f23ae;m=5827e17;t=577515b8c5ae7;x=25ac8414ca029950 kernel: 4.18.10-200.fc28.x86_64 package: gnome-software-3.28.2-2.fc28 reason: gnome-software killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1637368 has been marked as a duplicate of this bug. ***
*** Bug 1642199 has been marked as a duplicate of this bug. ***
*** Bug 1643865 has been marked as a duplicate of this bug. ***
*** Bug 1646941 has been marked as a duplicate of this bug. ***
*** Bug 1652275 has been marked as a duplicate of this bug. ***
*** Bug 1652731 has been marked as a duplicate of this bug. ***
*** Bug 1653004 has been marked as a duplicate of this bug. ***
*** Bug 1698882 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. 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 '28'. 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 28 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 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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.