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...
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' power-manager' received an X Window System error.
12
Gdk-ERROR **: The program 'gnome-
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...