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

Bug #148175 reported by dominique
94
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gnome-power
Expired
Critical
gnome-power-manager (Ubuntu)
Fix Released
Medium
Ted Gould

Bug Description

Binary package hint: gnome-power-manager

lagirardiere

ProblemType: Crash
Architecture: i386
Date: Tue Oct 2 11:57:43 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/gnome-power-manager
NonfreeKernelModules: fglrx
Package: gnome-power-manager 2.20.0-0ubuntu3
PackageArchitecture: i386
ProcCmdline: gnome-power-manager
ProcCwd: /
ProcEnviron:
 SHELL=/bin/bash
 PATH=/home/lagirardiere/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=fr_FR.UTF-8
Signal: 11
SourcePackage: gnome-power-manager
StacktraceTop:
 ?? ()
 g_cclosure_marshal_VOID__BOOLEAN ()
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
 ?? ()
Title: gnome-power-manager crashed with SIGSEGV in g_cclosure_marshal_VOID__BOOLEAN()
Uname: Linux lagirardiere-desktop 2.6.22-12-generic #1 SMP Sun Sep 23 18:11:30 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev powerdev scanner tape video

Tags: apport-crash
Revision history for this message
dominique (dominique-violeau) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:screensaver_auth_request_cb (screensaver=0x81c7b80, auth_begin=0, manager=0x80bc9e8) at gpm-manager.c:1175
IA__g_cclosure_marshal_VOID__BOOLEAN (closure=0x81d8288, return_value=0x0, n_param_values=2, param_values=0xbfb2fecc, invocation_hint=0xbfb2fddc,
IA__g_closure_invoke (closure=0x81d8288, return_value=0x0, n_param_values=2, param_values=0xbfb2fecc, invocation_hint=0xbfb2fddc)
signal_emit_unlocked_R (node=0x81cbe20, detail=0, instance=0x81c7b80, emission_return=0x0, instance_and_params=0xbfb2fecc)
IA__g_signal_emit_valist (instance=0x81c7b80, signal_id=188, detail=0, var_args=0xbfb30110 "") at /build/buildd/glib2.0-2.14.1/gobject/gsignal.c:2199

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Changed in gnome-power-manager:
importance: Undecided → Medium
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for your report, is this still an issue with the final release?

Revision history for this message
Pedro Villavicencio (pedro) wrote :
Changed in gnome-power-manager:
status: New → Fix Released
Changed in gnome-power:
status: Unknown → Fix Released
Changed in gnome-power:
status: Fix Released → Confirmed
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Re-opened upstream.

Changed in gnome-power-manager:
assignee: nobody → ted-gould
status: Fix Released → Triaged
Revision history for this message
Ted Gould (ted) wrote :

I'm reclosing, because the upstream bug was reopened because someone is having it crash on Fedora. We do have patches to fix things that haven't been integrated into GPM mainstream (2.20) and likely Fedora. I'd be interested if someone on Ubuntu has it, but until then I'll just assume that we're better than Fedora ;)

Thanks for reporting. Ted.

Changed in gnome-power-manager:
status: Triaged → Fix Released
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Re-opening bug 279293 according to apport has a similar stacktrace with Intrepid

Changed in gnome-power-manager:
status: Fix Released → Triaged
Changed in gnome-power:
status: Confirmed → Invalid
Revision history for this message
Pedro Villavicencio (pedro) wrote :

doesn't seems to be an issue anymore, closing this report please re open if you face the same issue with latest package on Jaunty, thanks in advance.

Changed in gnome-power-manager (Ubuntu):
status: Triaged → Fix Released
Changed in gnome-power:
importance: Unknown → Critical
status: Invalid → Expired
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.