Bug 1456997 - Date and time are incorrect when printing
Summary: Date and time are incorrect when printing
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox
Version: 25
Hardware: i686
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-05-30 23:47 UTC by Stefano Biagiotti
Modified: 2017-06-20 07:53 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-06-20 07:53:44 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Mozilla Foundation 1362817 0 None None None Never

Description Stefano Biagiotti 2017-05-30 23:47:21 UTC
Description of problem:
When printing, date and time in the footer are incorrect.
Printed date is always 1/1/70 and time is something between 00:00 and 01:59.

Version-Release number of selected component (if applicable):
firefox-53.0.2-5.fc25.i686

How reproducible:
Always. Just try to print and watch the incorrect date and time.

Additional info:

I downloaded firefox-52.0.2-2.fc25.i686.rpm from koji and it works as expected, date and time are ok. I suppose there is a bug in the new v53.

I tried to reproduce on an x86_64 PC, but x86_64 version works correctly. I suppose there is a bug in the 32-bit version only.

I tried to reproduce on another i686 PC, and I confirm the bug appeared after I dnf-updated.

I installed chromium and icecat and both work well.

System time is correct:
$ LANG=en_US timedatectl
      Local time: Wed 2017-05-31 01:00:29 CEST
  Universal time: Tue 2017-05-30 23:00:29 UTC
        RTC time: Tue 2017-05-30 23:00:29
       Time zone: Europe/Rome (CEST, +0200)
 Network time on: yes
NTP synchronized: yes
 RTC in local TZ: no

Comment 1 Jan Horak 2017-06-20 07:52:55 UTC
Hey, good work on finding the upstream bug! I guess we can close it now and track it upstream.


Note You need to log in before you can comment on or make changes to this bug.