Description of Problem: It appears that if you start up galeon with a saved session, if attempts to fork off netstat for some reason, and leaves it running in "<defunct>" status. I dont know why it would be running netstat, but... alikins 9778 4.9 9.0 40360 23268 ? S 16:56 0:06 /usr/bin/galeon-bin alikins 9829 0.0 9.0 40360 23268 ? S 16:56 0:00 \_ /usr/bin/galeon-bin alikins 9830 0.0 9.0 40360 23268 ? S 16:56 0:00 | \_ /usr/bin/galeon-bin alikins 9831 0.0 9.0 40360 23268 ? S 16:56 0:00 | \_ /usr/bin/galeon-bin alikins 9832 0.0 9.0 40360 23268 ? S 16:56 0:00 | \_ /usr/bin/galeon-bin alikins 9903 0.0 9.0 40360 23268 ? S 16:56 0:00 | \_ /usr/bin/galeon-bin alikins 9904 0.0 0.0 0 0 ? Z 16:56 0:00 \_ [netstat <defunct>] Version-Release number of selected component (if applicable): galeon-1.2.0-6 How Reproducible: pretty easy Steps to Reproduce: 1. start galeon, then "exit with session" or just crash it 2. restart galeon (choose "restore session" if it asks you) 3. ps auxf Expected Results: Dont really expect galeon to be running netstat, especially not running it poorly. I dont recall ever seeing this behaviour before.
That's NSS Generating IDs for keys.