X disables screen until logout if resolution is exceeded
Posted: 1. Nov 2011, 03:53
Today I tried hooking up my netbook to an external LCD monitor...
The displays were treated as one, and kept in sync. This I assume is normal (I don't think a netbook's video card would support a dual head configuration). And when I set the resolution on the external to something higher than the netbook's screen supported, the netbook's screen was blanked out. This, again, I assume to be normal (because anything else would be very unfriendly).
But when I set the resolution back down to something the netbook's screen could handle, the screen did not turn back on. It did turn back on after I logged out and logged back in; but within the Xfce session, there was apparently nothing I could do to get the netbook screen up again.
I figured at first this was due to KMS polling being turned off... But no, it wasn't. Same with X input hotplugging and X autoconfiguration. I'm pretty sure this behavior is buggy, seeing as it has the potential to lock the user out, but I'm wondering if anyone's seen this before and if there are any workarounds...
The displays were treated as one, and kept in sync. This I assume is normal (I don't think a netbook's video card would support a dual head configuration). And when I set the resolution on the external to something higher than the netbook's screen supported, the netbook's screen was blanked out. This, again, I assume to be normal (because anything else would be very unfriendly).
But when I set the resolution back down to something the netbook's screen could handle, the screen did not turn back on. It did turn back on after I logged out and logged back in; but within the Xfce session, there was apparently nothing I could do to get the netbook screen up again.
I figured at first this was due to KMS polling being turned off... But no, it wasn't. Same with X input hotplugging and X autoconfiguration. I'm pretty sure this behavior is buggy, seeing as it has the potential to lock the user out, but I'm wondering if anyone's seen this before and if there are any workarounds...