Only allows 320x240 and 640x480 when monitor off = bad VNC
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| displayconfig-gtk |
New
|
Undecided
|
Unassigned | ||
Bug Description
When the computer is booted up, displayconfig-gtk searches for available monitors and selects resolutions based on monitors and drivers.
But this is not good for home servers and others like home controllers and some media servers which usually stay with the monitor off to save on energy.
Usage like this causes X to select 640x480 resolution, which is a pain because most applications won't fit in that resolution (and GNOME won't allow the user to move the window upwards, and also vinagre won't allow one to Alt+move a window), and won't be usable unless a user "just knows" which keyboard buttons to press.
Turning on the monitor after X starts won't fix detection.
Apps that don't behave in small resolutions include displayconfig-gtk itself, which may hide OK/Cancel buttons in lower resolutions, and a lot of other Ubuntu config GUIs.
Possible solutions:
1) Make both GNOME and vinagre allow Alt+move windows (not ideal).
2) Make VNC create a virtual monitor, configurable through displayconfig-gtk itself, to set resolutions.
3) Make X/displayconfig-gtk detect a VNC connection and find the best resolution for transmission.
4) Allow displayconfig-gtk to "lock" a resolution after one that works is found.
In one view, this may cause a DoS, as one needs to at least restart X, which may stop some services.
