Bug 206487

Summary:	No new xorg.conf generated in installed openSUSE-10.2 alpha4
Product:	[openSUSE] openSUSE 10.2	Reporter:	Petr Mladek <pmladek>
Component:	Installation	Assignee:	Lukas Ocilka <locilka>
Status:	RESOLVED DUPLICATE	QA Contact:	Jiri Srain <jsrain>
Severity:	Normal
Priority:	P5 - None	CC:	ms
Version:	Alpha 4
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	y2logs xorg.conf used after installation. It was exactly the same as xorg.conf.install part of the source code - x11_finish

Description Petr Mladek 2006-09-18 15:32:18 UTC

The X server on the installed openSUSE-10.2-alpha4 was incredibly slow. It was because it was still running with the configuration that was used during installation (framebuffer).

It helped to generate new configuration via sax2.

Note that I neither changed nor even tested the X server configuration during installation. I have just accepted the X configuration.

Comment 1 Petr Mladek 2006-09-18 15:34:12 UTC

Created attachment 98960 [details]
y2logs

Comment 2 Petr Mladek 2006-09-18 15:35:20 UTC

Created attachment 98961 [details]
xorg.conf used after installation. It was exactly the same as xorg.conf.install

Comment 3 Marcus Schaefer 2006-09-21 12:14:38 UTC

The log doesn't show an error for the x11_proposal. I assume the code
for writing the configuration wasn't called. In the proposal I use

  //===================================================
  // writing configuration
  //---------------------------------------------------
  else if ( func == "Write" ) {
      boolean success = XLib::writeConfiguration();
      ret = $[ "success" : success ];
  } 

This hasn't change with 10.2 and the library call is also untouched.
So I assume the problem to be at the yast level ?

Comment 4 Thomas Fehr 2006-09-21 12:57:26 UTC

Reassigned to maintainer of yast2-installation

Comment 5 Lukas Ocilka 2006-09-21 16:04:48 UTC

Well, searching the log has revealed an obvious thing:

2006-09-18 12:02:10 <1> 10.20.1.17(3607) [wfm] clients/x11_finish.ycp:57 Pkg Builtin called: IsProvided                                                                
2006-09-18 12:02:10 <1> 10.20.1.17(3607) [wfm] Package.cc(IsProvided):434 IsProvided called                                                                           
2006-09-18 12:02:10 <1> 10.20.1.17(3607) [wfm] clients/x11_finish.ycp:60 Pkg Builtin called: IsSelected                                                               
2006-09-18 12:02:10 <1> 10.20.1.17(3607) [YCP] clients/x11_finish.ycp:63 x11_installed: <false>                                                                       
2006-09-18 12:02:10 <1> 10.20.1.17(3607) [YCP] clients/x11_finish.ycp:102 Include X11 config [instsys] to installed system: xorg.conf                                 
2006-09-18 12:02:10 <1> 10.20.1.17(3607) [YCP] clients/x11_finish.ycp:116 Include X11 config [instsys] to installed system: xorg.conf.install                         
2006-09-18 12:02:10 <1> 10.20.1.17(3607) [YCP] clients/x11_finish.ycp:130 x11_finish finished

The xorg.conf is copied from during the x11_finish.ycp, on the other hand this is the first stage of the installation. X configuration in the second stage should have changed the configuration if it was wrong.

Jiri, don't you know why this is here? (see the source code that [will be] is attached below).

Comment 6 Lukas Ocilka 2006-09-21 16:05:28 UTC

Created attachment 99357 [details]
part of the source code - x11_finish

Comment 7 Lukas Ocilka 2006-09-22 08:15:57 UTC

Ah, I see.

It's a bug in Pkg::/zypp

It's a temporary fix for the installation. However I still think that Xconfiguration (Marcus' one) should reconfigure xorg.conf. Otherwise we are going to get such bugreports from comunity in Alpha5.

*** This bug has been marked as a duplicate of bug 201121 ***