Bug 214539

Summary: Under Xen paravirt framebuffer, gnome-display-properties shows bogus refresh rate
Product: [Fedora] Fedora Reporter: Daniel Berrangé <berrange>
Component: xorg-x11-serverAssignee: Adam Jackson <ajax>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: rstrode, wtogami, xen-maint
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: F7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-02-26 23:40:12 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Screenshot of guest console
none
xdpyinfo -ext XFree86-VidModeExtension none

Description Daniel Berrangé 2006-11-08 02:35:46 UTC 
Description of problem:
When the GNOME app for adjusting display resolution is used within a Xen
paravirtualized  guest, the refresh rate is reported as -7203 HZ which is rather
odd!

Version-Release number of selected component (if applicable):
control-center-2.17.1-1.fc7

How reproducible:
Always

Steps to Reproduce:
1. Created a Xen paravirtualized guest running FC6
2. Open virt-manager
3. Connect to the guest console
4. Login to X in the guest
5. Run System -> preferences -> resolution menu
   
Actual results:
Refresh rate is -7203 HZ

Expected results:
Refresh rate is 0 HZ ? or disabled altogether ?

Additional info:
Since this is a virtual framebuffer with no real display attached, the whole
question of refresh rate is rather irrelevant. So if there is a sensible way to
detect this, I think it'd make sense to either disable the refresh rate widget,
or fix it at zero.
Comment 1 Daniel Berrangé 2006-11-08 02:38:00 UTC 
Created attachment 140620 [details]
Screenshot of guest console
Comment 2 Daniel Berrangé 2006-11-08 02:39:39 UTC 
It looks like xrandr  also reports the wrong refresh rate (see screenshot), so
quite possibly this bug component needs to be changed to belong to Xorg  instead.
Comment 3 Ray Strode [halfline] 2006-11-08 15:45:22 UTC 
Yea, looks like it.  Reassigning...
Comment 4 Daniel Berrangé 2006-11-08 16:08:45 UTC 
Created attachment 140660 [details]
xdpyinfo -ext XFree86-VidModeExtension
Comment 5 Adam Jackson 2006-11-08 16:12:35 UTC 
XFree86-VidModeExtension version 2.2 opcode: 134, base error: 130
  Monitor Information:
    Vendor: , Model: 
    Num hsync: 0, Num vsync: 0

Tee hee.  Pretty sure that's not going to work well.
Comment 6 Adam Jackson 2007-05-26 18:43:28 UTC 
Dan, can you retest this now?  In particular with Xorg 1.3.0.0-5 or later.  The
magic number fix we put in for making X start up properly in F7 xen should at
least make this fail in a new way.
Comment 7 Daniel Berrangé 2007-05-27 17:06:06 UTC 
It now reports a refresh rate of 0HZ, which sounds reasonable to me, given that
there isn't really any real refresh rate for the Xen paravirt framebuffer.
Comment 8 Chris Lalancette 2008-02-26 23:40:12 UTC 
Looks like this was resolved....closing out as CURRENTRELEASE