gnome-software crashed with SIGSEGV in gtk_stack_set_visible_child_name()

Bug #1552550 reported by NoOne
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gnome-software (Ubuntu)
Fix Committed
Medium
Unassigned

Bug Description

The App crashed when asking if there was any updates from the Details panel in System Preferences.

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: gnome-software 3.19.92~git20160303.26a927d-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3
Uname: Linux 4.4.0-9-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Mar 3 00:23:20 2016
ExecutablePath: /usr/bin/gnome-software
InstallationDate: Installed on 2016-03-03 (0 days ago)
InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160302)
ProcCmdline: /usr/bin/gnome-software --gapplication-service
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANGUAGE=fr_CA:fr
 LANG=fr_CA.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7fccee3a2207 <gtk_stack_set_visible_child_name+7>: mov 0x28(%rdi,%rax,1),%edx
 PC (0x7fccee3a2207) ok
 source "0x28(%rdi,%rax,1)" (0xfffffffffffffeb8) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-software
StacktraceTop:
 gtk_stack_set_visible_child_name () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? ()
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-software crashed with SIGSEGV in gtk_stack_set_visible_child_name()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
NoOne (1noname) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 gtk_stack_set_visible_child_name (stack=0x0, name=0x44eab2 "uptodate") at /build/gtk+3.0-qjgeoX/gtk+3.0-3.18.8/./gtk/gtkstack.c:1812
 gs_shell_updates_update_ui_state (self=0x19f77c0) at gs-shell-updates.c:363
 g_closure_invoke () from /tmp/apport_sandbox_8JD_BE/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 signal_emit_unlocked_R () from /tmp/apport_sandbox_8JD_BE/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /tmp/apport_sandbox_8JD_BE/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gnome-software (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnome-software (Ubuntu):
status: New → Confirmed
information type: Private → Public
Revision history for this message
Robert Ancell (robert-ancell) wrote :

I think this is caused when G-S is running in daemon mode. When the network changes state the updates page widget is no longer exists and causes this crash. So it probably doesn't happen anymore now we disabled daemon mode. Will fix upstream anyway.

Changed in gnome-software (Ubuntu):
status: Confirmed → Fix Committed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.