Bug 116326

Summary:	Analysing system fails
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	James Ots <novellbugzilla>
Component:	Installation	Assignee:	Marcus Schaefer <ms>
Status:	RESOLVED WORKSFORME	QA Contact:	Klaus Kämpf <kkaempf>
Severity:	Normal
Priority:	P5 - None	CC:	sndirsch
Version:	RC 1
Target Milestone:	---
Hardware:	Other
OS:	All
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	Yast logs Output from 'hwinfo --gfxcard' Sax log after 'sax2 -r'

Description James Ots 2005-09-10 12:46:58 UTC

When I got to the end of the install the system was analysed, and then the 
window which should have displayed the settings just hung at 'Analysing your 
system' - so I clicked Next and things seemed to carry on ok, but now I can't 
get a graphical system up. I ran ncurses yast and tried to set up the graphics 
card, but that failed too. There'a a lot of errors about undefined symbols 
coming up too. 
 
I checked the media before installing. There was one package which took two 
attempts to install - cups-drivers-stp, but it worked when I retried.

Comment 1 James Ots 2005-09-10 12:48:06 UTC

Created attachment 49512 [details]
Yast logs

Comment 2 Lukas Ocilka 2005-09-12 07:13:40 UTC

2005-09-10 13:29:51 <3> linux(5387) [Interpreter] clients/x11_proposal.ycp:122
Argument (resolution) to +(...) evaluates to nil

2005-09-10 13:29:51 <3> linux(5387) [Interpreter] clients/x11_proposal.ycp:122
Argument ((((((((proposal + LI) + XMessages::monitor) + "<a
href=\"sax-monitor\">") + monitorName) + "</a>") + " - (<a
href=\"sax-resolution\">") + resolution)) to +(...) evaluates to nil

.... more of failures ...

2005-09-10 13:29:51 <3> linux(5387) [Interpreter] clients/x11_proposal.ycp:150
Argument (proposal) to +(...) evaluates to nil

Comment 3 Lukas Ocilka 2005-09-12 07:14:50 UTC

Thanks for logs. Could you, please, also attach output of this command?

`hwinfo --gfxcard`

Thanks

Comment 4 Marcus Schaefer 2005-09-12 08:25:29 UTC

I need the sax logs to check what happens. 
 
Please call  
 
 sax2 -r  
 
from runlevel 3 as user root and send me the log file 
 
  /var/log/SaX.log 
 
Thanks

Comment 5 James Ots 2005-09-12 19:26:28 UTC

Created attachment 49674 [details]
Output from 'hwinfo --gfxcard'

Comment 6 James Ots 2005-09-12 19:27:35 UTC

Created attachment 49675 [details]
Sax log after 'sax2 -r'

Comment 7 Marcus Schaefer 2005-09-13 06:48:48 UTC

Hmm, the log of SaX doesn't show any error, I assume the call to 
sax2 -r was successfull ?  
 
Stefan if you have time could you do a test installation with a Matrox G400 
card. I'm on English training today... would be cool. 
 
Thanks

Comment 8 James Ots 2005-09-13 08:18:06 UTC

Yes, sax2 -r was successful, and now I can get into KDE fine.

Comment 9 Marcus Schaefer 2005-09-14 08:00:40 UTC

I made a installation with a Matrox G400 card (SuSE Linux 10.0 RC2) 
everything is working as expected.