Description of problem: The owncloud client does not retain anymore credentials Version-Release number of selected component (if applicable): owncloud-client 1.8.3 1.mga4 How reproducible: Every time I open my session, the owncloud client ask my credentials. It was not the case with the previous version (1.4 if I remember). I've tried to delete and recreate the folder sync, same behaviour, also try to delete .local/share/owncloud files and reconfigure the sync. My server is still the same : 6.0.9 Steps to Reproduce: 1. Run the owncloud client and setup a folder to sync, type you credentials username and password, sync is working fine. 2.Close your session or shut down the computer 3.Open the session, owncloud-client ask the password again whereas with the previous version it was stored. Reproducible: Steps to Reproduce:
CC: (none) => marja11
assigning to maintainer (without having tried to reproduce)
Assignee: bugsquad => mageia
It seem to use Kwallet to store credentials. (I am on KDE) When i log in to my desktop, kwallet pups up asking for my password for its database. After i enter it, owncloud logs on automaticaly. (i have it set to autostart) If i do not enter it, it seem owncloud (and kmail) get timeout and i have to enter credentials in those programs directly. Do you use KDE, and do you have kwallet installed? If you run another DE, i guess owncloud tries to use whatever is providing that functionality there.
CC: (none) => fri
Also see https://github.com/frankosterfeld/qtkeychain/issues/25
Hi Morgan, I'm using KDE and Kwallet is installed. I've also checked that Kwallet manager is started when i login to my session. If I recreate my connection, I see that my owncloud section in Kwallet is well up to date. I've also create a shortcut in Dolphin with a path like webdavs:// pointing to the same directory. It's asking the password the first time, it's stored in kwallet and Dolphin never ask the password again. So I don't think it's coming from Kwallet but really from this update of the client.
Created attachment 6990 [details] Kwallet Owncloud section
Have you checked owncloud bug tracker and forum, and maybe ask there? https://wiki.mageia.org/en/OwnCloud#Useful_links
Yes, I found this post on the github. https://github.com/owncloud/client/issues/1590 According to this article, the problem is not only on Mageia... that's a good point :-) There are some things I don't understand because I'm not a developer. Seem to be a problem with the version of qtkeychain. An user has resolved the problem with a script that delay the owncloud process to let the kwallet start before. I don't know if there's a KDE tool to specify that a process must start before another one.
__WORKAROUNDS__ Simplest is to not have dropbox start automatically, but then you have to remember to start it. Next simplest is to add a delay using KDE settings for autostarting programs; (naming below may not be accurate; i am translating from swedish) In KDE settings (the icon of the crossed tools in KDE menu) > last section "System administration" > Start and shutdown. There in section Automatic start, i guess you have an entry named ownCloud. Select it, then button "Properties...". In there select tab "Program" and in the "Command" field prepend "sleep 10; " before whatever is there. ( 10 is ten seconds, alter if you want ) Possibly also have it start kwalletd first, like Faldrian describe at https://github.com/owncloud/client/issues/1590#issuecomment-69790447 So also add that, so your total addition to the line should be: "kwalletd; sleep 10; " Please report back if that works for you. __FIXING__ I see even current mga5 and mha6/cauldron still use qtkeychain0 version 0.1.0 (jan 2013) , while latest release is 0.5.0 (may 2015) - Maybe time to update? I now posted Bug 16712 about that. On the other hand some people (on other distros) have tried versions 0.3.0 and 0.4.0 without success, but maybe would work better if updated before ownloud install - they say something about naming scheme differs.
Thanks you Morgan. It was easy, I've just never have to edit things in this menu. The only thing to notice is that I first edit the owncloud entry, it does not work. I had to delete the entry and recreate it and prefixed it with the sleep command. It does work ! I post the printscreen
Created attachment 6993 [details] Config to do for the owncloud client that ask password at each logon
Attachment 6993 mime type: text/plain => image/jpeg
1) Thanks for feedback :) I now added this problem solution to https://wiki.mageia.org/en/OwnCloud#Storing_Credentials 2) I too noticed something strange when editing it on mga5: the column for when it should start became empty, but closing and then opening KDE settigns again, it was listed again to execute at start, and works. If other too have problems there is a link in the wiki pointing here to your and my findings. 3) Firefox and Chromium browsers fail to view that attachement you made. Did you set wrong file type? This is just a workaround, so: While it is not a bug in ownCloud i suggest to keep this bug open until problems are resolved so someone else who sees this and search here can find the workaround and not issue a duplicate.
Created attachment 6994 [details] Configure owncloud startup
Attachment 6993 is obsolete: 0 => 1
Keywords: (none) => UPSTREAM
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version. Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't able to fix it before Mageia 4's end of life. If you are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. If it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version) If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED" 2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. 3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page: https://wiki.mageia.org/en/How_to_report_a_bug_properly If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
Status: NEW => RESOLVEDResolution: (none) => OLD
Hello, this case can be closed. I've updated to Mageia 5 a few days ago. I've deleted my startup script to verify and I confirm that the problem has disappeared.