You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
laptop:~$ ls -alth /var/run/keyd.socket
srw-rw---- 1 root keyd 0 Dec 24 03:12 /var/run/keyd.socket
laptop:~$ groups user
wheel input lp keyd users
laptop:~$ export KEYD_DEBUG=1
laptop:~$ keyd-application-mapper
Gnome detected
ERROR: Failed to connect to "/var/run/keyd.socket", make sure the daemon is running and you have permission to access the socket.
Matched kitty|*
ERROR: Failed to connect to "/var/run/keyd.socket", make sure the daemon is running and you have permission to access the socket.
Running keyd-application-mapper from the commandline outputs
Gnome detected
When I switch app focus it prints Matched kitty|* ERROR: Failed to connect to "/var/run/keyd.socket", make sure the daemon is running and you have permission to access the socket.
When I switch back to kitty it then prints Matched kitty|* ERROR: Failed to connect to "/var/run/keyd.socket", make sure the daemon is running and you have permission to access the socket.
I've added values 47 and 47.2 to the 45 version gnome extension's metadata file (#873) and linked /usr/share/gnome-shell/extensions/keyd to /usr/share/keyd/gnome-extension-45.
I have added my user to the keyd group as the manpage for keyd-application-mapper states to do. I suspect it's related to socket permissions based on the output.
The text was updated successfully, but these errors were encountered:
LaptopDev
changed the title
keyd-application-mapper arch gnome mutter 47.2
keyd-application-mapper arch socket perms gnome mutter 47.2
Dec 24, 2024
LaptopDev
changed the title
keyd-application-mapper arch socket perms gnome mutter 47.2
keyd-application-mapper arch not working gnome mutter 47.2
Dec 25, 2024
I have changed the title of this issue because a restart fixed the socket access issue. It no longer appears, and keyd-application-mapper -v finds windows
KEYD_DEBUG=1
keyd-application-mapper -v
Shows windows well and matches kitty, too, but the actual keymap is not applied with either of my mappings in ~/.conf/keyd/app.conf:
cmd output
Running keyd-application-mapper from the commandline outputs
Gnome detected
When I switch app focus it prints
Matched kitty|* ERROR: Failed to connect to "/var/run/keyd.socket", make sure the daemon is running and you have permission to access the socket.
When I switch back to kitty it then prints
Matched kitty|* ERROR: Failed to connect to "/var/run/keyd.socket", make sure the daemon is running and you have permission to access the socket.
~/.config/keyd/app.conf
keyd 2.5.0-1
I've added values 47 and 47.2 to the 45 version gnome extension's metadata file (#873) and linked
/usr/share/gnome-shell/extensions/keyd
to/usr/share/keyd/gnome-extension-45
.I have added my user to the keyd group as the manpage for keyd-application-mapper states to do. I suspect it's related to socket permissions based on the output.
The text was updated successfully, but these errors were encountered: