Re: [Banshee-List] Banshee already running/won't start up

[Samuel Gyger <samuel gyger at>]

Same Problem sometimes. Have to kill it on the console. So it's not
such a problem for me because most time I don't close banshee at all.

Samuel

On Thu, Apr 1, 2010 at 14:33, Michael Martin-Smucker
<mlmartin13 gmail com> wrote:
> For what it's worth, you're not alone.  I've run into this as well -
> infrequently, but still...  Banshee occasionally starts up as an
> unresponsive window; iirc, force quitting this window doesn't seem to end
> the process correctly, so when I attempt to restart Banshee, I get the
> "InQueue" message in Terminal.
> Popping up a message seems like the right thing to do in this scenario.
>  A dialog box with an error (and maybe some instructions on how to end the
> process) is definitely better than silently failing to start.
> Michael
>
> On Tue, Mar 30, 2010 at 11:02 PM, David Velazquez
> <david velazquez08 gmail com> wrote:
>>
>> I ran into an issue tonight where I went to start banshee via the
>> applications menu (Ubuntu Karmic) and banshee did not actually appear to
>> start. Banshee starting came up on the tray but the UI did not appear.
>> Subsequent attempts also failed. When trying start via the terminal with
>> debug mode to see what was up it simply stated
>>
>> "** Running Mono with --debug   **
>> [Debug 22:50:26.368] Bus.Session.RequestName
>> ('org.bansheeproject.Banshee') replied with InQueue"
>>
>> which I took to mean banshee was running. Searching for the banshee
>> process (ps aux | grep banshee) indeed showed me one instance of banshee
>> running which would explain the message in the terminal and also why the
>> banshee starting message came up and subsequently disappeared even though
>> the UI did not show up. Killing it allowed banshee to start right back up
>> with no ill affects. I've run into this at least once before (where banshee
>> started, but without the ui) but just realized what was happening today. I'm
>> wondering now if banshee just is not closing properly (the icon for it does
>> disappear) but I can't seem to replicate that to prove it and that's why
>> it's already running the next time I try it and it obviously won't start
>> again.
>>
>> I wonder if this sounds like a bug anyone has experienced before or sounds
>> like something similar. A search in bugzilla revealed something affecting
>> Macs way back in the 1.5 release, but nothing else I noticed at first
>> glance. If it is something that other people have experienced, would it be
>> possible to announce that banshee is already running and asking if we would
>> like to kill it and try again? Or maybe just show a message like that in the
>> terminal when users try to start it banshee or banshee --debug. Now that I
>> seem to have narrowed down what's happening I'll try to figure out why or at
>> least when it happens and get back to the list in my days off.
>>
>> Dave
>>
>> _______________________________________________
>> banshee-list mailing list
>> banshee-list gnome org
>> http://mail.gnome.org/mailman/listinfo/banshee-list  (unsubscribe here)
>
>
> _______________________________________________
> banshee-list mailing list
> banshee-list gnome org
> http://mail.gnome.org/mailman/listinfo/banshee-list  (unsubscribe here)
>