F-spot crashes when creating a stand alone gallery
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
f-spot (Ubuntu) |
Confirmed
|
Medium
|
Ubuntu Desktop Bugs |
Bug Description
When exporting to Folder -> stand alone gallery, F-spot suddenly crashes before the gallery is complete.
Running Ubuntu 8.10 on i386.
This is the messages written in the terminal:
Stacktrace:
Native stacktrace:
f-spot [0x817d3de]
f-spot [0x807f78b]
[0xb8045410]
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 0xb7d9f6d0 (LWP 28539)]
[New Thread 0xaf5c1b90 (LWP 28591)]
[New Thread 0xadfeeb90 (LWP 28586)]
[New Thread 0xaf330b90 (LWP 28578)]
[New Thread 0xb3881b90 (LWP 28547)]
[New Thread 0xb3986b90 (LWP 28546)]
[New Thread 0xb4e6bb90 (LWP 28542)]
[New Thread 0xb7326b90 (LWP 28541)]
[New Thread 0xb734ab90 (LWP 28540)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xb8045430 in __kernel_vsyscall ()
9 Thread 0xb734ab90 (LWP 28540) 0xb8045430 in __kernel_vsyscall ()
8 Thread 0xb7326b90 (LWP 28541) 0xb8045430 in __kernel_vsyscall ()
7 Thread 0xb4e6bb90 (LWP 28542) 0xb8045430 in __kernel_vsyscall ()
6 Thread 0xb3986b90 (LWP 28546) 0xb8045430 in __kernel_vsyscall ()
5 Thread 0xb3881b90 (LWP 28547) 0xb8045430 in __kernel_vsyscall ()
4 Thread 0xaf330b90 (LWP 28578) 0xb8045430 in __kernel_vsyscall ()
3 Thread 0xadfeeb90 (LWP 28586) 0xb8045430 in __kernel_vsyscall ()
2 Thread 0xaf5c1b90 (LWP 28591) 0xb8045430 in __kernel_vsyscall ()
1 Thread 0xb7d9f6d0 (LWP 28539) 0xb8045430 in __kernel_vsyscall ()
Thread 9 (Thread 0xb734ab90 (LWP 28540)):
#0 0xb8045430 in __kernel_vsyscall ()
#1 0xb7f5c8f6 in nanosleep () from /lib/tls/
#2 0x081114a8 in ?? ()
#3 0xb7f554ff in start_thread () from /lib/tls/
#4 0xb7eac64e in clone () from /lib/tls/
Thread 8 (Thread 0xb7326b90 (LWP 28541)):
#0 0xb8045430 in __kernel_vsyscall ()
#1 0xb7f59065 in pthread_
from /lib/tls/
#2 0x08114897 in ?? ()
#3 0x08116ecc in ?? ()
#4 0x08116f0c in ?? ()
#5 0x08129b6a in ?? ()
#6 0x080b5c6a in ?? ()
#7 0x080d61a4 in ?? ()
#8 0x08127f4e in ?? ()
#9 0x081404b5 in ?? ()
#10 0xb7f554ff in start_thread () from /lib/tls/
#11 0xb7eac64e in clone () from /lib/tls/
Thread 7 (Thread 0xb4e6bb90 (LWP 28542)):
#0 0xb8045430 in __kernel_vsyscall ()
#1 0xb7f59392 in pthread_
from /lib/tls/
#2 0x08114848 in ?? ()
#3 0x08116ecc in ?? ()
#4 0x08116f0c in ?? ()
#5 0x08129b6a in ?? ()
#6 0x080d3243 in ?? ()
#7 0xb501a1e2 in ?? ()
#8 0xb5019fd3 in ?? ()
#9 0xb5018e23 in ?? ()
#10 0xb5dc4761 in ?? ()
#11 0x08098c55 in mono_runtime_
#12 0x080d620f in ?? ()
#13 0x08127f4e in ?? ()
#14 0x081404b5 in ?? ()
#15 0xb7f554ff in start_thread () from /lib/tls/
#16 0xb7eac64e in clone () from /lib/tls/
Thread 6 (Thread 0xb3986b90 (LWP 28546)):
#0 0xb8045430 in __kernel_vsyscall ()
#1 0xb7f59392 in pthread_
from /lib/tls/
#2 0x08114848 in ?? ()
#3 0x08116ecc in ?? ()
#4 0x08116f0c in ?? ()
#5 0x08129b6a in ?? ()
#6 0x080d1a51 in ?? ()
#7 0xb398fdf2 in ?? ()
#8 0xb398fcd6 in ?? ()
#9 0xb398fbf8 in ?? ()
#10 0xb5dc4761 in ?? ()
#11 0x08098c55 in mono_runtime_
#12 0x080d620f in ?? ()
#13 0x08127f4e in ?? ()
#14 0x081404b5 in ?? ()
#15 0xb7f554ff in start_thread () from /lib/tls/
#16 0xb7eac64e in clone () from /lib/tls/
Thread 5 (Thread 0xb3881b90 (LWP 28547)):
#0 0xb8045430 in __kernel_vsyscall ()
#1 0xb7f59392 in pthread_
from /lib/tls/
#2 0x08114848 in ?? ()
#3 0x08116ecc in ?? ()
#4 0x08116f0c in ?? ()
#5 0x08129b6a in ?? ()
#6 0x080d1a51 in ?? ()
#7 0xb398fdf2 in ?? ()
#8 0xb398fcd6 in ?? ()
#9 0xb398ff86 in ?? ()
#10 0xb5dc4761 in ?? ()
#11 0x08098c55 in mono_runtime_
#12 0x080d620f in ?? ()
#13 0x08127f4e in ?? ()
#14 0x081404b5 in ?? ()
#15 0xb7f554ff in start_thread () from /lib/tls/
#16 0xb7eac64e in clone () from /lib/tls/
Thread 4 (Thread 0xaf330b90 (LWP 28578)):
#0 0xb8045430 in __kernel_vsyscall ()
#1 0xb7f59392 in pthread_
from /lib/tls/
#2 0x08114848 in ?? ()
#3 0x08116ecc in ?? ()
#4 0x08116f0c in ?? ()
#5 0x08129b6a in ?? ()
#6 0x080d1a51 in ?? ()
#7 0xb398fdf2 in ?? ()
#8 0xb398fcd6 in ?? ()
#9 0xb398ff86 in ?? ()
#10 0xb5dc4761 in ?? ()
#11 0x08098c55 in mono_runtime_
#12 0x080d620f in ?? ()
#13 0x08127f4e in ?? ()
#14 0x081404b5 in ?? ()
#15 0xb7f554ff in start_thread () from /lib/tls/
#16 0xb7eac64e in clone () from /lib/tls/
Thread 3 (Thread 0xadfeeb90 (LWP 28586)):
#0 0xb8045430 in __kernel_vsyscall ()
#1 0xb7ea4a71 in select () from /lib/tls/
#2 0xb7fde9bb in g_spawn_sync () from /usr/lib/
#3 0xb7fded6c in g_spawn_
#4 0x0817d495 in ?? ()
#5 0x0807f78b in ?? ()
#6 <signal handler called>
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
Thread 2 (Thread 0xaf5c1b90 (LWP 28591)):
#0 0xb8045430 in __kernel_vsyscall ()
#1 0xb7ea1de7 in poll () from /lib/tls/
#2 0xb7fa8c32 in ?? () from /usr/lib/
#3 0xb7fa92c2 in g_main_loop_run () from /usr/lib/
#4 0xb65718b0 in ?? () from /usr/lib/
#5 0xb7fd005f in ?? () from /usr/lib/
#6 0xb7f554ff in start_thread () from /lib/tls/
#7 0xb7eac64e in clone () from /lib/tls/
Thread 1 (Thread 0xb7d9f6d0 (LWP 28539)):
#0 0xb8045430 in __kernel_vsyscall ()
#1 0xb7ea1de7 in poll () from /lib/tls/
#2 0xb7fa8c32 in ?? () from /usr/lib/
#3 0xb7fa92c2 in g_main_loop_run () from /usr/lib/
#4 0xb698e299 in gtk_main () from /usr/lib/
#5 0xaf7bc376 in ?? ()
#6 0xaf7bc340 in ?? ()
#7 0xaf7bc328 in ?? ()
#8 0xb78b0840 in ?? ()
#9 0xb78af1c4 in ?? ()
#10 0x0809cbc7 in mono_runtime_
#11 0x0809d1ab in mono_runtime_
#12 0x0805aeee in mono_main ()
#13 0x0805a3f2 in ?? ()
#14 0xb7de1685 in __libc_start_main () from /lib/tls/
#15 0x0805a331 in ?? ()
#0 0xb8045430 in __kernel_vsyscall ()
=======
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.
=======
Aborted (core dumped)
Changed in f-spot (Ubuntu): | |
status: | Incomplete → New |
thanks for the report, it doesn't crash here, could you run f-spot from the command line as : f-spot --debug &> f-spot.txt and attach that file after the crash to the report? thanks.