> I'm just trying to show that this effects a lot of different hardware
and I do see this as a true "show-stopper"!
How do you know that? How much hardware did you try? How do you know if
doesn't do better job on some configurations and breaks some others?
What solution do you suggest? Changing the key value just workaround the
issue on some setups to trade with other broken ones. The safe way would
probably to go back to what lucid was doing though
** Changed in: gnome-settings-daemon (Ubuntu)
Assignee: Sebastien Bacher (seb128) => (unassigned)
** Also affects: gnome-settings-daemon (Ubuntu Maverick)
Importance: Undecided
Status: Confirmed
--
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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
