GNOME Bugzilla – Bug 589068
Won't launch properly
Last modified: 2009-07-22 19:35:52 UTC
Please describe the problem: Totally gray window area and unresponsive to the tray icon Steps to reproduce: 1. Open Terminal 2. Launch banshee 3. Actual results: The following error output and and a totally gray screen in place of the GUI Unhandled Exception: System.Exception: org.freedesktop.DBus.Error.UnknownMethod: Method "Present" with signature "" on interface "org.bansheeproject.Banshee.ClientWindow" doesn't exist 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] Expected results: The program to launch Does this happen every time? Yes Other information:
It looks like you already have a banshee instance running : Halie is only used if another banshee instance is detected. Maybe an old banshee process that is stuck ? Could you try to look at the list of processes for something containing "banshee" ? This command should do it : ps ax |grep -i banshee If there is one, kill it and then try starting banshee again.
patrick@grawp:~$ ps ax |grep -i banshee 5110 ? Sl 0:03 mono /usr/lib/banshee-1/Banshee.exe --redirect-log --play-enqueued 14399 pts/0 S+ 0:00 grep -i banshee patrick@grawp:~$ patrick@grawp:~$ kill 5110 patrick@grawp:~$ banshee [Info 16:05:15.711] Running Banshee 1.4.3: [Ubuntu 9.04 (linux-gnu, x86_64) @ 2009-04-21 13:26:14 UTC] [Warn 16:05:16.436] Service `Nereid.PlayerInterface' not started: An exception was thrown by the type initializer for Banshee.Collection.Gui.ColumnCellAlbum [Warn 16:05:16.438] Caught an exception - Object reference not set to an instance of an object (in `Hyena.Gui') at Hyena.Gui.PixbufImageSurface..ctor (Gdk.Pixbuf pixbuf, Boolean disposePixbuf) [0x00000] at Hyena.Gui.PixbufImageSurface..ctor (Gdk.Pixbuf pixbuf) [0x00000] at Banshee.Collection.Gui.ColumnCellAlbum..cctor () [0x00000] An exception was thrown by the type initializer for Banshee.Collection.Gui.ColumnCellAlbum (in `Banshee.ThickClient') at Banshee.Collection.Gui.AlbumListView..ctor () [0x00000] at Banshee.Sources.Gui.CompositeTrackSourceContents.InitializeViews () [0x00000] at Banshee.Sources.Gui.FilteredListSourceContents..ctor (System.String name) [0x00000] at Banshee.Sources.Gui.CompositeTrackSourceContents..ctor () [0x00000] at Nereid.PlayerInterface.BuildViews () [0x00000] at Nereid.PlayerInterface.BuildPrimaryLayout () [0x00000] at Nereid.PlayerInterface.Initialize () [0x00000] at Banshee.Gui.BaseClientWindow.InitializeWindow () [0x00000] at Banshee.Gui.BaseClientWindow..ctor (System.String title, System.String configNameSpace, Int32 defaultWidth, Int32 defaultHeight) [0x00000] at Nereid.PlayerInterface..ctor () [0x00000] at (wrapper managed-to-native) System.Reflection.MonoCMethod:InternalInvoke (object,object[],System.Exception&) at System.Reflection.MonoCMethod.Invoke (System.Object obj, BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x00000] [Info 16:05:16.834] All services are started 0.991995s (Banshee:14525): Gdk-CRITICAL **: gdk_window_get_origin: assertion `GDK_IS_WINDOW (window)' failed [Info 16:05:17.234] nereid Client Started This produced the same results
Thanks for investigating this. The stacktrace shows that the origin of your problem is the same as in bug 566846. Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version (probably 1.5.1 or above). *** This bug has been marked as a duplicate of 566846 ***