Bug 8320 – internal clock set to wrong timezone after SquezeNetwork use

Bug 8320 - internal clock set to wrong timezone after SquezeNetwork use

Summary:

internal clock set to wrong timezone after SquezeNetwork use

Status:	CLOSED FIXED

Product:	MySqueezebox.com
Classification:	Unclassified
Component:	Player UI
Version:	unspecified
Platform:	All All

Importance:	P1 normal (vote)
Target Milestone:	---
Assigned To:	Andy Grundman

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2008-06-04 05:35 UTC by Peter Watkins
Modified:	2008-12-15 12:16 UTC (History)
CC List:	0 users

See Also:
Category:	---

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 Peter Watkins 2008-06-04 05:35:33 UTC

I've had my Boom on the CAT "boomcat" SN service for a few days. I disconnected it from my local network. When I pressed the power button to display the internal clock, it was 3 hours "early". I assume this means that the boomcat server is in US/Pacific and the Boom clock was set to the local time of the SN server. It should be set to the user's local time -- when on SN, it should take into account the timezone specified by the user.

Comment 1 Caleb Crome 2008-06-04 09:15:43 UTC

Is this yours felix?  Or maybe Andy.

Comment 2 Chris Owens 2008-06-05 16:13:17 UTC

Andy, do the commands to change the boom clock take the user's time zone into account?  Is this your bug?

Comment 3 Andy Grundman 2008-06-06 06:16:58 UTC

Yeah the code that sets the RTC hasn't been changed to use the SN timezone yet.

Comment 4 Mickey Gee 2008-07-28 15:46:12 UTC

Moving to 7.2 to ensure visibility.

Comment 5 Andy Grundman 2008-07-30 14:40:44 UTC

Fixed in change 22245.

Comment 6 James Richardson 2008-12-15 12:16:56 UTC

This bug has been fixed in the latest release of SqueezeNetwork!

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