Troubleshooting

Daemon log: journalctl --user -u gkeyd -f
Daemon state: Settings menu and status bar of the application, or busctl --user call io.github.lordbooker.GKeyConfig /io/github/lordbooker/GKeyConfig io.github.lordbooker.GKeyConfig1 Status

Device not connected

The status bar of the application names the reason when the device is plugged in but not usable:

the kernel is too old (G13: Linux 6.19; G11: Linux 5.7; G15, G15 v2, G510: Linux 5.5),
the kernel driver hid-lg-g15 does not drive the device,
another program (e.g. linux-g13-driver) uses the device directly – stop it and replug the device.

Check that no other tool grabs the device (e.g. input-remapper) and replug the device. Check that the daemon runs (status bar).

See the Backlight tab. Changing LEDs needs membership in the group gkey; after joining it a complete logout is needed (Installation).

Open an issue and attach

the daemon log: journalctl --user -u gkeyd -b,
the output of scripts/probe-device.sh (all supported devices: input devices, LEDs, LCD node, access rights; no root needed). With --events it also records the keys you press, which is what is needed to confirm the key layout of an untested device.

Owners of a G510, G15, G15 v2 or G11: a short report whether the keys, the LEDs and the LCD work helps to mark the device as tested.

gkey-config

Devices