← Back to team overview

desktop-packages team mailing list archive

[Bug 1415385] Re: telepathy-indicator crashed with SIGSEGV

 

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to telepathy-indicator in Ubuntu.
https://bugs.launchpad.net/bugs/1415385

Title:
  telepathy-indicator crashed with SIGSEGV

Status in telepathy-indicator package in Ubuntu:
  New

Bug description:
  Who knows?

  Not me.

  Apport, maybe.

  (Got this prompt at login, could have happened at previous shutdown)

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: telepathy-indicator 0.3.1+14.10.20140908-0ubuntu1
  ProcVersionSignature: Ubuntu 3.18.0-11.12-generic 3.18.3
  Uname: Linux 3.18.0-9-generic x86_64
  ApportVersion: 2.15.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jan 27 16:25:26 2015
  ExecutablePath: /usr/bin/telepathy-indicator
  InstallationDate: Installed on 2012-10-07 (842 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007)
  ProcCmdline: telepathy-indicator
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x403e12:	mov    0x8(%rax),%rcx
   PC (0x00403e12) ok
   source "0x8(%rax)" (0x00000008) not located in a known VMA region (needed readable region)!
   destination "%rcx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: telepathy-indicator
  StacktraceTop:
   ()
   __libc_start_main (main=0x403bb0, argc=1, argv=0x7fffe9a68838, init=<optimised out>, fini=<optimised out>, rtld_fini=<optimised out>, stack_end=0x7fffe9a68828) at libc-start.c:287
   ()
  Title: telepathy-indicator crashed with SIGSEGV
  UpgradeStatus: Upgraded to vivid on 2013-05-07 (631 days ago)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telepathy-indicator/+bug/1415385/+subscriptions