F-spot hangs, apparently syncing JPEG information

[Paul Fisher]

Binary package hint: f-spot

F-Spot version: 0.5.0.3-1ubuntu6
Ubuntu version: 9.04

I was converting a handful of RAW files to JPEGs. Shortly after I was done, F-Spot crashed. After that, I restarted F-Spot, and it hangs. Here's a backtrace:

[Info 19:13:05.945] Initializing DBus
[Info 19:13:06.076] Initializing Mono.Addins
[Info 19:13:06.299] Starting new FSpot server
[Info 19:13:07.549] Starting DBusService
[Info 19:13:07.556] Starting BeagleService
[Info 19:13:07.556] Hack for gnome-settings-daemon engaged
Syncing metadata to file...
old = "" new = "" heading = "ASCII"
value = 2009:04:25 11:59:38 len = 19
value = f-spot version 0.5.0.3 len = 22
value = 2009:04:25 19:13:08 len = 19
value = f-spot version 0.5.0.3 len = 22
value = 2009:04:25 19:13:08 len = 19
Stacktrace:

  at (wrapper managed-to-native) Exif.ExifData.exif_data_save_data (System.Runtime.InteropServices.HandleRef,intptr&,uint&) <0x00004>
  at (wrapper managed-to-native) Exif.ExifData.exif_data_save_data (System.Runtime.InteropServices.HandleRef,intptr&,uint&) <0xffffffff>
  at Exif.ExifData.Save () <0x0006c>
  at JpegHeader.SetExif (Exif.ExifData) <0x00014>
  at FSpot.JpegFile.SaveMetaData (System.IO.Stream,System.IO.Stream) <0x0004e>
  at FSpot.JpegFile.SaveMetaData (string) <0x00095>
  at FSpot.Jobs.SyncMetadataJob.WriteMetadataToImage (FSpot.Photo) <0x001d5>
  at FSpot.Jobs.SyncMetadataJob.Execute () <0x0008b>
  at Job.Run () <0x0001a>
  at Banshee.Kernel.Scheduler.ProcessJobThread () <0x0015d>
  at (wrapper runtime-invoke) System.Object.runtime_invoke_void__this__ (object,intptr,intptr,intptr) <0xffffffff>

Native stacktrace:

 f-spot [0x806d944]
 f-spot [0x808616b]
 [0xb7f97410]
 /usr/lib/libexif.so.12(exif_set_short+0x2c) [0xb415531c]
 /usr/lib/libexif.so.12 [0xb414c4a3]
 /usr/lib/libexif.so.12 [0xb414c66e]
 /usr/lib/libexif.so.12(exif_data_save_data+0x108) [0xb414cd28]
 [0xa0fe0cea]
 [0xa0fe0c4d]
 [0xa0fe0b85]
 [0xa0fe0ac7]
 [0xa0fe022e]
 [0xa1654836]
 [0xb3e91a74]
 [0xb3e919bb]
 [0xb4feb2a6]
 [0xb70b6559]
 f-spot(mono_runtime_delegate_invoke+0x34) [0x80b8974]
 f-spot [0x80f76bf]
 f-spot [0x81653b6]
 f-spot [0x81833b5]
 /lib/tls/i686/cmov/libpthread.so.0 [0xb7e9d4ff]
 /lib/tls/i686/cmov/libc.so.6(clone+0x5e) [0xb7df249e]

Debug info from gdb:

(no debugging symbols found)

[Paul Fisher (thetorpedodog)]

Launched it again, got more data:

[Info 19:45:49.394] Initializing DBus
[Info 19:45:49.538] Initializing Mono.Addins
[Info 19:45:49.889] Starting new FSpot server
[Info 19:45:51.353] Starting DBusService
[Info 19:45:51.361] Starting BeagleService
[Info 19:45:51.362] Hack for gnome-settings-daemon engaged
Syncing metadata to file...
old = "" new = "" heading = "ASCII"
value = 2009:04:25 11:59:38 len = 19
value = f-spot version 0.5.0.3 len = 22
value = 2009:04:25 19:45:51 len = 19
value = f-spot version 0.5.0.3 len = 22
value = 2009:04:25 19:45:52 len = 19
Stacktrace:

  at (wrapper managed-to-native) Exif.ExifData.exif_data_save_data (System.Runtime.InteropServices.HandleRef,intptr&,uint&) <0x00004>
  at (wrapper managed-to-native) Exif.ExifData.exif_data_save_data (System.Runtime.InteropServices.HandleRef,intptr&,uint&) <0xffffffff>
  at Exif.ExifData.Save () <0x0006c>
  at JpegHeader.SetExif (Exif.ExifData) <0x00014>
  at FSpot.JpegFile.SaveMetaData (System.IO.Stream,System.IO.Stream) <0x0004e>
  at FSpot.JpegFile.SaveMetaData (string) <0x00095>
  at FSpot.Jobs.SyncMetadataJob.WriteMetadataToImage (FSpot.Photo) <0x001d5>
  at FSpot.Jobs.SyncMetadataJob.Execute () <0x0008b>
  at Job.Run () <0x0001a>
  at Banshee.Kernel.Scheduler.ProcessJobThread () <0x0015d>
  at (wrapper runtime-invoke) System.Object.runtime_invoke_void__this__ (object,intptr,intptr,intptr) <0xffffffff>

