with mirage extension enable banshee crashes on startup

On Thursday 25,March,2010 04:15 AM, Cuppa-Chino wrote:
> Public bug reported:
>
> Binary package hint: banshee-extension-mirage
>
> on lucid lynx amd64 beta1 (fresh install)
> when I start up banshee with out mirage everything is fine, as soon as mirage is installed banshee crashes on startup -- crash reports to be submitted below
>
> this happened both with deleted banshee.db and an imported banshee.db
> from karmic installation
>
> http://pastebin.com/Fq25G9Tg
>
> ** Affects: banshee-extension-mirage (Ubuntu)
> Importance: Undecided
> Status: New
>
>
> ** Tags: amd64 lucid
>
banshee-extension-mirage (source) and its corresponding binary package (version
0.6.0-1) are due to be removed in Lucid. It will be replaced by the
banshee-extension-mirage binary package produced from
banshee-community-extensions (source), where this bug is not present. It is
currently waiting in Ubuntu's NEW queue at the moment.

--
Kind regards,
Chow Loong Jin (GPG: 0x8F02A411)
Ubuntu Developer

thanks sounds excellent!

I cannot see the banshee-community-extensions in the NEW queue at: https://edge.launchpad.net/ubuntu/lucid/+queue
Is there any news?

This bug was fixed in the package banshee - 1.6.0-1

---------------
banshee (1.6.0-1) unstable; urgency=low

  * New upstream release:
    + Notable bug fixes:
      - Fix device support on upcoming distros with DeviceKit rename
      - Restore equalizer preset correctly (bgo#614313)
      - Handle broken symlinks correctly (bgo#614065)
      - Allow overriding Android, Maemo, WebOS default settings (bgo#611991)
      - Fix crash deleting playlist on mass storage device (bgo#613734)
      - Fix issue with iTunes importer dialog sizing (bgo#613607)
      - Fix play count calculation with gapless enabled (bgo#613418)
      - Handle exceptions thrown by old plugins (LP: #546342)
      - Use panel-specific (eg monochrome) icon in notification area
        (LP: #525280)
    + Other bugs fixed:
      - Start HAL automatically if not already started (LP: #543354)
      - Fix bug where new podcasts could not be added (Closes: #575734)
  * debian/(control, rules):
    + Disable the clutter video sink
      - Uses deprecated functions, and will fail to build with a newer version
        clutter (1.2.X which is available in experimental)
 -- Chow Loong Jin <email address hidden> Fri, 02 Apr 2010 03:12:16 +0800

Reopening. Stack trace from Bug #556069:

Mirage - Open DB - URI=file:/home/jesus/.cache/banshee-mirage/mirage.db,version=3
Mirage - Database version 3 is up to date

** (Banshee:8710): WARNING **: Missing method Banshee.PlaybackController.IBasicPlaybackController::Next(bool) in assembly /usr/lib/banshee-1/Banshee.Services.dll, referenced in assembly /usr/lib/banshee-1/Extensions/Banshee.Mirage.dll
[Info 00:15:10.559] All services are started 1,302467s

** (Banshee:8710): WARNING **: Missing method Banshee.PlaybackController.IBasicPlaybackController::Next(bool) in assembly /usr/lib/banshee-1/Banshee.Services.dll, referenced in assembly /usr/lib/banshee-1/Extensions/Banshee.Mirage.dll
Stacktrace:

  at Banshee.Sources.Source..ctor () <0xffffffff>
  at Banshee.Sources.Source..ctor () <0x00072>
  at Banshee.Sources.DatabaseSource..ctor () <0x0000f>
  at Banshee.Playlist.AbstractPlaylistSource..ctor (string,string,Banshee.Sources.PrimarySource) <0x000c3>
  at Banshee.Playlist.PlaylistSource..ctor (string,Banshee.Sources.PrimarySource) <0x00033>
  at Banshee.Mirage.PlaylistGeneratorSource..ctor (Mirage.Db) <0x000df>
  at Banshee.Mirage.MiragePlugin.ServiceStartup () <0x00147>
  at Banshee.Mirage.MiragePlugin.OnSourceAdded (Banshee.Sources.SourceAddedArgs) <0x0000f>
  at (wrapper runtime-invoke) Banshee.Mirage.MiragePlugin.runtime_invoke_void__this___object (object,intptr,intptr,intptr) <0xffffffff>
  at (wrapper managed-to-native) System.Reflection.MonoMethod.InternalInvoke (object,object[],System.Exception&) <0x0004e>
  at (wrapper managed-to-native) System.Reflection.MonoMethod.InternalInvoke (object,object[],System.Exception&) <0xffffffff>
  at System.Reflection.MonoMethod.Invoke (object,System.Reflection.BindingFlags,System.Reflection.Binder,object[],System.Globalization.CultureInfo) <0x000bb>
  at System.Reflection.MethodBase.Invoke (object,object[]) <0x0002a>
  at System.Delegate.DynamicInvokeImpl (object[]) <0x0017b>
  at System.MulticastDelegate.DynamicInvokeImpl (object[]) <0x0003b>
  at System.Delegate.DynamicInvoke (object[]) <0x00015>
  at Hyena.EventExtensions.SafeInvoke<object> (object,object[]) <0x000cb>
  at Banshee.Sources.SourceManager.AddSource (Banshee.Sources.Source,bool) <0x00197>
  at Banshee.Sources.SourceManager.AddSource (Banshee.Sources.Source,bool) <0x003e3>
  at Banshee.ServiceStack.Application.Run () <0x000af>
  at Banshee.Gui.GtkBaseClient.Initialize (bool) <0x0026f>
  at Banshee.Gui.GtkBaseClient..ctor (bool,string) <0x00033>
  at Banshee.Gui.GtkBaseClient..ctor () <0x0001b>
  at Nereid.Client..ctor () <0x0000f>
  at (wrapper runtime-invoke) object.runtime_invoke_void__this__ (object,intptr,intptr,intptr) <0xffffffff>
  at (wrapper managed-to-native) System.Reflection.MonoCMethod.InternalInvoke (object,object[],System.Exception&) <0x0004e>
  at (wrapper managed-to-native) System.Reflection.MonoCMethod.InternalInvoke (object,object[],System.Exception&) <0xffffffff>
  at System.Reflection.MonoCMethod.Invoke (object,System.Reflection.BindingFlags,System.Reflection.Binder,object[],System.Globalization.CultureInfo) <0x0010b>
  at System.Reflection.MonoCMethod.Invoke (System.Reflecti...

I'm having this exact same problem in Lucid only I don't have the banshee-extension-mirage package, or any other extension install what-so-ever.

I'm using the 1.7.5 version from the http://ppa.launchpad.net/banshee-team/banshee-unstable/ubuntu repository.
Downgrading to 1.6.1~lucid1 fixes the problem but I'd like to use the latest as I have a few problems in mind I need to test out before I consider reporting them.

running banshee from terminal: http://pastebin.com/iVrcTNe3

Brendan,
If you don't have the banshee-extension-mirage package installed, then it's a different problem. You should probably file a separate bug for your problem.