Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

keyd-application-mapper arch not working gnome mutter 47.2 #896

Closed
LaptopDev opened this issue Dec 24, 2024 · 2 comments
Closed

keyd-application-mapper arch not working gnome mutter 47.2 #896

LaptopDev opened this issue Dec 24, 2024 · 2 comments

Comments

@LaptopDev
Copy link

LaptopDev commented Dec 24, 2024

cmd output
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.

~/.config/keyd/app.conf

[kitty]

capslock = esc

keyd 2.5.0-1

OS: Arch Linux x86_64 
Host: HP Spectre x360 2-in-1 Laptop 16-f1xxx 
Kernel: 6.6.65-1-lts 
Uptime: 4 days, 17 hours, 15 mins 
Packages: 1513 (pacman), 20 (flatpak) 
Shell: bash 5.2.37 
Resolution: 3072x1920 
DE: GNOME 47.2 
WM: Mutter 
WM Theme: Adwaita 
Theme: Adwaita [GTK2/3] 
Icons: Adwaita [GTK2/3] 
Terminal: kitty 
CPU: 12th Gen Intel i7-12700H (20) @ 400MHz 
GPU: Intel Alder Lake-P GT2 [Iris Xe Graphics] 
Memory: 2392MiB / 15688MiB 

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.

@LaptopDev 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 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
@LaptopDev
Copy link
Author

LaptopDev commented 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:

[kitty]

capslock = esc
T = t

@LaptopDev
Copy link
Author

Not sure what happened but you can tally 1 for user error and I will close this because it works.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant