telepathy-indicator crashed with SIGSEGV

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

Bug Description

I opened "Chat" -Empathy, from the standard quicklauncher on the top right, wrote my credentials for MSN and when it was logged in the error report showed up, Empathy seems to still be functional though.

Description: Ubuntu oneiric (development branch)
Release: 11.10

empathy:
  Installerad: 3.2.0-0ubuntu1
  Kandidat: 3.2.0-0ubuntu1
  Versionstabell:
 *** 3.2.0-0ubuntu1 0
        500 http://se.archive.ubuntu.com/ubuntu/ oneiric/main i386 Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: telepathy-indicator 0.0.6-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic i686
ApportVersion: 1.23-0ubuntu2
Architecture: i386
Date: Wed Oct 5 06:50:07 2011
ExecutablePath: /usr/bin/telepathy-indicator
ProcCmdline: telepathy-indicator
ProcEnviron:
 LANG=sv_SE.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x804966a: mov (%ebx),%eax
 PC (0x0804966a) ok
 source "(%ebx)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: telepathy-indicator
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/libtelepathy-glib.so.0
 ?? () from /usr/lib/libtelepathy-glib.so.0
 ?? () from /usr/lib/libtelepathy-glib.so.0
 ?? () from /usr/lib/libtelepathy-glib.so.0
Title: telepathy-indicator crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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 Ubuntu better. This particular crash has already been reported and is a duplicate of bug #851881, 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.