** Information type changed from Private to Public

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

Title:
  gnome-contacts crashed with SIGSEGV in __lambda29_()

Status in “gnome-contacts” package in Ubuntu:
  New

Bug description:
  gnome-contacts crashed

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: gnome-contacts 3.8.3-1ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-7.25-generic 3.13.1
  Uname: Linux 3.13.0-7-generic x86_64
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Feb  6 00:14:40 2014
  ExecutablePath: /usr/bin/gnome-contacts
  InstallationDate: Installed on 2013-10-15 (113 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 
(20131015)
  ProcCmdline: gnome-contacts
  SegvAnalysis:
   Segfault happened at: 0x42e188:      mov    0x40(%rbp),%r12
   PC (0x0042e188) ok
   source "0x40(%rbp)" (0x00000040) not located in a known VMA region (needed 
readable region)!
   destination "%r12" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-contacts
  StacktraceTop:
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_by_name () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-contacts crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: Upgraded to trusty on 2013-11-05 (92 days ago)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-contacts/+bug/1276856/+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