telepathy-idle crashed with SIGSEGV in g_io_stream_get_output_stream()

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

Bug Description

Telepathy crash, login with no Internet connection

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: telepathy-idle 0.1.11-2
ProcVersionSignature: Ubuntu 3.2.0-19.30-generic 3.2.11
Uname: Linux 3.2.0-19-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
Date: Tue Mar 20 09:04:32 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/telepathy/telepathy-idle
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120201.1)
ProcCmdline: /usr/lib/telepathy/telepathy-idle
SegvAnalysis:
 Segfault happened at: 0x7f6f6db3cfd4 <g_io_stream_get_output_stream+4>: mov (%rdi),%rax
 PC (0x7f6f6db3cfd4) 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 (stream=0x0) at /build/buildd/glib2.0-2.31.20/./gio/giostream.c:247
 idle_server_connection_send_async ()
 ?? ()
 g_timeout_dispatch (source=<optimized out>, callback=<optimized out>, user_data=<optimized out>) at /build/buildd/glib2.0-2.31.20/./glib/gmain.c:3854
 g_main_dispatch (context=0xcc9580) at /build/buildd/glib2.0-2.31.20/./glib/gmain.c:2510
Title: telepathy-idle crashed with SIGSEGV in g_io_stream_get_output_stream()
UpgradeStatus: Upgraded to precise on 2012-03-13 (6 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
graingert (tagrain) wrote :
visibility: private → public
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.

tags: removed: need-amd64-retrace
Revision history for this message
graingert (tagrain) wrote :

It's a duplicate of a private bug...

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.