On Wed, 2010-10-06 at 22:03 +0300, Pasi KÃrkkÃinen wrote: > On Tue, Oct 05, 2010 at 11:28:43AM -0700, Adam Williamson wrote: > > On Tue, 2010-10-05 at 19:20 +0100, Matthew Garrett wrote: > > > On Tue, Oct 05, 2010 at 11:18:32AM -0700, Adam Williamson wrote: > > > > > > > don't we already have default behaviours based on the lid switch, > > > > anyway? So why don't we have this problem with those? IIRC, we default > > > > to suspending the system when the lid is closed on battery power - so > > > > are we suspending people's systems at random, if those systems have > > > > lying lid switches? > > > > > > Because we only do that on lid state transitions. > > > > So we could at least cover the case where you plug in an external > > monitor, then close the lid? That would be better than nothing. I assume > > the problem case is booting with the lid closed and an external monitor > > connected. > > > > Exactly, that's the problematic case. > > When you boot F14 laptop lid closed and only external monitor > connected, GDM still appears only on the closed internal LVDS, > not on the external monitor where is should be. > So the behaviour is clearly wrong. > > This is on HP laptop with radeon graphics. > You're missing the nuance of the debate. What I mean by 'problem case' is that, according to mjg59, lid sensors don't always actually work correctly; there are many documented cases of systems whose lid switches report incorrect state, especially at boot. So we can't just say 'always enable the external monitor and disable the internal monitor if the lid switch says 'closed' and there's an external monitor connected', because the lid switch might be lying. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
