Ubuntu
gnome-power-manager package

gnome-power-manager:2651: GLib-GObject-WARNING **: /build/buildd/glib2.0-2.25.11/gobject/gsignal.c:2275: signal `proxy-status' is invalid for instance `0x85b24c8'

Bug #614248 reported by dino99
74
This bug affects 19 people
Affects Status Importance Assigned to Milestone
gnome-power-manager (Fedora)
Fix Released
Medium
gnome-power-manager (Ubuntu)
Fix Released
Undecided
Unassigned
Nominated for Lucid by NoOp

Bug Description

Binary package hint: gnome-power-manager

got this error when maverick start:

gnome-power-manager:2651: GLib-GObject-WARNING **: /build/buildd/glib2.0-2.25.11/gobject/gsignal.c:2275: signal `proxy-status' is invalid for instance `0x85b24c8'

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: gnome-power-manager 2.31.1-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-14.19-generic-pae 2.6.35
Uname: Linux 2.6.35-14-generic-pae i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Fri Aug 6 09:50:40 2010
ExecutablePath: /usr/bin/gnome-power-manager
GConfNonDefault:
 /apps/gnome-power-manager/lock/blank_screen=false
 /apps/gnome-power-manager/lock/use_screensaver_settings=false
 /apps/gnome-power-manager/notify/sleep_failed_uri=
 /apps/gnome-power-manager/ui/icon_policy=charge
GnomeSessionIdleInhibited: No
GnomeSessionInhibitors: None
GnomeSessionSuspendInhibited: No
MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-14-generic-pae root=UUID=00c5de83-479c-4ab0-9b54-9af0a727175e ro vga=791 quiet splash
ProcEnviron:
 LANG=fr_FR.utf8
 SHELL=/bin/bash
SourcePackage: gnome-power-manager
XsessionErrors: (polkit-gnome-authentication-agent-1:2678): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
dmi.bios.date: 10/22/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3001
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5W DH Deluxe
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3001:bd10/22/2009:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: P5W DH Deluxe
dmi.product.version: System Version
dmi.sys.vendor: ASUSTEK COMPUTER INC

Revision history for this message
In , ritz (ritz-redhat-bugs) wrote :

Description of problem:
gpm crashes on startup

Version-Release number of selected component (if applicable):
gnome-power-manager-2.31.3-1.fc14.x86_64

How reproducible:
always

Additional info:
$ gnome-power-bugreport.sh
Distro version: Fedora release 14 (Rawhide)
Kernel version: 2.6.34-45.fc14.x86_64
g-p-m version: 2.31.3
HAL version: 0.5.14
System manufacturer: missing
System version: missing
System product: missing
AC adapter present: yes
Battery present: yes
Laptop panel present: yes
CPU scaling present: no

bt -
Gtk-Message: Failed to load module "pk-gtk-module": libpk-gtk-module.so: cannot open shared object file: No such file or directory
[New Thread 0x7ffff0a6f710 (LWP 2477)]

(gnome-power-manager:2474): GLib-GObject-WARNING **: gsignal.c:2276: signal `proxy-status' is invalid for instance `0x6b7260'
Detaching after fork from child process 2479.
The program 'gnome-power-manager' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAtom (invalid Atom parameter)'.
  (Details: serial 171 error_code 5 request_code 148 minor_code 15)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

(gdb) bt
#0 0x00000030646aa420 in _exit () from /lib64/libc.so.6
#1 0x0000003064636f52 in exit () from /lib64/libc.so.6
#2 0x00000037df867fcf in ?? () from /usr/lib64/libgdk-x11-3.0.so.0
#3 0x0000003067e46da4 in _XError () from /usr/lib64/libX11.so.6
#4 0x0000003067e4d277 in ?? () from /usr/lib64/libX11.so.6
#5 0x0000003067e4d983 in _XReply () from /usr/lib64/libX11.so.6
#6 0x000000306aa051bc in XRRGetOutputProperty () from /usr/lib64/libXrandr.so.2
#7 0x0000000000419e0a in ?? ()
#8 0x000000000041a330 in ?? ()
#9 0x000000000041aa4a in ?? ()
#10 0x0000000000409ba9 in ?? ()
#11 0x00007ffff7873915 in g_type_create_instance (type=<value optimized out>) at gtype.c:1888
#12 0x00007ffff785669c in g_object_constructor (type=<value optimized out>, n_construct_properties=0, construct_params=0x0)
    at gobject.c:1483
