Skip to content
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

Cannot find keyring #154

Open
ramiromagno opened this issue Nov 15, 2024 · 3 comments
Open

Cannot find keyring #154

ramiromagno opened this issue Nov 15, 2024 · 3 comments

Comments

@ramiromagno
Copy link

I'm on Arch Linux and I do have libsecret, libsodium and openssl installed.

> pak::pak("keyring")
✔ Updated metadata database: 3.05 MB in 7 files.                          
✔ Updating metadata database ... done                                     
                                                                           
→ Will install 1 package.
→ Will download 1 CRAN package (46.50 kB).
+ keyring   1.3.2 [bld][cmp][dl] (46.50 kB)
ℹ Getting 1 pkg (46.50 kB)
✔ Got keyring 1.3.2 (source) (46.50 kB)                                 
✔ Downloaded 1 package (46.50 kB) in 454ms                              
ℹ Building keyring 1.3.2
✔ Built keyring 1.3.2 (2.2s)                                     
✔ Installed keyring 1.3.2  (1s)                                     
✔ 1 pkg + 9 deps: kept 4, added 1, dld 1 (46.50 kB) [8.3s]          
> library(keyring)
> key_set("utg-pg")
Error in b_ss_set_with_value(self, private, service, username, password,  : 
  Cannot find keyring
@r2evans
Copy link

r2evans commented Nov 22, 2024

I'm now getting the same thing in my ubuntu-24.04 R-4.3.3, where keyring has been working without change for a couple of years ... I don't see anything obvious in ubuntu package updates, specifically libsecret packages have not been updated/touched since June (2024).

@gaborcsardi
Copy link
Member

Well, keyring hasn't changed for three years, so I beat you there. :D

@r2evans
Copy link

r2evans commented Nov 23, 2024

Yes you win :-D

The issue self-resolved after rebooting ubuntu, suggesting it is an issue with libsecret or gnome-keyring-daemon. I added my comment above to reinforce that it can easily be an issue unrelated to this package. In my case, there have been no updates recently for libsecret-* or gnome-keyring (OS-level) packages, so I hope it was "just a glitch". It's the first time I've experienced it since installing Ubuntu-24.04 (and for a bit with -23.10 before that), so ... uncommon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants