Bugzilla – Bug 10922
'Blank screen' screensaver causes screen freeze
Last modified: 2009-09-08 09:20:25 UTC
When the screensaver starts (screensaver set to 'blank screen', dimming set to 10 seconds and 'dim when charging') if you use the volume control buttons without moving the controller to cause the screen to come 'alive' then the screen will remain black (ie - no output). All functions will work but you have to switch off remote and back on to get output back onto screen again. v7.4 r3822 (remote control) Version: 7.4 - 24834 @ Sun Feb 1 01:05:19 PST 2009 Hostname: siduxbox IP: HTTP Port: 9000 OS: Debian - EN - utf8 Platform: i686-linux Perl Version: 5.10.0 - i486-linux-gnu-thread-multi MySQL Version: 5.0.75-1 Linux Distribution : Sidux (debian Sid + stabilized kernel)
Since there's now a planned 7.3.3 release, bugs which won't make the cut-off are being moved to the next target out. If you feel that this bug needs to be addressed more (or less) urgently than the 7.4 release, please cc chris@slimdevices.com and leave a comment in the bug to that effect so we can review it. Thanks.
Moving to the product SqueezePlay because this bug appears to apply to any player based on that application code. Feel free to move it back if it's specific to the original product.
Does this only happen with the specific repro provided below? I.e., only when you use the volume buttons before picking up the controller? And even then, only when the screensaver is set to "blank screen"?
(In reply to comment #3) > Does this only happen with the specific repro provided below? I.e., only when > you use the volume buttons before picking up the controller? And even then, > only when the screensaver is set to "blank screen"? Yes, I have found this does not happen if you have any of the other screensavers set, only with 'blank screen' screensaver. It also only seems to be triggered by using the volume keys. Other keys / moving the device cause the screensaver to stop and the screen becomes active again.
It sounds like this is "by design" behavior. Any screensaver will not disengage itself with just a volume change. However you should be able to press other keys (such as back or enter) or move the scroll wheel to make the screen not blank any more. If you find that this is not the case, please reopen
(In reply to comment #5) > It sounds like this is "by design" behavior. Any screensaver will not disengage > itself with just a volume change. However you should be able to press other > keys (such as back or enter) or move the scroll wheel to make the screen not > blank any more. If you find that this is not the case, please reopen This is not the case - as stated in the original post, you have to power down the device and switch on again to re-enable the screen. Just to reiterate, the buttons still function (if you have a good memory you can press the appropriate buttons to use the functions) but the screen remains blank - even AFTER moving scroll wheel or pressing buttons.
Ahh, I see "All functions will work", from the original post. Sorry for the misstatement. I'm switching to WORKSFORME, since I can't reproduce. Back and scroll disengage the 'Blank screen' SS for me (before or after having used volume keys) in the FW I am testing, r7013. QA (and original poster, if you are willing), please test this again when you have this version or higher.