Bug 5182 - Alarms changing
: Alarms changing
Status: CLOSED FIXED
Product: MySqueezebox.com
Classification: Unclassified
Component: Alarm
: unspecified
: PC Windows XP
: P2 normal (vote)
: Future
Assigned To: Andy Grundman
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-07-24 11:36 UTC by Anoop Mehta
Modified: 2008-12-15 13:05 UTC (History)
2 users (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Anoop Mehta 2007-07-24 11:36:07 UTC
When setting the Weekday Alarms on SqueezeNetwork via the Squeezebox, the values set for monday will change when tuesday is set and so on for the other days. For example when Monday is set for 5:00pm, then Tuesday gets set for 3:00pm, Monday will get changed to 3:00pm as well. Monday should stay at 5:00pm and Tuesday should stay at 3:00pm.
Comment 1 KDF 2007-07-24 12:05:14 UTC
I think this may be in slimserver, as I tried it and saw a tuesday time change the monday time.  However, it only happened once so might be a prefs problem (bad state, perhaps). I cannot compare the symptom I saw with that of squeezenetwork as the web UI on SQN currently errors out on any pref change saying "No such player associated with account slim-mail@deane-freeman.com".  None of my players seem valid, despite being listed.  Perhaps the prefs forms fail from behind corporate firewalls.  
Comment 2 Andy Grundman 2007-07-26 06:22:35 UTC
Just to clarify, the web UI is fine, and the problem is only in the player UI?
Comment 3 Anoop Mehta 2007-07-26 11:32:53 UTC

Yes the problem is only in the player UI. When connected to SN.
Comment 4 Chris Owens 2007-08-07 12:39:30 UTC
Did you see this problem yourself Anoop?  Should QA try to make sure we can reproduce it here?
Comment 5 Anoop Mehta 2007-08-07 12:40:08 UTC
Chris,
At the time I did manage to reproduce this. 
Comment 6 Max Spicer 2008-09-22 08:08:52 UTC
As the alarm code is a ground-up rewrite in 7.2 I'm marking this as fixed.
Comment 7 James Richardson 2008-12-15 13:05:06 UTC
This bug appears to have been fixed in the latest release!

If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.

Make sure to include the version number of the software you are seeing the error with.