telepathy-gabble crashed with SIGSEGV in getaddrinfo()

Bug #960090 reported by Simon Baconnais
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
telepathy-gabble (Ubuntu)
New
Undecided
Unassigned

Bug Description

Empathy was unable to connect acounts right on first launch after a reboot.
I had to click on refresh.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: telepathy-gabble 0.15.4-1ubuntu1
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
Date: Tue Mar 20 11:31:24 2012
ExecutablePath: /usr/lib/telepathy/telepathy-gabble
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120313)
ProcCmdline: /usr/lib/telepathy/telepathy-gabble
ProcEnviron:
 SHELL=/bin/bash
 LANG=fr_FR.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f53be26dbfe: lock xadd %eax,0x18(%rdi)
 PC (0x7f53be26dbfe) ok
 source "%eax" ok
 destination "0x18(%rdi)" (0x00000017) not located in a known VMA region (needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: telepathy-gabble
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 getaddrinfo () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: telepathy-gabble crashed with SIGSEGV in getaddrinfo()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Simon Baconnais (smon-deactivatedaccount) 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 #930692, 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-amd64-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.