gnome-software crashed with signal 5 in g_dbus_proxy_call_sync → fwupd_client_get_upgrades → gs_plugin_fwupd_add_updates → gs_plugin_loader_call_vfunc

Bug #1756695 reported by Joe Johnson
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
fwupd (Ubuntu)
Confirmed
Undecided
Unassigned
gnome-software (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

I need to get out more.

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-software 3.28.0-0ubuntu4
ProcVersionSignature: Ubuntu 4.15.0-13.14-lowlatency 4.15.10
Uname: Linux 4.15.0-13-lowlatency x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CrashCounter: 1
CurrentDesktop: XFCE
Date: Sun Mar 18 08:08:22 2018
ExecutablePath: /usr/bin/gnome-software
InstallationDate: Installed on 2018-03-17 (0 days ago)
InstallationMedia: Ubuntu-Studio 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180316)
InstalledPlugins:
 gnome-software-plugin-flatpak N/A
 gnome-software-plugin-limba N/A
 gnome-software-plugin-snap 3.28.0-0ubuntu4
ProcCmdline: gnome-software
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 5
SourcePackage: gnome-software
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_main_context_new () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_dbus_connection_send_message_with_reply_sync () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: gnome-software crashed with signal 5 in g_main_context_new()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout fax lpadmin netdev plugdev sambashare scanner sudo tape video

Revision history for this message
Joe Johnson (say2joe) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? () from /tmp/apport_sandbox_zw0dhd3z/lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_main_context_new () from /tmp/apport_sandbox_zw0dhd3z/lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_dbus_connection_send_message_with_reply_sync () from /tmp/apport_sandbox_zw0dhd3z/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /tmp/apport_sandbox_zw0dhd3z/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /tmp/apport_sandbox_zw0dhd3z/usr/lib/x86_64-linux-gnu/libgio-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
tags: added: apport-failed-retrace
tags: removed: need-amd64-retrace
summary: - gnome-software crashed with signal 5 in g_main_context_new()
+ gnome-software crashed with signal 5 in g_dbus_proxy_call_sync →
+ fwupd_client_get_upgrades → gs_plugin_fwupd_add_updates →
+ gs_plugin_loader_call_vfunc
information type: Private → Public
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
Revision history for this message
Mario Limonciello (superm1) wrote :

Unfortunately this stack trace is client side, but we don't know what actually happened on the daemon during this situation to get to the bottom of the problem.

Can you reproduce this again? If so, it would be really useful if you could run the daemon under debug (or possibly valgrind) to figure out what that side was doing.

Revision history for this message
Richard Hughes (richard-hughes) wrote :

Even a client stacktrace with debuginfo symbols would be useful...

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in fwupd (Ubuntu):
status: New → Confirmed
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

Possibly a duplicate of bug 1760795

Revision history for this message
Mario Limonciello (superm1) wrote :

I'll mark it as such, if we have evidence it's not at some point we can re-visit.

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.