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

[Muelli]

Binary package hint: gnome-power-manager

Hm, I suspended my machine and resumed it. The keyboard didn't work at all, I had to click "switch user" in order to bring my keyboard back to live. As the other bugreports seem to be old and I didn't mark this one as dup of one other.

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/gnome-power-manager
Package: gnome-power-manager 2.23.6-0ubuntu1
ProcAttrCurrent: unconfined
ProcCmdline: gnome-power-manager
Signal: 11
SourcePackage: gnome-power-manager
StacktraceTop:
 ?? ()
 ?? ()
 g_closure_invoke ()
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_signal_emit_valist ()
Title: gnome-power-manager crashed with SIGSEGV in g_closure_invoke()
Uname: Linux 2.6.26-5-generic x86_64
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin netdev plugdev powerdev scanner vboxusers video

[Rafal Kwasny (mag)]

Exactly same crash here, random moment after resuming from suspend - also on amd64

[Nizar Kerkeni (nizarus)]

same crash on intrepid amd64 but not resuming from suspend. Just few minutes after logging.

[Fernando Miguel (fernandomiguel)]

after several months without gnome-power-manager working, it started working this weekend.
From clean boot it would work as expected, but after any number of hibernate/resume cycles it would stop working.

Manually starting it, makes it close (crash?) after a few minutes (less then 5).

My latest crash was after i remove my power cord, and remain to battery.

[Niels Egberts (nielsegberts)]

I have confirmed this bug too a few times, I was just browsing the internet on battery.

[Dylan Hunter (dylan-dylanhunter)]

Confirmed, but also not from suspend, just from a period of inactivity.

[Hebert (hebert-bernardo)]

Distributor ID: Ubuntu
Description: Ubuntu intrepid (development branch)
Release: 8.10
Codename: intrepid (X86_64)

Kernel 2.6.26-5-generic #1

My electric power went down for about a minute and gnome-power-manager failed to display the gnome-panel battery icon of my APC UPS 600 No-Break.

After electric power was restored a crash report send me right here.

it used to work on hardy.

Hope that helps.

[Chris Halse Rogers (raof)]

My bug 260314 is probably a dupe of this.

That crash occurs each time the % battery charge changes. That seems to be the trigger for the other descriptions here, but care to check? :)

[Fernando Miguel (fernandomiguel)]

someone said they need a backtrace.... how can i produce one an attach it?

[Salvador Velázquez de la Cruz (salvador-vc)]

i just work normally and the crash occurs

[vanant (vanant)]

Please find the attached retrace

On Tue, Aug 26, 2008 at 10:30 PM, Pedro Villavicencio <email address hidden>wrote:

> ** Tags added: need-amd64-retrace
>
> --
> gnome-power-manager crashed with SIGSEGV in g_closure_invoke()
> https://bugs.launchpad.net/bugs/260597
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in "gnome-power-manager" source package in Ubuntu: New
>
> Bug description:
> Binary package hint: gnome-power-manager
>
> Hm, I suspended my machine and resumed it. The keyboard didn't work at all,
> I had to click "switch user" in order to bring my keyboard back to live. As
> the other bugreports seem to be old and I didn't mark this one as dup of one
> other.
>
> ProblemType: Crash
> Architecture: amd64
> DistroRelease: Ubuntu 8.10
> ExecutablePath: /usr/bin/gnome-power-manager
> Package: gnome-power-manager 2.23.6-0ubuntu1
> ProcAttrCurrent: unconfined
> ProcCmdline: gnome-power-manager
> Signal: 11
> SourcePackage: gnome-power-manager
> StacktraceTop:
> ?? ()
> ?? ()
> g_closure_invoke ()
> ?? () from /usr/lib/libgobject-2.0.so.0
> g_signal_emit_valist ()
> Title: gnome-power-manager crashed with SIGSEGV in g_closure_invoke()
> Uname: Linux 2.6.26-5-generic x86_64
> UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin netdev
> plugdev powerdev scanner vboxusers video
>

[Pedro Villavicencio (pedro)]

vanant, it needs to be retraced by apport, that's why i marked it as such, thanks.

[Chris Halse Rogers (raof)]

Here's a gdb trace with all the relevant dbgsym packages installed; I think it might be time to take this upstream.