On 17 December 2011 19:44, Magnus Therning wrote:

On Sat, Dec 17, 2011 at 02:28:54PM +0200, Hector Martinez-Seara wrote:

...

Hi, for some time ( one week maybe) I see the following message regarding gnome-keyring.

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

This meassage can be seen for example in my .xsession-errors file or when opening winecfg among others.

The issue is that indeed this file do not exist. I have the /tmp/keyring-3TI6ND/dir but is empty. I guess that this means that gnonome-keyring was not somehow initialized properly. I'm using gdm+xfce. I'm fully updated.

I have seen the same behavior in my 3 archlinux machines.

Any ideas whats going on? or I should fill a bug. I yes where in arch or upstream?

You don't mention whether you *want* to use gnome-keyring for anything.  Do you?

I used to see this behaviour in SVN just after I replaced Gnome3 with LXDE.  I solved it by removing all gnome-keyring packages that were lingering on my system.  That solved my problems since I wasn't interested in using gnome-keyring any more.

Some of my users use gnome3. So I guess that removing gnome-keyring is not an option. Besides when it works doesn't annoy me. Thanks

On 17 December 2011 19:54, Ionut Biru wrote:

On 12/17/2011 02:28 PM, Hector Martinez-Seara wrote:

...

Hi, for some time ( one week maybe) I see the following message regarding gnome-keyring.

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

is a gnome-keyring bug.

https://bugzilla.gnome.org/show_bug.cgi?id=665961

be sure that gnome-keyring-daemon really runs and if is it paste the env output in the report.

a working keyring should have $ ps aux | grep keyring ioni      1169  0.0  0.6  71060 12552 ?        Sl   17:45   0:00 /usr/bin/gnome-keyring-daemon --daemonize --login

$ env | grep GNOME_KEYRING GNOME_KEYRING_CONTROL=/tmp/keyring-pxYetE GNOME_KEYRING_PID=1169

In my case I get the following output: [hector@apolo ~]$ ps aux | grep keyring hector 1372 0.0 0.2 42392 8144 ? SLl 14:07 0:00 /usr/bin/gnome-keyring-daemon --daemonize --login hector 1635 0.0 0.0 10692 1680 ? S 14:08 0:00 /usr/bin/gnome-keyring-daemon --start --foreground --components=secrets hector 4372 0.0 0.0 5860 884 pts/0 S+ 20:18 0:00 grep keyring [hector@apolo ~]$ env | grep GNOME_KEYRING GNOME_KEYRING_CONTROL=/tmp/keyring-3TI6ND GNOME_KEYRING_PID=1372 Still I do not think that this means that the keyring is working. The file pkcs11 is not inside the /tmp/keyring-3TI6ND. If I execute manually: /usr/bin/gnome-keyring-daemon --start --components=pkcs11 This creates the pkcs11 file the lack of which triggers the error. After this command no more messages like the ones I reported appear any longer. Seems to be that the file: "/etc/xdg/autostart/gnome-keyring-pkcs11.desktop" belonging to "extra/gnome-keyring" is not executed when login in. Anybody knows what is program is responsible in theory to execute this file? Thanks in advance, Hector

Hi, no change. Can it be that I have to configure something for policykit to be opened correcty in xfce? I haven't seen anything particular in the wiki respect to this point but who knows. At least, is there anybody seen the same? Shall I fill a bug instead of spamming the mailing list? Hector On 19 December 2011 14:47, Ionut Biru wrote:

Can you please test this packages and let me know if is fixed?

http://pkgbuild.com/~ioni/gnome-keyring/

-- Ionuț

-- Hector Martínez-Seara Monné mail: hseara@gmail.com Tel: +34656271145 Tel: +358442709253