Thanks for the pointers. I'm pretty convinced it happens when there is a problem with my network mounted filesystem (/etc/fstab): //192.168.1.74/music /mnt/htpc-music cifs noauto,credentials=/etc/samba/user,noexec,uid=john,gid=john 0 0
The advice in the noah.org article looks good but I'm using CIFS not NFS. Apparently CIFS mounts in a soft fashion by default. I'll have to check my configuration. I might have a look at switching to NFS with the soft option. Thanks a lot for all the help it is really appreciated. -- 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
