GNOME Bugzilla – Bug 661515
Wrong date is shown in chat window
Last modified: 2012-03-06 13:58:02 UTC
Created attachment 198833 [details] Screen shot of a wrong date; the date is highlighted When I access a chat window, the date of the last message(s) seems to be wrong. It says Wednesday the 12th but it's clearly Tuesday the 11th in the previous conversation window. The time is right, just the date is wrong. See the attachment for a visual representation.
for me work fine y all protocols (gtalk, msn, gabber, xmpp) empathy 3.2 ubuntu 11.10
This date is created in empathy-log-window:get_parent_iter_for_message using: date = g_date_time_new_from_unix_local ( tpl_event_get_timestamp (event)); pretty_date = g_date_time_format (date, C_("A date with the time", "%A, %e %B %Y %X")); Could you please look at the date stored in the XML files in ~/.local/share/TpLogger/logs ?
For that particular message it says <message time='20111012T02:59:13' I would assume it's UTC and I since live in UTC-5, thus it's completely correct. If I would take a guess, it seems very plausible it's taking the UTC date but the UTC-5 timestamp.
Is the date wrong in the treeview top-right? Or next to the messages themselves?
(In reply to comment #2) > This date is created in empathy-log-window:get_parent_iter_for_message using: > > > date = g_date_time_new_from_unix_local ( > tpl_event_get_timestamp (event)); > > pretty_date = g_date_time_format (date, > C_("A date with the time", "%A, %e %B %Y %X")); > > > Could you please look at the date stored in the XML files in > ~/.local/share/TpLogger/logs ? Guillaume, that piece of code is probably not the cause of this problem because it is used by the Empathy log window, which has the correct date. Danielle, the date is wrong in the actual message window.
Created attachment 209077 [details] [review] Proposed fix
Review of attachment 209077 [details] [review]: Looks like the same fix I did in the log window one time. Also being in the legacy themes explains why some people don't notice it. ++
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.
*** Bug 668150 has been marked as a duplicate of this bug. ***