No conversion & bad error message with SQLite 2.x database
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
F-Spot |
Invalid
|
Critical
|
|||
f-spot (Ubuntu) |
Fix Released
|
Low
|
Unassigned |
Bug Description
Binary package hint: f-spot
Ok, Andrew told me to open up a new bug, here it is :)
This is what I get when I start f-spot on my installed edgy system:
Starting new FSpot server
XXXXX
Mono.Data.
at Mono.Data.
at Mono.Data.
at Mono.Data.
at MetaStore.
at MetaStore..ctor (Mono.Data.
at Db.Init (System.String path, Boolean create_if_missing) [0x00000]
at FSpot.Core..ctor () [0x00000]
at FSpot.Driver.Main (System.String[] args) [0x00000]
XXXXX
Starting new FSpot server
Starting new FSpot server
Starting new FSpot server
=======
Got a SIGSEGV while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.
=======
Stacktrace:
at (wrapper managed-to-native) System.
at (wrapper managed-to-native) System.
at System.
at (wrapper synchronized) DBus.Service.
at FSpot.Core.
at (wrapper runtime-invoke) System.
Native stacktrace:
mono [0x8122f18]
mono [0x80c3af3]
mono [0x80af143]
mono [0x8115b81]
mono [0x80af277]
mono [0x80c6484]
mono [0x8109ade]
mono [0x811fe85]
Aborted (core dumped)
Hopefully this information is useful!
Changed in f-spot: | |
status: | Unknown → Rejected |
Changed in f-spot: | |
assignee: | sikon → nobody |
status: | Incomplete → Fix Released |
Changed in f-spot: | |
importance: | Unknown → Critical |
Thanks, do you have /home on NFS, or did you run f-spot back in breezy/early dapper when the default database version was sqlite 2?