#13 0x00007ffff785796a in g_object_newv (object_type=7159312, n_parameters=0, parameters=0x0) at gobject.c:1267
#14 0x00007ffff785819c in g_object_new (object_type=7159312, first_property_name=0x0) at gobject.c:1179
#15 0x000000000040d912 in ?? ()
#16 0x00007ffff7873915 in g_type_create_instance (type=<value optimized out>) at gtype.c:1888
#17 0x00007ffff785669c in g_object_constructor (type=<value optimized out>, n_construct_properties=0, construct_params=0x0)
    at gobject.c:1483
#18 0x00007ffff785796a in g_object_newv (object_type=7025504, n_parameters=0, parameters=0x0) at gobject.c:1267
#19 0x00007ffff785819c in g_object_new (object_type=7025504, first_property_name=0x0) at gobject.c:1179
#20 0x000000000040d312 in ?? ()
#21 0x000000000040ce7c in ?? ()
#22 0x000000306461ed6d in __libc_start_main () from /lib64/libc.so.6

Revision history for this message
In , Richard (richard-redhat-bugs) wrote :

Your backtrace is meanlingless. You need to install the debuginfo packages.

Revision history for this message
In , ritz (ritz-redhat-bugs) wrote :
Download full text (3.4 KiB)

Breakpoint 1, 0x0000003b500aa260 in _exit () from /lib64/libc.so.6
(gdb) bt
#0 0x0000003b500aa260 in _exit () from /lib64/libc.so.6
#1 0x0000003b50036f12 in exit () from /lib64/libc.so.6
#2 0x0000003423c65cff in ?? () from /usr/lib64/libgdk-x11-3.0.so.0
#3 0x0000003b53c46da4 in _XError () from /usr/lib64/libX11.so.6
#4 0x0000003b53c4d277 in ?? () from /usr/lib64/libX11.so.6
#5 0x0000003b53c4d983 in _XReply () from /usr/lib64/libX11.so.6
#6 0x0000003b584051bc in XRRGetOutputProperty ()
   from /usr/lib64/libXrandr.so.2
#7 0x000000000041c25a in gpm_brightness_output_get_internal (brightness=
    0x6d5180, output=81, cur=0x7fffffffd644) at gpm-brightness.c:178
#8 0x000000000041c780 in gpm_brightness_output_get_percentage (brightness=
    0x6d5180, op=<value optimized out>) at gpm-brightness.c:323
#9 gpm_brightness_foreach_resource (brightness=0x6d5180,
    op=<value optimized out>) at gpm-brightness.c:489
#10 gpm_brightness_foreach_screen (brightness=0x6d5180,
    op=<value optimized out>) at gpm-brightness.c:526
#11 0x000000000041ce9a in gpm_brightness_get (brightness=0x6d5180, percentage=
    0x7fffffffd6d4) at gpm-brightness.c:633
#12 0x000000000040c349 in gpm_backlight_brightness_evaluate_and_set (backlight=
    0x665a80, interactive=0) at gpm-backlight.c:342
#13 0x0000003b52430915 in g_type_create_instance ()
   from /lib64/libgobject-2.0.so.0
#14 0x0000003b5241369c in ?? () from /lib64/libgobject-2.0.so.0
---Type <return> to continue, or q <return> to quit---fram 7
#15 0x0000003b5241496a in g_object_newv () from /lib64/libgobject-2.0.so.0
#16 0x0000003b5241519c in g_object_new () from /lib64/libgobject-2.0.so.0
#17 0x000000000041033b in gpm_manager_init (manager=0x673440)
    at gpm-manager.c:1985
