← Back to team overview

desktop-packages team mailing list archive

[Bug 1417309] Re: goa-daemon crashed with SIGSEGV in magazine_chain_pop_head()


** Information type changed from Private to Public

** Bug watch added: GNOME Bug Tracker #743903

** Also affects: gnome-online-accounts via
   Importance: Unknown
       Status: Unknown

You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-online-accounts in Ubuntu.

  goa-daemon crashed with SIGSEGV in magazine_chain_pop_head()

Status in GNOME Online Accounts:
Status in gnome-online-accounts package in Ubuntu:

Bug description:
  Upgrade Ubuntu vidid and reboot and crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: gnome-online-accounts 3.14.2-1
  Uname: Linux 3.19.0-031900rc7-generic x86_64
  ApportVersion: 2.15.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Feb  2 19:46:37 2015
  ExecutablePath: /usr/lib/gnome-online-accounts/goa-daemon
  InstallationDate: Installed on 2014-09-25 (130 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140923)
  ProcCmdline: /usr/lib/gnome-online-accounts/goa-daemon
   Segfault happened at: 0x7f55b957e94d:	mov    (%rcx),%rax
   PC (0x7f55b957e94d) ok
   source "(%rcx)" (0xffffffff) not located in a known VMA region (needed readable region)!
   destination "%rax" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-online-accounts
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   __nptl_deallocate_tsd () at pthread_create.c:157
   start_thread (arg=0x7f5597182700) at pthread_create.c:322
   clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111
  Title: goa-daemon crashed with SIGSEGV in __nptl_deallocate_tsd()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

To manage notifications about this bug go to: