On Monday, 03.06.2019 at 00:19, Jamie Zawinski wrote: > I'd like to include your code with the next xscreensaver release if that's ok > with you -- is the latest version on GitHub what you'd like to go with?
Take the version I've just pushed -- I went hunting for the suspected memory leak, confirmed and fixed it, hopefully not making the program less reliable in the process. sd_bus_unref_message() has surprising semantics, see commit history if interested. Also, let me know if you want it under a different LICENSE. Note that after using this for 15 days now, I still occasionally (say 1 in 10 times?) get a flash of the unlocked screen content on resume, followed by the XScreenSaver password dialog. Unclear to me what is going on here other than "random scheduling races" but that's precisely what this inhibitor mechanism is supposed to avoid, so hmm, go figure?! Martin
