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 167777 - Viewing EXIF tags crashes f-spot
Viewing EXIF tags crashes f-spot
Status: RESOLVED FIXED
Product: f-spot
Classification: Other
Component: Browsing
CVS
Other All
: High critical
: ---
Assigned To: F-spot maintainers
F-spot maintainers
Depends on:
Blocks:
 
 
Reported: 2005-02-18 04:50 UTC by Bengt Thuree
Modified: 2005-02-20 11:12 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
A picture with EXIF and IPTC tags that cause f-spot to crash (723.22 KB, image/jpeg)
2005-02-18 12:12 UTC, Bengt Thuree
Details

Description Bengt Thuree 2005-02-18 04:50:27 UTC
Steps to reproduce:
1. select a photo with a lot of different EXIF tags
2. View EXIF tags
3. Crash!


Stack trace:
(F-Spot:20162): GLib-GObject-CRITICAL **: g_signal_emit_valist:
assertion `signal_id > 0' failed

(F-Spot:20162): GLib-GObject-CRITICAL **: g_signal_emit_valist:
assertion `signal_id > 0' failed

(F-Spot:20162): GLib-GObject-CRITICAL **: g_signal_emit_valist:
assertion `signal_id > 0' failed

(F-Spot:20162): GLib-GObject-CRITICAL **: g_signal_emit_valist:
assertion `signal_id > 0' failed

(F-Spot:20162): GLib-GObject-CRITICAL **: g_signal_emit_valist:
assertion `signal_id > 0' failed

(F-Spot:20162): GLib-GObject-CRITICAL **: g_signal_emit_valist:
assertion `signal_id > 0' failed

(F-Spot:20162): GLib-GObject-CRITICAL **: g_signal_emit_valist:
assertion `signal_id > 0' failed

(F-Spot:20162): GLib-GObject-CRITICAL **: g_signal_emit_valist:
assertion `signal_id > 0' failed

Unhandled Exception: System.NullReferenceException: Object reference not
set to an instance of an object
in (unmanaged) Exif.ExifEntry:get_Value ()
in [0x00031] (at /home/bengt/CVS/f-spot/f-spot-0.0.7/src/Exif.cs:679)
Exif.ExifEntry:get_Value ()
in [0x0014d] (at
/home/bengt/CVS/f-spot/f-spot-0.0.7/src/InfoDisplay.cs:81)
FSpot.InfoDisplay:Update ()
in [0x0004b] (at
/home/bengt/CVS/f-spot/f-spot-0.0.7/src/InfoDisplay.cs:29)
FSpot.InfoDisplay:set_Photo (Photo)
in [0x0007d] (at
/home/bengt/CVS/f-spot/f-spot-0.0.7/src/MainWindow.cs:896)
MainWindow:HandleViewFullExif (object,System.EventArgs)
in <0x00069> (wrapper delegate-invoke)
System.MulticastDelegate:invoke_void_object_EventArgs
(object,System.EventArgs)
in <0x0012d> GtkSharp.voidObjectSignal:voidObjectCallback (intptr,int)
in <0x0005a> (wrapper native-to-managed)
GtkSharp.voidObjectSignal:voidObjectCallback (intptr,int)
in (unmanaged) (wrapper managed-to-native) Gtk.Application:gtk_main ()
in <0x00004> (wrapper managed-to-native) Gtk.Application:gtk_main ()
in <0x00007> Gtk.Application:Run ()
in <0x00007> Gnome.Program:Run ()
in [0x00076] (at /home/bengt/CVS/f-spot/f-spot-0.0.7/src/main.cs:30)
Driver:Main (string[])


Other information:
A photo can be submitted upon request.
I have in general the following tags created
Copyright, owner, timestamp, country, city, location, heading, tags, comment
(Both EXIF and IPTC data)
Comment 1 Larry Ewing 2005-02-18 05:22:23 UTC
what version of libexif do you have?
Comment 2 Bengt Thuree 2005-02-18 07:31:57 UTC
Ubuntu Hoary

