Ok. There seem to now be different issues here: 1) Hans-Gerd reports that newer upstream kernels fail to drive the external monitor correctly. It looks like the problem there is that when X starts it chooses to clone the screens, looks for the best mode common to the laptop display and the external display, and chooses a mode that the external display doesn't like.
In this case it'd be good to have the EDID information for the external display - is the Intel driver picking a mode not in the EDID, or is the monitor's EDID incorrect when it says that it supports the 1024x768 modeline. 2) Torsten reports that when resuming after the docking-station suspend/undock/resume/suspend/dock dance the display sometimes doesn't come back on, fixable by switching VTs. Furthermore he reports that in at least one case the displays were not cloned and the LVDS was primary - resulting in the unlock dialog being displayed only on the (closed) laptop monitor. I suspect *this* might be a race between gnome-settings-daemon and X - they have different behaviours on monitor hotplug. G-S-D will add the new monitor as a separate, spanned display, X will clone the displays. Disabling the gnome-settings-daemon xrandr plugin should disable g-s-d's monitor hotplug behaviour, allowing this to be tested. I've now got access to a docking station, so I'll test this out locally with my x200s. -- Display error when returning from sleep after docking https://bugs.launchpad.net/bugs/531069 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in ubuntu. _______________________________________________ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp