Thanks for writing. In my case it was a miss behaving program, bst.linux, which is an IDE for writing programs for Propeller. This program was never completely finished and was last updated in March 2010. I suspect that it could not cope with the newer GTK files as it would crash when opening a child window. The source code was never released so someone could take it over.
It would then cause Nautilus or Gedit it to crash. I no longer use bst as I wrote a spin.lang file for Gedit and an addon compiler. I did not notice a uname zombie. I have not been able to start a second instance of nautilus. Yes I did a lot of reboots to clean up the mess bst left. We agreed to close the bug report because I found the cause and no one else reported a problem until now. Is it possible that you are using a similar program that causes Nautilus to crash? Mike On 12-03-27 06:53 PM, Bachsau wrote: > I'm also encountering this issue since a few days, and I'm using Lucid. > When it happens, there's always an "uname" zombie too. As natilus > refuses to start another instance, and both are children of init, the > only option is to reboot the system. > -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/939661 Title: After a short period of use nautilus no longer reponds and becomes a zombie To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/939661/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
