Journal Sax Maniac's Journal: GNOME leaking daemons, part 2
I think I finally have this one figured out, and, while GNOME still likes to leak daemons in other situations, this seems to be a pulseaudio problem.
If your home directory is on NFS, pulseaudio gets very unhappy. And, since gnome-settings-daemon invokes pulseaudio for you, once you have an unhappy (ah, totally wedged) pulseaudio you have an unhappy GNOME. Any GNOME app that tries to get some settings hangs. Which means an unhappy hacker at the terminal.
Why: pulse tries to do a lock on $HOME/.pulse-cookie, and this hangs hard. I don't know if it's because I'm not running the proper locking daemon or it's an attribute of our NFS server.
Solution: move $HOME/.pulse-cookie to a local disk, and link $HOME/.pulse-cookie to that.
How did I figure this out?
1. ps -ef --forest -- showed a defunct pulseaudio process as a child of gnome-settings-daemon (pid 12345), which was apparently stuck waiting for it.
2. strace -p 12345 -- showed g-s-d was hung on an fcntl call trying to F_SETLK64 on fd 21
3. ls -l
I actually blew away Fedora 10 and decided to play with Ubuntu 8.10 because this was annoying me so much, only to discover it afflicted both!
GNOME leaking daemons, part 2 More Login
GNOME leaking daemons, part 2
Slashdot Top Deals