f-spot crashes in Xlib after a few moments of use

[Glyphobet]

f-spot crashes after a few minutes of use. There is no single action that seems to cause a crash -- it happens randomly:

Xlib: unexpected async reply (sequence 0x13d77f)!

I can't figure out how to run mono programs through gdb; if someone could share that information with me, I would be glad to provide a gdb backtrace.

This is in dapper.

[Vassilis Pandis (pandisv)]

Hi. Can you please try to obtain a backtrace by following https://wiki.ubuntu,.com/DebuggingProgramCrash ? Without that, it's pretty hard to fnd the problem.Thanks for taking the time to file this :)

[Glyphobet (glyphobet)]

the instructions at
https://wiki.ubuntu.com/DebuggingProgramCrash
are for creating a -dbg package for a package that does not have a -dbg package. Do you recommend that I create a f-spot-dbg package, or did you mean to point me at instructions for obtaining a backtrace from a Mono program?

[Glyphobet (glyphobet)]

I cannot build -dbg package for f-spot. I have made a separate bug here:

https://launchpad.net/distros/ubuntu/+source/f-spot/+bug/47816

[Glyphobet (glyphobet)]

I am following the instructions for attaching to an already-running process with gdb here:

https://wiki.ubuntu.com/Backtrace

bt produces this if I attach to a f-spot process that has already died with

Xlib: unexpected async reply (sequence 0x13d77f)!

#0 0xffffe410 in __kernel_vsyscall ()
#1 0xb7caf8c4 in poll () from /lib/tls/i686/cmov/libc.so.6
#2 0xb66d3e2a in _XEnq () from /usr/lib/libX11.so.6
#3 0xb66d4261 in _XRead () from /usr/lib/libX11.so.6
#4 0xb66d51d8 in _XReply () from /usr/lib/libX11.so.6
#5 0xb66ccee3 in XSync () from /usr/lib/libX11.so.6
#6 0xb6897175 in gdk_flush () from /usr/lib/libgdk-x11-2.0.so.0
#7 0xb6873a81 in gdk_image_get_colormap () from /usr/lib/libgdk-x11-2.0.so.0
#8 0xb6873d43 in _gdk_image_get_scratch () from /usr/lib/libgdk-x11-2.0.so.0
#9 0xb687e406 in gdk_rgb_find_color () from /usr/lib/libgdk-x11-2.0.so.0
#10 0xb686fc7e in _gdk_drawable_get_scratch_gc () from /usr/lib/libgdk-x11-2.0.so.0
#11 0xb689387f in _gdk_x11_convert_to_format () from /usr/lib/libgdk-x11-2.0.so.0
#12 0xb686e8e7 in gdk_draw_pixbuf () from /usr/lib/libgdk-x11-2.0.so.0
#13 0xb6878a35 in gdk_pixmap_get_type () from /usr/lib/libgdk-x11-2.0.so.0
#14 0xb686e8e7 in gdk_draw_pixbuf () from /usr/lib/libgdk-x11-2.0.so.0
#15 0xb68844ac in gdk_window_clear_area_e () from /usr/lib/libgdk-x11-2.0.so.0
#16 0xb686e8e7 in gdk_draw_pixbuf () from /usr/lib/libgdk-x11-2.0.so.0
#17 0xb68781eb in gdk_pixbuf_render_to_drawable () from /usr/lib/libgdk-x11-2.0.so.0
#18 0xb3eb4365 in ?? ()
#19 0x087df350 in ?? ()
#20 0x08480730 in ?? ()
#21 0x0839f738 in ?? ()
#22 0x00000000 in ?? ()

[Glyphobet (glyphobet)]

running
$ f-spot --sync

and attaching to the process once it has crashed produces this:

