[Solved] Polkit /policykit-1-gnome question

[cds60601]

Hey all -

I don't seem to recall this happening in the past (not a huge deal of course).
When invoking a policy kit (policykit-1-gnome) and having gnome-keyring also, I seem to recall that it prompting for a password one time only. Now, when ever I reboot and the services that require this information, I seem to experience the request for a password and when I check to save, am prompted again for a keyring password.

I cleared out ~/.local/share/keyrings thinking that the copy of the files that were there may have the incorrect permissions. Again,I don't seem to recall this happening before and since this is happening on a fresh build - I don't know if this is a SOP or not. And if not, what has someone done to correct this.

TIA
C.

[Head_on_a_Stick]

So is this for your i3 desktop?

How are you launching policykit-1-gnome?

Have you exported the secrets for the gnome-keyring-daemon?

For example:

Code: Select all

# ~/.profile
export $(gnome-keyring-daemon --start --components=pkcs11,secrets)

^ That will need to go before the startx line (if you're using my suggestion).

[cds60601]

So is this for your i3 desktop?

How are you launching policykit-1-gnome?

Have you exported the secrets for the gnome-keyring-daemon?

For example:

Code: Select all

# ~/.profile
export $(gnome-keyring-daemon --start --components=pkcs11,secrets)

^ That will need to go before the startx line (if you're using my suggestion).

Sorry for the lateness in the reply, HoaS. Well - I'm not sure how to answer that so allow me to show you what I DO have.

I have opted to remove most of my listings (runonce etc) from my i3 config in favor of adding them to my .xprofile - so here are the 2 entries.

Code: Select all

/usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1 &
/usr/bin/gnome-keyring-daemon --start --components=pkcs11 &

That's all I really ever had and it seemed to work as I described. Of course I could be wrong but I dont recall it ever asking on each boot up.
I hope that tells you something.

UPDATE:
Meh - I worked it out after a little reading (it would help if I actually read the prompts when prompted). D'oh!!!

C.

[Head_on_a_Stick]

I worked it out

Please post your solution, it may be useful to the community.

[cds60601]

I worked it out

Please post your solution, it may be useful to the community.

Sure! It's probably NOT the best solution as there are some ramifications to this. But in a nutshell, I changed the password (via seahorse) to use no password. This eliminated the prompting at every reboot. Again, I know its not the ideal solution (I think if I read correctly, it leaves the credentials in the keyring unencrypted).

I'll still investigate a more suitable solution and in the end, it really wasn't a huge deal to input the password. Just something I noticed that was different from say an install of ArchLabs or Arch.

UPDATE: Pending...