telepathy-idle crashed with SIGSEGV in g_io_stream_get_output_stream()

[Andrei Emeltchenko]

crash

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: telepathy-idle 0.1.11-2
ProcVersionSignature: Ubuntu 3.2.0-22.35-generic-pae 3.2.14
Uname: Linux 3.2.0-22-generic-pae i686
ApportVersion: 2.0.1-0ubuntu4
Architecture: i386
CrashCounter: 1
Date: Thu Apr 19 09:20:17 2012
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-dell-maverick-une-20101010-0
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/telepathy/telepathy-idle
InstallationMedia: Ubuntu 10.10 "Maverick" - Build i386 LIVE Binary 20101010-01:50
ProcCmdline: /usr/lib/telepathy/telepathy-idle
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0xb75f8d23 <g_io_stream_get_output_stream+19>: mov (%edx),%eax
 PC (0xb75f8d23) ok
 source "(%edx)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: telepathy-idle
StacktraceTop:
 g_io_stream_get_output_stream () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
 idle_server_connection_send_async ()
 ?? ()
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
Title: telepathy-idle crashed with SIGSEGV in g_io_stream_get_output_stream()
UpgradeStatus: Upgraded to precise on 2012-02-01 (77 days ago)
UserGroups: adm admin bluetooth cdrom dialout disk lpadmin netdev plugdev sambashare vboxusers

[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 #918744, 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.