but what about this solution: Not calling xdg-screensaver at all
do-release-upgrade is a console application.
Let the GUIs handle the screensaver if necessary. (And perhaps just by telling the screensaver to disable?)
Also: what about upgrades ran over ssh with X11 forwarding enabled?
The queries needlessly consume the (possibly quite limited) bandwidth.
another example: I use ubuntu on pandaboard, which has slow SD card, the upgrade-related IO takes long to finish.
I am glad I know I have to unset "DISPLAY" to prevent the screen from shining quite bringht whole night.
Yeah, that would be a little bit better.
but what about this solution: Not calling xdg-screensaver at all
do-release-upgrade is a console application.
Let the GUIs handle the screensaver if necessary. (And perhaps just by telling the screensaver to disable?)
Also: what about upgrades ran over ssh with X11 forwarding enabled?
The queries needlessly consume the (possibly quite limited) bandwidth.
another example: I use ubuntu on pandaboard, which has slow SD card, the upgrade-related IO takes long to finish.
I am glad I know I have to unset "DISPLAY" to prevent the screen from shining quite bringht whole night.
Thanks