Ubuntu
limba package

gnome-software crashed with SIGSEGV in g_main_loop_is_running()

Bug #1716508 reported by TheWickerman666
30
This bug affects 3 people
Affects Status Importance Assigned to Milestone
limba (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

some gnome-software install problem

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-software 3.25.91-1ubuntu5
ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
Uname: Linux 4.12.0-13-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Sun Sep 10 06:20:48 2017
ExecutablePath: /usr/bin/gnome-software
InstallationDate: Installed on 2017-07-08 (64 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
InstalledPlugins:
 gnome-software-plugin-flatpak 3.25.91-1ubuntu5
 gnome-software-plugin-limba 3.25.91-1ubuntu5
 gnome-software-plugin-snap 3.25.91-1ubuntu5
ProcCmdline: /usr/bin/gnome-software --gapplication-service
SegvAnalysis:
 Segfault happened at: 0x7f37797265c9 <g_main_loop_is_running+9>: mov 0xc(%rdi),%eax
 PC (0x7f37797265c9) ok
 source "0xc(%rdi)" (0x0000000d) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-software
StacktraceTop:
 g_main_loop_is_running () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/liblimba.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_main_loop_is_running()
UpgradeStatus: Upgraded to artful on 2017-07-19 (53 days ago)
UserGroups: adm bluetooth cdrom dialout dip fax floppy lpadmin netdev plugdev sambashare scanner sudo tape users vboxusers

Revision history for this message
TheWickerman666 (thewickerman666) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_main_loop_is_running (loop=0x1) at ../../../../glib/gmain.c:4130
 li_manager_bus_vanished (connection=<optimized out>, name=<optimized out>, mgr=<optimized out>) at ./src/li-manager.c:153
 do_call (client=client@entry=0x7f374444b400, call_type=call_type@entry=CALL_TYPE_NAME_VANISHED) at ../../../../gio/gdbusnamewatching.c:219
 call_vanished_handler (client=client@entry=0x7f374444b400, ignore_cancelled=0) at ../../../../gio/gdbusnamewatching.c:245
 call_vanished_handler (ignore_cancelled=0, client=0x7f374444b400) 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
Revision history for this message
Sebastien Bacher (seb128) wrote :

the issue is in the limba code

information type: Private → Public
affects: gnome-software (Ubuntu) → limba (Ubuntu)
Apport retracing service (apport)
tags: added: bionic
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in limba (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

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