Bug 118383 - X11 settings are not correct if you generate a reference file
Summary: X11 settings are not correct if you generate a reference file
Status: RESOLVED FIXED
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: AutoYaST (show other bugs)
Version: RC 4
Hardware: i386 SUSE Other
: P5 - None : Normal
Target Milestone: ---
Assignee: Marcus Schaefer
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 97395
  Show dependency tree / graph
 
Reported: 2005-09-22 12:42 UTC by Efthimios Toulas
Modified: 2005-09-29 13:26 UTC (History)
1 user (show)

See Also:
Found By: Development
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Efthimios Toulas 2005-09-22 12:42:54 UTC 
The X11 section of the reference file looks like the following.
The value for <display_manager> and <window_manager> are interchanged.

  <x11>
	  <color_depth>24</color_depth>
	  <display_manager>kde</display_manager>
	  <enable_3d config:type="boolean">false</enable_3d>
	  <monitor>
		  <display>
			  <max_hsync config:type="integer">65</max_hsync>
			  <max_vsync config:type="integer">120</max_vsync>
			  <min_hsync config:type="integer">30</min_hsync>
			  <min_vsync config:type="integer">50</min_vsync>
		  </display>
		  <monitor_device>102020</monitor_device>
		  <monitor_vendor>BELINEA</monitor_vendor>
	  </monitor>
	  <resolution>1024x768</resolution>
	  <window_manager>kdm</window_manager>
  </x11>
Comment 1 Uwe Gansert 2005-09-23 08:57:52 UTC 
Markus, this seems to be a bug in AutoinstX11.ycp in the Read() function:

        x11["window_manager"] = (string) eval (SCR::Read(
                .sysconfig.displaymanager.DISPLAYMANAGER
        ));
        x11["display_manager"] = (string) eval (SCR::Read(
                .sysconfig.windowmanager.DEFAULT_WM
        ));

I would have fixed this on my own but it looks like the resolution is broken too
and I'm not sure how to fix that in the best way. It should be "1024x768 (SVGA)"
or something like that.
If I remember correctly, you changed those values with the new libsax.
Comment 2 Marcus Schaefer 2005-09-27 14:00:40 UTC 
1) yes window_manager and display_manager seems to be exchanged. 
   fixed  
  
2) yes libsax is using the entries from:  
  
 cat /usr/share/sax/api/data/MonitorResolution   
  
640x480=640x480 (VGA)  
768x576=768x576 (PAL)  
800x600=800x600 (SVGA)  
1024x768=1024x768 (XGA)  
1152x864=1152x864 (XGA)  
1280x768=1280x768 (WXGA)  
1280x800=1280x800 (WXGA)  
1280x960=1280x960 (QVGA)  
1280x1024=1280x1024 (SXGA)  
1440x900=1440x900 (WXGA)  
1400x1050=1400x1050 (SXGA+)  
1600x1000=1600x1000  
1600x1024=1600x1024 (WSXGA)  
1600x1200=1600x1200 (UXGA)  
1680x1050=1680x1050 (WSXGA+)  
1900x1200=1900x1200  
1920x1200=1920x1200 (WUXGA)   
2048x1536=2048x1536 (QXGA)   
2560x2048=2560x2048 (QSXGA)  
2800x2100=2800x2100 (QSXGA+)  
3200x2400=3200x2400 (QUXGA)  
  
If you want to set a resolution you have to use that strings otherwise  
libsax will not accept the resolution
Comment 3 Efthimios Toulas 2005-09-28 13:05:25 UTC 
Marcus fixed the issue with the window_manager and display_manager.

Uwe, can you adjust the monitor resolution settings please.
Comment 4 Uwe Gansert 2005-09-29 08:31:21 UTC 
Markus, in Read() of AutoinstX11.ycp you call:
x11["resolution"]  = (string) XLib::getActiveResolution();

that returns a wrong String (just "1024x768" for example) and that can't be used
in the profile.
That is the bug that I mentioned in comment #1 and where I'm not sure what would
be the best way to fix it.
Comment 5 Marcus Schaefer 2005-09-29 13:26:26 UTC 
yes this is correct, a very simple fix is to use  
  
   XLib::getActiveResolutionString() 
 
fixed