Bug 1665728

Summary: nextcloud-client must depend on libgnome-keyring to avoid No keychain service available
Product: [Fedora] Fedora Reporter: Eric Lavarde <elavarde>
Component: nextcloud-clientAssignee: Germano Massullo <germano.massullo>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 29CC: claudiorodrigo, comzeradd, germano.massullo, nb, nonamedotc, pokorra.mailinglists
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: 2019-01-14 09:35:23 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:
Embargoed:

Description Eric Lavarde 2019-01-13 10:28:10 UTC
Description of problem:

when installing nextcloud-client, after a reboot, the client is missing its password, which needs to be re-entered manually. It pops a message that no keychain service is available. Installing the package libgnome-keyring solves the issue.

Version-Release number of selected component (if applicable):

nextcloud-client-2.3.3-2.fc28.x86_64
libgnome-keyring-3.12.0-15.fc29.x86_64

How reproducible:

Always, stopping the client and trying again, as well as rebooting doesn't help.

Steps to Reproduce:
1. Install the nextcloud client (make sure libgnome-keyring isn't installed)
2. Configure the client once with an application password
3. reboot

Actual results:

When the client starts after login into the desktop (Cinnamon in my case), the client complains that it can't grab the password because no keychain service is available. Stopping and restarting the nextcloud client doesn't help (I had first thought about a race condition during start of the desktop).

After having installed libgnome-keyring manually, everything started to work as expected and application password survives a reboot / restart of the client.

Expected results:

The password is save in the desktop's keyring and I don't need to generate a new application password, respectively libgnome-keyring had been installed automatically as I installed nextcloud-client.

Additional info:

I found the workaround in https://github.com/owncloud/client/issues/6500 even if it concerns OwnCloud and Ubuntu (there are comments about Fedora though).

Comment 1 Germano Massullo 2019-01-14 09:35:23 UTC

*** This bug has been marked as a duplicate of bug 1652973 ***