[power]: gnome-control-center crashed with SIGSEGV in cc_strength_bar_set_fraction()

Bug #996200 reported by John Robert Sion
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-control-center (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

[power]: gnome-control-center crashed with SIGSEGV in cc_strength_bar_set_fraction()

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-control-center 1:3.4.1-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-24.38-generic 3.2.16
Uname: Linux 3.2.0-24-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu7
Architecture: i386
Date: Tue May 8 05:27:00 2012
ExecutablePath: /usr/bin/gnome-control-center
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
ProcCmdline: gnome-control-center power
SegvAnalysis:
 Segfault happened at: 0x8a00c5 <cc_strength_bar_set_fraction+37>: fstpl (%eax)
 PC (0x008a00c5) ok
 source "(%eax)" (0x73754244) not located in a known VMA region (needed readable region)!
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 cc_strength_bar_set_fraction ()
 ?? () from /usr/lib/control-center-1/panels/libpower.so
 g_simple_async_result_complete () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
 g_simple_async_result_complete () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
Title: [power]: gnome-control-center crashed with SIGSEGV in cc_strength_bar_set_fraction()
UpgradeStatus: Upgraded to precise on 2012-03-03 (65 days ago)
UserGroups: adm admin cdrom dialout dip fax floppy fuse lpadmin plugdev sambashare tape video
usr_lib_gnome-control-center:
 activity-log-manager-control-center 0.9.4-0ubuntu3
 deja-dup 22.0-0ubuntu2
 gnome-bluetooth 3.2.2-0ubuntu5
 indicator-datetime 0.3.94-0ubuntu2

Revision history for this message
John Robert Sion (johnrobertsion) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 cc_strength_bar_set_fraction ()
 set_device_battery_primary (device=0x223a0808, panel=0x22349a28) at cc-power-panel.c:222
 get_devices_cb (source_object=0x222a58b8, res=0x2254b968, user_data=0x22349a28) at cc-power-panel.c:735
 g_simple_async_result_complete (simple=0x2254b968) at /build/buildd/glib2.0-2.32.1/./gio/gsimpleasyncresult.c:767
 reply_cb (connection=0xb6c06008, res=0x2254b4b0, user_data=0x2254b968) at /build/buildd/glib2.0-2.32.1/./gio/gdbusproxy.c:2614

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gnome-control-center (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
information type: Private → Public
Revision history for this message
Sebastien Bacher (seb128) wrote :

The bug hasn't seen any activity in years and there has been no recent similar reports, the code also changed quite a lot since and it's likely the issue doesn't exist anymore. Closing, feel free to open a new report if you still get problems in recent Ubuntu versions

Changed in gnome-control-center (Ubuntu):
status: New → Invalid
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.