gtwitter computes times as if local clock is set to UTC
Bug #201766 reported by
Mary Gardiner
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gtwitter (Debian) |
Fix Released
|
Unknown
|
|||
gtwitter (Ubuntu) |
Confirmed
|
Low
|
Unassigned |
Bug Description
Binary package hint: gtwitter
Recent twitter posts show up in gTwitter with my UTC offset added to them. A post I make was immediately posted "about 11 hours ago" (I am UTC+11). A post an hour old was posted "about 12 hours ago", and so on. (Goodness knows what happens with someone who is behind UTC, as it will think recent posts are from the future.)
For information, my system is set to use local time on the hardware clock, not UTC.
$ cat /etc/adjtime
-0.157515 1205406294 0.000000
1205406294
LOCAL
This is a regression from the Gutsy version.
Package: 1.0~beta-6ubuntu1
Changed in gtwitter: | |
status: | Unknown → New |
Changed in gtwitter: | |
importance: | Undecided → Low |
status: | New → Confirmed |
Changed in gtwitter (Debian): | |
status: | New → Fix Released |
To post a comment you must log in.
I can confirm this behavior for myself at GMT+2 and all posts in twitter are listed as "about 2 hours ago". On my Gutsy 7.10 system, the exact same post appears with "2 minutes ago".
What is Hardy doing different than Gutsy for time?