Home How to How to fix WARNING: gnome-keyring:: couldn’t connect to: /root/.cache/keyring-yNzNuC/pkcs11: No such file or directory?

How to fix WARNING: gnome-keyring:: couldn’t connect to: /root/.cache/keyring-yNzNuC/pkcs11: No such file or directory?

by blackMORE
How to fix WARNING: gnome-keyring error-3 - blackMORE Ops.jpg

Couple of days back I was trying to run WPSCAN and I received an interesting warning on my XFCE Desktop. WARNING: gnome-keyring:: couldn't connect to: /root/.cache/keyring-yNzNuC/pkcs11: No such file or directory?. The warning doesn’t actually stops me from doing anything, but I was obviously curious and found that I had exactly the same WARNING: gnome-keyring on my LXDE Desktop as well. This was not the same on my GNOME Desktop.

 

How to fix WARNING: gnome-keyring issue

I get this warning when I try to run wpscan.

WARNING: gnome-keyring:: couldn't connect to: /root/.cache/keyring-XxxXxXx/pkcs11: No such file or directory

How to fix WARNING: gnome-keyring error-1 - blackMORE Ops

Same warning appears when I try to ssh to git.

WARNING: gnome-keyring:: couldn't connect to: /root/.cache/keyring-XxxXxXx/pkcs11: No such file or directory

A quick Google search shows many users get this warning in different distributions, such as Ubuntu, Kali, Linux Mint Debian Edition, Debian, Slackware etc.

WARNING: gnome-keyring:: couldn't connect to: /tmp/keyring-IVaeDO/pkcs11: No such file or directory

When using PYLOTRO:

WARNING: gnome-keyring:: couldn't connect to: /tmp/keyring-YPU1bi/pkcs11: No such file or directory
*** Finished ***

Here’s how to fix it..

Edit /etc/xdg/autostart/gnome-keyring-pkcs11.desktop file:

leafpad /etc/xdg/autostart/gnome-keyring-pkcs11.desktop

How to fix WARNING: gnome-keyring error-2 - blackMORE Ops.jpg

 

Go to the OnlyShowIn line and add XFCE; at the end of it.

Note: If you’re using KDE, MATE, LXDE, XFCE, GNOME, Unity, Cinnamon etc. Window Managers, add accordingly. In my case it was XFCE.

 

How to fix WARNING: gnome-keyring error-3 - blackMORE Ops.jpg

Save the file and close it.

Now reboot.

How to fix WARNING: gnome-keyring error-4 - blackMORE Ops.jpg

That’s it. Now you won’t see that WARNING: gnome-keyring:: couldn’t connect to again.

Thanks for reading.

You may also like

9 comments

Matheus Ferreira Geres March 27, 2014 - 7:33 am

Hi,

You helped me with solution my problem.
Thanks a lot!

Matheus Ferreira Geres

Reply
blackMORE Ops March 27, 2014 - 9:11 am

Thanks Matheus.

Reply
cousteau May 6, 2014 - 6:54 pm

(1) Can’t I just comment out the OnlyShowIn line?
(2) Instead of rebooting, you can just run the command “gnome-keyring-daemon –start –components=pkcs11“ which (in my case) printed “GNOME_KEYRING_CONTROL=/tmp/keyring-57uwl2”, and then run “export GNOME_KEYRING_CONTROL=/tmp/keyring-57uwl2“ (i.e. export + the line you got) so that all commands you run from that terminal get the right keyring directory.
(3) Can’t I just disable this gnome-keyring thing for good?
(4) What was the reasoning behind showing the content of the .desktop file as an image? Preventing me from selecting the command? >:(

Reply
cousteau May 6, 2014 - 7:03 pm

Another solution, for XFCE only (although other environments may have similar options) is the one shown in http://askubuntu.com/a/243274
Go to Menu > Settings > Settings manager > Session and startup > Advanced > Launch GNOME services on startup

(And maybe a third solution would be to just uninstall this damn gnome-keyring thing, but I don’t know if it will actually solve the problem and what side effects it can have)

Reply
Ahmet August 23, 2014 - 11:35 pm

That solution was right on spot… Thanks BlackMORE

Reply
Vasw Siskou September 11, 2014 - 12:34 am

it is working for me..!!!
tnx

Reply
Stepan November 19, 2014 - 5:23 am

Doesn’t work!

Reply
jean-marie January 23, 2015 - 7:10 pm

it is working for me.
thanks !

Reply
Llewen March 27, 2019 - 10:38 pm

I’ve been looking for a solution to this for months. Finally one that works. Thank you.

Reply

Leave a Reply to StepanCancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.