I investigated the problem deeper. The issues occurs on _ALL_ scrennsaver modules. The problem occurs _ONLY_ when the screensaver is started via timeout. A manually starting (lock screen) does not show the issue.
When multiple screensavers are running you can also see this on the monitor.
I investigated the problem deeper. The issues occurs on _ALL_ scrennsaver modules. The problem occurs _ONLY_ when the screensaver is started via timeout. A manually starting (lock screen) does not show the issue.
When multiple screensavers are running you can also see this on the monitor.