https://bugzilla.novell.com/show_bug.cgi?id=623250
https://bugzilla.novell.com/show_bug.cgi?id=623250#c11
--- Comment #11 from Stefan Dirsch
But IMHO the Xserver default does not make sense. I would rather have something like the patch by David Reveman in comment 2 from bug #537488
The intersection of the resolutions from both monitors will rarely be useful, at least for me and I guess for others too.
I agree that it makes sense to have such a patch for netbooks where the intersection of the resolutions ends up with 640x480. Otherwise I do *not* agree.
My laptop has 1280x800 and I use two different external monitors, one at my home with 1680x1050 and the other at the institute with 1920x1200. And for _both_ the Xserver default is useless and it makes no sense.
Hey, it's just the login screen (xdm, gdm, kdm), which shows this resolution. Imagine the external 1920x1200 monitor is turned off, but still connected (you forgot about that or even don't know that). The displaymanager will likely optimize everything for the big external screen and you can't reach any longer the gdm panel or even user/password text field. We had such bug reports in the past. No kidding! We really need a safe setup to avoid such situations.
I guess people always want the best of what the monitor has to offer, and the desktop has to be adjusted to fit, not the reverse (I use wmaker, so no krandr stuff etc).
The desktop needs to take care about your preferences by using the previous RANDR setup or if a change in monitor setup has been detected a safe setting. We do support KDE and Gnome as desktops. Use xrandr, if you prefer an unsupported WM.
In my case I simply use the external monitors and turn off the laptop screen.
Easy to manage with xrandr during login.
Suppose also a beamer presentation in some conference. If you boot your laptop with the cable to the beamer connected, you want it to display correctly at the conference room screen, using whatever native resolution the beamer uses. Then your desktop or window manager has to be clever enough to do the right thing.
Especially with beamers it makes sense to use the same resolution, in most cases this is 1024x768 anyway.
So is there no hope for me to get the resolutions correct in a flicker-free boot process? The kernel got it right already, that's what disturbs me. When xorg loads it screws up the resolutions which the kernel thought were good, and I thought the point with the kernel mode setting was to avoid this resolution changes from boot.
Good point, but not everybody is using more than one monitor with different resolutions.
So I am sorry to write all this, but as things stand now they don't look like they make sense. I fear that I will have to patch the xserver myself and use it instead, but that is painful and it will go away once I move to opensuse 11.4 etc.
Your decision of course, which we need to accept. We try the best to make most users happy, which obviously doesn't work out for everybody. That's the way it is. Also I'm not sure why you're discussing this now in this bugreport. IMHO it belongs to Bug #537488. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.