gnome-power-manager crashed with SIGSEGV in gpm_cell_array_charge_low_cb()

Bug #279285 reported by Joakim Andersson
6
Affects Status Importance Assigned to Milestone
gnome-power-manager (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: gnome-power-manager

gnome-power-manager segfaults when battery critical or battery low is reached.

Right now, my battery accuracy profile isn't accurate enough for time thresholds, so percentage thresholds are used.

I think this is the same bug as bug #269083 but I managed to get a better stacktrace and couldn't find out any way that apport would let me add it to the original report. Anyway, this report shows the real(?) source of the SIGSEGV.

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/gnome-power-manager
NonfreeKernelModules: nvidia
Package: gnome-power-manager 2.24.0-0ubuntu3 [modified: usr/bin/gnome-power-manager usr/bin/gnome-power-preferences usr/bin/gnome-power-statistics usr/share/applications/gnome-power-preferences.desktop usr/lib/gnome-power-manager/gnome-brightness-applet usr/lib/gnome-power-manager/gnome-inhibit-applet usr/lib/bonobo/servers/GNOME_BrightnessApplet.server usr/lib/bonobo/servers/GNOME_InhibitApplet.server]
ProcAttrCurrent: unconfined
ProcCmdline: gnome-power-manager
ProcEnviron:
 SHELL=/bin/zsh
 LANG=en_US.UTF-8
 PATH=/home/username/bin:/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
Signal: 11
SourcePackage: gnome-power-manager
StacktraceTop:
 gpm_cell_array_charge_low_cb (cell_array=0x223b3f0,
 IA__g_closure_invoke (closure=0x2457e60,
 signal_emit_unlocked_R (node=0x2454b60, detail=0,
 IA__g_signal_emit_valist (instance=0x223b3f0,
 IA__g_signal_emit (instance=0x223b3f0,
Title: gnome-power-manager crashed with SIGSEGV in gpm_cell_array_charge_low_cb()
Uname: Linux 2.6.27-5-generic x86_64
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev video www-data

Tags: apport-crash
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.