Arch Linux

mudkipscience

Member

Registered: 2021-05-16

Posts: 3

[SOLVED] installing CUPS breaks gnome-keyring on gnome 40.1-1

Hi, I'm using GNOME 40.1-1 with gnome-keyring 1:40.0-1 and with CUPS installed gnome-keyring seems to hang/crash, and applications that rely on it break. If I kill the process and start gnome-keyring manually, it works but does not automatically log in, I'm assuming thats normal though since my login password isn't being passed to it by PAM/GDM or whatever handles that

The below logs from journal seem to be relevant, specifically the last two lines:

May 16 12:31:38 stargazer gnome-keyring-secrets.desktop[27147]: GNOME_KEYRING_CONTROL=/run/user/1000/keyring
May 16 12:31:38 stargazer gnome-keyring-secrets.desktop[27147]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
May 16 12:31:38 stargazer gnome-keyring-daemon[6867]: The Secret Service was already initialized
May 16 12:31:38 stargazer gnome-keyring-daemon[6867]: The SSH agent was already initialized
May 16 12:31:38 stargazer gnome-keyring-ssh.desktop[27148]: GNOME_KEYRING_CONTROL=/run/user/1000/keyring
May 16 12:31:38 stargazer gnome-keyring-ssh.desktop[27148]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
May 16 12:31:38 stargazer gnome-keyring-daemon[6867]: The PKCS#11 component was already initialized
May 16 12:31:38 stargazer gnome-keyring-pkcs11.desktop[27149]: GNOME_KEYRING_CONTROL=/run/user/1000/keyring
May 16 12:31:38 stargazer gnome-keyring-pkcs11.desktop[27149]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
May 16 12:31:44 stargazer gnome-keyring-daemon[6867]: The Secret Service was already initialized
May 16 12:31:58 stargazer gnome-keyring-daemon[27763]: Replacing daemon, using directory: /run/user/1000/keyring
May 16 12:31:58 stargazer gnome-keyring-daemon[27763]: couldn't set environment variable in session: GDBus.Error:org.gnome.SessionManager.NotInInitialization: Setenv interface is only available during the DisplayServer and Initialization phase
May 16 12:31:58 stargazer gnome-keyring-daemon[27763]: couldn't set environment variable in session: GDBus.Error:org.gnome.SessionManager.NotInInitialization: Setenv interface is only available during the DisplayServer and Initialization phase

When I remove CUPS and its dependencies, the bottom two lines in the logs I posted disappear and when I log in gnome-keyring works as expected and unlocks automatically, no hangs/crashes.

I'd appreciate it if anyone would be able to help me out resolving this issue - I haven't filed a bug report because I don't think I have enough information to pass on to the developers. I'm not new to Linux but I came from Ubuntu and I'm still getting used to tinkering with stuff! Thank you for any assistance and if there are any more logs/info I can provide, please ask

Last edited by mudkipscience (2021-05-17 04:11:21)

mudkipscience

Member

Registered: 2021-05-16

Posts: 3

Re: [SOLVED] installing CUPS breaks gnome-keyring on gnome 40.1-1

Forgot to enable the avahi daemon, whoops. Issue seems to be resolved now, keyring unlocks normally (no idea why cups affected it though)