When I try to reboot (or power down) 13.0 32-bit after exiting KDE 4 (run level 3), the system always hangs because the NFS share point /home is remounted read-only. My /home directory is an NFS share point hosted on a different box.

If I wait 20 seconds then the remount does not occur.

Scenario:

1. Exit KDE 4 (Ctrl-Alt-Delete).
2. Return to console.
3. Logout.
4. Immediately reboot (Ctrl-Alt-Delete).

The remount happens because the rc.6 script is using the umount -r option. I understand that part.

I don't understand how or why KDE is preventing umount from unmounting /home. In rc.6 I added the -f (force) option to no avail.

Something in KDE 4 keeps /home locked for about 20 seconds.

I ran ps ax before and after starting KDE 4. The only difference is the gam_server process. The gam_server process does not disappear for about 30 seconds, beyond the approximate 20 seconds I need to reboot without a hang.

I temporarily renamed ~/.kde and started with a fresh configuration directory. Same result --- I can't reboot or power down immediately.

Any ideas?

This does not seem to be a KDE 4 problem. Same box, using 12.2 and KDE 3.5.10 in run level 4.

Any ideas what in KDE 3 or 4 could be preventing the home mount from unmounting?

This is quite a nuisance.

I'm not sure but /etc/rc.d/rc.6 is the script that holds the clues.

Um, no, rc.6 holds no clues.

Update: Using the lsof and fuser commands I discovered that gam_server is the culprit. That process disappears about 20 seconds after I exit a KDE session. I don't understand why the process remains open for so long after exiting KDE. Regardless, I'll add something to my rc.shutdown script to kill all gam_server processes.