[feisty] f-spot does not start

Bug #81905 reported by Janek
22
This bug affects 1 person
Affects Status Importance Assigned to Milestone
f-spot (Ubuntu)
Invalid
Undecided
Unassigned
Nominated for Feisty by Janek

Bug Description

Binary package hint: f-spot

When I try to start f-spot in feisty I get the following in the console:

[code]
$ f-spot
Starting new FSpot server
XXXXX
Mono.Data.SqliteClient.SqliteSyntaxException: no such table: tags
  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.ExecuteReader (CommandBehavior behavior) [0x00000]
  at Mono.Data.SqliteClient.SqliteCommand.ExecuteReader () [0x00000]
  at TagStore.LoadAllTags () [0x00000]
  at TagStore..ctor (Mono.Data.SqliteClient.SqliteConnection connection, Boolean is_new) [0x00000]
  at Db.Init (System.String path, Boolean create_if_missing) [0x00000]
  at FSpot.Core..ctor (Boolean nodb) [0x00000]
  at FSpot.Driver.Main (System.String[] args) [0x00000]
XXXXX
Starting new FSpot server
Starting new FSpot server
Starting new FSpot server
Starting new FSpot server
Starting new FSpot server
Starting new FSpot server
Starting new FSpot server
Starting new FSpot server
Starting new FSpot server
Starting new FSpot server
Starting new FSpot server
Starting new FSpot server
Starting new FSpot server
...
[/code]

The "Starting new FSpot server"'s don't stop and the RAM is getting filled more and more...
That's also after upgrading to F-Sport 0.3.2.
When I give the -b/-basedir option f-spot starts without any problems.

Revision history for this message
Brad Johnson (brad-bkjohnson) wrote :

F-Spot error details:

An unhandled exception was thrown: GL

  at (wrapper managed-to-native) GdkGlx.Context:glXChooseVisual (intptr,int,int[])
  at GdkGlx.Context..ctor (Gdk.Screen screen, GdkGlx.Context share_list, System.Int32[] attr) [0x00000]
  at GdkGlx.Context..ctor (Gdk.Screen screen, System.Int32[] attr) [0x00000]
  at FSpot.PhotoImageView.HandleRealized (System.Object sender, System.EventArgs args) [0x00000]
  at FSpot.PhotoImageView..ctor (IBrowsableCollection query) [0x00000]
  at FSpot.PhotoView..ctor (IBrowsableCollection query) [0x00000]
  at MainWindow..ctor (.Db db) [0x00000]
  at FSpot.Core.get_MainWindow () [0x00000]
  at FSpot.Core.Organize () [0x00000]
  at FSpot.Driver.Main (System.String[] args) [0x00000]
.NET Version: 2.0.50727.42

Assembly Version Information:

google-sharp (0.1.0.0)
FlickrNet (2.1.2.3191)
SmugMugNet (0.0.0.0)
pango-sharp (2.10.0.0)
SemWeb (0.7.1.0)
glade-sharp (2.10.0.0)
gtkhtml-sharp (2.16.0.0)
gconf-sharp (2.16.0.0)
System.Data (2.0.0.0)
Mono.Data.SqliteClient (2.0.0.0)
gdk-sharp (2.10.0.0)
gnome-vfs-sharp (2.16.0.0)
NDesk.DBus (0.0.0.0)
System (2.0.0.0)
Mono.Posix (2.0.0.0)
NDesk.DBus.GLib (0.0.0.0)
atk-sharp (2.10.0.0)
gtk-sharp (2.10.0.0)
glib-sharp (2.10.0.0)
gnome-sharp (2.16.0.0)
f-spot (0.3.2.0)
Mono.GetOptions (2.0.0.0)
mscorlib (2.0.0.0)

Platform Information: Linux 2.6.20-6-generic i686 unknown GNU/Linux

Distribution Information:

[/etc/debian_version]
4.0

[/etc/lsb-release]
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=7.04
DISTRIB_CODENAME=feisty
DISTRIB_DESCRIPTION="Ubuntu feisty (development branch)"

Revision history for this message
Dean Sas (dsas) wrote :

Brad: Your error is a different one being tracked as bug 81578. Thanks for reporting.

Revision history for this message
Emiliano (emiliano-perulli) wrote :

Exactly the same error that happens to me in the Ubuntu/Edgy ver.

Revision history for this message
Janek (thefoxx) wrote :

Today I upgraded to f-spot 0.3.3 but there is still the same problem.

Revision history for this message
Emiliano (emiliano-perulli) wrote :

I guess the bug is generated by the security update for the mono libraries, I haven't still tried to downgrade them, but f-spot worked with the older libmono version

Revision history for this message
Emiliano (emiliano-perulli) wrote :

- b/ basedir option? What does it mean? I'm a novice

Revision history for this message
Guy Gibson (techhead) wrote :

Also getting F-spot exception error

guy@pinot:~$ f-spot
Starting new FSpot server

