Bug 105847

Summary:	Hang Condition Behaviour in SuSEConfig.tetex during Installation
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	Chad Collins <collinscdj>
Component:	Installation	Assignee:	Dr. Werner Fink <werner>
Status:	RESOLVED DUPLICATE	QA Contact:	Klaus Kämpf <kkaempf>
Severity:	Normal
Priority:	P5 - None	Keywords:	beta_customer, Install
Version:	Beta 1
Target Milestone:	---
Hardware:	x86-64
OS:	SUSE Other
Whiteboard:
Found By:	Beta-Customer	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	YAST2 Logs

Description Chad Collins 2005-08-19 13:55:42 UTC

During the SuSEConfig.tetex phase of an OpenSUSE 10.0 Beta1 installation,
SuSEConfig appears to hang.

More information can be displayed by powering the system off, then bac on, and
watching boot messages that are displayed (by pressing F2).

SuSEConfig attempts to run one more time during this boot process, since it did
not complete during the installation.  When SuSEConfig.tetex is executed, it
prompts the user for "OldPassword:".  Since the SuSEConfig portion of the
installation does not allow for user input at this stage, the user may see this
as a hang during installation.

To circumvent this problem:

1.  Power off the system when the "hang" occurs duing GUI mode phase of
installation, at the point SuSECOnfig.tetex "failure".
2.  Power system back on.
3.  When presented with the "OldPassword:" prompt. press then ENTER key.
4.  Repeat step #3 2 more times (generating 3 unsuccessfull password attempts.)


Miscellanous Information:

- User is doing a complete installation, selecting ALL packages.

Comment 1 Chad Collins 2005-08-19 13:57:45 UTC

Created attachment 46695 [details]
YAST2 Logs

Comment 2 Stefan Hundhammer 2005-08-19 14:35:28 UTC

Package problem -> tetex package maintainer. 
 
SuSEconfig should not require any user input.

Comment 3 Dr. Werner Fink 2005-08-22 09:27:20 UTC

This is a YAST bug due to the fact that YAST modifies /etc/shadow in
a wrong way.  And this bug is fixed in the Beta2.

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