When looking at file .xsession-errors I See this trace: org.kde.kgapi: Received reply from QUrl("https://accounts.google.com/o/oauth2/token") org.kde.kgapi: Status code: 0 org.kde.kgapi.raw: "" org.kde.kgapi: Failed to parse server response. org.kde.kgapi.raw: "" org.kde.kgapi: 0 requests in requestQueue. org.kde.kgapi: org.kde.kgapi: Requesting AccountInfo org.kde.kgapi.raw: ("Authorization: Bearer ") org.kde.kgapi: Queued QUrl("https://www.googleapis.com/oauth2/v1/userinfo") org.kde.kgapi: KGAPI2::AccountInfoFetchJob(0x21d68e0) Dispatching request to QUrl("https://www.googleapis.com/oauth2/v1/userinfo") org.kde.kgapi.raw: "" QQuickItem::ungrabMouse(): Item is not the mouse grabber. org.kde.kgapi: Received reply from QUrl("https://www.googleapis.com/oauth2/v1/userinfo") org.kde.kgapi: Status code: 0 org.kde.kgapi.raw: "" org.kde.kgapi: org.kde.kgapi: Error when retrieving AccountInfo: "Invalid response content type" org.kde.kgapi: org.kde.kgapi: 4 It probably fails at receiving the data because when the token data is fetched with curl, curl succeeds. Reproducible: Always Steps to Reproduce: 1. Add Google calendar resource 2. Wait a long time on Authorizing token, this should take just a moment... 3. No account is added(seemingly) Actual Results: No account is added and when trying to reload I get: Invalid response content type Expected Results: Add a google calendar account correctly
I got the same error message 'Error when retrieving AccountInfo: "Invalid response content type"', during adding google credentials on System Settings -> PIM accounts. After google login and accepting the permissions, everything seems fine, but the account select box is empty. org.kde.kgapi: Requesting AccountInfo org.kde.kgapi.raw: ("Authorization: Bearer ya29._QEFlDDH0eqAFIA-kO1JbftAcER6reL0XY4FfY13heXmGzZLnRIGmRK6nzGMkqfDCpak") org.kde.kgapi: Queued QUrl( "https://www.googleapis.com/oauth2/v1/userinfo" ) org.kde.kgapi: KGAPI2::AccountInfoFetchJob(0x1ffda00) Dispatching request to QUrl( "https://www.googleapis.com/oauth2/v1/userinfo" ) org.kde.kgapi.raw: "" org.kde.kgapi: Received reply from QUrl( "https://www.googleapis.com/oauth2/v1/userinfo" ) org.kde.kgapi: Status code: 0 org.kde.kgapi.raw: "" org.kde.kgapi: org.kde.kgapi: Error when retrieving AccountInfo: "Invalid response content type" org.kde.kgapi: org.kde.kgapi: 4
I'm currently experiencing the same bug with 17.08.1 - it is then impossible to sync with google calendar as the account login doesn't work... Any known workaround?
Apparently, recompiling some libraries did the trick.. sorry for the noise.
Seeing this with kontact 17.12.0-40.5 (openSUSE RPM).
I am unable to add a Google calendar to korganizer version 17.12.0-1. I run Arch Linux. The process is stuck at a window where we read: "Authorizing token. This should take a moment..."
The same thing with latest Arch Linux, in korganizer , kontact and akonadi console. I tried to copy the link of the authorization process to an external browser and it gives me an authorization code to copy-paste to my application.
(In reply to Dimitris Damigos from comment #6) > The same thing with latest Arch Linux, in korganizer , kontact and akonadi > console. I tried to copy the link of the authorization process to an > external browser and it gives me an authorization code to copy-paste to my > application. How exactly were you able to copy the link of the authorization process? From where did you copy it?
Created attachment 109650 [details] "Authorizing token. This should take a moment..."
(In reply to Francisco Cribari from comment #7) > (In reply to Dimitris Damigos from comment #6) > > The same thing with latest Arch Linux, in korganizer , kontact and akonadi > > console. I tried to copy the link of the authorization process to an > > external browser and it gives me an authorization code to copy-paste to my > > application. > > How exactly were you able to copy the link of the authorization process? > From where did you copy it? It's visible in the address bar, before the message "Authorizing token. This should take a moment..." appears. Check the screenshot.
(In reply to Dimitris Damigos from comment #9) > (In reply to Francisco Cribari from comment #7) > > (In reply to Dimitris Damigos from comment #6) > > > The same thing with latest Arch Linux, in korganizer , kontact and akonadi > > > console. I tried to copy the link of the authorization process to an > > > external browser and it gives me an authorization code to copy-paste to my > > > application. > > > > How exactly were you able to copy the link of the authorization process? > > From where did you copy it? > > It's visible in the address bar, before the message "Authorizing token. This > should take a moment..." appears. Check the screenshot. Thank you. I was able to copy the code. Where exactly did you paste it in KOrganizer? (In reply to Dimitris Damigos from comment #9) > (In reply to Francisco Cribari from comment #7) > > (In reply to Dimitris Damigos from comment #6) > > > The same thing with latest Arch Linux, in korganizer , kontact and akonadi > > > console. I tried to copy the link of the authorization process to an > > > external browser and it gives me an authorization code to copy-paste to my > > > application. > > > > How exactly were you able to copy the link of the authorization process? > > From where did you copy it? > > It's visible in the address bar, before the message "Authorizing token. This > should take a moment..." appears. Check the screenshot. Thank you. I was able to get the code and copied it. Where exactly did you paste it in KOrganizer?
You cannot paste it anywhere. This should happened automatically, and I guess this is the step where the authentication halts... And I don't have the knowledge to debug it further.
The issue in the last few comments has arised recently and is surely unrelated to this 2015 bug. Please continue the discussion in bug 388483
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!