Bug 1404505

Summary:	Unable to login into Google Drive and Dropbox
Product:	[Fedora] Fedora	Reporter:	Pedro Albuquerque Santos <petersaints>
Component:	clementine	Assignee:	Jan Grulich <jgrulich>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	25	CC:	jgrulich, sphinx.ligustri
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-12-12 10:40:20 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Pedro Albuquerque Santos 2016-12-14 00:35:27 UTC

Description of problem:
Unable to login into Google Drive and Dropbox.

Version-Release number of selected component (if applicable):
1.3.1-2.fc25

How reproducible:
ALWAYS. It happens everytime I try it.

Steps to Reproduce:
1. Open Clementine
2. Go to Tools > Preferences > Internet Providers > Google Drive
3. Press the Login button
4. You are redirected to your default browser for authentication and authorization.
5. You give Clementine permission to access your data.
6. You are greeted with the following message in your browser
"Success!
Please close your browser and return to Clementine."
7. You get back to Clementine to check if have been successfully signed in.

Actual results:
The Google Drive preferences continue to show "You are not signed in".

Expected results:
The Google Drive preferences should show that you are signed in.

Additional info:
I tested it on a VM running the latest openSUSE Tumbleweed snapshot it worked fine there. To be sure that it was nothing wrong with my Fedora installation I also tried it from a Fedora 25 Workstation live session but the behavior was exactly the same as on my live install. Therefore, it seems to be some packaging or configuration error.

Meanwhile, I also run Clementine directly from the command line and at the moment that you authorize your Google account and that Clementine should have captured the OAuth tokens I get the following error messages on the terminal:
"00:18:49.302 ERROR unknown JSonScanner::yylex - error while reading from io device
00:18:49.302 ERROR unknown json_parser - syntax error found, forcing abort, Line 1 Column 1"

I tried to Google a little bit about it but I was unable to find anything concrete that linked this errors to Clementine on Fedora or on any other distro.

If you need any extra information from me to fix this bug, feel free to contact me.

Comment 1 Pedro Albuquerque Santos 2016-12-14 12:21:07 UTC

I'd like to add that I the latest Fedora Rawhide snapshot (Fedora-Workstation-ostree-x86_64-Rawhide-20161018.n.0.iso) and the bug is still present. I also tried on Ubuntu GNOME 16.10 and it works as intended.

I did the Ubuntu GNOME 16.10 test because I thought that it could be due to some dependencies that were newer on Fedora that could break compatibility with how Clementine expects them to work. 

However, that MAY not be the case since the bug is also absent on openSUSE Tumbleweed and they tend to be very up to date. Tumbleweed should at least be on par with Fedora 25 and it can possibly match Rawhide in terms of package freshness.

Comment 2 Fedora End Of Life 2017-11-16 19:20:49 UTC

This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2017-12-12 10:40:20 UTC

Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.