Skip to content

Troubleshooting

Jump to bottom
Marcel Grolms edited this page Sep 12, 2023 · 8 revisions

So you stumbled on an issue and you don't know where to look at what went wrong. No problem, I'm here to help.

Installation Troubleshooting

First you need to make sure that the version of Python is >=3.7 with python3 --version.
If you have the 3.7 installed but the above command returns some other version, try command sudo update-alternatives --config python3.

This should output something like this:

  Auswahl      Pfad                 Priorität Status
------------------------------------------------------------
  0            /usr/bin/python3.11   4         automatischer Modus
  1            /usr/bin/python3.11   4         manueller Modus
  2            /usr/bin/python3.12   3         manueller Modus
* 3            /usr/bin/python3.8    1         manueller Modus
  4            /usr/bin/python3.9    2         manueller Modus

If the other versions you installed doesn't show here you can add a new version like this:

sudo update-alternatives --install /usr/local/bin/python3 python3 /usr/bin/python3.8 1

On some distros there was also problems with not having python devel, pip and gcc installed so try check that you have those packages installed.

There has also been a few reported issues with installing the software on various platforms. Check out the Issues with tag good first issue.

Execution Troubleshooting

The main information you can get is systemd logs and driver's log. Systemd status and logs can be found by running:

  • status: systemctl --user status g910-gkeys
  • logs: journalctl --user -u g910-gkeys

Those two should give you enough information to figure out why the driver didn't start or why it shut down unexpectedly.

If the driver runs but does not work as you expect it to, then your best place to look is in: $HOME/g910-gkeys.log, where the behaviour of the driver is logged. There you can see if there is a problem with your configuration or if there are errors (like not finding the device).

If you want to see exactly if driver catches the GKey or media button event and what the HEX-code is, change logger level to DEBUG in config.json and restart the driver systemctl --user restart g910-gkeys.

If you still can't figure out why it doesn't work, check that GKey to FKey mapping is disabled (you can do this by pressing G5 in a browser. If the page reloads the mapping is not disabled). If the mapping is not disabled try restarting the driver but if that still doesn't work install g810-led controller and disable the mapping with g910-led -gkm 1 then restart the driver.

If still nothing then try restarting your computer or plugging the keyboard in and out.

If still no luck, try reinstalling the software and then if still nothing please post an issue, describe the problem in detail add the configuration, logs and systemctl log via pastebin (or whatever you prefer) and I will try to help.

Clone this wiki locally