Description of problem: When starting nextcloud, after reboot, there is a dialog to enter the password with the message: No keychain service available Version-Release number of selected component (if applicable): 2.3.3 How reproducible: The dialog pops up after every reboot Steps to Reproduce: 1.Reboot Actual results: Dialog to input password pops up Expected results: The password should be stored Additional info: Problem can be fixed by installing "sudo dnf install libgnome-keyring"
from #fedora-devel: most apps have migrated from old libgnome-keyring to newer libsecret, that's why it's no longer installed as default Moreover, as stated in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892359 The libgnome-keyring library is deprecated and its usage is strongly discouraged [2]. Waiting for upstream to implement libsecret usage. [2] https://git.gnome.org/browse/libgnome-keyring/commit/?id=6a5adea4aec93
*** Bug 1665728 has been marked as a duplicate of this bug. ***
I don't think that the issue is actually closed because the problem is still there until the software uses and the package depends on libsecret, but anyway, I've referenced this bug towards https://github.com/nextcloud/desktop/issues/990 and https://github.com/nextcloud/desktop/issues/883 - hopefully we'll get sooner than later an upstream fix of the issue.
*** Bug 1669590 has been marked as a duplicate of this bug. ***
*** Bug 1674106 has been marked as a duplicate of this bug. ***
*** Bug 1754003 has been marked as a duplicate of this bug. ***
I just hit this issue on Fedora 31. My reading of the upstream issue: https://github.com/nextcloud/desktop/issues/427 is that the problem is due to qtkeychain-qt5 (nextcloud-client dependency) missing support for libsecret. I'm out of my depth here, so could be talking nonsense!
IMHO the problem is still there because the nextcloud-client package still doesn't depend on libsecret. Install libsecret and the issue is gone.
The issue is still present. Installing libgnome-keyring manually is still a quick fix. Can't libgnome-keyring be added as a dependency until upstream uses libsecret?
Indeed, [this](https://help.nextcloud.com/t/fedora-30-nextcloud-client-issues-does-not-preserve-login-after-user-account-logout-or-reboot/56770/3 "Fedora 30 Nextcloud client issues — does not preserve login after user account logout or reboot") is still an issue with F31. Apparently the nextcloud client is kinda QT5-centric and does not seem to include any Gnome libraries at all: ------------------------------------------------------------------------ $ dnf deplist `rpm -qa | grep nextcloud` | egrep -i '^package|key|gnome|^$' package: nextcloud-client-2.6.4-3.fc31.x86_64 dependency: libqt5keychain.so.1()(64bit) provider: qtkeychain-qt5-0.9.1-3.fc31.x86_64 package: nextcloud-client-libs-2.6.4-3.fc31.x86_64 dependency: libqt5keychain.so.1()(64bit) provider: qtkeychain-qt5-0.9.1-3.fc31.x86_64 package: nextcloud-client-nautilus-2.6.4-3.fc31.x86_64 ------------------------------------------------------------------------ Can this bug be re-opened or shall we open a new report?
FEDORA-2020-3532b01b96 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-3532b01b96
FEDORA-2020-55ce43f6c4 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2020-55ce43f6c4
FEDORA-2020-973ee8680b has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-973ee8680b
Please test the just submitted new testing updates and leave a karma feedback Thank you
*** Bug 1791915 has been marked as a duplicate of this bug. ***
FEDORA-2020-973ee8680b has been pushed to the Fedora 32 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-973ee8680b` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-973ee8680b See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-55ce43f6c4 has been pushed to the Fedora 30 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-55ce43f6c4` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-55ce43f6c4 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-3532b01b96 has been pushed to the Fedora 31 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-3532b01b96` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-3532b01b96 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-973ee8680b has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2020-3532b01b96 has been pushed to the Fedora 31 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2020-55ce43f6c4 has been pushed to the Fedora 30 stable repository. If problem still persists, please make note of it in this bug report.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days