Bug 12370 - Altering the alarm schedule for another day turns of other scheduled alarms ? if the time is close to each other
: Altering the alarm schedule for another day turns of other scheduled alarms ?...
Status: CLOSED FIXED
Product: Logitech Media Server
Classification: Unclassified
Component: Alarm
: 7.4.0
: PC RedHat Linux
: -- normal with 1 vote (vote)
: 7.4.0
Assigned To: James Richardson
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-06-12 21:29 UTC by Mikael Nyberg
Modified: 2009-10-05 14:25 UTC (History)
1 user (show)

See Also:
Category: ---


Attachments
100 lines of server log (9.74 KB, text/plain)
2009-07-07 00:51 UTC, Mikael Nyberg
Details
possible broken log file (6.85 MB, text/plain)
2009-07-07 00:53 UTC, Mikael Nyberg
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Mikael Nyberg 2009-06-12 21:29:25 UTC
Sorry for the weird description.
And I'm unsure if this is SqueezeBox Server controller or boom issue ?

I goes like this I have 4 different alarm schedules I adjusted the time on one of these with the help of the controller, that alarm went of fine.

But I noticed that afterwards the boom lacked that little bell symbol that indicates that one have pending alarms ?
So i checked the alarms schedule and all looked ok to me ?
Then I changed back the time I altered before time and reapplied the settings.
And that little bell on the boom comes back ?

Some fault tracing I'we done

I have one Monday to Friday schedule set at 5:50 AM "alarm 2"
And one Saturday schedule at 08:00 AM "alarm 1"

I had to get up early this Saturday so I moved my Saturday wake up to 5:50 AM too and then this happens.

If I make some experiments I see that any time close 5:50 will reproduce this 6:10 will also get you the same effect.

I'm running:

Version: 7.4 - 27039 @ Fri Jun 12 04:05:24 PDT 2009
Hostname: hal.home.lan
IP: 192.168.1.5
HTTP Port: 9000
OS: Red Hat - EN - utf8
Platform: i686-linux
Perl Version: 5.8.8 - i686-linux-thread-multi
Total Players Recognized: 3

Controller at 7.4 - 5580

boom at firmware 47
Comment 1 Mikael Nyberg 2009-06-12 21:53:47 UTC
Doh forget one important piece of information:

I have "alarm 3" my Sunday 09:00 AM schedule !

Thats the weird thing I should have the "bell" symbol on my boom on saturday because i have a pending sunday alarm, but as i described this is influenced by some clash between mon-fri and sat alarms ?
Comment 2 James Richardson 2009-06-13 06:41:48 UTC
Can you include a log file; with Alarm set to debug, then recreate the error condition.

Attach the log to this bug file as an attachment, not in the body of the bug
Comment 3 Mikael Nyberg 2009-06-14 05:25:11 UTC
I'm away working, will not be home for a while, you have to wait for that test.
Comment 4 Mikael Nyberg 2009-07-07 00:48:57 UTC
Well with the latest nightly this is working now ?

I did the test all was ok

had some sftp problems so i cut and pasted the last 100 log lines to a file
Comment 5 Mikael Nyberg 2009-07-07 00:51:13 UTC
Created attachment 5417 [details]
100 lines of server log
Comment 6 Mikael Nyberg 2009-07-07 00:53:52 UTC
Created attachment 5418 [details]
possible broken log file
Comment 7 James Richardson 2009-07-07 08:42:19 UTC
I'm going to mark this one as fixed then, since it's working for you now.

Feel free to reopen the bug if you run into the issue again.
Comment 8 James Richardson 2009-10-05 14:25:50 UTC
This bug has been marked as fixed in the 7.4.0 release version of SqueezeBox Server!
    * SqueezeCenter: 28672
    * Squeezebox 2 and 3: 130
    * Transporter: 80
    * Receiver: 65
    * Boom: 50
    * Controller: 7790
    * Radio: 7790  

Please see the Release Notes for all the details: http://wiki.slimdevices.com/index.php/Release_Notes

If you haven't already, please download and install the new version from http://www.logitechsqueezebox.com/support/download-squeezebox-server.html

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