Ubuntu
indicator-power package

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

Bug #1295821 reported by Sergio Schneider on 2014-03-21

64

This bug affects 12 people

Affects		Status	Importance	Assigned to	Milestone
	indicator-power (Ubuntu)	Confirmed	Medium	Unassigned

Bug Description

None

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: indicator-power 12.10.6+14.04.20140314-0ubuntu1
Uname: Linux 3.14.0-031400rc6-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
Date: Fri Mar 14 16:55:35 2014
ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-power/indicator-power-service
InstallationDate: Installed on 2014-03-05 (15 days ago)
InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140305)
ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-power/indicator-power-service
SegvAnalysis:
Segfault happened at: 0x7f1532489c1c <g_object_unref+12>: mov (%rdi),%rax
PC (0x7f1532489c1c) 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_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
g_bus_unwatch_name () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
?? ()
Title: indicator-power-service crashed with SIGSEGV in g_object_unref()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Tags:

Revision history for this message

Sergio Schneider (spsf) wrote on 2014-03-21:

#1

Dependencies.txt Edit (16.9 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (1.1 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (291 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (10.5 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (807 bytes, text/plain; charset="utf-8")
Registers.txt Edit (732 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (317 bytes, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (2.8 KiB, text/plain; charset="utf-8")
UPowerDump.txt Edit (436 bytes, text/plain; charset="utf-8")

information type:

Private → Public

Revision history for this message

Apport retracing service (apport) wrote on 2014-03-21:

#2

StacktraceTop:
g_object_unref (_object=0x21) at /build/buildd/glib2.0-2.39.92/./gobject/gobject.c:3009
g_bus_unwatch_name (watcher_id=33) at /build/buildd/glib2.0-2.39.92/./gio/gdbusnamewatching.c:823
?? ()
?? ()
ffi_call (cif=0x8445c70200cf81, cif@entry=<error reading variable: Cannot access memory at address 0x7f1530f1aae4>, fn=0xf03fa83c0960f03, rvalue=0xd2843774c084c296, avalue=0x7f152f4ed760) at ../src/x86/ffi64.c:522

Revision history for this message

Apport retracing service (apport) wrote on 2014-03-21: Stacktrace.txt

#3

Stacktrace.txt Edit (1.5 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2014-03-21: StacktraceSource.txt

#4

StacktraceSource.txt Edit (787 bytes, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2014-03-21: ThreadStacktrace.txt

#5

ThreadStacktrace.txt Edit (5.4 KiB, text/plain)

Changed in indicator-power (Ubuntu):
importance:	Undecided → Medium
tags:	removed: need-amd64-retrace

Revision history for this message

Launchpad Janitor (janitor) wrote on 2014-03-31:

#6

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

Changed in indicator-power (Ubuntu):
status:	New → Confirmed

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

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