exausted, after tried several commands (included rm -r chatty related directories), being part of basic package so unable to purge it, I’m reflashing L5!! Incredible!! So:
first, I’m not going to use it because still highly unstable. I stored in my notes actual release 0.8.0.rc0 and I’ll wait for improvements before to use it
anyway is there a way, also considering commands in terminal, to remove an account?
Why to include it in a bigger package instead of single app?
I think the account info for chatty is stored in a “keyring” which is some kind of system-wide thing, which is why that info can still be there even after you removed chatty and its files.
The files for the “keyring” thing are in ~/.local/share/keyrings/ but things are binary and/or encrypted there so you may not be able to easily see what’s there. To see it, you can install the program seahorse (apt install seahorse) which will show up as an app called “Passwords and Keys”. Open that and select the right keyring (could be “default” or “login” or something like that) and then you can see stored secrets there and one of them is for chatty.
It’s all very confusing, even more so because there are several keyrings which has something to do with older and newer ways of doing things, at some point the default keyring was no longer called “default” but instead “login”, or the other way around, I don’t know.
I don’t know for sure either but I think the answer is:
The default keyring is whatever is nominated by the user as the default keyring. There is a file that points at it. And you can change the default keyring from the GUI i.e. seahorse - so there was no change in the software to the default keyring but perhaps there is a change to the default default keyring. I believe that the default keyring will receive any new keys added by default but you can override that in the GUI at the time of adding each new key.
The “login” keyring is the one that gets unlocked when you log in but it is possible that that also follows the setting of the default keyring. It is possible that you can alter that behaviour via PAM config (but it doesn’t work properly yet? on Librem 5 anyway).
I think that the current behaviour (on desktop) is not appropriate for me - where I want to unlock the login keyring at the time of login but I want by default to add new keys to a different keyring.
You can have any number of keyrings. For me, there is nothing confusing about that. That is just organising things in a logical way (just like you might not put all your files in your home directory) and organising things in a way that recognises that there is a hierarchy of security. (At the highest level are the passwords that are too important to store on a computer, ranging down through highly important passwords that require stronger protection, to random web site passwords that don’t require particularly strong protection, perhaps to the login keyring which will be unlocked by default.)
I believe that the default keyring will receive any new keys added by default but you can override that in the GUI at the time of adding each new key.