Bug 14367 – Alarms do not always honor preferences or configured values

Bug 14367 - Alarms do not always honor preferences or configured values

Summary:

Alarms do not always honor preferences or configured values

Status:	RESOLVED WORKSFORME

Product:	Logitech Media Server
Classification:	Unclassified
Component:	Alarm
Version:	7.3.4
Platform:	PC Windows XP

Importance:	-- normal (vote)
Target Milestone:	7.4.0
Assigned To:	Unassigned bug - please assign me!

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2009-09-28 09:59 UTC by Mike Cappella
Modified:	2009-10-01 10:08 UTC (History)
CC List:	2 users (show)

See Also:
Category:	Bug

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Mike Cappella 2009-09-28 09:59:35 UTC

Within the past few days, I've experienced two alarm misfires with Boom, using 7.3.4 svn latest (as of 9/24).

1) Disabled Alarm #3 fired when it was configured to be *off*.  Settings were verified.  Boom showed no Alarm icon.

2) Enabled Alarm #3's time was modified (at about 1am) from 7am to 8am.  Alarm fired at 7am.  Settings were verified. Boom showed 8am as next alarm time when taping snooze.

Comment 1 James Richardson 2009-09-29 11:17:13 UTC

Please retest with 7.4.0

Provide logs with player.alarmclock = debug

Did you enable or disable SC > SN sync?

Comment 2 James Richardson 2009-10-01 10:08:21 UTC

I am unable to replicate this bug.  Please reopen the bug, and provide logs if you are still seeing any issues.