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

doesn't log #230

Open
Ash3781 opened this issue Aug 4, 2021 · 6 comments
Open

doesn't log #230

Ash3781 opened this issue Aug 4, 2021 · 6 comments

Comments

@Ash3781
Copy link

Ash3781 commented Aug 4, 2021

okay so i'm running garuda linux on my pc, no virtual machine, no virtual keyboard, just a plain normal installed linux with a normal keyboard, i do everything in the guide, even regenerate keymaps but all i get in the log is when it started and when i closed it... but no keys, not even gibberish
2021-08-04_13-46

@kernc
Copy link
Owner

kernc commented Aug 5, 2021

Have you tried running with -u or -m path/to/keymaps/de.map?

@RUDRA78372
Copy link

Same here. Tried exported keymaps too, doesn't work. Is this because of ibus or what?

@kernc
Copy link
Owner

kernc commented Aug 8, 2021

It's also of primary importance to select correct input device (--device). See Troubleshooting.

@nocibambi
Copy link

I have the same issue (Ubuntu 20.04).

  • I tried the tips in troubleshooting. I could type characters for all of the existing devices [0, 24].
  • I tried -u but that did not help. This command setxkbmap -print | awk -F"+" '/xkb_symbols/ {print $2}' from here gives us as the keymap (I also have Hungarian installed).

Here is the content of /proc/bus/input/devices.

@nucleare
Copy link

nucleare commented Oct 26, 2021

okay so i'm running garuda linux on my pc, no virtual machine, no virtual keyboard, just a plain normal installed linux with a normal keyboard, i do everything in the guide, even regenerate keymaps but all i get in the log is when it started and when i closed it... but no keys, not even gibberish

You're not setting the key map in your launching of logkeys. You need to specify those parameters when you launch logkeys and include their switches in the command.

For example:

sudo logkeys --start --keymap=/some/directory/{yourkey.map} --output=/var/log/logkeys.log --device=event3

You can exclude the = if not running in a bash script, the --device=event3 may vary based on your system.
I'm not familiar with Garuda linux but in Ubuntu you can find the exacty path using
egrep -i "keyboard.+\/dev" /var/log/Xorg.0.log or otherwise find it in your equivalent /dev/input/event

Most likely you just need to specify the device event for your keyboard

@nucleare
Copy link

nucleare commented Oct 26, 2021

I have the same issue (Ubuntu 20.04).

  • I tried the tips in troubleshooting. I could type characters for all of the existing devices [0, 24].
  • I tried -u but that did not help. This command setxkbmap -print | awk -F"+" '/xkb_symbols/ {print $2}' from here gives us as the keymap (I also have Hungarian installed).

Here is the content of /proc/bus/input/devices.

This issue is about not being able to log. You mentioned being able to type characters and refer to the keymap being reported as US when you have Hungarian installed. So it's not clear exactly which issue you are having

  • Keymap issues usually involve recording incorrect characters
  • Device event issues usually mean no logging is being done

If your issue is recording of symbols instead of letters, try applying a keymap manually as suggested in the troubleshoot. If you can't record at all, you need to find the device event not the keymap.

There are slight variations between the README.md and the DOCUMENTATION.md ; I strongly suggest reviewing the documentation if you're having trouble, especially if you are not installing from source but are using something like apt install logkeys

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

5 participants