A message from seconds ago is reported as being from several hours ago

Bug #871444 reported by Arturo Torres Sánchez
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
FBuntu
New
Undecided
Unassigned

Bug Description

I have just received a poke, and the indicator shows up correctly, but after entering the menu, it says something like “153453 h” (That was NOT the number, I don't remember the exact number. The next time it shows up I'll check it)

Revision history for this message
Greg A (etulfetulf) wrote :

Just leaving a comment to let you know I've seen your bug report. Thanks for reporting it!

I got a friend to poke me, and my messaging menu showed the correct time. Hopefully you won't get the problem again, but of course post again here if it does and I'll look into it further.

Revision history for this message
Arturo Torres Sánchez (r2d2.art2005) wrote :

I'm still having this bug. Here's a relevant part from my log to help solve the issue:

2011-10-09 16:08:44 fbuntu.py:56 INFO: Update #455 starting
2011-10-09 16:08:44 graphNotificationChecker.py:32 INFO: Checking Facebook
2011-10-09 16:08:45 graphNotificationChecker.py:38 DEBUG: [{u'from': {u'name': u'Kat Doo', u'id': u'100000213414330'}, u'title': u'Kat Doo pu\u015detis vin.', u'updated_time': u'2011-10-09T20:37:07+0000', u'to': {u'name': u'Arturo Torres S\xe1nchez', u'id': u'1162874940'}, u'link': u'http://www.facebook.com/katy.shaga', u'created_time': u'2011-10-09T20:37:07+0000', u'unread': 1, u'id': u'notif_1162874940_49647856'}]

It says that I received a poke from Kat at 20:37 UTC, or 15:37 CDT (my current timezone). I don't know if the timezone, or the language of Facebook (I set it to Esperanto) is causing some conflicts.

Revision history for this message
Arturo Torres Sánchez (r2d2.art2005) wrote :

I've just checked the exact time it says. It's 1193040 hours. I don't know if this may help.

Revision history for this message
Frank (asianhippie) wrote :

This bug affects me as well. Every one of my notifications show long, large number of hours that seem unreasonable (e.g. mine's show 1193038 h for my latest notification). I'm thinking the problem Arturo encountered above applies to me as well, except that I the notification is in the same timezone as my computer. Hopefully a fix can be quickly made!

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.