Package: f-spot Version: 0.3.5-1
When I run F-spot from the command-line, this is what happens: Starting new FSpot server XXXXX System.ArgumentNullException: Argument cannot be null. Parameter name: s 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 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... <continues forever..> This causes F-Spot to consume the entire CPU as it tries to start a new FSpot server several times per second. Running on a Debian unstable machine that has been recently upgraded from a fresh install of etch. uname -a Linux icarus 2.6.21-2-amd64 #1 SMP Mon Jun 25 22:01:38 CEST 2007 x86_64 GNU/Linux
