** Description changed: In Ubuntu 10.04 when adding new modes using "--newmode" the pixel clock is truncated, for example 119.9 will become 119. This is due to check_strtod in xrandr.c returning an int when it should be returning in double. This bug is already fixed upstream. Please consider adding the following patch to either -updates or -backports, which every is more appropriate. Thank You. + + [IMPACT] Unable to get the required pixel clock and hence potential for + difficulty in getting some video systems to operate correctly. Probably + fairly rare. + + [Development Fix] It's working in current development versions, but + hasn't been explicitly tracked. + + [Stable Fix] Original reporter reports that the patch at + http://cgit.freedesktop.org/xorg/app/xrandr/commit/?id=27f86db064a5ea60b942fd3d3ddeb462d980df9b + is the required fix. + + [Test Case] From comment #3:"It's easy to reproduce, for example: + + xrandr --newmode "640x480_75.00" 30.75 640 664 728 816 480 483 487 504 -hsync +vsync" + xrandr + + The output will be: + ... + 640x480_75.00 (0x115) 30.0MHz + h: width 640 start 664 end 728 total 816 skew 0 clock 36.8KHz + v: height 480 start 483 end 487 total 504 clock 72.9Hz + + Notice how the pixel clock freq. was truncated to 30.00 and the refresh + rate is 72.9 instead of 75.0 like it should be." + + [Regression Potential] Apparently small; although one has to worry about + changing something like xrandr.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
