[karmic] gnome-power-manager crashed with SIGSEGV in malloc_consolidate()

[Philip Muškovac]

Binary package hint: gnome-power-manager

Happens every time when I plug the power supply IN when the battery is charged. When I plug it out everything's ok. It also doesn't crash when the battery is being charged after I plug it in. But then g-p-m crashes once the charging process is finished.

ProblemType: Crash
Architecture: amd64
Date: Fri Jul 10 20:25:11 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/gnome-power-manager
Package: gnome-power-manager 2.27.2-0ubuntu1
ProcCmdline: gnome-power-manager
ProcEnviron:
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-2.16-generic
SegvAnalysis:
 Segfault happened at: 0x7f68bb542769 <malloc_consolidate+265>: mov 0x18(%rdx),%rcx
 PC (0x7f68bb542769) ok
 source "0x18(%rdx)" (0x00000018) not located in a known VMA region (needed readable region)!
 destination "%rcx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-power-manager
StacktraceTop:
 malloc_consolidate (av=0x7f68bb837a00)
 _int_free (av=0x7f68bb837a00, mem=0x187a060)
 *__GI___libc_free (mem=0x187a060) at malloc.c:3625
 gdk_pixbuf_finalize (object=0x1687d40)
 IA__g_object_unref (_object=<value optimized out>)
Title: gnome-power-manager crashed with SIGSEGV in malloc_consolidate()
Uname: Linux 2.6.31-2-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin netdev plugdev root sambashare

[Apport retracing service (apport)]

StacktraceTop:?? ()

[Scott Howard (showard314)]

Thanks for the bug report and helping make Ubuntu better. Is this bug repeatable? How often does it crash?

[Philip Muškovac (yofel)]

Well, I can reproduce it immeadiatly here:
(With charged battery) Pull power cable out - stick it back in -> crash.

[Philip Muškovac (yofel)]

And it crashes every time I try that.

[Philip Muškovac (yofel)]

I just got to try it on my eeePC and it doesn't crash there. So it might be thinkpad or amd64 related?

[Scott Howard (showard314)]

Thanks for working on debugging this. I believe this is a duplicate of bug #397248. We've got it fixed upstream and am working on getting it into Ubuntu quickly. If it persists after the fix is released in Ubuntu, reset this bug to new and remove the duplicate.

 duplicate 397248