Bug 103873 - Running SuSEconfig.tetex at the end of installation never completes
Summary: Running SuSEconfig.tetex at the end of installation never completes
Status: RESOLVED FIXED
: 104937 105847 112772 113692 (view as bug list)
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Basesystem (show other bugs)
Version: Beta 1
Hardware: All SUSE Other
: P5 - None : Blocker
Target Milestone: ---
Assignee: Jiří Suchomel
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-10 16:20 UTC by Bryan Perry
Modified: 2005-08-31 14:18 UTC (History)
5 users (show)

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


Attachments
Y2Logs (236.71 KB, application/octet-stream)
2005-08-11 14:13 UTC, Bryan Perry
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Bryan Perry 2005-08-10 16:20:42 UTC
When doing a full install on various hardware platforms of SuSE Linux 10.0 Beta
1, the installation get to the very end of all 5 cds where it is writing the
system configuration "Running SuSEconfig.tetex" and never completes this step.
Manually switching to another console and killing the tetex process allows the
installation to continue and complete successfully.

I will attach hwinfo and y2logs shortly.
Comment 1 Lukas Ocilka 2005-08-10 22:31:41 UTC
OK, please, attach those logs and I'll have a look at it...
Comment 2 Klaus Kämpf 2005-08-11 06:19:09 UTC
This is already known. There is a password expiration for user nobody 
 
-> werner 
Comment 3 Dr. Werner Fink 2005-08-11 09:46:37 UTC
Please run as root

        grep nobody /etc/shadow

and report this line in your comment, thanks.
Comment 4 Bryan Perry 2005-08-11 14:07:57 UTC
Results of 'grep nobody /etc/shadow':

nobody:*:13004:0:0::::
Comment 5 Bryan Perry 2005-08-11 14:13:50 UTC
Created attachment 45765 [details]
Y2Logs

Y2Logs
Comment 6 Ruediger Oertel 2005-08-11 14:25:19 UTC
bug in YaST2 user module: 
 
before yast2-users: 
nobody:*:8902:::::: 
after yast2-users (adding one local user): 
nobody:*:8902:0:0:::: 
 
Comment 7 Jiří Suchomel 2005-08-11 14:43:06 UTC
actually, it is yast2-pam
Comment 8 Jiří Suchomel 2005-08-11 15:08:02 UTC
Fixed in yast2-pam-2.12.2
(http://lide.suse.cz/~~jsuchome/yast2/rpms/yast2-pam-2.12.2-0.noarch.rpm)

which will go to beta2.
Comment 9 Jiří Suchomel 2005-08-16 15:57:11 UTC
*** Bug 104937 has been marked as a duplicate of this bug. ***
Comment 10 Ulrich Windl 2005-08-17 12:28:59 UTC
FYI: I've found a workaround (temporary solution):
kill the "su - nobody" process
passwd -x 99999 nobody
After that SuSEconfig finished normally.
Comment 11 Dr. Werner Fink 2005-08-22 09:27:20 UTC
*** Bug 105847 has been marked as a duplicate of this bug. ***
Comment 12 Jiří Suchomel 2005-08-29 10:12:48 UTC
*** Bug 113692 has been marked as a duplicate of this bug. ***
Comment 13 Jiří Suchomel 2005-08-29 10:30:27 UTC
*** Bug 113692 has been marked as a duplicate of this bug. ***
Comment 14 Andreas Schwab 2005-08-31 14:18:43 UTC
*** Bug 112772 has been marked as a duplicate of this bug. ***