Closed TravisPasta closed 2 years ago
Just curious, but what do you see to the left of the "Press to Set" button when you press a key to make it into a hotkey after you press the "Press to Set" button? Does it say "Key (None) and never change or does it change to something else in response to the keypress?
The above will probably not be of any use, so I'm going to bet that you're using Wayland. Issue 293 seems mighty similar to yours. Wayland and AutoKey don't yet get along because of the sandboxed type of environment that Wayland offers.
Hey, thanks for the fast answer! The only thing that is there and stays there is
Since afaik Wayland is the main thing used in Fedora to display GUIs, the issue is based on that. Ive tried a live version of Lubuntu and it worked totally fine there. So its not my keyboards either.
Ill try to solve it within the JSON File itself, since its literally just 3 Hotkeys with each beeing one line of keyboard.send_keys(). Thanks for the help again. Ive started my linux migration yesterday and was super desperate to get it done.
Edit: Ive changed the Fedora Windowing System to X11 and now it works fine. Will see which solution I like best.
I'm glad you found a workable solution, but it's a shame that you had to choose a different desktop to make it happen.
If you're still going to tinker with getting AutoKey to work with Wayland, if you figure out a way, please let us know either in this issue report or in the AutoKey Google group or in the AutoKey Gitter chat.
This topic has come up from time to time and is likely to again, so I'm sure there are at least a few people who would be interested in any progress that you make and there will quite likely eventually be many more.
AFAIK, AutoKey does not work with native Wayland. You have to tell your system to use X11 instead.
While Wayland does include some sort of X11 compatibility feature, AFAIK, this option still lacks things that AutoKey needs to function correctly.
We would be very happy to have some developers well versed in Wayland take a look at this to see what could be done to resolve it, but we don't have any at the moment.
Wayland seems to be all about efficiency and security. It combines the compositor, display server, and window manager into one step, which is great for efficiency and doesn't seem like it would have a negative effect on AutoKey. The problem for AutoKey will be Wayland's security measures since Wayland doesn't allow common interfaces that can manipulate or be aware of each other.
My understanding is that the Wayland team doesn't want to forbid users from having such interfaces and will provide protocols for them to do so in specific use-cases. What I haven't found out is how far-reaching those use-cases can be or whether the protocols supporting use-cases have even been designed yet.
I'm not sure if that will mean that the end user will have to either solve individual issues as they arise or prepare for them in advance by thinking them out and creating the specific use-cases from those protocols or have them taken care of by AutoKey or give some of them up entirely. I suspect that at least one of those will be our path forward, but this is all still speculation.
By the way, as an unrelated aside, I noticed something interesting when @TravisPasta edited one of these messages and I received it in email. If you have GitHub set up to send you emails when there are new issues or new posts to issues, only the original version of a new post will be sent in email. If the person edits the post, that edited version of the post will not be emailed, so those of us who only read these posts in email may be missing some content and will probably want to follow up the email by coming onto GitHub each time and checking for edits.
Has this issue already been reported?
Is this a question rather than an issue?
What type of issue is this?
Crash/Hang/Data loss
Which Linux distribution did you use?
Fedora Workstation 36
Which AutoKey GUI did you use?
Both
Which AutoKey version did you use?
I have tried it in the newest (0.96.0), in the newest that the package manager offers (0.95.10) and custom install (0.95.6).
How did you install AutoKey?
Tried everything. Git, pip3 install, using alien to make deb files rpm files and installed through this.
Can you briefly describe the issue?
Can the issue be reproduced?
No response
What are the steps to reproduce the issue?
Install in the favourite way. Create new folder/Script or change hotkey of existing one. click "press to set"
What should have happened?
recognize the keyboard input
What actually happened?
error message and the program gets kinda stuck in the loop of wanting an input
Do you have screenshots?
Can you provide the output of the AutoKey command?
Anything else?
ive tried it with every versions gtk and qt subversion