Bug 1331049

Summary: [abrt] gnome-power-manager: gpm_stats_startup_cb(): gnome-power-statistics killed by SIGSEGV
Product: [Fedora] Fedora Reporter: moshe
Component: gnome-power-managerAssignee: Richard Hughes <rhughes>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: rhughes
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/e1a1bf76df926f80ccaa34b25a135ab0cb8cca79
Whiteboard: abrt_hash:27472dedf32f821c99b67622e63689b0bdd4d32e;VARIANT_ID=workstation;
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 18:48:19 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: mountinfo
none
File: namespaces
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description moshe 2016-04-27 14:33:25 UTC 
Description of problem:
Some sort of problem with the underlying upower service.  The gnome battery icon would stay stuck in an old state and not update when i plugged or unplugged my laptop.  gnome-power-statistics was crashing on startup.  Starting  gnome-power-statistics from a terminal resulted in:
$ gnome-power-statistics 
Failed to register: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)

So I guess that something was wrong with the underlying power control service.

Doing

$ systemctl restart upower

seems to have fixed things.  The battery icon is updating correctly now and gnome-power-statistics runs fine.

Version-Release number of selected component:
gnome-power-manager-3.16.1-2.fc22

Additional info:
reporter:       libreport-2.6.4
backtrace_rating: 4
cmdline:        gnome-power-statistics
crash_function: gpm_stats_startup_cb
executable:     /usr/bin/gnome-power-statistics
global_pid:     8551
kernel:         4.4.6-201.fc22.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (1 frames)
 #0 gpm_stats_startup_cb at gpm-statistics.c:2034
Comment 1 moshe 2016-04-27 14:33:29 UTC 
Created attachment 1151410 [details]
File: backtrace
Comment 2 moshe 2016-04-27 14:33:29 UTC 
Created attachment 1151411 [details]
File: cgroup
Comment 3 moshe 2016-04-27 14:33:30 UTC 
Created attachment 1151412 [details]
File: core_backtrace
Comment 4 moshe 2016-04-27 14:33:32 UTC 
Created attachment 1151413 [details]
File: dso_list
Comment 5 moshe 2016-04-27 14:33:32 UTC 
Created attachment 1151414 [details]
File: environ
Comment 6 moshe 2016-04-27 14:33:34 UTC 
Created attachment 1151415 [details]
File: limits
Comment 7 moshe 2016-04-27 14:33:35 UTC 
Created attachment 1151416 [details]
File: maps
Comment 8 moshe 2016-04-27 14:33:36 UTC 
Created attachment 1151417 [details]
File: mountinfo
Comment 9 moshe 2016-04-27 14:33:37 UTC 
Created attachment 1151418 [details]
File: namespaces
Comment 10 moshe 2016-04-27 14:33:38 UTC 
Created attachment 1151419 [details]
File: open_fds
Comment 11 moshe 2016-04-27 14:33:39 UTC 
Created attachment 1151420 [details]
File: proc_pid_status
Comment 12 moshe 2016-04-27 14:33:39 UTC 
Created attachment 1151421 [details]
File: var_log_messages
Comment 13 Fedora End Of Life 2016-07-19 18:48:19 UTC 
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.