lucid has seen the end of its life and is no longer receiving any
updates. Marking the lucid task for this ticket as Won't Fix.
** Changed in: x11-xserver-utils (Ubuntu Lucid)
Status: New = Won't Fix
--
You received this bug notification because you are a member of Ubuntu-X,
which is
** Also affects: x11-xserver-utils (Ubuntu Lucid)
Importance: Undecided
Status: New
--
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
** Tags added: lucid
--
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. [Lucid]
To manage notifications about this bug go to:
** Summary changed:
- xrandr client truncates pixel clock freq.
+ xrandr client truncates pixel clock freq. [Lucid]
--
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:
Medium-Moderate impact on core app
** Changed in: x11-xserver-utils (Ubuntu)
Importance: Undecided = Medium
** Changed in: x11-xserver-utils (Ubuntu)
Status: New = Triaged
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
** Tags added: patch-accepted-upstream
--
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
** 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
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
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
Hi Kevin,
Do you have a reference to the upstream bug that this patch came from?
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
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
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.
** 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.
13 matches
Mail list logo
