This really needs attention, obviously the best fix would be to go back in 
time and change a few things so this didn't happen in the first place but it 
is probably more cost effective and quicker if the devs were more proactive 
about sorting things out with google.

FWIW the "fix" isn't working for every instance - it seems ok for the first 
machine on the account but subsequent ones trigger an amazing cascade of 
google lockouts and security warnings which sends akonadi on that machine into 
CPU melt that needs killing (and restarts everytime the network resumes) (yes 
I should report this as yet another akonadi / gmail bug but, franky, what's 
the point?).

SA




Reply via email to