Adium

Opened 13 years ago

Closed 13 years ago

Last modified 13 years ago

#5383 closed defect (fixed)

Time zone does not update while Adium is running

Reported by: Matt Owned by: evands
Milestone: Adium X 1.1 Component: Adium Core
Version: Severity: minor
Keywords: Cc:
Patch Status:

Description

The time stamp seems to be stuck in the wrong timezone, despite my computer saying it's an hour earlier. Screen shot attached.

Attachments (1)

adiumtimestamp.tiff (67.6 KB) - added by Matt 13 years ago.
screencap of the time being wrong.

Download all attachments as: .zip

Change History (13)

Changed 13 years ago by Matt

Attachment: adiumtimestamp.tiff added

screencap of the time being wrong.

comment:1 Changed 13 years ago by Evan Schoenberg

DId you change timezones while Adium was running?

comment:2 in reply to:  1 Changed 13 years ago by anonymous

Replying to evands:

DId you change timezones while Adium was running?

I believe I did, and then forgot about it since my uptime was pushing a week. I restarted and the problem is resolved.

comment:3 Changed 13 years ago by anonymous

Neat, a time zone with a 59-minute difference...

comment:4 Changed 13 years ago by Evan Schoenberg

Milestone: Adium X 1.0
priority: normallow
Severity: normaltrivial
Summary: Timestamp not displaying correctlyTime zone does not update while Adium is running
Version: 0.891.0b9

comment:5 Changed 13 years ago by Chris Forsythe

Resolution: invalid
Status: newclosed

Anonymous said this is resolved, closing.

comment:6 Changed 13 years ago by Eoban

Resolution: invalid
Status: closedreopened

I'm on beta 15, now, and this is definitely still a current problem. I noticed that other applications (e.g. X-Chat Aqua) notice the time zone change right away and change the timestamps as soon as the new time is set. This should be Adium behaviour as well.

comment:7 Changed 13 years ago by Ryan Govostes

If you expect messages from before the time zone shift to update their timestamps, this won't be implemented. If messages sent after the time zone shift aren't displaying the right timestamp, this is an issue.

comment:8 Changed 13 years ago by Daniel M. Zimmerman

Version: 1.0b91.0.1

This is definitely still an issue in 1.0.1; I just experienced it. Messages logged after a time zone change (from US/Pacific to US/Eastern) were still logged as being at (for example) 2007-03-15T23:05:58-07:00. Also, all times displayed in the message view were in US/Pacific (so I sent a message at 02:15, and it showed as having been sent at 23:15 in the message window). A quit and restart makes Adium notice the correct time zone, and of course it is the correct absolute time that is being logged (2007-03-15T23:05:58-07:00 is the same as 2007-03-16T02:05:58-04:00) - just with the incorrect zone offset.

comment:9 Changed 13 years ago by Evan Schoenberg

Milestone: Adium X 1.1
Owner: changed from nobody to Evan Schoenberg
Patch Status: None
Status: reopenednew

comment:10 Changed 13 years ago by Evan Schoenberg

Status: newassigned

Issue confirmed. It's somewhat silly that NSTimeZone doesn't take care of this itself...

comment:11 Changed 13 years ago by Evan Schoenberg

Resolution: fixed
Status: assignedclosed

(In [19189]) When the system time zone changes, as notified via the (undocumented) NSSystemTimeZoneDidChangeDistributedNotification distributed notification, reset NSTimeZone's cache for the system time zone. It then updates it next time it's used... which means that NSDateFormatters everywhere see the new time zone, as well. Fixes #5383

comment:12 Changed 13 years ago by Evan Schoenberg

(In [19720]) Merged [19719]: Patch from Joe Ranieri, discussed on adium-devl, which publishes Adium via NSConnection under the name 'com.adiumx.adiumx' to allow distant object (out of process) communication.

Merged [19189]: When the system time zone changes, as notified via the (undocumented) NSSystemTimeZoneDidChangeDistributedNotification distributed notification, reset NSTimeZone's cache for the system time zone. It then updates it next time it's used... which means that NSDateFormatters everywhere see the new time zone, as well. Fixes #5383

Note: See TracTickets for help on using tickets.