> Ok well that shouldn't be. I don't know what's wrong.
This is what the ticket is all the years talking about :)
Comment #14 implied just a bit that this behavior could be intended if the screensaver is disabled so I wrote comment #15 with the potential possibilities how this could be handled.
Good to know that this is indeed just a bug. The question is now why it happens. It is now over 5 years since I reported this issue against XScreenSaver 5.15 (currently I'm on XScreenSaver 5.36) and was not able to utilize DPMS in all this time. Also currently 7 other users have enabled the flag that they are affected by this bug too as this ticket shows.
> Ok well that shouldn't be. I don't know what's wrong.
This is what the ticket is all the years talking about :)
Comment #14 implied just a bit that this behavior could be intended if the screensaver is disabled so I wrote comment #15 with the potential possibilities how this could be handled.
Good to know that this is indeed just a bug. The question is now why it happens. It is now over 5 years since I reported this issue against XScreenSaver 5.15 (currently I'm on XScreenSaver 5.36) and was not able to utilize DPMS in all this time. Also currently 7 other users have enabled the flag that they are affected by this bug too as this ticket shows.