Bug 545481 - gnome-power-manager-and-blanking-removal-of-bodges
Summary: gnome-power-manager-and-blanking-removal-of-bodges
Keywords:
Status: CLOSED DUPLICATE of bug 527964
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-server
Version: 12
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-12-08 17:11 UTC by udo
Modified: 2018-04-11 13:11 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-12-08 23:41:58 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description udo 2009-12-08 17:11:26 UTC
Description of problem:
http://blogs.gnome.org/hughsie/2009/08/17/gnome-power-manager-and-blanking-removal-of-bodges/

Version-Release number of selected component (if applicable):


How reproducible:
Upgrade to Fedora 12

Steps to Reproduce:
1. upgrade to Fedora 12
2. wait
3. see an unknown icon appear in the gnome session top right hand with a tooltip referencing to http://blogs.gnome.org/hughsie/2009/08/17/gnome-power-manager-and-blanking-removal-of-bodges/
  
Actual results:
tooltip/icon referencing http://blogs.gnome.org/hughsie/2009/08/17/gnome-power-manager-and-blanking-removal-of-bodges/

Expected results:
No icon, bugs fixed, etc.

Additional info:
Current Fedora 12.

Comment 1 udo 2009-12-08 17:24:14 UTC
"So, I’ll remove the kludges from gnome-power-manager git master today and will depend on a runtime version of the xserver that has these patches applied. If you are trying to run gnome-power-manager with a broken version of X, gnome-power-manager will warn you in the notification area. 

==> Distributors will just need to patch xserver with my previous patch and the current one to have all the issues resolved with git master."

Comment 2 Matěj Cepl 2009-12-08 23:41:58 UTC

*** This bug has been marked as a duplicate of bug 527964 ***


Note You need to log in before you can comment on or make changes to this bug.