f-spot sigsevs on AMD64

[Daeng Bo]

Binary package hint: f-spot

1) Description: Ubuntu hardy (development branch)
Release: 8.04
Linux danielbo-desktop 2.6.24-15-generic #1 SMP Fri Apr 4 03:10:59 UTC 2008 x86_64 GNU/Linux

2) f-spot_0.4.2-1ubuntu2_amd64.deb and libmono2.0-cil_1.2.6+dfsg-6ubuntu3_all.deb

3) I expect the program to launch when started from the menu or command line

4) It doesn't start. Running f-spot on 64-bit Hardy (from upgrade) results in the following error:

Stacktrace:

  at FSpot.Global..cctor () <0xffffffff>
  at FSpot.Global..cctor () <0x0000d>
  at (wrapper runtime-invoke) FSpot.Defines.runtime_invoke_void (object,intptr,intptr,intptr) <0xffffffff>
  at FSpot.Driver.Main (string[]) <0xffffffff>
  at FSpot.Driver.Main (string[]) <0x00144>
  at (wrapper runtime-invoke) FSpot.Driver.runtime_invoke_int_string[] (object,intptr,intptr,intptr) <0xffffffff>

Native stacktrace:

 f-spot [0x51bb67]
 f-spot [0x43dacd]
 /lib/libpthread.so.0 [0x7f147b1be7d0]
 /lib/libc.so.6(memcpy+0x60) [0x7f147ac49d50]
 f-spot(mono_breakpoint_clean_code+0x1b) [0x42725b]
 f-spot [0x43f78d]
 f-spot [0x44005e]
 [0x4145a15b]

Debug info from gdb:

