Releases: itz-me-zappex/flux
Releases · itz-me-zappex/flux
flux v1.7.14
- Fixed a bug when daemon unable to change FPS limit if MangoHud config contains
fps_limit=[int]
string. - Fixed a bug when after changing of FPS limit daemon adds new blank line to config file.
- Fixed a bug when requests for limits were ignored until next focus event.
- Removed useless echoing of names of FPS limited sections on daemon termination.
Check commit 61de2a9.
flux v1.7.13
This release considered to be stable and I do not expect issues caused by implementation of request based limit applying algorithm as they should be fixed, but if you found an issue related to event handling, please downgrade to v1.7.8 and report an issue.
- Fixed an issue when daemon detects single focus event twice.
- Fixed an issue when daemon checks repeating event with list of stacking windows.
- Fixed an issue when left-button clicks in single window caused new events detection in Openbox window manager.
- Fixed recognizing of
0x0
event which appears when clicking on background in Openbox. - Small fixes and improvements.
Check commit e5acfcc.
flux v1.7.12
flux v1.7.11
- Fixed broken cache cleaning up algorithm which could cause memory leaks and inability to unset limits on windows termination.
Check commit 980b6b2.
flux v1.7.10
- Fixed a bug when daemon does not apply limits to windows randomly, that happened because
xprop
throws events without order and that simply breaks a whole event handling.
Check commit 5b611ac.
flux v1.7.9
- Fixed a bug when daemon accepts lines like
[key name] [anything else] = [value]
as valid in config file during INI parsing. - Fixed a bug when daemon accepts lines like
fps_limit [anything else] = [integer]
as valid in MangoHud config when sets FPS limit frommangohud_fps_set
function. - Fixed issue when daemon uses saved set UID instead of effective when reads status file of process.
- Reworked algorithm required to apply limits, now it uses requests and sets limits only after check for window existence, that fixes issue when daemon thinks that window termination is unfocus event and tries to apply limits, what causes a bunch of warnings in output.
- Small fixes and improvements.
Check commits bb7cea5, 46a6028, 693baa1, 0b5f191, 2c5e70f and 2ca927b.
flux v1.7.8
- Now daemon sets FPS limit in MangoHud config directly, instead of replacing a whole line with
fps_limit=<value>
. - Fixed a bug when daemon starts with unreadable config file.
- Fixed absent
[i]
prefix in$advice_on_option_error
. - Fixed a bug when combined options like
-v-
are recognized as-v --
and daemon thinks that is fine, now daemon exits with an error in this case. - Added
$advice_on_option_error
to error message when--lazy
specified w/o--hot
. - Now daemon can recognize multiple spaces before and after equal symbol in config (e.g.
key = value
) and remove them properly. - Now daemon checks for
$XDG_CONFIG_HOME/flux.ini
,$HOME/.config/flux.ini
and/etc/flux.ini
config files by default, instead of prefering for/etc/flux.ini
first. - Small fixes and improvements.
flux v1.7.7
- Fixed a bug when daemon refuses to start after relogin.
Check commit 5cf7b5e.
flux v1.7.6
- Small optimization change, now daemon does not unset actions on
SIGUSR1
andSIGUSR2
signals until it starts read X11 events. - Now errors in
xprop_event_reader
displayed as warnings. - Updated prefix style, now that is just first letter of message type in square brackets.
- Fixed mistake in message on FPS limit unset.
- Updated description of
--focus
and--pick
options. - Now daemon notifies about termination of target meaning window and not process, as it does not check for process existence on cache cleaning up and relies on window existence, that is should be more correct.
- Small fixes and improvements.
Check commits b03e4db, 749cfbf, d3c985d, 7d4b09c, 45a9d63, 0b28675 and 24c9f24.
flux v1.7.5
- Following issues were fixed, now daemon:
- Does not print messages about unsetting of CPU limit when receives
SIGINT
/SIGTERM
signal. - Prints proper messages about unsetting of CPU limit on both focus event and termination of target process.
- Prints info about applying of CPU limit in non-quiet mode.
- Does not print messages about unsetting of CPU limit when receives