All the best,
-HG
]]>gnome-shell 3.8.3-1
gnome-keyring 3.8.2-1
edit:
Damn, should've read...
In this thread, comment 10 gives instructions for using an application specific password instear of the regular google password that seahorse is storing. I did this, logged in, and everything started working, with no errors. Hopefully this will help someone else looking for an answer.
https://bugzilla.gnome.org/show_bug.cgi?id=688364#c2
In this thread, comment 10 gives instructions for using an application specific password instear of the regular google password that seahorse is storing. I did this, logged in, and everything started working, with no errors. Hopefully this will help someone else looking for an answer.
Ivan [reporter] 2012-11-15 16:39:40 UTC
However I found a way to fix, thanks @Ionut showing a path
In my GOA_ entry I edited 'password' field
So I removed my generic google password and inserted google application
password, I got in my 2-factor authentication page. So it's working fine now,
but it should be fixed I think ti work out of box
Ivan [reporter] 2012-11-20 03:20:38 UTC
(In reply to comment #20)
> Use Seahorse to look at your keyring and try to locate the entry associated
> with your Google account. (Hint: You can put "GOA" in the search bar to filter
> the view to show only things stored by GOA.)
>
> You will see that it has a dictionary. Locate the key called "password".
> Replace the value associated with that key with your application specific
> password.
Yes. Check the show password, you'll see a long GOA_ string. At the end you'll
see your google password. If you enable 2-factor auth and reproduces a bug, you
should make an application password in google account and replace your google
password in seahorse with it. Logoff and login again after solves the
"expiration" problem
If I remove/re-add account from GNOME3's "Online Account" setting box. It did not fix it.
I have to do use the Empathy/Accounts dialogue box. But when I did this in GNOME, it brought me to the "Online Account" box. When I did it later in XFCE, that fixes it.
Utter stupidity...
]]>