I think I might be able to shed some more light on this issue. I have only noticed this problem in the last few days. First on a machine running 8.04, then on a machine running 7.04 (I'm guessing because some part of X.org in 7.04 has recently been updated via Update Manager).
See also: http://ubuntuforums.org/archive/index.php/t-437194.html http://ubuntuforums.org/showthread.php?t=846128 https://help.ubuntu.com/community/XORGHardy The first two describe a similar problem. The third may describe part of the cause. Earlier versions of X.org would create the /etc/xorg.conf file during installation. This is fine until you change some of your video hardware. Later versions of X.org now use 'dynamic recognition' of video hardware during boot. Of course, if the machine is connected via a KVM switch and does not have 'sight' of the monitor during boot, X.org will default to 'safe' settings. My assumption is that, prior to the very latest version, X.org would fall back on the xorg.conf file if it couldn't see the monitor. Perhaps the X.org guys decided that, not 'seeing' the monitor might mean that an old monitor had been plugged in. In which case, using the settings in xorg.conf could damage the monitor. This, of course, doesn't help those of us simply using a KVM switch. Short term solution (tested and working for me): Give the booting machine focus via the KVM until it's up. -- screen size wrong while using kvm switch https://bugs.launchpad.net/bugs/238263 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
