Bug 433374

Summary:	doesn't exit cleanly ...
Product:	[openSUSE] openSUSE 11.1	Reporter:	Michael Meeks <mmeeks>
Component:	Banshee	Assignee:	Gabriel Burt <gburt>
Status:	RESOLVED FIXED	QA Contact:	Aaron Bockover <abockover>
Severity:	Critical
Priority:	P2 - High	Flags:	coolo: SHIP_STOPPER-
Version:	Beta 2
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Michael Meeks 2008-10-08 09:24:57 UTC

I launch banshee-1 from the slab - and try to play some mp3 audio files [ which fails ]. I then close the main window, right click the sys-tray applet and 'Quit' it.

Unfortunately banshee-1 hangs around like a bad smell:

16871 ?        Sl     0:03 banshee-1 /usr/lib/banshee-1/Banshee.exe --redirect-log --play-enqueued

[ some minutes later this is still there ]

Sadly this process appears to then stop any other banshee's running: they all hang in 'read' - presumably waiting for some factory process to actually respond when it is not so.

a killall -9 banshee-1 in this situation seems to yield:

Unhandled Exception: System.Exception: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)
  at IClientWindowProxy.Present () [0x00000] 
  at Halie.Client.HandleWindowCommands (Boolean present) [0x00000] 
  at Halie.Client.Main () [0x00000] 
  at (wrapper managed-to-native) System.AppDomain:ExecuteAssembly (System.Reflection.Assembly,string[])
  at System.AppDomain.ExecuteAssemblyInternal (System.Reflection.Assembly a, System.String[] args) [0x00000] 
  at System.AppDomain.ExecuteAssembly (System.String assemblyFile, System.Security.Policy.Evidence assemblySecurity, System.String[] args) [0x00000] 
  at (wrapper remoting-invoke-with-check) System.AppDomain:ExecuteAssembly (string,System.Security.Policy.Evidence,string[])
  at System.AppDomain.ExecuteAssembly (System.String assemblyFile) [0x00000] 
  at (wrapper remoting-invoke-with-check) System.AppDomain:ExecuteAssembly (string)
  at Booter.Booter.BootClient (System.String clientName) [0x00000] 
  at Booter.Booter.Main () [0x00000] 

in case that is at all helpful.

FWIW - paplay works fine on this system, so presumably it's not an underlying audio issue.

Comment 1 Gabriel Burt 2009-01-28 21:23:59 UTC

Can you get the thread stacktrace dump with "kill -s QUIT $(pidof banshee-1)" when the app is hung?  Ideally launch with banshee-1 --debug as well, but that's not critical.

Does it freeze like this every time you quit via the notification icon?

Does it ever freeze when you quit another way (ctrl-q or Media -> Quit)?

Comment 2 Gabriel Burt 2009-01-28 21:27:22 UTC

Sorry, forgot to mention:

If you launch banshee from the cmd line, use banshee-1 --debug --redirect-log

Then, after running the kill -s QUIT, attach your entire banshee log located at ~/.config/banshee-1/log

Comment 3 Michael Meeks 2009-01-29 10:17:51 UTC

This appears to be fixed now; I can't reproduce it at least. OTOH - I found another nice bug for you which I'll file ;-)

Comment 4 Gabriel Burt 2009-01-29 16:11:12 UTC

OK, closing.