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

[mario catena]

Description: Ubuntu precise (development branch)
Release: 12.04

deja-dup:
  Installato: 21.2-0ubuntu2
  Candidato: 21.2-0ubuntu2
  Tabella versione:
 *** 21.2-0ubuntu2 0
        500 http://it.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
        100 /var/lib/dpkg/status

check if this bug while upgrading the system with the update manager, although not involved very much, I noticed that it appears at that time.

I do not know what should I expect it should be according to an automated process.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: deja-dup 21.2-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-7.13-generic 3.2.0-rc7
Uname: Linux 3.2.0-7-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.90-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Sat Jan 7 12:14:59 2012
ExecutablePath: /usr/lib/deja-dup/deja-dup/deja-dup-monitor
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20111204)
ProcCmdline: /usr/lib/deja-dup/deja-dup/deja-dup-monitor
ProcEnviron:
 PATH=(custom, no user)
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fd2b5a91cab: mov %r9b,(%rax)
 PC (0x7fd2b5a91cab) ok
 source "%r9b" ok
 destination "(%rax)" (0x7fd2b52b13a0) in non-writable VMA region: 0x7fd2b52a6000-0x7fd2b5396000 r-xp /lib/x86_64-linux-gnu/libglib-2.0.so.0.3106.0
SegvReason: writing VMA /lib/x86_64-linux-gnu/libglib-2.0.so.0.3106.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-12-14 (24 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

This crash has the same stack trace characteristics as bug #901388. However, the latter was already fixed in an earlier package version than the one in this report. This might be a regression or because the problem is in a dependent package.