On Thu, Jul 18, 2013 at 01:33:05PM -0000, John Reid wrote: > Is it really solved though? Despite the problem being caused by a > cifs/nfs error, banshee's behaviour is still quite bad. A GUI shouldn't > really be unresponsive even if there are network problems behind the > scenes. BTW I have been running using a NFS mount instead of CIFS mount > for a few days now and I've seen similar behaviour.
Well, that's true. It probably a deadlock of some kind. Create an empty file ~/.config/banshee-1/always-debug, restart Banshee, and and the next time it hangs, run "killall -SIGQUIT banshee". After that attach ~/.config/banshee-1/log here. That being said, even if Banshee didn't deadlock, the situation wouldn't be much better. Thing is, Banshee plays media files from that mount. If the mount hangs, then it follows that your playback is going to hang, or in this case, based on your logs, writing metadata changes back to file (presumably play counts). And because it's hanging in the middle of a system call, you're also not going to be able to quit and restart, because at least one thread will be completely stuck (and unkillable). -- Kind regards, Loong Jin -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1196828 Title: Cannot restart banshee after crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/1196828/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
