Created attachment 697351 [details] File's time on Linux Bug still present with Fedora 18 (kernel 3.7.6-201.fc18.i686) See the 2 screen-shots (from cloned bug #873894) to see the problem. On Windows -> the time displayed is the correct time of the file. On Linux -> the time displayed is the NOT correct for the files before last DST. +++ This bug was initially created as a clone of Bug #873894 +++ Created attachment 639673 [details] Results on Windows (As expected) Description of problem: The time of files on USB key or SD cards (FAT formatted) are not correct after DST (Daylight Saving Time). See this example: 1) before DST (21th of August) at 15:36, I had saved a file "15h36.txt" on an USB stick 2) after DST (today 6th of November) at 10:26, I have saved another file "10h26.txt" on the USB stick Results: - On Windows => everthing is OK concerning the dates, before and after DST (see Attachement) - Idem with "DIR" MSDOS command - On Linux => before DST, the time of the single file "15h36.txt" was correct - On Linux => after DST, the time of the new file "10h26.txt" is correct BUT the time of the old file "15h36.txt" is now erroneous !! There is one hour shift ! (see Attachement) How reproducible: Always Actual results: There is a one-hour shift for files after DST => it is not possible to have every files at the correct time: if the ones after DST are correct, the ones before are not (or vice versa I guess) Expected results: Every files should have the correct time displayed ! - This is the case in Windows (see attachement) and MSDOS - This is the case in Linux for the other FS (EXT2/3, NTFS) Additional info: 1) Same problem for FAT SD card (from camera) 2) FAT USB key is mounted automatically in KDE or GNOME ; mount options are: /dev/sdf1 on /media/440E-003D type vfat (rw,nosuid,nodev,relatime,uid=1000,gid=1000,fmask=0022,dmask=0077,codepage=cp437,iocharset=ascii,shortname=mixed,showexec,utf8,flush,errors=remount-ro,uhelper=udisks) (I have tried to mount the FAT FS manually using different mount options: no change) --- Additional comment from nicofo on 2012-11-06 17:29:46 EST --- Created attachment 639674 [details] Results on Linux (NOT as expected) --- Additional comment from on 2012-11-20 13:31:50 EST --- Hi, I can confirm this bug: every night at 10 PM, I save a log file on an SD card (fat formatted). The files of November (after DST) are at 10 PM: correct The files of October (before DST) are at 11 PM: not correct ! Windows XP always shows the correct times
Created attachment 697352 [details] File's time on Windows
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 18 kernel bugs. Fedora 18 has now been rebased to 3.11.4-101.fc18. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 19, and are still experiencing this issue, please change the version to Fedora 19. If you experience different issues, please open a new bug report for those.
Problem still present with F19 and kernel 3.11.4-201.fc19.i686 Now it is Summer time: the time of the files saved during Winter time is not displayed correctly in Linux (while it is on Windows).
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Same problem with Fedora 20 (kernel 3.12.5)
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs. Fedora 20 has now been rebased to 3.13.4-200.fc20. Please test this kernel update and let us know if you issue has been resolved or if it is still present with the newer kernel. If you experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE ************** This bug has been in a needinfo state for several weeks and is being closed with insufficient data due to inactivity. If this is still an issue with Fedora 20, please feel free to reopen the bug and provide the additional information requested.