After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 323330 - F-Spot crashes after running once
F-Spot crashes after running once
Status: RESOLVED FIXED
Product: f-spot
Classification: Other
Component: General
0.1.3
Other All
: High critical
: ---
Assigned To: F-spot maintainers
F-spot maintainers
Depends on:
Blocks:
 
 
Reported: 2005-12-06 01:42 UTC by Andrew Mitchell
Modified: 2006-04-09 22:34 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Andrew Mitchell 2005-12-06 01:42:47 UTC
Steps to reproduce:
1. Run program, close it
2. Crash on next start


Stack trace:
Package: f-spot
Version: 0.1.3-1
Severity: grave
Justification: renders package unusable

F-spot works fine the first time it is run, I can import, browse,
add tags etc. However as soon as I quit it, it will no longer run the 
next time, instead it crashes giving this message:

Unhandled Exception: System.NullReferenceException: Object reference not
set to an instance of an object
in <0x001e5> PhotoStore:Query (System.String query)
in <0x005b4> PhotoStore:Query (.Tag[] tags, .DateRange range)
in <0x0002c> FSpot.PhotoQuery:.ctor (.PhotoStore store)
in <0x006fe> MainWindow:.ctor (.Db db)
in <0x00039> FSpot.Core:get_MainWindow ()
in <0x00018> FSpot.Core:Organize ()
in <0x00559> Driver:Main (System.String[] args)

When I delete/move the file .gnome2/f-spot/photos.db it will start
again, but then, of course, all my sorting is gone.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12-1-amd64-k8
Locale: LANG=sv_SE.UTF-8, LC_CTYPE=sv_SE.UTF-8 (charmap=UTF-8)

Versions of packages f-spot depends on:
ii  libc6                         2.3.5-7    GNU C Library: Shared libraries an
ii  libdbus-cil                   0.23.4-7   CLI binding for D-BUS interprocess
ii  libexif12                     0.6.12-2   library to parse EXIF files
ii  libgconf2.0-cil               2.3.92-2   CLI binding for GConf 2.0, unstabl
ii  libglade2.0-cil               2.3.92-2   CLI binding for the Glade librarie
ii  libglib2.0-0                  2.8.3-1    The GLib library of C routines
ii  libglib2.0-cil                2.3.92-2   CLI binding for the GLib utility l
ii  libgnome2.0-cil               2.3.92-2   CLI binding for GNOME 2.0, unstabl
ii  libgnomeui-0                  2.10.1-1   The GNOME 2 libraries (User Interf
di  libgnomevfs2-0                2.10.1-5   The GNOME virtual file-system libr
ii  libgphoto2-2                  2.1.6-5.2  gphoto2 digital camera library
ii  libgtk2.0-0                   2.6.10-1   The GTK+ graphical user interface 
ii  libgtk2.0-cil                 2.3.92-2   CLI binding for the Gtk+ toolkit 2
ii  libjpeg62                     6b-10      The Independent JPEG Group's JPEG 
ii  liblcms1                      1.13-1     Color management library
ii  libmono0                      1.1.9.2-1  libraries for the Mono JIT
ii  libsqlite0                    2.8.16-1   SQLite shared library
ii  mono-classlib-1.0             1.1.9.2-1  Mono class library (1.0)
ii  mono-jit                      1.1.9.2-1  fast CLI (.NET) JIT compiler for M

f-spot recommends no packages.

-- no debconf information

Other information:
As Debian maintainer I can't reproduce this on my system, but I've received 3
bug reports of this happening (2 debian, 1 ubuntu). I suspect some photos or
actions may trigger it, which I don't do.
Comment 1 Andrew Mitchell 2005-12-06 02:00:32 UTC
Looks like I missed this when reported as
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=330568 (same exceptions thrown)
Comment 2 Andrew Mitchell 2005-12-30 10:37:16 UTC
This also occurs with 0.1.5 according to the debian bug reporter
Comment 3 Larry Ewing 2006-01-09 05:10:00 UTC
I can't reproduce this at all.  Can one of you edit the f-spot script and add --debug to the mono command line then paste that stack trace?
Comment 4 Bengt Thuree 2006-02-20 04:56:08 UTC
Any possibility of getting a stack trace, and/or a photo that causes the problem?
Comment 5 Larry Ewing 2006-02-26 02:40:59 UTC
I'm marking this needinfo because there is nothing I can do until some more info is available.  As soon as you hear back from the reporters reopen it.
Comment 6 Larry Ewing 2006-03-02 15:54:16 UTC
ok this bug appears to be caused by a 64bit unclean problem in the mono sqlite bindings that is fixed in mono-1.1.13.4
Comment 7 mriester 2006-04-08 22:29:09 UTC
have the same problems with an uptodate debian unstable. worked once, restart:

Starting new FSpot server

Unhandled Exception: System.NullReferenceException: Object reference not set to an instance of an object
in <0x000c6> TagStore:LoadAllTags ()
in <0x0005c> TagStore:.ctor (Mono.Data.SqliteClient.SqliteConnection connection, Boolean is_new)
in <0x000c2> Db:.ctor (System.String path, Boolean create_if_missing)
in <0x002f1> Driver:Main (System.String[] args)
Comment 8 mriester 2006-04-09 22:34:20 UTC
f-spot was updated today in debian unstable and now everything works fine.