Bug 1379391 - Battery status isn't displayed correctly in F24
Summary: Battery status isn't displayed correctly in F24
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-power-manager
Version: 24
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Richard Hughes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-26 14:48 UTC by Jim Scarborough
Modified: 2016-10-18 19:54 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-18 19:54:57 UTC
Type: Bug

Attachments (Terms of Use)
screenshot (4.91 KB, image/png)
2016-09-26 14:48 UTC, Jim Scarborough 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Jim Scarborough 2016-09-26 14:48:27 UTC 
Created attachment 1204852 [details]
screenshot

Description of problem:
The battery status in the corner of the screen doesn't update regularly.

Version-Release number of selected component (if applicable): 3.20.0-1.fc24


Steps to Reproduce:
1. Upgrade from Fedora 23 to 24
2. Reboot

Actual results:
gnome-power-manager is not installed.  An install wants to remove kernel and several other kernel* packages.

Display shows a constant battery status - unchanging when A/C power is available or not, and after time charging or discharging.

See screenshot of the display when the battery is full or very nearly full and plugged in.

Expected results:
Display changes as battery status changes, indicating charging and discharging.
Comment 1 Jim Scarborough 2016-09-27 14:02:01 UTC 
This problem may be lower level than Gnome.  I say that because the computer suspended while inactive and plugged in according to the timeout for suspending when on battery, though I had it set to not suspend when plugged in.
Comment 2 Jim Scarborough 2016-10-18 19:54:57 UTC 
Reboot and/or dnf update seems to have fixed it.
Note You need to log in before you can comment on or make changes to this bug.