-
Notifications
You must be signed in to change notification settings - Fork 32
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
Linux - pydio-sync is not able to use gnome-keyring to save credentials in Ubuntu 18.04 #173
Comments
hi @casasfernando |
Ok. Thanks for looking into this. |
BTW Charles, while building pydio-sync I found also that there may be an issue with the code in pydio python sdk "python-2" branch that cause file upload to fail with error "Upload error: file is partial (410)". There is an issue already open in github for a long time in case you can take a look at it: pydio/pydio-sdk-python#2 |
Please disregard this last message. I already found the cause of the problem and updated the open issue in pydio-sdk-python. |
Thanks for your post, I ran into the same issue after upgrading to 18.04 months ago and finally could solve it with pydio-sync running in a virtualenv and upgrading versions of
|
After upgrading from Ubuntu 16.04 to 18.04 I found that pydio-agent is not able to use gnome-keyring anymore so is falling back to python file keyring backend to save credentials.
Because of this now is not possible to run the agent on startup (unattended) and the only way to make it work is to start it manually from a terminal so the file keyring password can be entered.
In order to solve this problem I rebuild the module using a more recent keyring python module (the one that is shipped with Ubuntu 18.04 - v10.6.0) and the problem was solved. The agent is able to use gnome-keyring again and it can be started without the use of a terminal since it doesn't require any interaction anymore.
Can you please look into updating the keyring module version dependency in requirements.txt file and build a new pydio-agent binary?
The text was updated successfully, but these errors were encountered: