Ubuntu
gnome-online-accounts package

goa-daemon starts broken

Bug #1651575 reported by Richard on 2016-12-20

This bug report is a duplicate of: Bug #1610944: GNOME Online Accounts breaks if you log out (until you reboot). Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	gnome-online-accounts (Fedora)	Unknown	Unknown	redhat-bugs #1350678
	gnome-online-accounts (Ubuntu)	New	Undecided	Unassigned

Bug Description

goa-daemon, that is started with GNOME Shell/Wayland on login, on 16.10 launches in a corrupt state where all authentication fails.

This can be seen by launching Evolution which fails to use credential from goa.

GETAROUND
restart goa

killall goa-daemon

- goa-daemon retarts by itself
- authentication now works

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: gnome-online-accounts 3.22.2-1~ubuntu16.10.1 [origin: LP-PPA-gnome3-team-gnome3-staging]
ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
Uname: Linux 4.8.0-30-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Dec 20 12:17:37 2016
SourcePackage: gnome-online-accounts
UpgradeStatus: Upgraded to yakkety on 2016-11-16 (34 days ago)

Tags:

Revision history for this message

Richard (ismail-a) wrote on 2016-12-20:

CrashDB.txt Edit (263 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (21.9 KiB, text/plain; charset="utf-8")
JournalErrors.txt Edit (99.5 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (107 bytes, text/plain; charset="utf-8")

Revision history for this message

Richard (ismail-a) wrote on 2016-12-20:

https://bugzilla.redhat.com/show_bug.cgi?id=1350678

affects:

ubuntu-gnome → gnome-online-accounts (Ubuntu)

Revision history for this message

Jeremy Bícha (jbicha) wrote on 2016-12-24:

Your problem is just with Google accounts, right? This is because of a bug in evolution-data-server that is being worked on.

The bugs tracking this issue are:
https://launchpad.net/bugs/1639926
https://launchpad.net/bugs/1649995

Therefore, I'm marking this bug as a duplicate.

Revision history for this message

Richard (ismail-a) wrote on 2016-12-24:

It appear to not be the same as those two bugs, although the getaround is the same: restart the daemon

In this case, evolution is attempting to authenticate against a locally hosted plain password login wrapped in https (off-the-mill php)

Evolution does not offer to store the credentials somewhere, it accepts them and the next time you start evolution, it says authentication failed. I could not authenticate until I realized goa-daemon needs a restart. I had no idea there was a goa-daemon before it broke.