goa-daemon crashed with SIGSEGV in ffi_call_SYSV()

Bug #846503 reported by Reiner B.
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-online-accounts (Ubuntu)
New
Undecided
Unassigned

Bug Description

After login this error occures. I had to do nothing.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gnome-online-accounts 3.1.90-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
Uname: Linux 3.0.0-10-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 1.22.1-0ubuntu2
Architecture: i386
CrashCounter: 1
Date: Sat Sep 10 17:52:45 2011
ExecutablePath: /usr/lib/gnome-online-accounts/goa-daemon
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110705.1)
ProcCmdline: /usr/lib/gnome-online-accounts/goa-daemon
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
SegvAnalysis:
 Segfault happened at: 0x73a3c2: mov 0x0(%ebp),%eax
 PC (0x0073a3c2) ok
 source "0x0(%ebp)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-online-accounts
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/i386-linux-gnu/libnotify.so.4
 ffi_call_SYSV () from /usr/lib/i386-linux-gnu/libffi.so.6
 ffi_call () from /usr/lib/i386-linux-gnu/libffi.so.6
 g_cclosure_marshal_generic () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
Title: goa-daemon crashed with SIGSEGV in ffi_call_SYSV()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Reiner B. (rbarth) wrote :
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 #843375, 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
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.