banshee won't start on Jaunty powerpc (Mono.Data.SQLiteClient exception thrown)

[Matteo Settenvini]

Binary package hint: banshee

It's some months (sorry I didn't report this earlier), that banshee won't start on my powerpc system.

Launching it always gives:

matteo@Dahlia:~$ banshee
[Info 10:48:19.571] Running Banshee 1.4.3: [Ubuntu jaunty (development branch) (linux-gnu, powerpc) @ 2009-03-22 18:34:40 UTC]
[Warn 10:48:24.330] Caught an exception - SQL logic error or missing database (in `Mono.Data.SqliteClient')
  at Mono.Data.SqliteClient.SqliteCommand.ExecuteStatement (IntPtr pStmt, System.Int32& cols, System.IntPtr& pazValue, System.IntPtr& pazColName) [0x00000]
  at Mono.Data.SqliteClient.SqliteCommand.ExecuteStatement (IntPtr pStmt) [0x00000]
  at Mono.Data.SqliteClient.SqliteCommand.ExecuteReader (CommandBehavior behavior, Boolean want_results, System.Int32& rows_affected) [0x00000]
  at Mono.Data.SqliteClient.SqliteCommand.ExecuteNonQuery () [0x00000]
  at Hyena.Data.Sqlite.HyenaSqliteCommand.Execute (Hyena.Data.Sqlite.HyenaSqliteConnection hconnection, Mono.Data.SqliteClient.SqliteConnection connection) [0x00000]
[Warn 10:48:24.332] Extension `/Banshee/ServiceManager/Service/__nid_9' not started: Exception has been thrown by the target of an invocation.
[Info 10:48:25.331] All services are started 5,230956s
Exception has been thrown by the target of an invocation.
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> Mono.Data.SqliteClient.SqliteExecutionException: SQL logic error or missing database
  at Mono.Data.SqliteClient.SqliteCommand.ExecuteStatement (IntPtr pStmt, System.Int32& cols, System.IntPtr& pazValue, System.IntPtr& pazColName) [0x00000]
  at Mono.Data.SqliteClient.SqliteCommand.ExecuteStatement (IntPtr pStmt) [0x00000]
  at Mono.Data.SqliteClient.SqliteCommand.ExecuteReader (CommandBehavior behavior, Boolean want_results, System.Int32& rows_affected) [0x00000]
  at Mono.Data.SqliteClient.SqliteCommand.ExecuteNonQuery () [0x00000]
  at Hyena.Data.Sqlite.HyenaSqliteCommand.Execute (Hyena.Data.Sqlite.HyenaSqliteConnection hconnection, Mono.Data.SqliteClient.SqliteConnection connection) [0x00000]
  --- End of inner exception stack trace ---
  at System.Reflection.MonoCMethod.Invoke (System.Object obj, BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x00000]
  at System.Reflection.MonoCMethod.Invoke (BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x00000]
  at System.Reflection.ConstructorInfo.Invoke (System.Object[] parameters) [0x00000]
  at System.Activator.CreateInstance (System.Type type, Boolean nonPublic) [0x00000]
  at System.Activator.CreateInstance (System.Type type) [0x00000]
  at Banshee.Gui.GtkBaseClient.Startup () [0x00000]
  at Hyena.Gui.CleanRoomStartup.Startup (Hyena.Gui.StartupInvocationHandler startup) [0x00000]

This is a fatal error, and the application does exit.

However, I can use the sqlite3 binary to normally open and show tables of ~/.config/banshee-1/banshee.db. Deleting it doesn't work, either, and it's recreated again normally.

banshee is at version 1.4.3-3ubuntu2, and mono at version 2.0.1-4.
libmono-sqlite2.0-cil is at 2.0.1-4 too.

[Chow Loong Jin (hyperair)]

Do you have a ~/.config/banshee/ folder? If you do, could you attach the
banshee.db from that folder here? I reckon there's a problem with the
migration code from Banshee 0.1x.x's database.
--
Regards,
Chow Loong Jin

[Matteo Settenvini (tchernobog)]

I did remove that folder and it got re-created anew by banshee 1.4.3. Attaching the db nevertheless.

[Chow Loong Jin (hyperair)]

On Wed, 2009-05-20 at 18:57 +0000, Matteo Settenvini wrote:
>
> I did remove that folder and it got re-created anew by banshee 1.4.3.
> Attaching the db nevertheless.
~/.config/banshee-1 will be created by banshee 1.4.3. Did you remove
~/.config/banshee?
--
Regards,
Chow Loong Jin

[Matteo Settenvini (tchernobog)]

Yes, no such directory exists ("~/.config/banshee").
"~/.config/banshee-1" gets re-created at banshee startup.

[Chow Loong Jin (hyperair)]

On Wed, 2009-05-20 at 21:10 +0000, Matteo Settenvini wrote:
> Yes, no such directory exists ("~/.config/banshee").
> "~/.config/banshee-1" gets re-created at banshee startup.
>
That's to be expected. ~/.config/banshee-1 is required to store
Banshee's configuration, library metadata and whatnot. It's strange that
you are encountering such crashes though. I'll try to reproduce this bug
tomorrow.
--
Regards,
Chow Loong Jin

[Fred (f-destat)]

Same problem here.

I also receive this error message (attached)

I restored a backup of my banshee.db and managed to open banshee at least once. Then it started to crash again.

Also tried to delete banshee.db. Banshee opened fine. But after reimporting the whole library it started to crash again

My banshee.db is about 50 Mio.

[Onkar Shinde (onkarshinde)]

I can confirm this bug. I encountered this on a jaunty install fully updated. I had never used banshee before (hence didn't have any database). I was trying it first time when I read that it may replace rhythmbox as default player in karmic.

[Onkar Shinde (onkarshinde)]

I am attaching the exceptions I have seen when launching banshee for first time (no config directory exists).
I am also attaching the schema of the DB created. Please note that even though DB is created, banshee still exits after showing exception.

[Onkar Shinde (onkarshinde)]

One more piece of information. The problem is seen on Debian testing as well.

[Jo Shields (directhex)]

I'm attaching an "empty" database from Banshee 1.4.3 on AMD64 to this bug. Can a PPC owner please try dropping it in place instead of their current file, and see if Banshee starts? I want to see whether the problem is happening at the point where the DB is populated, or when it is subsequently read back.

It would also be very valuable to test against Mono 2.4 - this is available for PPC in Debian Unstable, but not in any Ubuntu yet for PPC (i have i386 on my PPA, you could recompile the source package locally)

[Onkar Shinde (onkarshinde)]

I dropped the empty db in place of the empty db I had. I get different error in terminal.
onkar@iBook:~/.config$ banshee
[Info 10:14:00.031] Running Banshee 1.4.3: [Ubuntu jaunty (development branch) (linux-gnu, powerpc) @ 2009-03-22 18:34:40 UTC]
[Warn 10:14:02.419] Rolling back database migration
[Error 10:14:02.441] Error initializing required service DbConnection
Exception has been thrown by the target of an invocation.
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> Mono.Data.SqliteClient.SqliteSyntaxException: table CorePrimarySources already exists
  at Mono.Data.SqliteClient.SqliteCommand.GetNextStatement (IntPtr pzStart, System.IntPtr& pzTail, System.IntPtr& pStmt) [0x00000]
  at Mono.Data.SqliteClient.SqliteCommand.ExecuteReader (CommandBehavior behavior, Boolean want_results, System.Int32& rows_affected) [0x00000]
  at Mono.Data.SqliteClient.SqliteCommand.ExecuteNonQuery () [0x00000]
  at Hyena.Data.Sqlite.HyenaSqliteCommand.Execute (Hyena.Data.Sqlite.HyenaSqliteConnection hconnection, Mono.Data.SqliteClient.SqliteConnection connection) [0x00000]
  --- End of inner exception stack trace ---
  at System.Reflection.MonoMethod.Invoke (System.Object obj, BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x00000]
  at System.Reflection.MethodBase.Invoke (System.Object obj, System.Object[] parameters) [0x00000]
  at Banshee.Database.BansheeDbFormatMigrator.InnerMigrate () [0x00000]
  at Banshee.Database.BansheeDbFormatMigrator.Migrate () [0x00000]
  --- End of inner exception stack trace ---
  at System.Reflection.MonoCMethod.Invoke (System.Object obj, BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x00000]
  at System.Reflection.MonoCMethod.Invoke (BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x00000]
  at System.Reflection.ConstructorInfo.Invoke (System.Object[] parameters) [0x00000]
  at System.Activator.CreateInstance (System.Type type, Boolean nonPublic) [0x00000]
  at System.Activator.CreateInstance (System.Type type) [0x00000]
  at Banshee.Gui.GtkBaseClient.Startup () [0x00000]
  at Hyena.Gui.CleanRoomStartup.Startup (Hyena.Gui.StartupInvocationHandler startup) [0x00000]

Banshee shows different error.
An unhandled exception was thrown: table CorePrimarySources already exists

  at Mono.Data.SqliteClient.SqliteCommand.GetNextStatement (IntPtr pzStart, System.IntPtr& pzTail, System.IntPtr& pStmt) [0x00000]
  at Mono.Data.SqliteClient.SqliteCommand.ExecuteReader (CommandBehavior behavior, Boolean want_results, System.Int32& rows_affected) [0x00000]
  at Mono.Data.SqliteClient.SqliteCommand.ExecuteNonQuery () [0x00000]
  at Hyena.Data.Sqlite.HyenaSqliteCommand.Execute (Hyena.Data.Sqlite.HyenaSqliteConnection hconnection, Mono.Data.SqliteClient.SqliteConnection connection) [0x00000]
Exception has been thrown ...

[Michael Martin-Smucker (mmartinsmucker)]

A fix was committed several days ago. I'll mark this as such (isn't that what Bug Watch Updater is for?)

[Michael Martin-Smucker (mmartinsmucker)]

hmm, a warning here says that bgo#547218 doesn't exist (it does). Apparently I can't update it manually until the Remote Watch is turned off. Should I do that? Something seems wrong here... maybe someone with more Launchpad experience than me has some suggestions.

[Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount)]

This bug should be fixed in Ubuntu 9.10 now. Thanks for reporting.

As for the broken bugwatch: This is nothing unusual and is caused by the large amount of bugwatches against the gnome bugtracker, which are all supposed to be synced each 24 hours. If you notice a bug is fixed upstream and the bugwatch is broken, you may use the status "fix commited" for the Ubuntu related task (so in this case you could have set "banshee (Ubuntu)" to "fix commited" to make it clear that this bug is fixed upstream).