Sebastien, I disagree that this is an xorg issue, since xorg can handle the scenario fine.
When autodetection works, it reports the valid modes which are detected. When autodetection doesn't work, it's got no choice but to await a manual specification of a valid mode since it has no way of knowing what's valid. Assuming that someone manually specifies the horiz, vertical and refreshrate in the xorg.conf file, then both xorg.conf and xrandr can then handle the scenario fine. It's for this reason that it's important that this common situation (where autodetection doesn't work for some reason) is handled by the gui tool. The gui tool should assist in the definition of the manually defined modeline which only the user knows (from reading their monitor manual). It should not require them to edit xorg.conf to handle this situation. Currently this is only possible through spending half a day finding out how. With a change to the graphical tool, there could be an advanced option to specify horiz, vertical and refreshrate, and a simple change to the xorg.conf file can take place, just like the tool does with the Virtual resolution when you move the positions of your monitors. -- Unable to force screen resolution with vtswitch/splitter https://bugs.launchpad.net/bugs/260436 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
