Bugzilla – Bug 4916
Alarms don't work.
Last modified: 2008-12-18 11:11:58 UTC
Not sure if there is a better component for this. I've tried setting alarms from the player settings section of the web UI, or with the remote. The little bell symbol shows on the screen, and the settings are stored in the .pref file, the alarm just doesn't go off. SlimServer version 6.5.2 - 11753 XP
try looking at d_command and d_source when the alarm is supposed to trigger. might also want to add a line in Slim::Buttons::AlarmClock::checkAlarms to make sure it's checking ok, perhaps after line 439: msg("checking for alarm at $alarmtime\n");
oh, d_prefs maybe as well to make sure the prefs for the alarm are being set correctly on the test system.
as a note, it seems to be working for me. What are the contents of your prefs file for all of the alarm preferences on the given player?
Ross, I am not able to reproduce either. Do you still see the behavior with the latest nightly? SlimServer Version: 6.5.2 - 11764
Ping Ross. If this is a real bug, I'd definitely like to try to get it fixed for 6.5.2 since it would be a feature which is completely broken.
Still easily reproduced with 6.5.2 - 11881 - Windows XP - EN - cp1252
I'll point again to comment #1 & 3 :)
Created attachment 1928 [details] log
Sorry about that KDF!
and an interesting log it is, thanks. deffo something to work on now :)
Ross, I'm cuious about the appearance of the PLUGIN_RANDOM_ARTIST_ITEM string. That shoudln't be there at all. Can you try again with d_plugins and d_prefs enabled. Then, AFTER that please try setting the playlist choice to something other than random artist...then you can switch it back to Random Artist and see if everything works.
sorry, nevermind. I know where the string is coming from now.
fixed in trunk at change 11888 and in 6.5.2 at change 11889 please reopen if you have any further troubles.
It works! Thanks KDF.
Fixed in 6.5.2, which is now released and available for download at http://www.slimdevices.com/su_downloads.html If you're still experiencing this bug, please re-open it!