I filed a new one: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/654660
Not to be a pain in the rear but I didn't see an exact parallel to what I've experienced, and I thought it couldn't hurt to gather info. I'm just trying to show that this effects a lot of different hardware and I do see this as a true "show-stopper"! Are we going to release Maverick final this way? If others are unable to even boot the Live image, as I was, how many will decide that Ubuntu just doesn't work for them? While repeating what I said there I was able to finally boot the Live CD this way: " pressing F6, then ESC, then typing "text" (w/o the quotes), and then typing: gconftool-2 --type bool -s "/apps/gnome_settings_daemon/xrandr/turn_on_external_monitors_at_startup" false Then just typing "startx" (again w/o the quotes) I got a desktop with the expected modes". I just don't see how we can release like this :^( IMHO Maverick is otherwise an exemplary release. I just want to know how we're going to handle this for the final release. -- Forces low refresh rate on CRT monitor https://bugs.launchpad.net/bugs/640807 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
