Gwibber

Errors dialog should show local time instead of UTC

Bug #249984 reported by Sandy Armstrong
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Gwibber
Fix Released
Undecided
Unassigned

Bug Description

Earlier I had trouble connecting to twitter, and the errors showed times in UTC instead of local. I don't recall there being any indication of AM/PM, either, but I don't currently have any errors so I'm not sure.

Related branches

lp:~segphault/gwibber/webkitui (Merged)
Revision history for this message
Ryan Paul (segphault) wrote :

Yup. I was using datetime.utcnow() instead of datetime.now(). I have fixed this in both the main and webkitui branches. I don't remember now why I used utcnow in the errors... I hope there wasn't a good reason. ;-)

Changed in gwibber:
status: New → Fix Released
Revision history for this message
Sense Egbert Hofstede (sense) wrote :

This bug still seems to occure in the daily PPA.
At least it's back here.

If I'm correct this is caused by line 949 of client.py:
      "time": mx.DateTime.gmt(),
This should probably be
      "time": mx.DateTime.now(),

Changed in gwibber:
status: Fix Released → Confirmed
Revision history for this message
Sense Egbert Hofstede (sense) wrote :

This bug still seems to occure in the daily PPA.
At least it's back here.

If I'm correct this is caused by line 949 of client.py:
      "time": mx.DateTime.gmt(),
This should probably be
      "time": mx.DateTime.now(),

Sense Egbert Hofstede (sense)
Changed in gwibber:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Bug attachments

Remote bug watches

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