(gdb) backtrace
#0 0xffffe410 in __kernel_vsyscall ()
#1 0xb7c5f8c4 in poll () from /lib/tls/i686/cmov/libc.so.6
#2 0xb6683e2a in _XEnq () from /usr/lib/libX11.so.6
#3 0xb6684261 in _XRead () from /usr/lib/libX11.so.6
#4 0xb66851d8 in _XReply () from /usr/lib/libX11.so.6
#5 0xb667cee3 in XSync () from /usr/lib/libX11.so.6
#6 0xb667cf79 in XSync () from /usr/lib/libX11.so.6
#7 0xb665c20b in XChangeGC () from /usr/lib/libX11.so.6
#8 0xb6849983 in _gdk_x11_gc_new () from /usr/lib/libgdk-x11-2.0.so.0
#9 0xb6821d40 in gdk_gc_set_values () from /usr/lib/libgdk-x11-2.0.so.0
#10 0xb68222ab in gdk_gc_set_ts_origin () from /usr/lib/libgdk-x11-2.0.so.0
#11 0xb6833689 in gdk_window_get_internal_paint_info () from /usr/lib/libgdk-x11-2.0.so.0
#12 0xb681df7b in gdk_draw_line () from /usr/lib/libgdk-x11-2.0.so.0
#13 0xb4dd5c88 in ?? () from /usr/lib/gtk-2.0/2.4.0/engines/libcrux-engine.so
#14 0x083bdf30 in ?? ()
#15 0x082dda20 in ?? ()
#16 0x0000032b in ?? ()
#17 0x00000458 in ?? ()
#18 0x0000032b in ?? ()
#19 0x000004b9 in ?? ()
#20 0xbff96bb8 in ?? ()
#21 0x0000032a in ?? ()
#22 0x082dda20 in ?? ()
#23 0x083bdf30 in ?? ()
#24 0x00000000 in ?? ()
(gdb) thread apply all backtrace

Thread 5 (Thread -1208509520 (LWP 30774)):
#0 0xffffe410 in __kernel_vsyscall ()
#1 0xb7d04d56 in __nanosleep_nocancel () from /lib/tls/i686/cmov/libpthread.so.0
#2 0xb7ed2956 in mono_disasm_code_one () from /usr/lib/libmono.so.0
#3 0xb7cff341 in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#4 0xb7c694ee in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 4 (Thread -1222435920 (LWP 30775)):
#0 0xffffe410 in __kernel_vsyscall ()
#1 0xb7d01eec in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0
#2 0xb7ed59e8 in _wapi_handle_ops_prewait () from /usr/lib/libmono.so.0
#3 0xb7ed78e3 in _wapi_handle_timedwait_signal_handle () from /usr/lib/libmono.so.0
#4 0xb7ed7947 in _wapi_handle_wait_signal_handle () from /usr/lib/libmono.so.0
#5 0xb7ee53f7 in WaitForSingleObjectEx () from /usr/lib/libmono.so.0
#6 0xb7e83c53 in mono_domain_finalize () from /usr/lib/libmono.so.0
#7 0xb7e9a456 in mono_thread_get_pending_exception () from /usr/lib/libmono.so.0
#8 0xb7ee460f in CreateThread () from /usr/lib/libmono.so.0
#9 0xb7efe3b3 in GC_start_routine () from /usr/lib/libmono.so.0
#10 0xb7cff341 in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#11 0xb7c694ee in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 3 (Thread -1273996368 (LWP 30779)):
#0 0xffffe410 in __kernel_vsyscall ()
#1 0xb7d01eec in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0
#2 0xb7ed59e8 in _wapi_handle_ops_prewait () from /usr/lib/libmono.so.0
#3 0xb7ed78e3 in _wapi_handle_timedwait_signal_handle () from /usr/lib/libmono.so.0
#4 0xb7ed7947 in _wapi_handle_wait_signal_handle () from /usr/lib/libmono.so.0
#5 0xb7ee53f7 in WaitForSingleObjectEx () from /usr/lib/libmono.so.0
#6 0xb7e97dbd in ves_icall_System_Threading_Monitor_Monitor_wait () from /usr/lib/libmono.so.0
...

[Andrew Mitchell (ajmitch)]

It helps only a little, since mono is a threaded program which requires special gdb magic :)
Could you change your theme to human or clearlooks & try this again? It's a little suspicious seeing the crux theme mentioned

[Glyphobet (glyphobet)]

After much testing, I have seen f-spot crash in the same way while using Ubuntu's default "Human" theme.

The crash seems more likely to occur right after I've imported more images, but it's still very intermittent.

If you tell me what GDB magic is necessary, I will gladly provide a better stack trace.

[Glyphobet (glyphobet)]

This time f-spot crashed with this output:

Stacktrace:

in (wrapper managed-to-native) GLib.Object:g_object_unref (intptr) <0x4>
in (wrapper managed-to-native) GLib.Object:g_object_unref (intptr) <0xffffff2c>
in GLib.Object:PerformQueuedUnrefs () <0x11c>
in (wrapper delegate-invoke) System.MulticastDelegate:invoke_bool () <0xffffffb2>
in TimeoutProxy:Handler () <0x2a>
in (wrapper native-to-managed) TimeoutProxy:Handler () <0xaf4a5ec7>
in (wrapper managed-to-native) Gtk.Application:gtk_main () <0x4>
in (wrapper managed-to-native) Gtk.Application:gtk_main () <0xffffffe7>
in Gtk.Application:Run () <0x7>
in Gnome.Program:Run () <0x7>
in FSpot.Driver:Main (string[]) <0x542>
in (wrapper runtime-invoke) System.Object:runtime_invoke_void_string[] (object,intptr,intptr,intptr) <0xbd2c3f>

