After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 539354 - Banshee won't restart after quit
Banshee won't restart after quit
Status: RESOLVED FIXED
Product: banshee
Classification: Other
Component: general
git master
Other Linux
: Normal major
: 1.x
Assigned To: Banshee Maintainers
Banshee Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-06-20 19:24 UTC by Chris Van Steenlandt
Modified: 2008-10-16 20:06 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
--debug output of banshee not quiting, but hanging without errors (4.88 KB, text/plain)
2008-06-22 09:22 UTC, Peter de Kraker
Details

Description Chris Van Steenlandt 2008-06-20 19:24:40 UTC
If I leave banshee after I've quit before (not close but really quit) and then start up banshee again, it won't start anymore. This happened with banshee 1.00 and also the current SVN Trunk I installed.
When I restart from the desktop, nothing happens. When I start from the terminal using the command 'banshee-1' it just hangs until I ctrl-c.

I'm running Ubuntu Hardy.
Comment 1 Kevin Duffus 2008-06-20 21:05:56 UTC
Strider, may you please run Banshee with the debug switch (e.g., "banshee-1 --debug"). Create an attachment with the crash trace. Note: Please, don't just paste the text into the bug comments section here. Thanks.
Comment 2 Chris Van Steenlandt 2008-06-20 21:27:54 UTC
Kevin,

where is the crash trace created ?

I started 'banshee-1 --debug' from CLI (and again had to ctrl-c to end the application) and I see the following info :

** Running Mono with --debug   **
[Debug 23:19:07.139] NDesk.DBus.Bus.Session.RequestName ('org.bansheeproject.Banshee') => InQueue

but I don't know where I can find the trace file..
Comment 3 Kevin Duffus 2008-06-21 02:00:17 UTC
there is no actual file that written. When the program crashes, you should see output about exceptions. You need to pipe the output spew to a file. Example of writing the output to a file:

            banshee-1 --debug > debug_ouput.txt

Attach the created file "debug_output.txt"
Comment 4 Bertrand Lorentz 2008-06-21 08:33:59 UTC
The "InQueue" in the output you have means that banshee has detected another instance already running.

You can check if you have a "banshee-1" process by running the following command :
ps -ef | grep banshee

When you start "banshee-1 --debug" and there is no other instance already running, the debug output starts with :
NDesk.DBus.Bus.Session.RequestName ('org.bansheeproject.Banshee') => PrimaryOwner
Comment 5 Peter de Kraker 2008-06-22 09:22:06 UTC
Created attachment 113190 [details]
--debug output of banshee not quiting, but hanging without errors

I am having the same issue with latest svn on Opensuse 11. Banshee won't quit, but hangs.
Comment 6 Chris Van Steenlandt 2008-06-23 20:59:13 UTC
I can confirm once again what Peter just mentioned. It's easy reproducable :
1) start up 'banshee-1' from the command line in a terminal window
2) in the application choose Media -> quit
3) a 'ps -ef | grep banshee' from another terminal window shows banshee is still running
4) go back to the orignal window and tap ctrl-c
5) a ps -ef now shows that the process is gone
6) you can restart banshee again.

As said before, this happens with svn trunk version. I am not sure I had the same behaviour with 1.0.0 though. Therefore I changed the version in the bug to 'svn trunk'. 
Comment 7 Chris Van Steenlandt 2008-10-16 20:01:41 UTC
This bug can be closed now.

As of version 1.3.2. Banshee closes correctly if I choose Media>quit and I can restart again.
Comment 8 Andrew Conkling 2008-10-16 20:06:59 UTC
Thanks for reporting back!