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

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

Bug Description

Binary package hint: gnome-power-manager

I just got this on 8.10 beta. I was doing some updates, and trying to use the fast user switcher. The switch failed, and when I came back, the bug report thing was waiting for me.

ivan@ivan-ubuntu:~$ lsb_release -rd
Description: Ubuntu intrepid (development branch)
Release: 8.10

ivan@ivan-ubuntu:~$ apt-cache policy gnome-power-manager
gnome-power-manager:
  Installed: 2.24.0-0ubuntu3
  Candidate: 2.24.0-0ubuntu3
  Version table:
 *** 2.24.0-0ubuntu3 0
        500 http://us.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/gnome-power-manager
NonfreeKernelModules: nvidia
Package: gnome-power-manager 2.24.0-0ubuntu3
ProcAttrCurrent: unconfined
ProcCmdline: gnome-power-manager
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
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
 g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
Title: gnome-power-manager crashed with SIGSEGV in g_cclosure_marshal_VOID__BOOLEAN()
Uname: Linux 2.6.27-5-generic i686
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin plugdev sambashare scanner tape video

Revision history for this message
Eviltechie (eviltechie) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Possible regression detected

This crash has the same stack trace characteristics as bug #148175. However, the latter was already fixed in an earlier package version than the one in this report. This might be a regression or because the problem is in a dependent package.

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.