Remy Blank wrote: > Alan McKinnon wrote: >> But I was not able to make the problem re-appear in short reboot >> cycles. So whatever is hanging the box is something that starts up in >> the course of work, it doesn't appear to be there directly after a KDE >> login. > > I have observed that kded4 and nepomukserver sometimes don't terminate > after logging out of KDE. At the next login, I get another copy of each, > and so they accumulate. It's so bad that I added a script to > ~/.kde4/shutdown to "kill -9" them if they are still running 15 seconds > after logging out. > > Both processes keep open file descriptors to ~/.xsession-errors, so they > would indeed prevent /home from unmounting. > > -- Remy >
I run into that a LOT here too. After a large upgrade, I usually switch to the boot runlevel to make sure most everything gets reloaded. When I do that, I have to kill some leftover kde stuff manually. I have been known to let it sit for several minutes to see if it will eventually kill itself but it never has. The nepomukserver is one of them but there is another one that I can't recall the name of. May be on to something, hopefully. Care to share that script? ;-) May try that myself. Dale :-) :-) -- I am only responsible for what I said ... Not for what you understood or how you interpreted my words!
