[Ubuntu-x-swat] [Bug 835817] Re: xrandr client truncates pixel clock freq.

2011-08-29 Thread Kevin Atkinson
Like I said its fixed upstream, so naturally it should work correctly with Oneiric. The refresh rate it correct at 74.8 (really 74.77). This modeline should give you exactly 75: 640x480x75.00 30.906000 640 664 728 816 480 484 488 505 -HSync +VSync when the bug is not present. This bug

[Ubuntu-x-swat] [Bug 835817] Re: xrandr client truncates pixel clock freq.

2011-08-28 Thread Kevin Atkinson
I not sure a bug report was ever filed on this specific issue, but here is the reference to the git commit which fixes this bug: http://cgit.freedesktop.org/xorg/app/xrandr/commit/?id=27f86db064a5ea60b942fd3d3ddeb462d980df9b It's easy to reproduce, for example: xrandr --newmode 640x480_75.00

[Ubuntu-x-swat] [Bug 835817] Re: xrandr client truncates pixel clock freq.

2011-08-28 Thread Kevin Atkinson
Sorry the bug system wrapped the output badly, the last part of the command should be -hsync +vsync and the extra quote character should't be there. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to x11-xserver-utils in Ubuntu.

[Ubuntu-x-swat] [Bug 835817] [NEW] xrandr client truncates pixel clock freq.

2011-08-27 Thread Kevin Atkinson
Public bug reported: 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

[Ubuntu-x-swat] [Bug 835817] Re: xrandr client truncates pixel clock freq.

2011-08-27 Thread Kevin Atkinson
** Attachment added: Patch to fix truncating of pixel clock freq. https://bugs.launchpad.net/bugs/835817/+attachment/2324810/+files/xrandr.patch -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to x11-xserver-utils in Ubuntu.