2013-03-06, 00:32
Hi!
I've discovered a repeatable misbehaviour of the built-in screensavers (dim and blank). When enabling vsync as "always on", the screensavers can't kick in. If I choose to preview the screensaver, I know it's running because XBMC ignores one keypress, but the screen never actually dims or blanks. The logs show no screensaver error during this test.
This behaviour is consistent and repeatable on my setup - enabling "vsync always on" makes the screensavers "Dim" and "Black screen" not actually do anything. Active 3D screensavers do work. Disabling vsync lets the Dim and Black screen screensavers do their thing properly again.
This problem occurs on an Intel i3 3220 (Intel HD2500 iGPU) running Frodo final (bug(?) is also present in earlier nightlies) under Ubuntu 12.10 in standalone mode.
I can't seem to find a bug report of this nature in the Bugtracker, nor on the forums. Has anyone else seen it and has a solution/workaround/known active bug report, or should I open a new ticket for this?
I've discovered a repeatable misbehaviour of the built-in screensavers (dim and blank). When enabling vsync as "always on", the screensavers can't kick in. If I choose to preview the screensaver, I know it's running because XBMC ignores one keypress, but the screen never actually dims or blanks. The logs show no screensaver error during this test.
This behaviour is consistent and repeatable on my setup - enabling "vsync always on" makes the screensavers "Dim" and "Black screen" not actually do anything. Active 3D screensavers do work. Disabling vsync lets the Dim and Black screen screensavers do their thing properly again.
This problem occurs on an Intel i3 3220 (Intel HD2500 iGPU) running Frodo final (bug(?) is also present in earlier nightlies) under Ubuntu 12.10 in standalone mode.
I can't seem to find a bug report of this nature in the Bugtracker, nor on the forums. Has anyone else seen it and has a solution/workaround/known active bug report, or should I open a new ticket for this?