FS#40220 - [gnome-keyring] gnome-keyring-daemon warnings after updrade to gnome 3.12

Attached to Project: Arch Linux
Opened by guoqiyi (guoqiyi) - Monday, 05 May 2014, 01:00 GMT
Last edited by Jan Alexander Steffens (heftig) - Tuesday, 06 May 2014, 02:06 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Jan Alexander Steffens (heftig)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

After upgrade to gnome 3.12.1,I checked my system log and found a lot of error warning about gnome-keyring,I don't know why.

Additional info:
* package version(s)
* config and/or log files etc.
eerors in my journalctl:

May 05 08:15:25 Arch gnome-keyring-daemon[346]: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory
May 05 08:15:25 Arch gnome-session[295]: ** Message: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory
May 05 08:15:25 Arch gnome-keyring-daemon[332]: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory
May 05 08:15:25 Arch gnome-keyring-daemon[335]: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory
May 05 08:15:25 Arch gnome-session[295]: ** Message: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory
May 05 08:15:25 Arch gnome-keyring-daemon[341]: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory
May 05 08:15:25 Arch gnome-session[295]: ** Message: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory
May 05 08:15:25 Arch gnome-session[295]: ** Message: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory

Steps to reproduce:
This task depends upon

Closed by  Jan Alexander Steffens (heftig)
Tuesday, 06 May 2014, 02:06 GMT
Reason for closing:  Works for me
Comment by Jan de Groot (JGC) - Monday, 05 May 2014, 08:45 GMT
Can't reproduce this on my system. The only thing I can think of is either a completely missing /run/user/1000, or a /run/user/1000 that has the wrong permissions. This is often caused by using gksu or su.
Comment by guoqiyi (guoqiyi) - Monday, 05 May 2014, 09:49 GMT
well，the number 1000 is my UID number in the system,I've enabled gdm.service and chosen autologin to gnome-shell,after login I checked the system log by run journalctl --this-boot and found these errors,so I have no chance to excute any command with gksu or su before that.But you've remind me,maybe I should check if there are some permission errors with my account,I'll report later after check,thanks.
Comment by guoqiyi (guoqiyi) - Monday, 05 May 2014, 17:54 GMT
Sorry,It seems like this was caused by my last time system crash and I just force to reboot it.When I totally power off and then power on ,this problem disappears and don't show anymore.It's my fault to waste your time,Sorry.
My system crash because a Xorg keyboard error,I'll report it in next bugreport....
sorry for that again..

Loading...