deja-dup-monitor crashed with SIGSEGV in child_setup(), g_spawn_async_with_pipes()

[Alex Chiang]

No further information. Was simply running precise, did a daily apt-get update ; apt-get dist-upgrade and was presented with this crash report.

Happy to help debug further.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: deja-dup 21.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-3.8-generic 3.2.0-rc4
Uname: Linux 3.2.0-3-generic x86_64
ApportVersion: 1.90-0ubuntu1
Architecture: amd64
Date: Wed Dec 7 12:00:00 2011
ExecutablePath: /usr/lib/deja-dup/deja-dup/deja-dup-monitor
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcCmdline: /usr/lib/deja-dup/deja-dup/deja-dup-monitor
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fa3b70716ab: mov %r9b,(%rax)
 PC (0x7fa3b70716ab) ok
 source "%r9b" ok
 destination "(%rax)" (0x7fa3b6893e40) in non-writable VMA region: 0x7fa3b6889000-0x7fa3b6978000 r-xp /lib/x86_64-linux-gnu/libglib-2.0.so.0.3102.0
SegvReason: writing VMA /lib/x86_64-linux-gnu/libglib-2.0.so.0.3102.0
Signal: 11
SourcePackage: deja-dup
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_spawn_async_with_pipes () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_spawn_async () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: deja-dup-monitor crashed with SIGSEGV in g_spawn_async_with_pipes()
UpgradeStatus: Upgraded to precise on 2011-11-19 (18 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:
 child_setup (user_data=0x7fffb6ac76a0) at /build/buildd/glib2.0-2.31.2/./gio/gdesktopappinfo.c:1150
 do_exec (child_err_report_fd=13, stdin_fd=-1, stdout_fd=-1, stderr_fd=-1, working_directory=<optimized out>, argv=0x22315a0, envp=0x222f110, close_descriptors=1, search_path=1, stdout_to_null=0, stderr_to_null=0, child_inherits_stdin=0, file_and_argv_zero=0, child_setup=0x7fa3b7071620 <child_setup>, user_data=0x7fffb6ac76a0) at /build/buildd/glib2.0-2.31.2/./glib/gspawn.c:1129
 fork_exec_with_pipes (intermediate_child=1, working_directory=0x0, argv=0x22315a0, envp=0x222f110, close_descriptors=1, search_path=1, stdout_to_null=0, stderr_to_null=0, child_inherits_stdin=0, file_and_argv_zero=0, child_setup=0x7fa3b7071620 <child_setup>, user_data=0x7fffb6ac76a0, child_pid=0x7fffb6ac76cc, standard_input=0x0, standard_output=0x0, standard_error=0x0, error=0x7fffb6ac7788) at /build/buildd/glib2.0-2.31.2/./glib/gspawn.c:1324
 g_spawn_async_with_pipes (working_directory=<optimized out>, argv=<optimized out>, envp=<optimized out>, flags=<optimized out>, child_setup=<optimized out>, user_data=<optimized out>, child_pid=0x7fffb6ac76cc, standard_input=0x0, standard_output=0x0, standard_error=0x0, error=0x7fffb6ac7788) at /build/buildd/glib2.0-2.31.2/./glib/gspawn.c:653
 g_spawn_async (working_directory=<optimized out>, argv=<optimized out>, envp=<optimized out>, flags=<optimized out>, child_setup=<optimized out>, user_data=<optimized out>, child_pid=0x7fffb6ac76cc, error=0x7fffb6ac7788) at /build/buildd/glib2.0-2.31.2/./glib/gspawn.c:138

[Launchpad Janitor (janitor)]

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

[crtm (carlosrtm)]

When start Unity, then crash

[Jani Uusitalo (uusijani)]

I suggest that the title be changed to somehow reflect that this is (apparently indirectly) related to g_spawn_async_with_pipes() too. I was about to report a duplicate with the title this bug initially had, and I see others have fallen for it too (Ref: Bug #904899). As it stands, bug reporters have to catch g_spawn_async_with_pipes() from a greyed-out comment made by a bot. I think some confusion could be avoided if Launchpad, when suggesting this, had g_spawn_async_with_pipes() right in the title. How about "deja-dup-monitor crashed with SIGSEGV in child_setup(), g_spawn_async_with_pipes()"?

[Michael Terry (mterry)]

Switching to glib2.0 because that seems to be where the crash is. See upstream bug I filed for a patch.

[Launchpad Janitor (janitor)]

This bug was fixed in the package glib2.0 - 2.31.6-0ubuntu2

---------------
glib2.0 (2.31.6-0ubuntu2) precise; urgency=low

  * debian/patches/62_avoid_child_setup_crash.patch:
    - Don't crash when spawning some commandline apps (LP: #901388)
 -- Michael Terry <email address hidden> Fri, 06 Jan 2012 10:44:17 -0500