https://bugzilla.novell.com/show_bug.cgi?id=402581
User ms@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=402581#c12
Marcus Schaefer changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |NEW
Info Provider|ms@novell.com |
--- Comment #12 from Marcus Schaefer 2008-06-24 10:44:44 MDT ---
why do we post comments privately now ??
* the not detected monitor has nothing to do with the PreferredMode
setup. The monitor information is obtained from hwinfo (DDC probing)
if there is no data the default framebuffer console settings are used
(most often 800x600)
* I'm sorry for not informing you earlier about this PreferredMode
change but the x11 setup during installation is a unique code which
uses libsax but has its own workflow so changes in the sax2 GUI
are not directly related to yast2. As long as I maintained the code
I've tested the sax2 GUI and the yast2 x11 setup separately and this
bug turns out that nobody from Alpha to RC has changed the resolution
during the installation process which would have disclose this bug
in the sax2 GUI I adapt the preferred mode to the first resolution
selected when the configuration is about to be saved:
if (saxCard.getCardDriver() != "fbdev") {
saxDesktop.setColorDepth ( display->getColorDepth() );
saxDesktop.setPreferredMode (
display->getResolution().at(0)
);
}
you can do exactly the same thing in yast2-x11 in the perl code with
the libsax perl binding when saving the configuration
--
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.