KDE/Plasma: gnome-keyring-daemon: couldn't access control socket: /run/user/1000/keyring/control
Sedat Dilek
sedat.dilek at gmail.com
Thu Apr 16 22:16:58 BST 2020
Hi,
I am here on Debian/testing AMD64 running KDE/Plasma.
While discovering a problem with Skype4Linux - I fell over in my logs:
gnome-keyring-daemon: couldn't access control socket:
/run/user/1000/keyring/control
I am not 100% sure this is related to my Skye4Linux problem - incoming
call shows "trap invalid opcode".
I found several hints like in [1] and [2].
Following [2] and adapting it for KDE/Plasma I added "KDE" to the
"OnlyShowIn" entry in these 3 file:
[ gnome-keyring-pkcs11.desktop ]
[ gnome-keyring-secrets.desktop ]
[ gnome-keyring-ssh.desktop ]
-OnlyShowIn=GNOME;Unity;MATE;
+OnlyShowIn=GNOME;Unity;MATE;KDE;
After a logoff and re-login via SDDM I checked my logs and
gnome-keyring-daemon process:
root# journalctl -xe | grep gnome-keyring-daemon
Apr 16 23:01:03 iniza sddm-helper[7257]: gkr-pam: gnome-keyring-daemon
started properly and unlocked keyring
user$ ps -ef | grep gn[o]me-keyring-daemon
dileks 7262 1 0 23:01 ? 00:00:00
/usr/bin/gnome-keyring-daemon --daemonize --login
Can you add these modifications to the *.desktop files?
Thanks in advance.
Regards,
- Sedat -
[1] https://bbs.archlinux.org/viewtopic.php?id=224652
[2] https://askubuntu.com/questions/243210/why-do-i-get-this-warning-from-gnome-keyring-in-xubuntu
More information about the pkg-gnome-maintainers
mailing list