Ok, the 1366 mode is causing problems no matter what external monitor is attached. I think it does it more reliably fails with the larger external screen.
Switching the last monitors.xml to 1360 seems to allow it to work. ** Summary changed: - corrupt monitors.xml makes gnome unusable + monitors.xml settings from the display applet can make gnome unusable on next login -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1066048 Title: monitors.xml settings from the display applet can make gnome unusable on next login Status in “gnome-settings-daemon” package in Ubuntu: New Bug description: I was trying to switch the "primary" monitor for Ubuntu and after some back-n-forth, both monitors went blank. Switched to a text console, restarted gdm and after logging in the monitors both went blank. Upgraded everything and got the same problem. Finally managed to get firefox up with a minimal .xinitrc and found https://wiki.ubuntu.com/X/Config/Resolution which told me to look at ~/.config/monitors.xml. I edited the file in emacs (from which I have the original, buggy monitors.xml~ file) and managed to get a working session. Looking at the diffs, I'm not sure *why* the buggy setup blanked both monitors and I haven't logged in again with what I think is the bad monitors.xml to confirm it. I'll submit this bug and my monitors.xml + diff and then try to verify that the monitors.xml that I think causes the problems actually does. BBIAS ;) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1066048/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
