X11 is seeing renewed activity with the emergence of the Xlibre fork, prompting new releases of the X.org X server and Xwayland. The article discusses the history of the fork's creator, the controversy surrounding his contributions, and the broader debate around Wayland's usability and accessibility compared to X11.
This article details a workaround for a memory leak in Autokey on Linux, specifically addressing issues arising from the transition away from X11 and toward Wayland. The author implemented a wrapper script to monitor Autokey's memory usage and restart it when it exceeds a defined threshold.
> "I don't want that key to be customizable"
Wayland is a lose.
sudo raspi-config
Advanced Options menu, select the Wayland option – disable it, and reboot.
sudo raspi-config
Advanced Options menu, select the Wayland option – disable it, and reboot.
Must not be using wayland. Can't find any way to do half this stuff on wayland anyway. Switched back to X11.
$ sudo apt install gnome-tweak-tool
then use it to map caps lock to ctrl, and swap left-ctrl and right ctrl to hyper
would rather have meta in center left and 2nd from right
would rather super and hyper work
then use it to map caps lock to ctrl, and swap left-ctrl and right ctrl to hyper
would rather have meta in center left and 2nd from right
would rather super and hyper work
The normal xterm mouse functionality for such clicks is still available by holding down the SHIFT key when you press the mouse button
"xkb configuration is black magic in general and sheer luck in Ubuntu."
