I'm going to re-open this issue, as it's not solved, and in my case is
not a file system issue - as banshee is stuck in a fuse_write stae,
writing to the primary disk that everything else is running on quite
happily.
Banshee will restart once I reboot, which is not a viable option. I've
tried
Same problem. Banshee crashes almost after every 3-4 songs and the
process says `defunct`. Only way to start banshee again is to restart
the computer.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This happens to me with both banshee *and* rhythmbox. I prefer banshee
so it's most annoying for that. The only solution seems to be a reboot.
(I also have the defunct banshee process and it won't restart). I have
a pretty stock ubuntu 14.04 install.
--
You received this bug notification because
This happens to me pretty often too. I'm not using any kind of network
share. Happened after upgrading to Fedora 19, which I'm assuming means a
new version of mono. I suspect it's mono, because after this happens,
none of my other mono apps will work.
5247 1 0 Nov04 ?00:05:53
I did run that command. If it happens again I'll make doubly sure.
--
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
Agreed the situation wouldn't be much better in terms of playing music
but I think banshee's behaviour could be. At the moment Ubuntu appears
not to work as I try to start banshee and nothing happens (not even an
error message). Are there no system calls that can return errors instead
of
I think better than rebooting might be unmounting the network share.
I'll try that next time.
--
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
Here's the log you asked for.
** Attachment added: debug log as asked for
https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/1196828/+attachment/3742400/+files/log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On Fri, Jul 19, 2013 at 10:39:04AM -, John Reid wrote:
Here's the log you asked for.
** Attachment added: debug log as asked for
https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/1196828/+attachment/3742400/+files/log
Hmm, did you run the killall -SIGQUIT banshee command like I
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
On Thu, Jul 18, 2013 at 01:33:05PM -, 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
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
On Tue, Jul 16, 2013 at 06:42:17AM -, John Reid wrote:
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
Banshee crashed again but the process didn't disappear. Here's the log
for the banshee I'm trying to start.
john@W530$ banshee --debug
** Running Mono with --debug **
[1 Debug 17:54:39.785] Bus.Session.RequestName ('org.bansheeproject.Banshee')
replied with InQueue
I've attached the log for
Here is the current ps output:
john@W530$ ps -ef|grep banshee
john 2170 1711 0 17:58 pts/21 00:00:00 grep --color=auto banshee
john 25995 15673 4 13:00 pts/700:14:35 [banshee] defunct
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
What's process 15673? That's Banshee's current parent process.
--
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
Good point, I didn't check the output too closely. 15673 is the bash
shell I started banshee from:
~/Downloads
john@W530$ ps -ef|grep 15673
john 4724 4624 0 18:59 pts/21 00:00:00 grep --color=auto 15673
john 15673 10712 0 Jul09 pts/700:00:00 bash
john 25995 15673 4 13:00
On Mon, Jul 15, 2013 at 06:01:36PM -, John Reid wrote:
Good point, I didn't check the output too closely. 15673 is the bash
shell I started banshee from:
~/Downloads
john@W530$ ps -ef|grep 15673
john 4724 4624 0 18:59 pts/21 00:00:00 grep --color=auto 15673
john 15673
Killing bash make the PPID 1 and banshee won't start
~/Downloads
john@W530$ kill 15673
~/Downloads
john@W530$ kill -9 15673
~/Downloads
john@W530$ ps -ef|grep banshee
john 6435 4624 0 20:04 pts/21 00:00:00 grep --color=auto banshee
john 25995 1 3 13:00 ?00:14:35
OK I can try and kill bash but I'd like to know what to do when the
parent is 1. That is the problem and forces me to reboot.
--
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
On Mon, Jul 15, 2013 at 07:05:49PM -, John Reid wrote:
Killing bash make the PPID 1 and banshee won't start
~/Downloads
john@W530$ kill 15673
~/Downloads
john@W530$ kill -9 15673
~/Downloads
john@W530$ ps -ef|grep banshee
john 6435 4624 0 20:04 pts/21 00:00:00 grep
On Tue, Jul 16, 2013 at 09:58:19AM +0800, Chow Loong Jin wrote:
On Mon, Jul 15, 2013 at 07:05:49PM -, John Reid wrote:
Killing bash make the PPID 1 and banshee won't start
~/Downloads
john@W530$ kill 15673
~/Downloads
john@W530$ kill -9 15673
~/Downloads
john@W530$ ps
http://www.noah.org/wiki/Kill_-9_does_not_work mentions zombie processes
wedged on NFS, so some of the solutions mentioned there might help.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1196828
I see this on that link you provided: init can never have zombie
children. From the wikipedia article: When a process loses its parent,
init becomes its new parent. Init periodically executes the wait system
call to reap any zombies with init as parent. One of init's
responsibilities is reaping
On Mon, Jul 08, 2013 at 07:45:40AM -, John Reid wrote:
I see this on that link you provided: init can never have zombie
children. From the wikipedia article: When a process loses its parent,
init becomes its new parent. Init periodically executes the wait system
call to reap any zombies
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
See link to askubuntu question for ps output but I don't see what you
can learn from that. I'm not sure it is a banshee bug either. Banshee is
dead but why cannot I start another banshee process?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Package changed: initramfs-tools (Ubuntu) = banshee (Ubuntu)
--
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
Also see same question here: http://askubuntu.com/questions/315292/how-
to-restart-banshee-after-crash
--
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
29 matches
Mail list logo
