Yes, firefox was the unkillable process in that case. I did save a tiny shell log at the time:
acolin@thinkpad ~$ ps aux | grep firefox acolin 3904 51.4 8.9 774456 276596 ? Rs 18:06 18:20 /usr/lib/firefox/firefox acolin 5689 0.0 0.0 4392 808 pts/3 S+ 18:42 0:00 grep firefox acolin@thinkpad ~$ kill -9 3904 acolin@thinkpad ~$ ps aux | grep firefox acolin 3904 51.6 8.9 774456 276596 ? Ss 18:06 18:30 /usr/lib/firefox/firefox acolin 5693 0.0 0.0 4392 808 pts/3 S+ 18:42 0:00 grep firefox Sadly, I don't have any more information and don't have any hopes of reproducing this, but hopefully the stack trace shed's light on possible causes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/199420 Title: Running process cannot be kill -9'ed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/199420/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
