Bug 1565027

Summary: [abrt] gnome-software: gtk_stack_set_visible_child_name(): gnome-software killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Jonathan Haas <jonha87>
Component: gnome-softwareAssignee: Richard Hughes <rhughes>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 28CC: 7d28c752, acranford, ary.sousa, boyang, bugzilla.10.cyrils, elleander86, klember, laerciogilpb, luan.cestari, max, paulim.hardware, philipp.bobek, piotrek.rogowski+rh, pschindl, pundir.ashish, rhughes, tcfxfzoi, vanpivix, william.oprandi
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/1da743c666bbb6e00909c36799675f113ba1cd23
Whiteboard: abrt_hash:d72f23a3e1627624bac5f1ec88c3bb8af86890f3;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-05-28 23:54:13 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: cpuinfo
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: mountinfo
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages
none
File: backtrace none

Description Jonathan Haas 2018-04-09 07:48:59 UTC
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

Comment 1 Jonathan Haas 2018-04-09 07:49:05 UTC
Created attachment 1419136 [details]
File: backtrace

Comment 2 Jonathan Haas 2018-04-09 07:49:06 UTC
Created attachment 1419137 [details]
File: cgroup

Comment 3 Jonathan Haas 2018-04-09 07:49:08 UTC
Created attachment 1419138 [details]
File: core_backtrace

Comment 4 Jonathan Haas 2018-04-09 07:49:09 UTC
Created attachment 1419139 [details]
File: cpuinfo

Comment 5 Jonathan Haas 2018-04-09 07:49:11 UTC
Created attachment 1419140 [details]
File: dso_list

Comment 6 Jonathan Haas 2018-04-09 07:49:13 UTC
Created attachment 1419141 [details]
File: environ

Comment 7 Jonathan Haas 2018-04-09 07:49:14 UTC
Created attachment 1419142 [details]
File: exploitable

Comment 8 Jonathan Haas 2018-04-09 07:49:15 UTC
Created attachment 1419143 [details]
File: limits

Comment 9 Jonathan Haas 2018-04-09 07:49:17 UTC
Created attachment 1419144 [details]
File: maps

Comment 10 Jonathan Haas 2018-04-09 07:49:19 UTC
Created attachment 1419145 [details]
File: mountinfo

Comment 11 Jonathan Haas 2018-04-09 07:49:21 UTC
Created attachment 1419146 [details]
File: open_fds

Comment 12 Jonathan Haas 2018-04-09 07:49:22 UTC
Created attachment 1419147 [details]
File: proc_pid_status

Comment 13 Jonathan Haas 2018-04-09 07:49:23 UTC
Created attachment 1419148 [details]
File: var_log_messages

Comment 14 Bo Yang 2018-05-28 09:42:47 UTC
*** Bug 1583141 has been marked as a duplicate of this bug. ***

Comment 15 Paulim_hed 2018-06-06 21:31:30 UTC
*** Bug 1588188 has been marked as a duplicate of this bug. ***

Comment 16 Petr Schindler 2018-09-14 07:26:56 UTC
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

Comment 17 Petr Schindler 2018-09-14 07:27:00 UTC
Created attachment 1483206 [details]
File: backtrace

Comment 18 rugk 2018-10-03 11:37:57 UTC
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

Comment 19 Philipp Bobek 2018-10-09 07:09:05 UTC
*** Bug 1637368 has been marked as a duplicate of this bug. ***

Comment 20 Luan Cestari 2018-10-24 01:17:27 UTC
*** Bug 1642199 has been marked as a duplicate of this bug. ***

Comment 21 William Oprandi 2018-10-29 09:23:09 UTC
*** Bug 1643865 has been marked as a duplicate of this bug. ***

Comment 22 Ary Sousa 2018-11-06 11:09:00 UTC
*** Bug 1646941 has been marked as a duplicate of this bug. ***

Comment 23 Max E 2018-11-21 18:38:54 UTC
*** Bug 1652275 has been marked as a duplicate of this bug. ***

Comment 24 acranford 2018-11-22 17:52:05 UTC
*** Bug 1652731 has been marked as a duplicate of this bug. ***

Comment 25 a5ur 2018-11-24 06:22:03 UTC
*** Bug 1653004 has been marked as a duplicate of this bug. ***

Comment 26 Laercio GIl 2019-04-11 12:37:15 UTC
*** Bug 1698882 has been marked as a duplicate of this bug. ***

Comment 27 Ben Cotton 2019-05-02 19:41:33 UTC
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.

Comment 28 Ben Cotton 2019-05-28 23:54:13 UTC
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.