gnome-software crashed with SIGSEGV in gtk_stack_set_visible_child_name()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-software (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Crashed when trying to review installed updates from reboot.
- Restart computer with pending updates
- Tick the option to install pending updates
- Updates install at startup
- Login
- Notification appears to notify the user that updates were applied and the user can review.
- Clicked on the notification
- Gnome Software opens with a modal already open to display the recently installed software, but it hangs (waited 30-60 seconds).
- Closed modal.
- Clicked on the "Installed" button.
- Crash occurs within a few seconds
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-software 3.28.1-0ubuntu3
ProcVersionSign
Uname: Linux 4.15.0-15-generic x86_64
ApportVersion: 2.20.9-0ubuntu5
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Apr 18 21:28:43 2018
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2016-10-25 (539 days ago)
InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720)
InstalledPlugins:
gnome-
gnome-
gnome-
ProcCmdline: /usr/bin/
ProcEnviron:
LANGUAGE=en_ZA:en
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_ZA.UTF-8
SHELL=/usr/bin/zsh
SegvAnalysis:
Segfault happened at: 0x7fa750061087 <gtk_stack_
PC (0x7fa750061087) ok
source "0x30(%rdi,%rax,1)" (0xffffffffffff
destination "%edx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-software
StacktraceTop:
gtk_stack_
?? ()
?? () from /usr/lib/
?? () from /usr/lib/
g_main_
Title: gnome-software crashed with SIGSEGV in gtk_stack_
UpgradeStatus: Upgraded to bionic on 2018-01-24 (84 days ago)
UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sbuild sudo vboxusers
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1724188, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.