https://bugzilla.novell.com/show_bug.cgi?id=728555 https://bugzilla.novell.com/show_bug.cgi?id=728555#c1 Scott Couston changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |scott@aphofis.com --- Comment #1 from Scott Couston 2011-11-30 21:36:30 UTC --- Sorry for the delay - I have been away on holidays I logged in as root from a console session at the GUI part user login (non automated) and loaded yast text based interface. I shut down all Network Servers that I had configured,,,SAMBA, NFS client.Server...etc. I rebooted the PC and the GUI interface and PC runs perfectly. Apart from the Yast logs I can send you can you tell me the name/location of the login script by return. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=728555 https://bugzilla.novell.com/show_bug.cgi?id=728555#c3 Scott Couston changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Component|Kernel |YaST2 InfoProvider|mvidner@suse.com | AssignedTo|kernel-maintainers@forge.pr |bnc-team-screening@forge.pr |ovo.novell.com |ovo.novell.com Summary|PC Rendered Totally |PC Rendered Totally |Unassailable and Useless |Unassailable and Useless |after Loading Kernel Based |after Loading SAMBA,NFS, |NFS Server |NIS Services QAContact|qa@suse.de |jsrain@suse.com --- Comment #3 from Scott Couston 2011-12-22 03:08:32 UTC --- Bug Renamed and Reclassified - This is a compound bug bought on my adding SAMBA, NFS, NIS Services. The actual reason will only be evident in the logs. The latest change to NFS Services shut-down of X_64 PC cause every PC to hang and not complete the shut down script as it hangs on shutting down NFS Services. Again the logs will provide the necessary info. Please specifically request the logs you need, plus the login script and its audit file plus the shut-down script and its audit file -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=728555 https://bugzilla.novell.com/show_bug.cgi?id=728555#c5 Jiri Srain changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW CC| |jsrain@suse.com InfoProvider|jsrain@suse.com | --- Comment #5 from Jiri Srain 2011-12-22 07:01:38 UTC --- Scott, I think that you are asking the wrong audience. It looks to me that it is not YaST what's wrong, but some of the services (most likely NFS server) itself. The reason may be that it is configured improperly by YaST, then we'd need to know what is the exact mistake. I suggest to identify which service is the problematic one - by selective enabling. I'd bet on NFS from your initial description. The information about the reason of the time-out may be found in the system log (/var/log/messages). You may try to find out what the problem is there and check if the problem may be in the configuration. I suggest to reassign to different component after you identify the service, unless you find a specific misconfiguration. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=728555 https://bugzilla.novell.com/show_bug.cgi?id=728555#c Scott Couston changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |739077 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.