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 547911 - F-Spot crashes on clicking Import button
F-Spot crashes on clicking Import button
Status: RESOLVED INCOMPLETE
Product: f-spot
Classification: Other
Component: Import
SVN
Other All
: Normal critical
: ---
Assigned To: F-spot maintainers
F-spot maintainers
Depends on:
Blocks:
 
 
Reported: 2008-08-15 13:52 UTC by Alexandre Prokoudine
Modified: 2009-03-22 13:43 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Alexandre Prokoudine 2008-08-15 13:52:03 UTC
Steps to reproduce:
1. Compile and run F-Spot from trunk (revision 4269)
2. Click Import button
3. F-Spot crashes


Stack trace:
[avp@localhost f-spot]$ mono --debug /usr/lib/f-spot/f-spot.exe
[Info  17:47:18.033] Initializing DBus
[Info  17:47:18.186] Initializing Mono.Addins
[Info  17:47:18.446] Starting new FSpot server
/home/avp/.esd_auth: File exists
/home/avp/.esd_auth: File exists
/home/avp/.esd_auth: File exists
/home/avp/.esd_auth: File exists
/home/avp/.esd_auth: File exists
/home/avp/.esd_auth: File exists
/home/avp/.esd_auth: File exists
/home/avp/.esd_auth: File exists
/home/avp/.esd_auth: File exists
/home/avp/.esd_auth: File exists
/home/avp/.esd_auth: File exists
/home/avp/.esd_auth: File exists
[Info  17:47:20.565] Starting BeagleService
Exeption while reading jpeg headers
System.Exception: Invalid marker found 194
  at JpegHeader+Marker.Load (System.IO.Stream stream) [0x00000] 
  at JpegHeader.Load (System.IO.Stream stream, Boolean metadata_only) [0x00000] 
  at JpegHeader..ctor (System.IO.Stream stream, Boolean metadata_only) [0x00000] 
error checking orientation
GLib.GException: Unrecognized image file format
  at Gdk.PixbufLoader.Write (System.Byte[] buf, UInt64 count) [0x00000] 
  at PixbufUtils+AspectLoader.Load (System.IO.Stream stream, PixbufOrientation orientation) [0x00000] 
  at FSpot.ImageFile.Load (Int32 max_width, Int32 max_height) [0x00000] 
  at PixbufLoader.ProcessRequest (.RequestItem request) [0x00000] 
Exeption while reading jpeg headers
System.Exception: Invalid marker found 213
  at JpegHeader+Marker.Load (System.IO.Stream stream) [0x00000] 
  at JpegHeader.Load (System.IO.Stream stream, Boolean metadata_only) [0x00000] 
  at JpegHeader..ctor (System.IO.Stream stream, Boolean metadata_only) [0x00000] 
error checking orientation
GLib.GException: Unrecognized image file format
  at Gdk.PixbufLoader.Write (System.Byte[] buf, UInt64 count) [0x00000] 
  at PixbufUtils+AspectLoader.Load (System.IO.Stream stream, PixbufOrientation orientation) [0x00000] 
  at FSpot.ImageFile.Load (Int32 max_width, Int32 max_height) [0x00000] 
  at PixbufLoader.ProcessRequest (.RequestItem request) [0x00000] 
Exeption while reading jpeg headers
System.Exception: Invalid marker found 183
  at JpegHeader+Marker.Load (System.IO.Stream stream) [0x00000] 
  at JpegHeader.Load (System.IO.Stream stream, Boolean metadata_only) [0x00000] 
  at JpegHeader..ctor (System.IO.Stream stream, Boolean metadata_only) [0x00000] 
error checking orientation
GLib.GException: Unrecognized image file format
  at Gdk.PixbufLoader.Write (System.Byte[] buf, UInt64 count) [0x00000] 
  at PixbufUtils+AspectLoader.Load (System.IO.Stream stream, PixbufOrientation orientation) [0x00000] 
  at FSpot.ImageFile.Load (Int32 max_width, Int32 max_height) [0x00000] 
  at PixbufLoader.ProcessRequest (.RequestItem request) [0x00000] 
/home/avp/.esd_auth: File exists
Exeption while reading jpeg headers
System.Exception: Invalid marker found 85
  at JpegHeader+Marker.Load (System.IO.Stream stream) [0x00000] 
  at JpegHeader.Load (System.IO.Stream stream, Boolean metadata_only) [0x00000] 
  at JpegHeader..ctor (System.IO.Stream stream, Boolean metadata_only) [0x00000] 
error checking orientation
GLib.GException: Unrecognized image file format
  at Gdk.PixbufLoader.Write (System.Byte[] buf, UInt64 count) [0x00000] 
  at PixbufUtils+AspectLoader.Load (System.IO.Stream stream, PixbufOrientation orientation) [0x00000] 
  at FSpot.ImageFile.Load (Int32 max_width, Int32 max_height) [0x00000] 
  at PixbufLoader.ProcessRequest (.RequestItem request) [0x00000] 
EOS_DIGITAL - gnome-dev-media-cf - Mountpoint file:///media/EOS_DIGITAL True True MemoryStick
MemoryStick
Exception in Gtk# callback delegate
  Note: Applications can use GLib.ExceptionManager.UnhandledException to handle the exception.
System.DllNotFoundException: libgphoto2.so.2
  at (wrapper managed-to-native) LibGPhoto2.Context:gp_context_new ()
  at LibGPhoto2.Context..ctor () [0x00000] 
  at GPhotoCamera..ctor () [0x00000] 
  at ImportCommand+SourceMenu..ctor (.ImportCommand command) [0x00000] 
  at ImportCommand.ImportFromFile (.PhotoStore store, System.String path) [0x00000] 
  at MainWindow.HandleImportCommand (System.Object sender, System.EventArgs e) [0x00000] 
  at GLib.Signal.voidObjectCallback (IntPtr handle, IntPtr data) [0x00000] 
   at GLib.ExceptionManager.RaiseUnhandledException(System.Exception e, Boolean is_terminal)
   at GLib.Signal.voidObjectCallback(IntPtr handle, IntPtr data)
   at GLib.Signal.voidObjectCallback(IntPtr , IntPtr )
   at Gtk.Application.gtk_main()
   at Gtk.Application.gtk_main()
   at Gtk.Application.Run()
   at Gnome.Program.Run()
   at FSpot.Driver.Main(System.String[] args)
cleanup context
Segmentation fault


Other information:
Comment 1 Stephane Delcroix 2008-08-18 07:37:44 UTC
> System.DllNotFoundException: libgphoto2.so.2

do you have it installed ???
Comment 2 Alexandre Prokoudine 2008-08-18 11:12:34 UTC
$ locate libgphoto2.so  
/usr/lib/libgphoto2.so
/usr/lib/libgphoto2.so.6
/usr/lib/libgphoto2.so.6.0.0
Comment 3 Maxxer 2008-09-01 08:48:49 UTC
did you perhaps update libgphoto without re-compiling (re-configuring) f-spot?
Comment 4 Stephane Delcroix 2008-09-15 12:06:49 UTC
which version of libgphoto2 are you using ?
 
I just compiled the latest one, and the .so is still named .2.3.0

if it's named .6 on your machine, it means some kind of api breakage, so that all our bindings needs to be fixed
Comment 5 Tobias Mueller 2009-03-22 13:43:01 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!