(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x7f147be977a0 (LWP 27493)]
[New Thread 0x40df6950 (LWP 27495)]
[New Thread 0x4063f950 (LWP 27494)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0x00007f147ac6ac4b in fork () from /lib/libc.so.6
  3 Thread 0x4063f950 (LWP 27494) 0x00007f147b1bde81 in nanosleep ()
   from /lib/libpthread.so.0
  2 Thread 0x40df6950 (LWP 27495) 0x00007f147b1bab99 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
  1 Thread 0x7f147be977a0 (LWP 27493) 0x00007f147ac6ac4b in fork ()
   from /lib/libc.so.6

Thread 3 (Thread 0x4063f950 (LWP 27494)):
#0 0x00007f147b1bde81 in nanosleep () from /lib/libpthread.so.0
#1 0x00000000004b8f4f in ?? ()
#2 0x00007f147b1b63f7 in start_thread () from /lib/libpthread.so.0
#3 0x00007f147aca4b2d in clone () from /lib/libc.so.6
#4 0x0000000000000000 in ?? ()

Thread 2 (Thread 0x40df6950 (LWP 27495)):
#0 0x00007f147b1bab99 in pthread_cond_wait@@GLIBC_2.3.2 ()
   from /lib/libpthread.so.0
#1 0x00000000004bb585 in ?? ()
#2 0x00000000004bdb37 in ?? ()
#3 0x00000000004cbc03 in ?? ()
#4 0x000000000046b3c1 in ?? ()
#5 0x00000000004855c3 in ?? ()
#6 0x00000000004cb287 in ?? ()
#7 0x00000000004e07d2 in ?? ()
#8 0x00007f147b1b63f7 in start_thread () from /lib/libpthread.so.0
#9 0x00007f147aca4b2d in clone () from /lib/libc.so.6
#10 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f147be977a0 (LWP 27493)):
#0 0x00007f147ac6ac4b in fork () from /lib/libc.so.6
#1 0x00007f147b639d6d in ?? () from /usr/lib/libglib-2.0.so.0
#2 0x00007f147b63a8df in g_spawn_sync () from /usr/lib/libglib-2.0.so.0
#3 0x00007f147b63ad98 in g_spawn_command_line_sync ()
   from /usr/lib/libglib-2.0.so.0
#4 0x000000000051bbf9 in ?? ()
#5 0x000000000043dacd in ?? ()
#6 <signal handler called>
#7 0x00007f147ac49d50 in memcpy () from /lib/libc.so.6
#8 0x000000000042725b in mono_breakpoint_clean_code ()
#9 0x000000000043f78d in ?? ()
#10 0x000000000044005e in ?? ()
#11 0x000000004145a15b in ?? ()
#12 0x0000000000000000 in ?? ()
#0 0x00007f147ac6ac4b in fork () from /lib/libc.so.6

=================================================================
Got a SIGSEGV while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.
=================================================================

[1]+ Aborted (core dumped) f-spot

[Daeng Bo (daengbo)]

Can anyone else reproduce this? I have a pretty stock install. Purging all mono-related packages and reinstalling doesn't help. It's sad that we're only a few days away from an LTS release and a show-stopper bug in Hardy's default photo manager on 64 bit platforms.

After search like hell, I found some debugging help for mono (mono --debug /path/to/exe), but it just reported no debugging symbols found.

Intel(R) Pentium(R) Dual CPU E2140 @ 1.60GHz, if that helps.

[Daeng Bo (daengbo)]

I did a reinstall from the latest packages (netinst) this morning, moved the old f-spot dir out of the way, and tested again. Still have the same error. No one else is getting this?

[Rob (fryrfxmjpkvw)]

F-spot crashed also on my Hardy heron 64 LTS (fresh install) AMD Athlon(tm) 64 X2 Dual Core Processor 5000+

Stacktrace:

  at FSpot.Global..cctor () <0xffffffff>
  at FSpot.Global..cctor () <0x0000d>
  at (wrapper runtime-invoke) FSpot.Defines.runtime_invoke_void (object,intptr,intptr,intptr) <0xffffffff>
  at FSpot.Driver.Main (string[]) <0xffffffff>
  at FSpot.Driver.Main (string[]) <0x00144>
  at (wrapper runtime-invoke) FSpot.Driver.runtime_invoke_int_string[] (object,intptr,intptr,intptr) <0xffffffff>

Native stacktrace:

 f-spot [0x51bb67]
 f-spot [0x43dacd]
 /lib/libpthread.so.0 [0x7f49890db7d0]
 /lib/libc.so.6(memcpy+0x60) [0x7f4988b66d50]
 f-spot(mono_breakpoint_clean_code+0x1b) [0x42725b]
 f-spot [0x43f78d]
 f-spot [0x44005e]
 [0x41eff15b]

Debug info from gdb:

(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x7f4989dba7a0 (LWP 6840)]
[New Thread 0x41d21950 (LWP 6842)]
[New Thread 0x41fe1950 (LWP 6841)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0x00007f49890da5cb in read () from /lib/libpthread.so.0
  3 Thread 0x41fe1950 (LWP 6841) 0x00007f49890dae81 in nanosleep ()
   from /lib/libpthread.so.0
  2 Thread 0x41d21950 (LWP 6842) 0x00007f49890d7b99 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
  1 Thread 0x7f4989dba7a0 (LWP 6840) 0x00007f49890da5cb in read ()
   from /lib/libpthread.so.0

Thread 3 (Thread 0x41fe1950 (LWP 6841)):
#0 0x00007f49890dae81 in nanosleep () from /lib/libpthread.so.0
#1 0x00000000004b8f4f in ?? ()
#2 0x00007f49890d33f7 in start_thread () from /lib/libpthread.so.0
#3 0x00007f4988bc1b2d in clone () from /lib/libc.so.6
#4 0x0000000000000000 in ?? ()

Thread 2 (Thread 0x41d21950 (LWP 6842)):
#0 0x00007f49890d7b99 in pthread_cond_wait@@GLIBC_2.3.2 ()
   from /lib/libpthread.so.0
#1 0x00000000004bb585 in ?? ()
#2 0x00000000004bdb37 in ?? ()
#3 0x00000000004cbc03 in ?? ()
#4 0x000000000046b3c1 in ?? ()
#5 0x00000000004855c3 in ?? ()
#6 0x00000000004cb287 in ?? ()
#7 0x00000000004e07d2 in ?? ()
#8 0x00007f49890d33f7 in start_thread () from /lib/libpthread.so.0
#9 0x00007f4988bc1b2d in clone () from /lib/libc.so.6
#10 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f4989dba7a0 (LWP 6840)):
#0 0x00007f49890da5cb in read () from /lib/libpthread.so.0
#1 0x00007f4989556a90 in ?? () from /usr/lib/libglib-2.0.so.0
#2 0x00007f4989556f7e in ?? () from /usr/lib/libglib-2.0.so.0
#3 0x00007f49895578df in g_spawn_sync () from /usr/lib/libglib-2.0.so.0
#4 0x00007f4989557d98 in g_spawn_command_line_sync ()
   from /usr/lib/libglib-2.0.so.0
#5 0x000000000051bbf9 in ?? ()
#6 0x000000000043dacd in...

[Daeng Bo (daengbo)]

After additional investigation, the problem only occurs in conjunction with some GConf settings, though I'm not sure which ones yet. Deleting ALL GConf keys for F-Spot results in the program launching and performing as expected, but a second attempt to launch the program (after the keys have been reset by the program) segfaults as before. I'll look into it more tomorrow.

[Ge-org Brohammer (administrator-newadventure)]

Same here

[Robert McKee (bertmanphx)]

Hello,
the latest patch for f-spot from the "proposed" repository fixed my issue of f-spot not starting with the sigsevs on AMD 64

[Pedro Villavicencio (pedro)]

May someone else try to test the f-spot package from the proposed repository and see if it solve this issue? thanks.

[Cameron Braid (cameron-braid)]

works for me ... thanks :)

[mturilli (mturilli)]

f-spot 0.4.3.1-0ubuntu1 aborts on AMD64:

Posted initially in the wrong thread:
https://bugs.launchpad.net/ubuntu/+source/f-spot/+bug/230306/comments/13

Anyone may confirm the bug?

[Daeng Bo (daengbo)]

Well, you have five duplicates and three people in this thread confirming it. You also had a patch with two people claiming it fixed the problem. I would venture to say that the original bug was confirmed long ago and fixed.

I would't know, though, because Ubuntu shipped a default app which didn't launch. That was the last straw for me.

[mturilli (mturilli)]

I believe I am referring to the patched version of f-spot:

f-spot 0.4.3.1-0ubuntu1_amd64.deb vs f-spot_0.4.2-1ubuntu2_amd64.deb

As far as I can see there is no further version of f-spot in the 'proposed repository' to fix this issue. It seems to me that f-spot is broken again with an error very similar (if not equal) to the one that was affecting version 0.4.2. What I am missing? :)

[Daeng Bo (daengbo)]

I'm not sure. It was broken for a month. I believe it was fixed, but I had left by that time. It may well be broken again.

As I said, though, I can't test it.

Best of luck.

[Pedro Villavicencio (pedro)]

Still an issue? May someone try the same with the intrepid version of f-spot? thanks.

[Rob (fryrfxmjpkvw)]

For me itś not an issue anymore. Don know why but I can use F-spot 0.4.3.1 now without problems. Thanks for your attention.

[Pedro Villavicencio (pedro)]

closing the bug then, thanks.