/var/cache/apt/archives/libexif10_0.6.9-4_i386.deb
/var/cache/apt/archives/libexif-gtk4_0.3.3-6_i386.deb
/var/cache/apt/archives/libexif-dev_0.6.9-4_i386.deb
Comment 3 Bengt Thuree 2005-02-18 12:12:58 UTC
Created attachment 37635 [details]
A picture with EXIF and IPTC tags that cause f-spot to crash

I downloaded the EXIFUtils software for Linux
(http://www.hugsan.com/EXIFutils/html/downloads.html) and below is the extract
from this software. As you can see I am using both EXIF and IPTC tags.

bengt@jolly:~/EXIFutilsLinux2.5 $ ./exiflist /tmp/20000825_KohSamui_014.JPG
FILE: /tmp/20000825_KohSamui_014.JPG

Camera
  X Resolution		   : 180
  Y Resolution		   : 180
  Resolution Unit	   : Inch
  Date/Time Modified	   : 2004:08:28 03:14:42
  YCbCr Positioning	   : Datum Point
  Reference Black&White    : 0.00 9215.75 0.35 0.09 9280.00 0.01

Image
  EXIF Version		   : 0200
  Date/Time Taken	   : 2000:08:25 00:00:00
  Components Configuration : 01020300
  FlashPix Version	   : 0100
  Colour Space		   : sRGB
  Image Width		   : 1200
  Image Height		   : 1600

IPTC 2: Editorial
  Dataset 2 Record Version : 2
  Supplemental-Categories  : Vacation; Beach
  Byline		   : Jade and Bengt Thure'e
  City			   : Koh Samui
  Country		   : Thailand
  Headline		   : Our first Thailand vacation
  Copyright Notice	   : Jade and Bengt Thure'e

I can view the EXIF window on a few scanned pictures, but those pictures do not
have any predefined EXIF information.
Comment 4 Loz 2005-02-18 18:40:24 UTC
That picture worked fine here. I'm using libexif-0.5.12 and libexif-gtk-0.3.3,
the Exif Dialog displayed the following:

x-Resolution	180/1
y-Resolution	180/1
Resolution Unit	Inch
Date and Time	2004:08:28 03:14:42
YCbCr Positioning	co-sited
Reference Black/White	0/1, -1879048185/262151, 842006528/-1878839248,
1310722/15204352, -1862205440/262151, 33619968/-1610612733
1
EXIF
Exif Version	Exif Version 2.0
Date and Time (original)	2000:08:25 00:00:00
ComponentsConfiguration	Y Cb Cr -
FlashPixVersion	FlashPix Version 1.0
Color Space	sRGB
PixelXDimension	1200
PixelYDimension	1600
Comment 5 Larry Ewing 2005-02-20 02:13:41 UTC
this should be fixed in CVS now, please give it a try and reopen if I'm wrong.
Comment 6 Bengt Thuree 2005-02-20 08:22:10 UTC
I downloaded the latest from CVS, and did make, make install.
(error -> commented out the last row in libfspot.la, and did another make install)

Started f-spot, selected a picture, and view exif.

bengt@jolly:~/CVS/f-spot/f-spot/f-spot $ f-spot
pixbuf == null
/usr/local/bin/f-spot: line 11:  1816 Segmentation fault      mono --debug
$EXE_TO_RUN "$@"

Sorry, but I do not know how to get the extra debug information I got before.

Comment 7 Bengt Thuree 2005-02-20 09:50:04 UTC
This is the latest entry to the Changelog.

2005-02-19  Larry Ewing  <lewing@novell.com>

        * src/PixbufCache.cs: don't shrink the cache until we are done
        with loading the queue, this gives us better responsiveness while
        scrolling.
Comment 8 Bengt Thuree 2005-02-20 11:12:07 UTC
Ok, now I got the latest from CVS, and no more crashes :)
Thanks