https://bugzilla.novell.com/show_bug.cgi?id=739077 https://bugzilla.novell.com/show_bug.cgi?id=739077#c0 Summary: An X_64 PC Wont Shutdown from NON-Automated User Login and NFS Client Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86-64 OS/Version: openSUSE 11.4 Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: scott@aphofis.com QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:9.0) Gecko/20100101 Firefox/9.0 All PC's on my network are X_64 running Default KDE 11.4 X_64 either NFS Client and/or Server - NON V4! ALL PC's DO NOT have Auto User Login Enabled! After successful login from Non-Automated User Login, and after successfully finding the NFS Clients Server, in another PC, the fault becomes apparent. After shutting down the corresponding NFS Server PC via the use of the KDE Lock/Logout Applet and THEN selecting Turn Off the PC, the shutdown fails to Halt all processes. The logout script hangs on 'shutting down NFS Clent Services.......' for ever until I manually inter vein and hit the PC's turn off button Once. There are NO other Options to me that are available to shut down the PC. Reproducible: Always Steps to Reproduce: 1. Setup a default KDE PC with X_64 Architecture with NO-Auto_user Login and NON NFS Server exports. 2. Setup the same PC but with NON NFS V4 Client services running and mount the exported directory from the server above 3. Login to both PCs, The NFS Server PC, first from the non_automated user login screen. 4. Select 'Turn Off the PC' from the KDE default Applet and this will proceed perfectly and end up with total PC cold shutdown. 5. Try the same procedure with with NFS Client PC and the PC will never reach a shutdown, stalling as above, until forced by human interference on hitting the stop PC button once Actual Results: I do not believe this has anything to do with Architecture, nor version up to 12.x, this is yet another horror of NFS Severer and Client and SM-Notify that we cannot correct by looking at isolated bugs. I have set dependencies as such, however please note..the Yast team looking after NFS V4 and NFS NONV4 are right in the middle of these related problems Expected Results: IF! you cannot simply duplicate this with 12.x and 32 bit Architecture then be specific in the logs as well as login script and its audit and logout script and its audit. Its hight time we get NFS issues well out of the way and working and I have no idea what you have done with NON V4 Specified and Kernel Intervention??????? Please allocate sufficient resources to fix all these related bugs - I believe they will continue to plague us no matter the software version and Architecture. I DO NOT BELIEVE THAT NFS SERVER AND CLIENT are reliable and robust enough to be shipped into any enterprise product let alone the final RC of any version. All these problems date back as far as 10.1 and never once corrected and we are now seeing the consequences of doing nothing! -- 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.