Results 1 to 9 of 9

Thread: How to fix "access control socket: ... keyring/control" error

  1. #1
    Join Date
    Jun 2016
    Location
    Ireland
    Posts
    246

    Default How to fix "access control socket: ... keyring/control" error

    Hi,
    I have a pop up window when I want to connect to another box through sftp.
    It asks to enter password for keyring.
    Boot has errors
    Code:
    Feb 18 08:45:56 loja checkproc[2790]: checkproc: can not get session id for process 2786!
    Feb 18 08:45:56 loja org.a11y.Bus[2799]: Activating service name='org.a11y.atspi.Registry'
    Feb 18 08:45:56 loja org.a11y.Bus[2799]: Successfully activated service 'org.a11y.atspi.Registry'
    Feb 18 08:45:56 loja org.a11y.atspi.Registry[2809]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
    Feb 18 08:45:57 loja gnome-keyring-daemon[2842]: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory
    Feb 18 08:45:57 loja mate-session[2743]: WARNING: Unable to find provider '' of required component 'dock'
    Feb 18 08:45:58 loja gnome-keyring-daemon[2842]: The Secret Service was already initialized
    Feb 18 08:45:58 loja gnome-keyring-daemon[2842]: The SSH agent was already initialized
    Feb 18 08:45:58 loja gnome-keyring-daemon[2842]: The PKCS#11 component was already initialized
    Feb 18 08:45:58 loja org.gnome.OnlineAccounts[2799]: goa-daemon-Message: goa-daemon version 3.20.5 starting
    In the thread https://forums.opensuse.org/showthre...hlight=keyring
    the last post says to remove some packages to fix the issue
    uninstall the packages:

    gnome-keyring-32bit
    gnome-keyring-pam-32bit
    gnome-keyring-pam
    gnome-keyring
    libgck-modules-gnome-keyring
    I am afraid to do so.
    Is it the good fix? What about security after removing these packages?
    My last install with 42.3 as well didn't get this issue.

    Thanks for your help

  2. #2
    Join Date
    Oct 2014
    Location
    Rotterdam
    Posts
    704

    Default Re: How to fix "access control socket: ... keyring/control" error

    Which kind of GUI do you have? KDE, Gnome, LXDE, XFCE or ...

    As long as it is not Gnome I would just remove these packeages, if needed you can always reinstall them.

  3. #3
    Join Date
    Jun 2016
    Location
    Ireland
    Posts
    246

    Default Re: How to fix "access control socket: ... keyring/control" error

    Sorry I forgot, I use MATE

  4. #4
    Join Date
    Oct 2014
    Location
    Rotterdam
    Posts
    704

    Default Re: How to fix "access control socket: ... keyring/control" error

    I am not really into Gnome/MATE, but maybe this, Autostart gnome-keyring-daemon message can help. Otherwise have a look at initializing gnome-keyring-daemon in autostart.

  5. #5
    Join Date
    Jun 2016
    Location
    Ireland
    Posts
    246

    Default Re: How to fix "access control socket: ... keyring/control" error

    I restated and had a look on journalctl again.
    Now there is no error message any more.

    I think this is due to the fix I did for the other issue in the /dev/sda1 volume with boot/efi.
    https://forums.opensuse.org/showthre...erly-unmounted

    Fixed!
    Thank you for your help

  6. #6
    Join Date
    Jun 2016
    Location
    Ireland
    Posts
    246

    Default Re: How to fix "access control socket: ... keyring/control" error

    I am back with this thread as I thought it was fixed but in fact no.
    I sum up
    I run 42.3 MATE
    journalctl says
    Code:
    gnome-keyring-daemon[2830]: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory
    mate-session[2731]: WARNING: Unable to find provider '' of required component 'dock'
    ...
    gnome-keyring-daemon[2830]: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory
    ...
    python3[2897]: backintime (jp/1): WARNING: import keyring failed
    ...
    su[3549]: The gnome keyring socket is not owned with the same credentials as the user login: /run/user/1000/keyring/control
    su[3549]: gkr-pam: couldn't unlock the login keyring.
    ...
    Backintime can't run by itself (from cron), when I run it I have to enter the keyring.
    I need to enter the keyring to connect to another computer.
    I have another older HP desktop, 42.3 MATE with the same issue.

    The 2 links above didn't help me as I don't know what to do.
    Thank you for your help

  7. #7
    Join Date
    Jun 2016
    Location
    Ireland
    Posts
    246

    Default Re: How to fix "access control socket: ... keyring/control" error

    I had a look on a old laptop HP nx7300, intel CPU, the same error about keyring
    Code:
    gnome-keyring-daemon[3069]: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory
    mate-session[2977]: WARNING: Unable to find provider '' of required component 'dock'
    Could all users of Leap 42.3 have a look in the journal and report here?
    Is it a bug?
    Code:
    journalctl -b
    Thanks

  8. #8
    Join Date
    Jun 2016
    Location
    Ireland
    Posts
    246

    Default Re: How to fix "access control socket: ... keyring/control" error

    I did a lot of reading; This is an old issue that could be from many reasons: /etc/X11/xinit/xinitrc config, NVIDIA driver, /etc/pam.d/login config, /etc/pam.d/passwd config, enable Gnome services, /etc/xdg/autostart/gnome-keyring-pkcs11.desktop config and maybe more.

    The point is I checked my install and can't find what is the issue and what to do.

    Help is really welcome.

  9. #9
    Join Date
    Apr 2016
    Location
    North America
    Posts
    537

    Default Re: How to fix "access control socket: ... keyring/control" error


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •