Deleting files in ~/.config is suboptimail in my case;
I have very few applications installed and already have 122 objects in .config.
It would be nice if someone [who knows] told us what variable we are to look
for.
that Google seems to be the culprit in virtually all cases here, and that the
Thank you Mat, deleting the config files seems to have worked for me
too.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-calendar in Ubuntu.
https://bugs.launchpad.net/bugs/1726922
Title:
gnome-calendar keeps asking for my
I solved it by deleting the calendar. It's on my mobile phone, enough.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-calendar in Ubuntu.
https://bugs.launchpad.net/bugs/1726922
Title:
gnome-calendar keeps asking for my google
On this page
https://askubuntu.com/questions/967137/calendar-constantly-requiring-
google-authentication-on-17-10
a solution is suggested:
"I was having the same problem and resolve it by deleting the
configuration files of Evolution. Do this:
rm -rf ./.config/goa-1.0/accounts.conf
rm -rf
Well, the workaround that works for me is to toggle off the Calendar in
the Search section of the system settings.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-calendar in Ubuntu.
https://bugs.launchpad.net/bugs/1726922
Title:
I'm affected by this issue and do have 2FA enabled, but using an app
specific password did not fix the issue. I still get frequent popups.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-calendar in Ubuntu.
Here is the workaround for people coming into this bug with Two Factor
Auth set. You need to generate an application specific password for the
Google acct in "Online Accounts" from this page:
https://security.google.com/settings/security/apppasswords
Google's full documentation on generating
There is no account conversion on upgrades or anything like that, and
yes it's an upstream issue if the code doesn't work as it should
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-calendar in Ubuntu.
Doug that's exactly what the bug says and why I filled it, you are not
being asked for the auth code simply because there is a bug in the
login. I filled the bug, the annoyance is because the application is
asking for a password it doesn't need.
My feeling is that it is using some remanent
Could it be that I had previously allowed me in due to having performed
the second auth before the upgrade? Aside from that, it's possible I
performed the auth during the initial stages of the upgrade and don't
remember now.
That said, it just seemed strange and potentially relevant that I am
doug are you sure you didn't allow it in online accounts settings?
That's the account and authorization used by calendar, I have 2 factor
authentication and when I set it up in online accounts it asked me for the
second face auth.
There's no way an app can access your calendar or other info if
I just upgraded from 17.04 to 17.10 today and am experiencing the issue
as described. One thing not previously mentioned by others: I have two
factor auth enabled on my account. I was never asked for the 2nd auth,
yet I still see my calendar data being updated.
--
You received this bug
According to the Gmail email notice I received:
"Google will continue to block sign-in attempts from the app you're using
because it has known security problems or is out of date. You can continue to
use this app by allowing access to less secure apps, but this may leave your
account
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-calendar (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-calendar in Ubuntu.
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue you are reporting is an upstream one and it
would be nice if somebody having it could send the bug to the developers
of the software by following the instructions at
15 matches
Mail list logo
