Hi Kevin,
Interesting - I've just tried this in an Oneiric vm and it's not done a
straight truncation - it seems to have done a bit of a round though, which
makes me wonder if your original bug is present or not;
dg@kdedev:~$ xrandr --newmode "640x480_75.00" 30.75 640 664 728 816 480 483 487
504 -hsync +vsync
xrandr: Failed to get size of gamma for output default
dg@kdedev:~$ xrandr
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 640 x 480, current 1024 x 768, maximum 1024 x 768
default connected 1024x768+0+0 0mm x 0mm
1024x768 60.0*
800x600 60.0 56.0
640x480 60.0
640x480_75.00 (0x11b) 30.8MHz
h: width 640 start 664 end 728 total 816 skew 0 clock 37.7KHz
v: height 480 start 483 end 487 total 504 clock 74.8Hz
so, is that bug present or not?
Dave
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to x11-xserver-utils in Ubuntu.
https://bugs.launchpad.net/bugs/835817
Title:
xrandr client truncates pixel clock freq.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/x11-xserver-utils/+bug/835817/+subscriptions
_______________________________________________
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : [email protected]
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help : https://help.launchpad.net/ListHelp
