After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 714009 - Wrong date printed in header
Wrong date printed in header
Status: RESOLVED OBSOLETE
Product: geary
Classification: Other
Component: ux
master
Other All
: Normal normal
: ---
Assigned To: Geary Maintainers
Geary Maintainers
: 713230 (view as bug list)
Depends on: 765516 778022
Blocks:
 
 
Reported: 2013-09-10 10:47 UTC by Jim Nelson
Modified: 2018-04-13 01:15 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Charles Lindsay 2013-11-21 20:23:55 UTC


---- Reported by jim@yorba.org 2013-09-10 15:47:00 -0700 ----

Original Redmine bug id: 7467
Original URL: http://redmine.yorba.org/issues/7467
Searchable id: yorba-bug-7467
Original author: Jim Nelson
Original description:

When printing a message, it appears that the "pretty" date is printed before
the full date. The line at the top of the printout looks something like this:

    
    
    Date: 40m ago September 10, 2013 3:04 pm
    

or

    
    
    Date: Yesterday September 9, 2013 2:34 pm



---- Additional Comments From geary-maint@gnome.bugs 2013-09-23 15:34:00 -0700 ----

### History

####

#1

Updated by Jim Nelson about 1 month ago

  * **Target version** changed from _0.4.0_ to _0.5.0_



--- Bug imported by chaz@yorba.org 2013-11-21 20:24 UTC  ---

This bug was previously known as _bug_ 7467 at http://redmine.yorba.org/show_bug.cgi?id=7467

Unknown milestone "unknown in product geary. 
   Setting to default milestone for this product, "---".
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.
Resolution set on an open status.
   Dropping resolution 

Comment 1 Federico Bruni 2015-07-08 12:30:16 UTC
I can confirm it on version 0.10 (visible in the print preview)
Comment 2 Michael Gratton 2016-12-20 13:23:22 UTC
This is in part obsoleted by Bug 765516, but marking it as a dependency to make sure the same mistake isn't made there.
Comment 3 Michael Gratton 2018-04-13 01:14:16 UTC
*** Bug 713230 has been marked as a duplicate of this bug. ***
Comment 4 Michael Gratton 2018-04-13 01:15:27 UTC
Marking this as obsolete, since we aren't printing any date at the moment (Bug 778022)