gnome-software crashed with SIGSEGV in gtk_stack_set_visible_child_name()

[starkus]

not sure. installed some update and upgrade via apt-get.

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: gnome-software 3.19.92~git20160304.279bc80-0ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
Uname: Linux 4.4.0-10-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Mar 8 20:10:22 2016
ExecutablePath: /usr/bin/gnome-software
InstallationDate: Installed on 2015-09-20 (170 days ago)
InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422)
ProcCmdline: /usr/bin/gnome-software --gapplication-service
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fd6cb135207 <gtk_stack_set_visible_child_name+7>: mov 0x28(%rdi,%rax,1),%edx
 PC (0x7fd6cb135207) 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: Upgraded to xenial on 2016-01-22 (45 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

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 #1552074, 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.