** Visibility changed to: Public

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

Title:
  telepathy-gabble crashed with SIGSEGV in ffi_call_unix64()

Status in “telepathy-gabble” package in Ubuntu:
  New

Bug description:
  This seems to happen every time after an online account went offline
  (mostly Google) after a reboot or so.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: telepathy-gabble 0.16.1-1
  ProcVersionSignature: Ubuntu 3.5.0-14.19-generic 3.5.3
  Uname: Linux 3.5.0-14-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.5.1-0ubuntu7
  Architecture: amd64
  CrashCounter: 1
  Date: Mon Sep 17 08:06:47 2012
  EcryptfsInUse: Yes
  ExecutablePath: /usr/lib/telepathy/telepathy-gabble
  ProcCmdline: /usr/lib/telepathy/telepathy-gabble
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, user)
   LANG=en_US.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x48f750:      mov    (%rbx),%rdi
   PC (0x0048f750) ok
   source "(%rbx)" (0xd4569259) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: telepathy-gabble
  StacktraceTop:
   ?? ()
   ?? ()
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   g_cclosure_marshal_generic () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: telepathy-gabble crashed with SIGSEGV in ffi_call_unix64()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to