#18 0x0000003b52430915 in g_type_create_instance ()
   from /lib64/libgobject-2.0.so.0
#19 0x0000003b5241369c in ?? () from /lib64/libgobject-2.0.so.0
#20 0x0000003b5241496a in g_object_newv () from /lib64/libgobject-2.0.so.0
#21 0x0000003b5241519c in g_object_new () from /lib64/libgobject-2.0.so.0
#22 0x000000000040fa82 in gpm_manager_new () at gpm-manager.c:2104
#23 0x000000000040f5ec in main (argc=1, argv=0x7fffffffe208) at gpm-main.c:248
(gdb) fram 7
#7 0x000000000041c25a in gpm_brightness_output_get_internal (brightness=
    0x6d5180, output=81, cur=0x7fffffffd644) at gpm-brightness.c:178
178 if (XRRGetOutputProperty (brightness->priv->dpy, output, brightness->priv->backlight,
(gdb) list
173 int actual_format;
174 gboolean ret = FALSE;
175
176 g_return_val_if_fail (GPM_IS_BRIGHTNESS (brightness), FALSE);
177
178 if (XRRGetOutputProperty (brightness->priv->dpy, output, brightness->priv->backlight,
179 0, 4, False, False, None,
180 &actual_type, &actual_format,
181 &nitems, &bytes_after, ((unsigned char **)&prop)) != Success) {
182 egg_debug ("failed to get property");
(gdb) p *brightness
$1 = {parent = {g_type_instance = {g_class = 0x69ac70}, ref_count = 1, qdata =
    0x7fffec0018a0}, priv = 0x6d51a0}
(gdb) p *(brightness->priv)
$2 = {has_changed_events = 0, cache_trusted = 0, cache_percentage = 0,
  last_set_hw = 0, backlight = 0, dpy = 0x653e00, root_window = 0x669030,
  shared_value = 0, has_exte...

Read more...

Revision history for this message
In , Bug (bug-redhat-bugs) wrote :

This bug appears to have been reported against 'rawhide' during the Fedora 14 development cycle.
Changing version to '14'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Revision history for this message
dino99 (9d9) wrote :
Revision history for this message
peter s (nospam-shread) wrote :

I too am seeing crashes in gnome-power-management:

(gnome-power-manager:2355): GLib-GObject-WARNING **: /build/buildd/glib2.0-2.25.13/gobject/gsignal.c:2275: signal `proxy-status' is invalid for instance `0x1406230'
12
Gdk-ERROR **: The program 'gnome-power-manager' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAtom (invalid Atom parameter)'.
  (Details: serial 159 error_code 5 request_code 150 minor_code 15)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
aborting...

Revision history for this message
Connor Carney (cscarney) wrote :

I am seeing the same problem: gnome-power-manager crashes immediately on launch with this message:

(gnome-power-manager:3662): GLib-GObject-WARNING **: /build/buildd/glib2.0-2.25.13/gobject/gsignal.c:2275: signal `proxy-status' is invalid for instance `0x9274d30'

Gdk-ERROR **: The program 'gnome-power-manager' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAtom (invalid Atom parameter)'.
  (Details: serial 161 error_code 5 request_code 150 minor_code 15)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
aborting...

However, when I relaunch gnome-power-manager from the terminal, it asks for a password to run gnome-power-backlight-helper. If I refuse the password, gnome-power-manager does not crash (though it does still emit the proxy-status warning)

Revision history for this message
In , Will (will-redhat-bugs) wrote :

Created attachment 438783
output of 'bt full'

Reproducible here (New 13" Macbook Pro [7,1]). Backtrace goes through gpm_brightness_output_get_internal in about the same way.

Revision history for this message
In , Will (will-redhat-bugs) wrote :

Created attachment 438784
gnome-power-bugreport.sh output

Revision history for this message
In , Will (will-redhat-bugs) wrote :

Created attachment 438871
gnome-power-manager-2.31.6-backlight-is-None.patch

The problem (at least for my machine) is that some part of the system (upower? kernel? who knows) doesn't know how to deal with the backlight brightness. So gpm_backlight_init does:
  backlight->priv->brightness = gpm_brightness_new ();
which sets backlight->priv->brightness to 0 (i.e. None). So when we get to gpm_backlight_brightness_evaluate_and_set(), we end up trying to read the X property for something that's None, and X barfs at us, and gpm crashes.

Okay. So. Adding a nice simple check to gpm_brightness_output_get_internal():

        if (brightness->priv->backlight == None)
                return FALSE;

lets gpm at least start up and run without crashing. Brightness control obviously isn't working, and it doesn't think I have a lid on my laptop, but at least we're not crashing.

Revision history for this message
PeterPall (peterpall) wrote :

This bug might be a duplicate of Bug #615812 and Bug #618967; On my system gnome-power-manager no longer asks for a password.

Revision history for this message
PeterPall (peterpall) wrote :

Another duplicate of this bug might be Bug #615071.

Changed in gnome-power-manager (Ubuntu):
status: New → Incomplete
status: Incomplete → Confirmed
Revision history for this message
Jason Smith (jassmith) wrote :

This bug is caused by failed hardware recognition somewhere in uPower or the Kernel. This causes gpm to (rather awkwardly) pass a null off to xrandr, resulting in a crash. Fixing the crash will not restore functionality however.

Revision history for this message
Jason Smith (jassmith) wrote :

More precisely, the "Backlight" atom is not being set. Also GPM checks the "BACKLIGHT" atom and not the "Backlight" atom which is deprecated.

Revision history for this message
In , Fedora (fedora-redhat-bugs) wrote :

gnome-power-manager-2.31.90-3.fc14 has been submitted as an update for Fedora 14.
http://admin.fedoraproject.org/updates/gnome-power-manager-2.31.90-3.fc14

Revision history for this message
In , Matthias (matthias-redhat-bugs) wrote :

*** Bug 607008 has been marked as a duplicate of this bug. ***

Revision history for this message
In , Fedora (fedora-redhat-bugs) wrote :

gnome-power-manager-2.31.90-3.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.

Revision history for this message
In , Will (will-redhat-bugs) wrote :

*** Bug 621596 has been marked as a duplicate of this bug. ***

Revision history for this message
PeterPall (peterpall) wrote :

On my system the last update to gnome-power-manager seems to have resolved the crash. Can anyone confirm this?

Revision history for this message
Boris (boris-woerner) wrote : Re: [Bug 614248] Re: gnome-power-manager:2651: GLib-GObject-WARNING **: /build/buildd/glib2.0-2.25.11/gobject/gsignal.c:2275: signal `proxy-status' is invalid for instance `0x85b24c8'

 Yes, I confirm!

Am 25.08.2010 22:18, schrieb PeterPall:
> On my system the last update to gnome-power-manager seems to have
> resolved the crash. Can anyone confirm this?
>

Revision history for this message
John Broxholme (johnbrox) wrote : Re: [Bug 614248] Re: gnome-power-manager:2651: GLib-GObject-WARNING **: /build/buildd/glib2.0-2.25.11/gobject/gsignal.c:2275: signal `proxy-status' is invalid for instance `0x85b24c8'

It seems to be stable now (gnome-power-manager 2.31.90-0ubuntu4, Dell M65).
John

----- Original Message ----
From: PeterPall <email address hidden>
To: <email address hidden>
Sent: Wed, August 25, 2010 9:18:15 PM
Subject: [Bug 614248] Re: gnome-power-manager:2651: GLib-GObject-WARNING **:
/build/buildd/glib2.0-2.25.11/gobject/gsignal.c:2275: signal `proxy-status' is
invalid for instance `0x85b24c8'

On my system the last update to gnome-power-manager seems to have
resolved the crash. Can anyone confirm this?

--
gnome-power-manager:2651: GLib-GObject-WARNING **:
/build/buildd/glib2.0-2.25.11/gobject/gsignal.c:2275: signal `proxy-status' is
invalid for instance `0x85b24c8'
https://bugs.launchpad.net/bugs/614248
You received this bug notification because you are a direct subscriber
of the bug.

Status in “gnome-power-manager” package in Ubuntu: Confirmed
Status in “gnome-power-manager” package in Fedora: Unknown

Bug description:
Binary package hint: gnome-power-manager

got this error when maverick start:

gnome-power-manager:2651: GLib-GObject-WARNING **:
/build/buildd/glib2.0-2.25.11/gobject/gsignal.c:2275: signal `proxy-status' is
invalid for instance `0x85b24c8'

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: gnome-power-manager 2.31.1-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-14.19-generic-pae 2.6.35
Uname: Linux 2.6.35-14-generic-pae i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Fri Aug 6 09:50:40 2010
ExecutablePath: /usr/bin/gnome-power-manager
GConfNonDefault:
/apps/gnome-power-manager/lock/blank_screen=false
/apps/gnome-power-manager/lock/use_screensaver_settings=false
/apps/gnome-power-manager/notify/sleep_failed_uri=
/apps/gnome-power-manager/ui/icon_policy=charge
GnomeSessionIdleInhibited: No
GnomeSessionInhibitors: None
GnomeSessionSuspendInhibited: No
MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-14-generic-pae
root=UUID=00c5de83-479c-4ab0-9b54-9af0a727175e ro vga=791 quiet splash
ProcEnviron:
LANG=fr_FR.utf8
SHELL=/bin/bash
SourcePackage: gnome-power-manager
XsessionErrors: (polkit-gnome-authentication-agent-1:2678): GLib-CRITICAL **:
g_once_init_leave: assertion `initialization_value != 0' failed
dmi.bios.date: 10/22/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3001
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5W DH Deluxe
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr3001:bd10/22/2009:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:

dmi.product.name: P5W DH Deluxe
dmi.product.version: System Version
dmi.sys.vendor: ASUSTEK COMPUTER INC

To unsubscribe from this bug, go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/614248/+subscribe

Revision history for this message
paradoxheart (paradoxheart) wrote :

Likewise the current gnome-power-manager 2.31.90-0ubuntu4 appears to be stable on my system (HP ProBook 4310s).

Revision history for this message
PeterPall (peterpall) wrote :

Then I think it is time to close this bug and to thank everybody who was involved in fixing it; On my system another update of gnome-power-manager has passed without making the problem return.

Changed in gnome-power-manager (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
NoOp (glgxg) wrote :

Can this fix possibly be backported to Lucid? Or should I open a separate bug?

(gnome-power-manager:1719): GLib-GObject-WARNING **: /build/buildd/glib2.0-2.24.1/gobject/gsignal.c:2273: signal `proxy-status' is invalid for instance `0x88068f0'

$ apt-cache policy gnome-power-manager
gnome-power-manager:
  Installed: 2.30.0-0ubuntu1
  Candidate: 2.30.0-0ubuntu1
  Version table:
 *** 2.30.0-0ubuntu1 0
        500 http://us.archive.ubuntu.com/ubuntu/ lucid/main Packages
        100 /var/lib/dpkg/status

Revision history for this message
Chris Coulson (chrisccoulson) wrote :

It doesn't really justify a backport, it's only a warning

Revision history for this message
NoOp (glgxg) wrote : Re: [Bug 614248] Re: gnome-power-manager:2651: GLib-GObject-WARNING **: /build/buildd/glib2.0-2.25.11/gobject/gsignal.c:2275: signal `proxy-status' is invalid for instance `0x85b24c8'

On 09/21/2010 02:00 PM, Chris Coulson wrote:
> It doesn't really justify a backport, it's only a warning
>

Got it - thanks.

Bug Watch Updater (bug-watch-updater)
Changed in gnome-power-manager (Fedora):
importance: Unknown → Medium
status: Unknown → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.