abrt version: 1.1.5 architecture: x86_64 Attached file: backtrace cmdline: gnome-power-manager component: gnome-power-manager executable: /usr/bin/gnome-power-manager global_uuid: ef820b9f311381db17f790e5d34277b79a715517 kernel: 2.6.34-45.fc14.x86_64 package: gnome-power-manager-2.31.3-1.fc14 rating: 3 reason: Process /usr/bin/gnome-power-manager was killed by signal 11 (SIGSEGV) release: Fedora release 14 (Rawhide) time: 1277247171 uid: 500 comment ----- This message comes up when running gnome-power-manager from a CLI: [gene@Mobile-PC ~]$ gnome-power-manager Gtk-Message: Failed to load module "pk-gtk-module": libpk-gtk-module.so: cannot open shared object file: No such file or directory Segmentation fault (core dumped) How to reproduce ----- 1. It occurs at every login. 2. 3.
Created attachment 426104 [details] File: backtrace
$ gnome-power-manager Gtk-Message: Failed to load module "pk-gtk-module": libpk-gtk-module.so: cannot open shared object file: No such file or directory (gnome-power-manager:2061): GLib-GObject-WARNING **: gsignal.c:2276: signal `proxy-status' is invalid for instance `0x8b87518' 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 168 error_code 5 request_code 149 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.) $ uname -r 2.6.34-43.fc14.i686
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
*** This bug has been marked as a duplicate of bug 608402 ***