Native stacktrace:

        /usr/lib/libmono.so.0(mono_handle_native_sigsegv+0xe3) [0xb7e3e43f]
        /usr/lib/libmono.so.0 [0xb7e0003e]
        [0xffffe440]
        /lib/tls/i686/cmov/libc.so.6 [0xb7c19d50]
        /lib/tls/i686/cmov/libc.so.6(__libc_free+0x8a) [0xb7c1a34a]
        /usr/lib/libglib-2.0.so.0(g_free+0x2d) [0xb7d62eec]
        /usr/lib/libgdk_pixbuf-2.0.so.0 [0xb67f3d7e]
        /usr/lib/libgdk_pixbuf-2.0.so.0 [0xb67f3d08]
        /usr/lib/libgobject-2.0.so.0(g_object_unref+0x161) [0xb6517f48]
        [0xb424d4cc]
        [0xb424d3cd]
        [0xb424d288]
        [0xb424d1f3]
        [0x88b7617]
        /usr/lib/libglib-2.0.so.0 [0xb7d5d4a8]
        /usr/lib/libglib-2.0.so.0(g_main_context_dispatch+0x1d7) [0xb7d5b8d6]
        /usr/lib/libglib-2.0.so.0 [0xb7d5e996]
        /usr/lib/libglib-2.0.so.0(g_main_loop_run+0x1d6) [0xb7d5ecb8]
        /usr/lib/libgtk-x11-2.0.so.0(gtk_main+0xb4) [0xb69b96d5]
        [0xb424d1a9]
        [0xb424d168]
        [0xb424d148]
        [0xb724b683]
        [0xb724a823]
        /usr/lib/libmono.so.0 [0xb7e1d438]
        /usr/lib/libmono.so.0(mono_runtime_invoke+0x33) [0xb7e7feed]
        /usr/lib/libmono.so.0(mono_runtime_exec_main+0x67) [0xb7e82a88]
        /usr/lib/libmono.so.0(mono_runtime_run_main+0x188) [0xb7e85bf0]
        /usr/lib/libmono.so.0(mono_jit_exec+0x90) [0xb7e2fb5e]
        /usr/lib/libmono.so.0(mono_main+0x962) [0xb7e3054f]
        /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xd2) [0xb7bcbea2]
        mono [0x8048459]

[edschofield (schofield)]

I'm seeing this all the time in Edgy (f-spot 0.2.1) with even trivial use (tagging and browsing photos).

I think it's an upstream bug in f-spot, based on information here:
http://www.mono-project.com/FAQ:_Gtk#My_application_crashes_with_threads

[Launchpad Janitor (janitor)]

[Expired for f-spot (Ubuntu) because there has been no activity for 60 days.]

[Jon-o Addleman (jaddle)]

I'm seeing the same problem in gutsy. I'll try to get a backtrace next time it happens.

[Øyvind Stegard (oyvindstegard)]

Seeing the very same thing. I'm on Ubuntu Gutsy x86. F-spot (v0.4.0) is basically unusable because it will crash with the Xlib error way too often. My photo-database isn't unusually large (quite the opposite).

I tried F-spot 0.4.1, hoping that the problem would be fixed (built the source deb from Hardy-repository), but it crashes too, with exactly the same error.

[Alexandre Prokoudine (alexandre-prokoudine)]

I don't think this bug report was forwarded to upstream.

Just in case, whenever you deal with Mono apps, use

$ mono --debug program.exe

e.g.

$ mono --debug /usr/lib/f-spot/f-spot.exe

My suggestion would be going to bugzilla.gnome.orgm checking if the bug is not reported there yet and then, if it's not, posting it with debugging info.

[Maxxer (lorenzo-milesi)]

The bug already exists upstream http://bugzilla.gnome.org/show_bug.cgi?id=333071
Sadly there's no solution yet.

[madbiologist (me-again)]

Official support for Ubuntu 8.04 "Hardy Heron" and earlier versions has ended. If you are still experiencing this bug on Ubuntu 14.10 "Utopic Unicorn" please run ubuntu-bug to file a new bug report so that we can get a fresh set of log files and system information.