the patch is an enhancement, not a workaround, the handling of screensavers is already built in, it uses the same approach as the original xscreensaver-command handler for gnome-screensaver-command, there might be a reason upstream added a handler to disable the screensaver, probably the reason causing this bug, i didnt test disabling the builting xscreensaver handler, in any case its only using an existing method with a different program to make it working compatible with this program.
the patch is an enhancement, not a workaround, the handling of screensavers is already built in, it uses the same approach as the original xscreensaver- command handler for gnome-screensav er-command, there might be a reason upstream added a handler to disable the screensaver, probably the reason causing this bug, i didnt test disabling the builting xscreensaver handler, in any case its only using an existing method with a different program to make it working compatible with this program.