indicator-power-service crashed with SIGSEGV in g_type_check_instance()

Bug #1272801 reported by martyfelker on 2014-01-26
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
indicator-power (Ubuntu)
Medium
Unassigned

Bug Description

Logged into KDE Plasma desktop Ubuntu 14.04

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: indicator-power 12.10.6+14.04.20140124-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
Uname: Linux 3.13.0-5-generic x86_64
ApportVersion: 2.13.1-0ubuntu2
Architecture: amd64
Date: Sat Jan 25 19:48:58 2014
ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-power/indicator-power-service
InstallationDate: Installed on 2014-01-25 (0 days ago)
InstallationMedia: Kubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130822)
ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-power/indicator-power-service
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/false
SegvAnalysis:
 Segfault happened at: 0x7fa61cffa6dd <g_type_check_instance+13>: mov (%rdi),%rax
 PC (0x7fa61cffa6dd) ok
 source "(%rdi)" (0x00000021) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: indicator-power
StacktraceTop:
 g_type_check_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_handler_disconnect () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
Title: indicator-power-service crashed with SIGSEGV in g_type_check_instance()
UpgradeStatus: Upgraded to trusty on 2014-01-25 (0 days ago)
UserGroups:

martyfelker (martyfelker-gmail) wrote :

StacktraceTop:
 g_type_check_instance (type_instance=type_instance@entry=0x21) at /build/buildd/glib2.0-2.39.3/./gobject/gtype.c:4080
 g_signal_handler_disconnect (instance=0x21, handler_id=140351430766768) at /build/buildd/glib2.0-2.39.3/./gobject/gsignal.c:2572
 on_connection_disconnected (connection=<optimized out>, remote_peer_vanished=<optimized out>, error=<optimized out>, user_data=0x17bb9c0) at /build/buildd/glib2.0-2.39.3/./gio/gdbusnamewatching.c:260
 ffi_call_unix64 () at ../src/x86/unix64.S:76
 ffi_call (cif=cif@entry=0x7fa61a716850, fn=0x7fa61d2f1680 <on_connection_disconnected>, rvalue=0x7fa61a7167c0, avalue=avalue@entry=0x7fa61a716760) at ../src/x86/ffi64.c:522

Changed in indicator-power (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Jackson Doak (noskcaj) on 2014-01-26
information type: Private → Public
Charles Kerr (charlesk) wrote :

> #1 0x00007fa61cfe7ee3 in g_signal_handler_disconnect (instance=0x21, handler_id=140351430766768) at /build/buildd/glib2.0-2.39.3/./gobject/gsignal.c:2572

That instance pointer is suspicious... possibly a NULL structure pointer got dereferenced? Although it's an odd number...

Launchpad Janitor (janitor) wrote :

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

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

Other bug subscribers