Public bug reported:
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
** Affects: f-spot (Ubuntu)
Importance: Undecided
Status: New
--
f-spot sigsevs on AMD64
https://bugs.launchpad.net/bugs/214410
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to f-spot in ubuntu.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
