*** This bug is a duplicate of bug 92599 ***
https://bugs.launchpad.net/bugs/92599
Reporter sent the following in a private mail:
> You missunderstood me. When I wrote that I had tried it and the problem was
> away. That's why I proposed to close the bug.
Sorry for the misunderstanding Frank
Leaving in needsinfo pending Frank's reply.
--
VertRefresh is not read in 'xorg.conf
https://bugs.launchpad.net/bugs/42322
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://l
Frank:
Bug #104105 affects people who are using single head too. Try adding
Option "DynamicTwinView" "false"
to the Device section of /etc/X11/xorg.conf and see whether the problem goes
away...
--
VertRefresh is not read in 'xorg.conf
https://bugs.launchpad.net/bugs/42322
You received this bug n
I'm now using Feisty and I think the bug is the same as Bug #104105. The
only difference is that I use no twin screen. So I think you can close
this bug!
--
VertRefresh is not read in 'xorg.conf
https://bugs.launchpad.net/bugs/42322
You received this bug notification because you are a member of U
Frank:
VertRefresh should always be a range not a single value. It doesn't control the
final refresh rate in the way that you are imagining. Can you set it to range
and then check to use
xrandr -q
to see what refresh ranges are available? Also be warned because Bug #92599 can
lead to distorted r
