telepathy-idle crashed with SIGSEGV in g_io_stream_get_output_stream()

Bug #952526 reported by Alex Solanos
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
telepathy-idle (Ubuntu)
New
Undecided
Unassigned

Bug Description

Program actually crashed when I clicked
'Offline' from the top right messaging menu of ubuntu (that small icon of a message)
and then I clicked on 'Quit' from empathy's icon from unity sidebar.

That's all :)

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: telepathy-idle 0.1.11-2
ProcVersionSignature: Ubuntu 3.2.0-17.27-generic-pae 3.2.6
Uname: Linux 3.2.0-17-generic-pae i686
ApportVersion: 1.94.1-0ubuntu2
Architecture: i386
Date: Sun Mar 11 22:52:57 2012
ExecutablePath: /usr/lib/telepathy/telepathy-idle
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120301)
ProcCmdline: /usr/lib/telepathy/telepathy-idle
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0xb7663a53 <g_io_stream_get_output_stream+19>: mov (%edx),%eax
 PC (0xb7663a53) 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: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Alex Solanos (hakermania) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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.

visibility: private → public
visibility: private → public
tags: removed: need-i386-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.