-
Notifications
You must be signed in to change notification settings - Fork 669
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ownCloud 2.6rc2 fails to read keychain on Debian 10 #7536
Comments
Thanks for testing the RC2 Did it work with the previous version of the client? |
|
I don't have a setup ready to test Debian 10. Does the log not show some more information about the reason why this fails? |
My gnome-keyring version is 3.28.2. Here is the std output to the terminal, stripped of my personal information. It seems to just say "Invalid credentials for "xyz" asking user". Is there anything else I can log to pin down the problem? |
Bump to this issue, the client won't remember the password on Ubuntu 19.10 or CentOS Stream for me.. Ubuntu using keyring version |
see #7578 |
2.6.0 still produces this bug even without libgnome-keyring, but it seems to be fixed in the testing repo. |
Was most likely caused by #7578 |
Expected behaviour
ownCloud saves my credentials and uses them for logging in on startup.
Actual behaviour
I have two accounts linked to different servers. One of the connections now fails telling me "reading from keychain failed with error: unknown error" and asks to enter my password. The other one always pops up the browser asking me to authorize this app. After entering my pw and authorizing it works.
Client configuration
Client version:
2.6.0~rc2+oc-1598
Operating system:
Debian 10 (buster)
4.19.0-6-amd64
Gnome 3.30.2
OS language:
English (UK)
Client package (From ownCloud or distro) (Linux only):
latest ownCloud package from
https://software.opensuse.org//download.html?project=isv:ownCloud:desktop:testing&package=owncloud-client
Sorry, but as of now I can't provide any logfiles etc. please ask if you need more info.
The text was updated successfully, but these errors were encountered: