Releases: foresto/joystickwake
Releases · foresto/joystickwake
v0.4.2
- Log udev details if a device node is missing.
This can occur, for example, if the user has installed 51-these-are-not-joysticks-rm.rules from the udev-joystick-blacklist project. (Please don't use that rules file; it tries to be helpful by breaking your system.) Thanks to @KayJay7 for the help in tracing the problem to its source.
v0.4.1
v0.4
This release ought to interest GNOME users, especially those running Wayland.
Significant changes:
- Rename the 'interval' option to 'cooldown', to make its meaning more intuitive to gamers. The old spelling is now deprecated, and will likely disappear next release. If you use it, please update your configs accordingly.
- Support the D-Bus org.freedesktop.ScreenSaver Idle Inhibition Service on systems that have the python3 dbus-next package installed.
- Add a pair of heartbeat-style wake commands (using dbus-send) for modern GNOME. One forces the screen awake, and the other resets the blanker countdown. Together, they seem to work about as well as the new Idle Inhibitor, without requiring dbus-next. (Tested on GNOME 3.38, 42.2, 43.0, both X11 and Wayland.)
- Use dbus-send instead of qdbus in the KDE waker.
- Rename the xset and gnome-screensaver wakers.
- Rephrase various log messages.
- Expand the man page.
Support python 3.10. Require python >= 3.5. Improve xset support.
This release is mainly to accommodate new asyncio behavior introduced by python 3.10. We now use the async/await keywords, so python 3.4 and older are no longer supported.
Wakers can now detect command failures with a stderr regex match, for commands like xset that sometimes fail with exit status code 0.
Support KDE screen locker
- Support KDE Plasma via dbus SimulateUserActivity call (thanks @Tatsh)
- Document a custom waker command for KDE+XWayland screen energy saving mode. (KDE's power saving mode responds to our new built-in dbus call when using X.Org, but ignores it on XWayland. Our README now notes a custom blanker command that can work around the problem.)
v0.2.4: Support xfce4-screensaver by default
Support xfce4-screensaver by default