telepathy-idle crashed with SIGSEGV in g_simple_async_result_complete()

[Ruudsch Ma' Hinda]

While Ubuntu One was uploading a 2.5 GB file this error-report came up after which ubuntu one restarted uploading that file from start. At least that's what it seems like, since Ubuntu One has no real status bar.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: telepathy-idle 0.1.11-2
ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9
Uname: Linux 3.2.0-18-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
Date: Sun Mar 11 23:01:17 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/telepathy/telepathy-idle
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
ProcCmdline: /usr/lib/telepathy/telepathy-idle
ProcEnviron:
 SHELL=/bin/bash
 LANG=de_DE.UTF-8
SegvAnalysis:
 Segfault happened at: 0x40a088: mov 0x8(%rax),%rcx
 PC (0x0040a088) ok
 source "0x8(%rax)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%rcx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: telepathy-idle
StacktraceTop:
 ?? ()
 g_simple_async_result_complete () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: telepathy-idle crashed with SIGSEGV in g_simple_async_result_complete()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Ruudsch Ma' Hinda (ruudschi)]

EDIT:
Ubuntu One did not restart the upload. It just finished about 15 minutes after the crash.

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #905816, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.