Bug 555597

Summary:	System hangs after reboot and configuration when it comes to login
Product:	[openSUSE] openSUSE 11.2	Reporter:	Lars Koraeus <lars.koraeus>
Component:	Installation	Assignee:	E-mail List <bnc-team-screening>
Status:	RESOLVED DUPLICATE	QA Contact:	Jiri Srain <jsrain>
Severity:	Critical
Priority:	P2 - High	CC:	coolo, jsrain, ro, werner
Version:	Final	Flags:	werner: SHIP_STOPPER+
Target Milestone:	---
Hardware:	x86-64
OS:	openSUSE 11.2
Whiteboard:
Found By:	Beta-Customer	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	A ls list from one working and two other now working installations

Description Lars Koraeus 2009-11-15 04:04:24 UTC

Created attachment 327572 [details]
A ls list from one working and two other now working installations

User-Agent:       Opera/9.80 (X11; Linux i686; U; en-GB) Presto/2.2.15
Version/10.00

A follow up for the 555555 bug, which I not can find and follow up.
I should also perhaps be classified as a YaST2 bug during the install.

/etc/group
/etc/group-YaST2save
/etc/passwd
/etc/passwd.YaST2save
/etc/shadow
/etc/shadow.Yast2save
are all empty
but the respective .old exist and looks OK.
All the errors during the init is related to unknown user and or group
For a KDE install it hangs before KDM comes up with a window telling that the
installation is corrupted.
For other the XDM comes up and I can see in the log window all the user related
errors.


Reproducible: Always

Steps to Reproduce:
1.A normal installation
2.Reboot
3.Auto configuration
4.Hangs. Nothing works. No mouse, no keyboard
Actual Results:  
Hangs. Only power of or hardware reset works

Expected Results:  
KDM/GDM/XDM for log in

Not more that this is the first time since SuSE 5.0 we not have been able to
install a SuSE distribution. Now we will stay on 11.1 with KDE 3.5.
Not good as we now have been able to migrate to Linux in the whole company

Comment 1 Shuang Qiu 2009-11-20 07:30:13 UTC

Lars,could you answer Werner's question on bnc555555 first.
Thanks.

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