Bugzilla – Bug 9073
When in alarm mode remote keypresses are unresponsive
Last modified: 2009-07-31 10:26:46 UTC
When an alarm goes off, I see the now playing screensaver. After 30 seconds into songs, if I try to press keys, the first keypress is ignored or causes strange things to happen. Sometimes I briefly see the power-off screensaver or idle screensaver. A second keypress is often needed, but it depends if I have waited ~30 seconds since the last keypress (i think this problem is screensaver related, as my screensaver delay time is 30 secs). I have the screensaver when playing set to "Now Playing".
I don't understand why you see the now playing screensaver when an alarm goes off. Could you confirm that you're not using any plugins which change the alarm screensaver or indeed any non-standard screensaver-related plugins? A log covering the alarm going off, with alarm debugging enabled, would also be very useful. Please disable ALL 3rd party plugins before compiling such a log though.
I tried this again with no third-party plugins. It does indeed work as expected. So, I guess that one of my third-party plugins interferes with this new alarm screensaver mode somehow. The date/time screensaver still displays when the alarm goes off (with a flashing alarm symbol), rather than the Now Playing screensaver. I guess this is what you mean by a third-party screensaver that changes the alarm screensaver (because I can't see a setting for alarm screensaver, I assume this is programmatic only)? However, once a remote button is pressed, the player works as normal.
For the benefit of other users who may be experiencing this problem, I've found that the issue appears to be with Erland's Dynamic Playlist plugin. I Restored all third-party plugins and tried configuring various screensavers, which didn't cause the problem. The problem only appears to occur when selecting a Dynamic Playlist as the alarm playlist. i.e. When I select a favorite as the alarm playlist, with many third-party plugins enabled, alarm functionality it works fine. I will point Erland at this bug report, but I guess this bug can be closed, as it is a third-party plugin issue.
I'll take that back. I tried a Random Song Mix with no 3rd party plugins. When the alarm went off, the date/time remained displayed with a flashing alarm symbol. I waited for the music to play for over 30 seconds (my screensaver delay time), and then pressed right-arrow. This took me to the Main menu, displaying "Home - Now Playing ->". Another press is required to display the now playing song. If I then wait another 30 secs, the Now Playing screensaver displays the now playing song. Pressing right-arrow goes back to "Home - Now Playing ->". My now playing screensaver is "Now Playing", so when it kicks in, I should remain on Now Playing page. I see slightly different issues when I have other 3rd party plugins enabled, but I guess there's something here that is causing the problem.
When an alarm kicks in your normal now playing screensaver is overriden with the DateTime screensaver. This will be displayed until you cancel it by pressing a button or by ending the alarm (pressing stop, power etc). This is all by design. From your last comment, it sounds as if things are working as expected.
>When an alarm kicks in your normal now playing screensaver is overriden with >the DateTime screensaver. This will be displayed until you cancel it by >pressing a button or by ending the alarm (pressing stop, power etc). This is >all by design. From your last comment, it sounds as if things are working as >expected. No, I don't believe it is. When an alarm kicks in, the DateTime screensaver is indeed displayed (I don't particularly like this, but agree that this bit is working as designed). The DateTime screen is displayed until I cancel it by pressing a button. If I press a button, it displays the Menu, not the playing screensaver that is configured. If I then wait 30 secs for the screensaver timeout to occur, it displays my chosen "Now Playing" screen. If I press a button, it returns me to the Menu, instead of actually passing the keypress to the now playing screen. Hence, when I see the Now Playing screen, I have to press right-arrow twice to get into the song info for the currently playing track.
This isn't a bug with the alarm code, so I'm marking Invalid. Exiting the alarm screensaver (datetime) should drop you out of screensaver mode, not into another screensaver so you should not see now playing when exiting it. Please file another bug if there's a problem with your now playing screensaver. You should probably also check that you've got Now Playing set as your when playing screensaver, not Now Playing (jump back on wake). Generally, exiting a screensaver puts you back to where you were when it started.
>This isn't a bug with the alarm code, so I'm marking Invalid. Exiting the >alarm screensaver (datetime) should drop you out of screensaver mode, not into >another screensaver so you should not see now playing when exiting it. > Drop out of screensaver mode into what though? If power was off, the user wasn't anywhere previously. It has to go somewhere, and I'd expect that place to be Now Playing.
Reduce number of active targets for SC