gnome-software crashed with SIGSEGV in g_mutex_lock → g_main_loop_quit → do_call → call_vanished_handler → call_vanished_handler → #5 → emit_signal_instance_in_idle_cb → g_main_dispatch

Bug #1758499 reported by nabin
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gnome-software (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Just logged in and this bug comes out of nowhere. Moreover, when trying to launch gnome-software from terminal , It doesn't launch and shows a timeout error.

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-software 3.28.0-0ubuntu7
Uname: Linux 4.15.12-041512-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: GNOME
Date: Sat Mar 24 12:34:30 2018
ExecutablePath: /usr/bin/gnome-software
InstalledPlugins:
 gnome-software-plugin-flatpak 3.28.0-0ubuntu7
 gnome-software-plugin-limba 3.28.0-0ubuntu7
 gnome-software-plugin-snap 3.28.0-0ubuntu7
ProcCmdline: /usr/bin/gnome-software --gapplication-service
SegvAnalysis:
 Segfault happened at: 0x7f956ce4fcd5 <g_mutex_lock+5>: lock xadd %eax,(%rdi)
 PC (0x7f956ce4fcd5) ok
 source "%eax" ok
 destination "(%rdi)" (0x00000000) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: gnome-software
StacktraceTop:
 g_mutex_lock () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_main_loop_quit () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: gnome-software crashed with SIGSEGV in g_mutex_lock()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo

Revision history for this message
nabin (nabin6707-7) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_mutex_lock (mutex=0x0) at ../../../../glib/gthread-posix.c:1343
 g_main_loop_quit (loop=0x7f953c0cf190) at ../../../../glib/gmain.c:4124
 do_call (client=client@entry=0x7f953400d550, call_type=call_type@entry=CALL_TYPE_NAME_VANISHED) at ../../../../gio/gdbusnamewatching.c:219
 call_vanished_handler (client=client@entry=0x7f953400d550, ignore_cancelled=0) at ../../../../gio/gdbusnamewatching.c:245
 call_vanished_handler (ignore_cancelled=0, client=0x7f953400d550) at ../../../../gio/gdbusnamewatching.c:243

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
summary: - gnome-software crashed with SIGSEGV in g_mutex_lock()
+ gnome-software crashed with SIGSEGV in g_mutex_lock → g_main_loop_quit →
+ do_call → call_vanished_handler → call_vanished_handler → #5 →
+ emit_signal_instance_in_idle_cb → g_main_dispatch
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
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.