keyboard VS earlyoom

check out the docs here https://github.com/boppreh/keyboard

You can install the keyboard library, then do keyboard.wait('enter').

Name: keyboard Version: 0.13.5 Summary: Hook and simulate keyboard events on Windows and Linux Home-page: https://github.com/boppreh/keyboard Author: BoppreH Author-email: [email protected] License: MIT Location: /home/me/.local/lib/python3.10/site-packages Requires: Required-by:

LOL, here you go

I'm trying to create an autoclicker using the pyautogui library. I want to create a fail safe for the user to break out of the auto clicker in case the cursor is not able to be moved and the user can't stop the program. I'm using the keyboard library to implement a hotkey to stop the auto clicker from running, but I'm not getting the intended behavior. The click() function is only executed once and the program quits. I'm on a Arch Linux, and gave the program root privileges as mentioned in the readme of keyboard

As an example here is how the keyboard module does it: https://github.com/boppreh/keyboard/blob/master/keyboard/_winmouse.py

If you needed a cross-platform solution today, I would recommend looking into Python and some of its related ecosystem, such as the keyboard package, which provides cross-platform hotkey support and keyboard automation, including 'word listeners' and its companion module mouse.

And according to this issue, there's no support for key suppression in the Linux version of keyboard.

> The system is not supposed to 'lock up' when you run out of physical RAM. If it does, something is wrong. It might become slower as pages are flushed to disk but it shouldn't be terrible unless you are really constrained and thrashing. If the Kernel still can't allocate memory, you should expect the OOMKiller to start removing processes. It should not just 'lock up'. Something is wrong.

I don't why but locking up is my usual experience for Desktop Linux for many years and distros, and I remember seeing at least one article explaining why. The only real solution is calling the OOMKiller early either with a daemon or SysRq.

> It should not take minutes. Should happen really quickly once thresholds are reached and allocations are attempted. What is probably happening is that the system has not run out of memory just yet but it is very close and is busy thrashing the swap. If this is happening frequently you may need to adjust your settings (vm.overcommit, vm.admin_reserve_kbytes, etc). Or even deploy something like EarlyOOM (https://github.com/rfjakob/earlyoom). Or you might just need more RAM, honestly.

Yeah. Exactly. But as the thread says, why aren't those things set up automatically?

It's not that simple: some defaults may differ, and some features may arrive at different times (if ever). For example, earlyoom has been enabled on Workstation since F32, but the KDE Plasma spin got it one release later.

Most answers will answer your question, but you can do better and avoid the freezes in the first place. IME almost every time the system froze up and didn't come back in a few seconds it was out of memory. The obvious solution is to add memory, but you can use Early OOM to kill hungry processes if you're running out of memory instead.

It sounds like you're running out of memory though, so if your OS's OOM killer isn't working as well as it should, you can try earlyoom as an alternative.

Swap is indeed supposed to prevent this AFAIK. You can though try some tools like EarlyOOM and see if it helps : https://github.com/rfjakob/earlyoom