F-Spot db upgrade issue

[hackel]

Binary package hint: f-spot

Package: f-spot
Version: 0.4.2-0ubuntu2

After upgrading from gutsy to hardy alpha6, F-Spot crashes upon launching. The following is output on the console:

Initializing Mono.Addins
Starting new FSpot server
Updating F-Spot Database
Updated database from version 6 to 7
Rolling back database changes because of Exception
XXXXX
System.InvalidCastException: Cannot cast from source type to destination type.
  at FSpot.Database.Updater+<>c__CompilerGenerated21.<Updater>c__58 () [0x00000]
  at FSpot.Database.Updater+Update.Execute (.Db db, .MetaItem db_version) [0x00000]
  at FSpot.Database.Updater.Run (.Db database) [0x00000]
XXXXX
Can't get a connection to the dbus. Trying again...
Starting new FSpot server
Can't get a connection to the dbus. Trying again...
Starting new FSpot server
Can't get a connection to the dbus. Trying again...
Starting new FSpot server
Can't get a connection to the dbus. Trying again...
Starting new FSpot server
Can't get a connection to the dbus. Trying again...
Starting new FSpot server
Can't get a connection to the dbus. Trying again...
Sorry, couldn't start F-Spot
Segmentation fault (core dumped)

I have to dbus-daemon processes running. ps shows the first as owned by pid "101," so perhaps this user was removed in the upgrade process? I've still got the user messagebus with uid 101 in /etc/passwd. I don't know if this is related to the f-spot issue, but I thought I would mention it. The other dbus is owned by my user account.

I'm assuming that apport is including the information it collected somewhere? (I don't see it here) If not, please advise how I can get a backtrace from a Mono application. Also let me know if I can provide any additional information.

ProblemType: Crash
Architecture: i386
Date: Mon Mar 10 12:54:53 2008
Disassembly: 0xb7054030:
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/lib/f-spot/f-spot.exe
InterpreterPath: /usr/bin/mono
NonfreeKernelModules: fglrx
Package: f-spot 0.4.2-0ubuntu2
PackageArchitecture: i386
ProcCmdline: f-spot /usr/lib/f-spot/f-spot.exe
ProcEnviron:
 LC_MONETARY=en_US.UTF-8
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
 LANG=C
Signal: 11
SourcePackage: f-spot
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/libgobject-2.0.so.0
 ?? ()
 ?? ()
 ?? ()
Title: f-spot.exe crashed with SIGSEGV
Uname: Linux 2.6.24-11-generic i686
UserGroups: adm admin audio cdrom dialout dip disk floppy fuse lp lpadmin plugdev scanner video www-data

[Apport retracing service (apport)]

StacktraceTop:?? ()
toggle_refs_notify (object=<value optimized out>, is_last_ref=1)
global_program_unref () at gnome-program.c:159
exit () from /lib/tls/i686/cmov/libc.so.6
__libc_start_main () from /lib/tls/i686/cmov/libc.so.6

[hackel (hackel)]

I believe the problem is caused by the DB auto-update process (migrating sqlite2 to 3?). If I move ~/.gnome2/f-spot out of the way, f-spot launches fine.

It still segfaults when I quit it, however I believe this is documented in other bug reports.

[Pedro Villavicencio (pedro)]

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

[hackel (hackel)]

Ugh, this is NOT a dupe of Bug 197629! Do you not think I looked at all the other similar bugs first before reporting? Did you even read and compare the two bug reports? They are completely different. MY bug is about converting the database from version 6 to 7. The other bug is the segfault on exit bug (which I am also experiencing, and is a completely separate issue).

It's really frustrating to have to clean up your work... Remove this dupe status immediately.

[Guillermo Pérez (bisho)]

I confirm this bug. I also have same problem, and moving ~/.gnome2/f-spot to any other place you are able to start f-spot

[Stephane Delcroix (stephane-delcroix)]

fixed upstream, in trunk and F_SPOT_0_4_2_STABLE branch

[Wilbur Harvey (wilbur-harvey-spirentcom)]

My f-spot crashes immediately on startup as follows.

Deleting .gnome2/f-spot didn't make any difference.

I have all updates as of this morning.

Stacktrace:

  at FSpot.Global..cctor () <0xffffffff>
  at FSpot.Global..cctor () <0x0000d>
  at (wrapper runtime-invoke) FSpot.Defines.runtime_invoke_void (object,intptr,intptr,intptr) <0xffffffff>
  at FSpot.Driver.Main (string[]) <0xffffffff>
  at FSpot.Driver.Main (string[]) <0x00144>
  at (wrapper runtime-invoke) FSpot.Driver.runtime_invoke_int_string[] (object,intptr,intptr,intptr) <0xffffffff>

[Sebastien Bacher (seb128)]

that should be fixed in hardy, feel free to reopen if you still get the issue though