nautilus crashed with SIGSEGV in g_closure_invoke()

[Ken VanDine]

This crash happened after installing updating ubuntuone-client-gnome to 2.99.0-0ubuntu1 (not uploaded yet)

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: nautilus 1:3.2.1-2ubuntu4
ProcVersionSignature: Ubuntu 3.2.0-6.12-generic 3.2.0-rc6
Uname: Linux 3.2.0-6-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.90-0ubuntu1
Architecture: amd64
Date: Fri Dec 23 16:13:45 2011
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110223)
ProcCmdline: nautilus
SegvAnalysis:
 Segfault happened at: 0x7f942ed2034c: mov 0x8(%rbp),%eax
 PC (0x7f942ed2034c) ok
 source "0x8(%rbp)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? () from /usr/lib/libsyncdaemon-1.0.so.1
 ?? () from /usr/lib/x86_64-linux-gnu/libdbus-glib-1.so.2
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: nautilus crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: Upgraded to precise on 2011-11-18 (35 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers

[Ken VanDine (ken-vandine)]

Downgrading libsyncdaemon-1.0-1 to 2.0.0-0ubuntu4 fixed it, so apparently the crash was introduced in libsyncdaemon-1.0-1 2.99.0-0ubuntu1

[Aaron Haviland (aaron-haviland)]

I believe I have the same issue, and here is a more informative bt:

Program received signal SIGSEGV, Segmentation fault.
got_public_files_cb (proxy=0x8268b18, files=0x0, user_data=0x823fe18) at syncdaemon-publicfiles-interface.c:90
90 for (i = 0; i < files->len; i++) {

(gdb) bt
#0 got_public_files_cb (proxy=0x8268b18, files=0x0, user_data=0x823fe18) at syncdaemon-publicfiles-interface.c:90
#1 0x00c81f8a in g_cclosure_marshal_VOID__POINTER (closure=0x81d55e0, return_value=0x0, n_param_values=2, param_values=0x866dae8,
    invocation_hint=0xbfffdf50, marshal_data=0x0) at /build/buildd/glib2.0-2.31.4.tested/./gobject/gmarshal.c:609
#2 0x0161117a in marshal_dbus_message_to_g_marshaller (closure=0x81d55e0, return_value=0x0, n_param_values=3, param_values=0x85e0c10,
    invocation_hint=0xbfffdf50, marshal_data=0x0) at dbus-gproxy.c:1734
#3 0x00c7fdac in g_closure_invoke (closure=0x81d55e0, return_value=0x0, n_param_values=3, param_values=0x85e0c10, invocation_hint=0xbfffdf50)
    at /build/buildd/glib2.0-2.31.4.tested/./gobject/gclosure.c:774
#4 0x00c910c5 in signal_emit_unlocked_R (node=0x8265180, detail=1224, instance=0x8268b18, emission_return=0x0, instance_and_params=0x85e0c10)
    at /build/buildd/glib2.0-2.31.4.tested/./gobject/gsignal.c:3302
#5 0x00c98942 in g_signal_emit_valist (instance=0x8268b18, signal_id=220, detail=1224, var_args=0xbfffe104 "")
    at /build/buildd/glib2.0-2.31.4.tested/./gobject/gsignal.c:3033
#6 0x00c98ad3 in g_signal_emit (instance=0x8268b18, signal_id=220, detail=1224) at /build/buildd/glib2.0-2.31.4.tested/./gobject/gsignal.c:3090
#7 0x01611820 in dbus_g_proxy_emit_remote_signal (message=0x8325748, proxy=<optimized out>) at dbus-gproxy.c:1787
#8 dbus_g_proxy_manager_filter (user_data=0x8268278, message=0x8325748, connection=<optimized out>) at dbus-gproxy.c:1354
#9 dbus_g_proxy_manager_filter (connection=0x8265438, message=0x8325748, user_data=0x8268278) at dbus-gproxy.c:1195
#10 0x01538441 in dbus_connection_dispatch () from /lib/i386-linux-gnu/libdbus-1.so.3
#11 0x016099ad in message_queue_dispatch (source=0x8267c48, callback=0, user_data=0x0) at dbus-gmain.c:90
#12 0x00d0728a in g_main_dispatch (context=0x81f6fa0) at /build/buildd/glib2.0-2.31.4.tested/./glib/gmain.c:2513
#13 g_main_context_dispatch (context=0x81f6fa0) at /build/buildd/glib2.0-2.31.4.tested/./glib/gmain.c:3050
#14 0x00d07695 in g_main_context_iterate (dispatch=1, block=13717552, context=0x81f6fa0, self=<optimized out>)
    at /build/buildd/glib2.0-2.31.4.tested/./glib/gmain.c:3121
#15 g_main_context_iterate (context=0x81f6fa0, block=13717552, dispatch=1, self=<optimized out>) at /build/buildd/glib2.0-2.31.4.tested/./glib/gmain.c:3058
#16 0x00d07771 in g_main_context_iteration (context=0x81f6fa0, may_block=1) at /build/buildd/glib2.0-2.31.4.tested/./glib/gmain.c:3182
#17 0x00b9562c in g_application_run (application=0x81c5c08, argc=1, argv=0xbfffe434) at /build/buildd/glib2.0-2.31.4.tested/./gio/gapplication.c:1548
#18 0x08067ae4 in main (argc=1, argv=0xbfffe434) at nautilus-main.c:102

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Aaron Haviland (aaron-haviland)]

Upon further searching, I wonder if this is related to bug #908787; Read comment #4 on that thread. I have done no testing of this with the workaround suggested in that comment.

[Apport retracing service (apport)]

StacktraceTop:
 got_public_files_cb (proxy=<optimized out>, files=0x0, user_data=<optimized out>) at syncdaemon-publicfiles-interface.c:90
 ?? ()
 ?? ()
 ?? ()
 ?? ()

[Apport retracing service (apport)]

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate an useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

liblaunchpad-integration-common version 0.1.54 required, but 0.1.54build1 is available
libdatrie1 version 0.2.5-2 required, but 0.2.5-3 is available
liblaunchpad-integration-3.0-1 version 0.1.54 required, but 0.1.54build1 is available
libp11-kit0 version 0.8-2 required, but 0.9-3 is available
libthai-data version 0.1.16-2 required, but 0.1.16-3 is available
libgnutls26 version 2.12.14-4 required, but 2.12.14-5 is available
libthai0 version 0.1.16-2 required, but 0.1.16-3 is available

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

[Launchpad Janitor (janitor)]

This bug was fixed in the package ubuntuone-client - 2.99.1-0ubuntu1

---------------
ubuntuone-client (2.99.1-0ubuntu1) precise; urgency=low

  * New upstream release.
    - Avoid using hint files with size 0. (LP: #825366)
    - Use g_return_if_fail to avoid NULL for important args (LP: #908805)
    - Don't register a new VOID__POINTER marshaller for dbus as it breaks now
      (LP: #908787, LP: #908261)
  * debian/watch:
    - Point at the release milestone
 -- Rodney Dawes <email address hidden> Wed, 04 Jan 2012 09:44:36 -0500