Search found 2 matches
- Sun Apr 19, 2020 4:44 am
- Forum: V7.5.1 Public Release Windows/Linux/MacOS X [deprecated]
- Topic: Client not respecting "On Idle" Setting
- Replies: 5
- Views: 1710
Re: Client not respecting "On Idle" Setting
I poked around the FAHClient and found I can send pause and unpause events to a running instance on lock/unlock events in dbus. Wrapped it up in this script, which monitors dbus with gdbus, filters for events with the string "LockedHint," and unpauses when lock is "<true>" and pa...
- Fri Apr 17, 2020 8:20 pm
- Forum: V7.5.1 Public Release Windows/Linux/MacOS X [deprecated]
- Topic: Client not respecting "On Idle" Setting
- Replies: 5
- Views: 1710
Re: Client not respecting "On Idle" Setting
I'm having a similar issue on Fedora 31 under Gnome 3.34.5. What determines idle on a Linux machine? Things I've tried so far: * up the logging verbosity to 5 to see if any attempts to go into idle fail, but I don't see any logs to that effect * increase the priority of F@H with the "Folding Co...