On Friday 10 June 2016 09:17:51 Hans Vanpee wrote: > Tobias Ellinghaus <me@...> writes: > > I am actually using KDE. And I have no idea how to configure that secret > > service stuff (in general, not even limited to any KDE specific parts). > > Are > > you > > > aware of any documentation? > > For KDE darktable uses kwallet in stead of libsecret.
Wrong. darktable uses whatever it's configured to use. > My patch concerns > libsecret only so it should not make any difference for you. Libsecret itself doesn't store any passwords. It's just an abstraction so that applications (like dt) only need to talk to one service. In the background the secret service is supposed to hand the data to Gnome Keyring, Kwallet or others. So eventually only libsecret should be needed to make everyone happy. However, until now I didn't find any way to actually configure what backend should be used. Or to determine which is used. > Kwallet and libsecret are the only password storage backends supported by dt > for the moment. Kwallet is selected for the KDE desktop only. Libsecret is > used for Gnome, Unity and XFCE. As pointed out that is only true for the "auto" setting. > I have no experience at all with KDE nor with kwallet. I don't even know if > password storage works fine on KDE. Can you confirm if it works? I didn't > look at the backend_kwallet code because I have no means of testing it. Directly talking to kwallet works like a charm. But that is not the issue we are having. The problem is that libsecret isn't working as intended. And limiting its use to environments where Gnome Keyring is used in the back is not acceptable as it's intended to work across different DEs. Tobias
signature.asc
Description: This is a digitally signed message part.