(f-spot:29432): libglade-WARNING **: unknown attribute `comment' for <property>.
System.DllNotFoundException: GL
  at (wrapper managed-to-native) GdkGlx.Context:glXChooseVisual (intptr,int,int[])
  at GdkGlx.Context..ctor (Gdk.Screen screen, GdkGlx.Context share_list, System.Int32[] attr) [0x00000]
  at GdkGlx.Context..ctor (Gdk.Screen screen, System.Int32[] attr) [0x00000]
  at FSpot.PhotoImageView.HandleRealized (System.Object sender, System.EventArgs args) [0x00000]
  at FSpot.PhotoImageView..ctor (IBrowsableCollection query) [0x00000]
  at FSpot.PhotoView..ctor (IBrowsableCollection query) [0x00000]
  at MainWindow..ctor (.Db db) [0x00000]
  at FSpot.Core.get_MainWindow () [0x00000]
  at FSpot.Core.Organize () [0x00000]
  at FSpot.Driver.Main (System.String[] args) [0x00000]
guy@pinot:~$

Revision history for this message
Janek (thefoxx) wrote :

@Emillano:
$ f-spot --help
...
-b -basedir:PARAM path to the photo database folder
...

Revision history for this message
Janek (thefoxx) wrote :

today, I tryed f-spot again without any parameters and got the following:

$ f-spot
Starting new FSpot server
XXXXX
Mono.Data.SqliteClient.SqliteSyntaxException: no such table: tags
  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.ExecuteReader (CommandBehavior behavior) [0x00000]
  at Mono.Data.SqliteClient.SqliteCommand.ExecuteReader () [0x00000]
  at (wrapper remoting-invoke-with-check) Mono.Data.SqliteClient.SqliteCommand:ExecuteReader ()
  at TagStore.LoadAllTags () [0x00000]
  at TagStore..ctor (Mono.Data.SqliteClient.SqliteConnection connection, Boolean is_new) [0x00000]
  at Db.Init (System.String path, Boolean create_if_missing) [0x00000]
  at FSpot.Core..ctor (Boolean nodb) [0x00000]
  at FSpot.Driver.Main (System.String[] args) [0x00000]
XXXXX
Cant' get a connection to the dbus. Trying again...
Starting new FSpot server
Cant' get a connection to the dbus. Trying again...
Starting new FSpot server
Cant' get a connection to the dbus. Trying again...
Starting new FSpot server
Cant' get a connection to the dbus. Trying again...
Starting new FSpot server
Cant' get a connection to the dbus. Trying again...
Starting new FSpot server
Cant' get a connection to the dbus. Trying again...
Starting new FSpot server
....

Maybe this can help you. In past, there where many problemlos with other applications using python-apport (Okay, I don't think that a mono application uses Python modules :))

Revision history for this message
Marco Aicardi (launchpad-net-aicardi) wrote :

Same problem here.

I just re-installed from scratch Kubuntu Feisty Fawn 7.04 Beta, which has got F-Spot 0.35 packaged.

F-Spot refuse to run, this is the output:

marco@rolly:~$ f-spot
Starting new FSpot server
XXXXX
System.FormatException: Input string was not in the correct format
  at System.Int32.Parse (System.String s) [0x00000]
  at MetaItem.get_ValueAsInt () [0x00000]
  at FSpot.Database.Updater.Run (.Db database) [0x00000]
  at Db.Init (System.String path, Boolean create_if_missing) [0x00000]
  at FSpot.Core..ctor (Boolean nodb) [0x00000]
  at FSpot.Driver.Main (System.String[] args) [0x00000]
XXXXX
Cant' get a connection to the dbus. Trying again...
Starting new FSpot server
Cant' get a connection to the dbus. Trying again...
Starting new FSpot server
....................

Adding the -b/-basedir option, F-Spot lauches with no problem.

Marco

Revision history for this message
Janek (thefoxx) wrote :

Can anybody fix this bug? When this isn't fixed in feisty stable f-spot is unusable for many people (The most people don't know the trick with the -b/-basedir option!)

Revision history for this message
Emiliano (emiliano-perulli) wrote :

By the way the -b/ -basedir option seems don't work with the version bundled in edgy

Revision history for this message
Amon_Re (ochal) wrote :

Your problems are with the old f-spot database, you seem to be lacking the table "tags".

Do this:

Go to the terminal, and type in the following command:

sqlite ~/.gnome2/f-spot/photos.db

You'll get an sql prompt, at this prompt type:
.tables

You should get a list of all tables present in the database, on my system, this is my output:

ochal@Homer:/$ sqlite ~/.gnome2/f-spot/photos.db
SQLite version 2.8.17
Enter ".help" for instructions
sqlite> .tables
exports meta photo_versions tags
imports photo_tags photos
sqlite>

Notice the presence of the table "tags", if you lack this table, you should be able to add it sqlite.

this is what the table should be:

TABLE tags ( id INTEGER PR
IMARY KEY NOT NULL, name TEXT UNIQUE, cate
gory_id INTEGER, is_category BOOLEAN,
                          sort_priority INTEGER,
  icon TEXT );

Notice that you'll need sqlite and not sqlite3

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Thanks in advance.

Changed in f-spot:
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.

Changed in f-spot:
status: Incomplete → Invalid
Revision history for this message
Jeffrey Patrick Lui (punong-bisyonaryo) wrote :

This happened in Gutsy for me, out of the blue. I got the same error message as the original reporter of the bug, and this was not due to an upgrade. I have been using f-spot for quite a while and have four years' worth of tag data. For my case, it was not an outdated db problem; it was already sqlite 3.x for a long time. Further, sqlite couldn't open my db file. I needed sqlite3. Opening the file, I find that I have nothing left but the meta table (WT?!?!). Now I have 6564 photos that all need to be retagged. This is a serious bug, or at least f-spot needs better failure tolerance i.e. auto-backup/recovery/rollback.

Revision history for this message
phill.wall@gmail.com (phill-wall) wrote :

I tried running the suggested command and it failed - unable to connect.
 I tried a number of things (tried to make sure SQLLITE was installed etc) and got no where.

however - eventually I looked to see if photos.db existed and it did... and as I couldnt seem to login to look at the Schema, i deleted it (got the idea from another logged problem). When I deleted it, f-spot started OK//

Thanks
Phill

Revision history for this message
Matthias Rahlf (rahlf) wrote :

I had to move the old database out of the way: "mv ~/.config/f-spot ~/.config/f-spot.old".
Then everything worked.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.