Hmm, judging by the ps output, that looks like an init bug -- like I mentioned, defunct processes come from the parent process not reaping the child after it has died. However, it looks like the parent process is init (ppid=1) and init isn't reaping it, which shouldn't be the case[1].
Could you post the output of `banshee --debug` please? [1] http://unix.stackexchange.com/questions/11172/how-can-i-kill-a -defunct-process-whose-parent-is-init -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to banshee in Ubuntu. https://bugs.launchpad.net/bugs/1196828 Title: Cannot restart banshee after crash Status in “banshee” package in Ubuntu: Incomplete Bug description: If banshee crashes the sound/audio system menu still shows it as available but nothing happens if I click on it. With ps I can see a defunct banshee process that cannot be removed. If I try to run banshee from the command line nothing happens. Restarting gdm and/or unity also has no effect. As far as I can tell there is now no way to start banshee short of rebooting which is annoying. Does anyone know how I can start banshee without closing everything down and rebooting? Perhaps there is some part of Ubuntu that controls the sound menu and I can restart that? I was hoping it was part of gdm or unity but restarting them didn't help. Description: Ubuntu 13.04 Release: 13.04 but I have seen the same behaviour in 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/1196828/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
