Bug 539331

Summary: IDELCOUNTER/DPMS bug in vnc server
Product: [Fedora] Fedora Reporter: Jonathan Underwood <jonathan.underwood>
Component: tigervncAssignee: Adam Tkac <atkac>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: atkac, ovasik
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: tigervnc-1.0.0-3.fc12 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-11-30 11:17:14 EST Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Jonathan Underwood 2009-11-19 16:39:17 EST
Description of problem:
When running a gnome session in a remote vnc session, gnome-power-manager puts an icon in the toolbar with a hover over message which reads:

"Session active, not inhibited, screen idle. If you can see this text, your display server is broken and you should notify your distributor. Please see http://blogs.gnome.org/hughsie/2009/08/17/gnome-power-manager-and-blanking-removal-of-bodges/ for more information"

If you go to: 


You can read about the problem that was fixed in the xserver, but presumably still exists in the tigervnc server?

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

How reproducible:

Steps to Reproduce:
1. Start a gnome session inside vnc
Actual results:

Expected results:

Additional info:
Comment 1 Jonathan Underwood 2009-11-19 16:48:26 EST
This may be a bug in gnome-power-manager really, since power management inside of a vnc session  is presumably fairly meaningless. Not sure.
Comment 2 Jonathan Underwood 2009-11-19 18:22:21 EST
Interestingly, I just pulled across the tigervnc-server-1.0.0-3.fc12.x86_64 package from updates testing and restarted the session, and let the screen saver kick in, and now I don't see the icon from gnome-power-manager, so it seems fixed in this package, probably by the change in 1.0.0-2:

- update underlying X source to 1.6.4-0.3.fc11

Will leave this open for now until I'm sure it's fixed.
Comment 3 Adam Tkac 2009-11-30 11:17:14 EST
If it was a bug in the main X.Org source then this issue should be fixed. Closing.