Keyboard keys not importing or loading in.

[ArcSpammer]

AutoKey is a Xorg application and will not function in a Wayland session. Do you use Xorg (X11) or Wayland?

Xorg

Has this issue already been reported?

• I have searched through the existing issues.

Is this a question rather than an issue?

• This is not a question.

What type of issue is this?

Crash/Hang/Data loss

Choose one or more terms that describe this issue:

• autokey triggers
• autokey-gtk
• autokey-qt
• beta
• bug
• critical
• development
• documentation
• enhancement
• installation/configuration
• phrase expansion
• scripting
• technical debt
• user interface

Other terms that describe this issue if not provided above:

No response

Which Linux distribution did you use?

Linux 6.5.9-arch2-1
Laptop Ryzen chip with amdgpu drivers

Which AutoKey GUI did you use?

GTK

Which AutoKey version did you use?

0.96.0

How did you install AutoKey?

git

Can you briefly describe the issue?

I don't exactly know what is going on but everything keyboard related does not work properly. I've made 2 scripts with mouse and cursor only, those worked fine. I think something is going wrong at the startup, but I cannot decrypt the logs.

Can the issue be reproduced?

Always

What are the steps to reproduce the issue?

1. Launch autokey-gtk

What should have happened?

I hope work properly.

What actually happened?

My keyboard keys have not been imported or configured correctly.

Do you have screenshots?

logs.txt
These are the startup logs. I hope I am not very stupid.

Can you provide the output of the AutoKey command?

[logs.txt](https://github.com/autokey/autokey/files/13291682/logs.txt)

Anything else?

No rush, I really like your program. I like making these simple scripts. Keep up the good work!

[josephj11]

Welcome to the AutoKey community @ArcSpammer !

Your trace output looks like what AutoKey normally does to start up, but does not show you pressing any keys to trigger it to do anything.

I do not understand what you mean by

"My keyboard keys have not been imported or configured correctly." How do you know that and what are you specifically doing that produces no/unexpected results?

BTW, there are AutoKey packages in aur for both autokey-gtk and autokey-qt, so you shouldn't need to install it with git unless you plan on modifying it or contributing pull requests. However, installing from git shouldn't hurt anything as long as you took care of installing all of the dependencies.

[ArcSpammer]

Hey thank you for responding, I tried all the ways of sending key presses noted on the documentation. They all didn't work and I was stuck figuring out what happened. Then I looked trough the log with the --verbose option and saw that it was only grabbing this super + k combination I thought something had gone wrong. I can't make sense of it.
Sorry for the inconvenience.

[josephj11]

We need specific details to understand/recreate this issue. Exactly what did you do and what didn't or did happen.

One test should be enough to start with.

The first part of the trace output is effectively noise that displays every time. It can almost always be ignored. I've been trying to get the devs to suppress most of those messages forever. It's quite a bit better than it was originally.

Looking at the log again, a few things stand out

2023-11-08 05:14:21,937 DEBUG - autokey.interface - Grabbing hotkey: ['<alt_gr>'] 'l'
2023-11-08 05:14:21,937 DEBUG - autokey.interface - Grabbing hotkey: ['<shift>'] '¡'
2023-11-08 05:14:21,937 DEBUG - autokey.interface - Grabbing hotkey: [] '¡'
2023-11-08 05:14:21,937 DEBUG - autokey.interface - Grabbing hotkey: ['<alt_gr>'] "'"
2023-11-08 05:14:21,937 DEBUG - autokey.interface - Grabbing hotkey: [] 'º'
2023-11-08 05:14:21,937 DEBUG - autokey.interface - Grabbing hotkey: ['<ctrl>'] '<f7>'
2023-11-08 05:14:29,716 DEBUG - autokey.iomediator.iomediator - Key.CONTROL pressed
2023-11-08 05:14:30,526 DEBUG - autokey.service - Raw key: 'c', modifiers: [<Key.CONTROL: '<ctrl>'>], Key: c
2023-11-08 05:14:30,527 DEBUG - autokey.service - Window visible title: 'teunb@archlinux:~/autokey', Window class: 'Alacritty.Alacritty'
2023-11-08 05:14:30,759 DEBUG - autokey.iomediator.iomediator - Key.CONTROL released
2023-11-08 05:14:31,621 DEBUG - autokey.iomediator.iomediator - Key.CONTROL pressed

The first five lines look odd. AutoKey appears to be grabbing things as hotkeys that are normally not hotkeys. It looks like you may be using a non-EN US keyboard/keyboard layout - which should be OK - as long as it's the primary keyboard layout. AutoKey tends to ignore secondary keyboard layouts causing unexpected results.

Then it shows you pressing Ctrl+c.

Unless you have Ctrl+c defined as a hotkey (usually not the best idea in Linux), pressing it shouldn't cause AutoKey to do anything. To close AutoKey, you have to do it from the AutoKey menu window, the AutoKey panel icon context menu, or by killing its process.

I haven't used Alacritty. Some native X applications ignore synthetic keypresses (which are what AutoKey emits). Things like xterm and xsane. So you should also test in another application window such as kate or konsole - anything not specifically designed for X11. Gedit should work as well. The specific app doesn't matter when we're trying to establish/debug general functionality.

[ArcSpammer]

Hey joseph,

thanks so much for responding. I use a spanish keyboard layout, as a first keyboard layout. I don't have any secondary layouts. I didn't have Ctrl+C bound to a script, I just tried to exit the program. My mistake.
It's just acting weird when I try to use the keyboard keys in scripts. I have no idea what is causing the problem. What info do you need to work out what is causing the problem?

[josephj11]

Start with this.

We need a precise definition of what "acting weird" actually entails.

Generally, running an AutoKey trace (see link above) helps you see things from AutoKey's point of view.

Another thing to be aware of is that some apps can't keep up with the speed AutoKey types. See this for more information.