nextcloud does not attempt to unlock the gnome keyring on startup

[elinorbgr]

I'm running Gentoo, with the following versions of packages:

• nextcloud-client 2.3.3
• qtkeychain 0.8.0
• lignome-keyring 3.12.0
• gnome-keyring 3.20.1

Since my last system update, on startup of nextcloud-client I no longer get a popup prompting me for the password of my keyring, instead nextcloud-client directly prompts me for an app password. If I create a new one and enter it, then I am prompted for the password to unlock my keyring so that nextcloud can store it.

On the other hand, if I unlock the keyring beforehand (using seahorse for example) and start nextcloud afterwards, then it directly connects without prompting me for an app password.

[rullzer]

This should be fixed in master I believe.

[gerhardbeck]

snap connect nextcloud-client:password-manager-service might solve the problem when installed via snap

[ogasser]

I can confirm that this also happens for Arch Linux with the following package versions:

• nextcloud-client 2.3.3
• qtkeychain 0.9.0
• libgnome-keyring 3.12.0
• gnome-keyring 3.28.2

Manually unlocking the keyring before starting nextcloud works as a workaround.

[jancborchardt]

@rullzer @camilasan when is the next release scheduled which would include the fix? :)

[stacyharper]

Until the next release, how do you manually unlock gnome keyring ?

[elinorbgr]

@Eluminae Personally I'm using seahorse

[bpcurse]

Confirmed with Manjaro Linux:

• nextcloud-client 2.3.3
• qtkeychain 0.9.0-1
• libgnome-keyring 3.12.0-3
• gnome-keyring 3.28.2-1

Unlocking the keyring with seahorse prior to opening the client helps as described above.

[camilasan]

Hi All :) Could you try one of the daily builds?
https://download.nextcloud.com/desktop/daily/Linux/
As @rullzer said this should be fixed in master.

[bpcurse]

@camilasan
Thank you for proposing the daily builds. The issue is gone in my setup with 2.5.0.20180730 (tried only the latest)