Ubuntu
telepathy-idle package

telepathy-idle crashed with SIGSEGV in g_io_stream_get_output_stream()

Bug #952676 reported by Julian Menzie on 2012-03-12

This bug report is a duplicate of: Bug #918744: telepathy-idle crashed with SIGSEGV in g_io_stream_get_output_stream(). Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	telepathy-idle (Ubuntu)	New	Undecided	Unassigned

Bug Description

using HUD to switch user availability and app crashed

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: telepathy-idle 0.1.11-2
ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9
Uname: Linux 3.2.0-18-generic x86_64
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Sun Mar 11 22:02:26 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/telepathy/telepathy-idle
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120311)
ProcCmdline: /usr/lib/telepathy/telepathy-idle
ProcEnviron:
SHELL=/bin/bash
LANG=en_US.UTF-8
SegvAnalysis:
Segfault happened at: 0x7f87c846cf84 <g_io_stream_get_output_stream+4>: mov (%rdi),%rax
PC (0x7f87c846cf84) ok
source "(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: telepathy-idle
StacktraceTop:
g_io_stream_get_output_stream () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
idle_server_connection_send_async ()
?? ()
?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
g_main_context_dispatch () from /lib/x86_64-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

Tags:

Revision history for this message

Julian Menzie (jmenzie) wrote on 2012-03-12:

Dependencies.txt Edit (599 bytes, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2012-03-12: 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.