GNOME Bugzilla – Bug 545739
Banshee 1.2 not able to "quit"
Last modified: 2009-02-08 20:48:06 UTC
When I select from the menu Media-> quit banshee hangs. I have to close the window and do a "force quit" when prompted. I'm running Ubuntu 8.04 (Hardy Heron).
Can you attach the output of 'banshee-1 --debug'?
Also, when banshee is hung, run the following command several times and attach the output you get in the terminal where you started banshee : kill -QUIT `pidof banshee-1`
Created attachment 115638 [details] Stdout from "banshee-1 --debug"
Created attachment 115639 [details] Stderr from "banshee-1 --debug"
Andrew, I've attached a file from redirected stdout & stderr from the command 'banshee-1 --debug'. Bertrand, I executed the command several times (with Banshee started the way described above with the redirection) but was unable to quit Banshee that way. I had to do it via 'close window' and 'Force quit'. Regards,
Thanks for the info. The "kill -QUIT ..." command tell mono to dump a stacktrace of all threads, but it's not always reliable. The output is in the file you attached, but not useful. I think the DAAP extension may be messing things up. Could disable it and try again to reproduce the bug ?
If I disable DAAP, I can indeed quit. But then I can not restart again and I actually fall back into a old bug I already filed : bug 539354 ... If you want you can close this bug (although DAAP should not mess things up) but please take a look at 539354. Thanks
Created attachment 115644 [details] [review] Fix the DAAP NRE on exit This should fix the exception thrown by DAAP on exit, when it couldn't instantiate the browser on startup. I'm not using DAAP, so that's one of those "blind patches". Please test !
Looks good Bertrand, please commit.
This problem has been fixed in our software repository. The fix will go into the next software release. Thank you for your bug report.
*** Bug 547047 has been marked as a duplicate of this bug. ***
Created attachment 117729 [details] Output from running banshee with --debug option The log attached was the result of the following scenario : start up banshee, play a song for 10 seconds, pause it and than quit banshee via menu (Media-> quit). Result is that banshee still hangs and has to be terminated via 'kill pid' statement
Unfortunately, the debug output doesn't contains anything interesting. Could you please follow the instructions over there on how to get more information : http://banshee-project.org/contribute/file-bugs/ Specifically, for your case, that would mean doing the following steps : 1. Start banshee from the menu entry 2. Quit banshee. It hangs for you here 3. Open a terminal and run this command: kill -s QUIT $(pidof banshee-1); cp ~/.config/banshee-1/log ~/Desktop/banshee.log 4. Attach the banshee.log file that is now on your Desktop Thanks !
Bertrand, If I follow your instructions, I encounter the following : 1) I do not have a log file in the directory ~/.config/banshee-1. The cp command therefore gives an error 2) The banshee process does not react to the QUIT signal, it keeps on running. It does however recact to a TERM signal. I'm using the 1.2.1 version available in the ubuntu Hardy Heron repository. Regards, Strider
1) Are you sure you started banshee from the menu entry that was added when you installed it ? ie by clicking on its icon. If you're starting it from the command line, please run "banshee-1 --redirect-log" so that the output gets written to the log file. 2) As stated in comment #6, the point of the QUIT signal is not to exit banshee, it's to get mono to output a stacktrace of all running threads in the banshee process, so that we can try to figure out where and why it's hanged.
Created attachment 117804 [details] Banshee log file as demanded Bertrand, I started banshee from command prompt with the option you provided (--redirect-log), for some reason my menu entry just starts up banshee with '/usr/bin/banshee-1) (is the redirect log option the default way of starting up banshee ? I did not find that option in the ouput of banshee-1 --help-all ?) I do not think that the attached file gives a lot of usefull information since the thread dump did not produce much output (see last line of the file)
Normally, banshee installs a menu entry that starts it with the "--redirect-log" option. It's not in --help-all because it's handled by the startup script. The log show no threads, so not helpful. Was the banshee window still visible when you executed the "kill ..." command ? If you manage to get a log file with more info in the thread dump, please attach it here.
Created attachment 117871 [details] Log with banshee hanging When I quit the application, the window indeed closes but the process keeps on running (which should not be the case). I could however get the window to hang by enabling the DAAP extension (see previous comments) which I disabled and the selecting Media->quit. I then sent a QUIT signal to the banshee process and I now have something in the thread dump. Hope this helps more.
Created attachment 128208 [details] Banshee Log During a Hang Ubuntu 8.10 Intrepid Ibex Banshee 1.2.1
Strider, Ray, Could you update to the latest banshee version and try to reproduce the problem ?
(In reply to comment #20) > Strider, Ray, > Could you update to the latest banshee version and try to reproduce the problem > ? > Bertrand, I'm already on Banshee 1.4.2 and this problem disappeared already long time. If Ray could do the same, we can close the issue.
Closing, as the original issue is fixed. Ray, if you can reproduce your problem with banshee 1.4.x, please open another bug. Looking at your log, I think it's another issue anyway.