Native stacktrace:

 f-spot [0x806d944]
 f-spot [0x808616b]
 [0xb7f59410]
 /usr/lib/libexif.so.12(exif_set_short+0x2c) [0xb411531c]
 /usr/lib/libexif.so.12 [0xb410c4a3]
 /usr/lib/libexif.so.12 [0xb410c66e]
 /usr/lib/libexif.so.12(exif_data_save_data+0x108) [0xb410cd28]
 [0xa0daf5a2]
 [0xa0daf505]
 [0xa0daf43d]
 [0xa0daf37f]
 [0xa0daeae6]
 [0xa1621bae]
 [0xb3b4f51c]
 [0xb3b4f463]
 [0xb4faf116]
 [0xb7076559]
 f-spot(mono_runtime_delegate_invoke+0x34) [0x80b8974]
 f-spot [0x80f76bf]
 f-spot [0x81653b6]
 f-spot [0x81833b5]
 /lib/tls/i686/cmov/libpthread.so.0 [0xb7e5e4ff]
 /lib/tls/i686/cmov/libc.so.6(clone+0x5e) [0xb7db349e]

Debug info from gdb:

(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb7c9b6e0 (LWP 10233)]
[New Thread 0xb3c56b90 (LWP 10243)]
[New Thread 0xb3d57b90 (LWP 10242)]
[New Thread 0xb44f5b90 (LWP 10238)]
[New Thread 0xb45f6b90 (LWP 10237)]
[New Thread 0xb73a5b90 (LWP 10235)]
[New Thread 0xb7f45b90 (LWP 10234)]
0xb4183820 in cmsEvalMatShaper () from /usr/lib/liblcms.so.1
  7 Thread 0xb7f45b90 (LWP 10234) 0xb7f59430 in __kernel_vsyscall ()
  6 Thread 0xb73a5b90 (LWP 10235) 0xb7f59430 in __kernel_vsyscall ()
  5 Thread 0xb45f6b90 (LWP 10237) 0xb7f59430 in __kernel_vsyscall ()
  4 Thread 0xb44f5b90 (LWP 10238) 0xb7f59430 in __kernel_vsyscall ()
  3 Thread 0xb3d57b90 (LWP 10242) 0xb7f59430 in __kernel_vsyscall ()
  2 Thread 0xb3c56b90 (LWP 10243) 0xb7f59430 in __kernel_vsyscall ()
  1 Thread 0xb7c9b6e0 (LWP 10233) 0xb4183820 in cmsEvalMatShaper ()
   from /usr/lib/liblcms.so.1

Thread 7 (Thread 0xb7f45b90 (LWP 10234)):
#0 0xb7f59430 in __kernel_vsyscall ()
#1 0xb7e658f6 in nanosleep () from /lib/tls/i686/cmov/libpthread.so.0
#2 0x081492e8 in ?? ()
#3 0xb7e5e4ff in start_thread () from /lib/tls/i686/cmov/libp...

[Pedro Villavicencio (pedro)]

thanks for the report Paul, any chance to attach the jpeg file that 's causing the issue to the report?

[Pedro Villavicencio (pedro)]

could be a libexif crash.

[Paul Fisher (thetorpedodog)]

It looks to me like it's one of these 7 JPEGs (hosted on my reasonably-well-connected-and-reliable home computer):

http://munin.rh.rit.edu/f-spot-jpegs/

The issue started when I shifted their timestamps after "developing" them from Olympus RAW data using UFRaw.

[Sebastien Bacher (seb128)]

the bug should be sent to the software writters on bugzilla.gnome.org by somebody having the issue

[Pedro Villavicencio (pedro)]

did somebody sent this upstream ? may you tell us the bug number there?

[Pedro Villavicencio (pedro)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don\'t hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.