Red Hat Bugzilla – Bug 1301904
Wrong timestamp on ftp connection
Last modified: 2016-12-20 13:13:07 EST
Description of problem:
When browsing an ftp server using Dolphin, all of the server's file dates are at 7 Feb 2106
Version-Release number of selected component (if applicable):
15.12.1 (KDE Frameworks 5.18.0, Qt 5.5.1 (built against 5.5.1))
Steps to Reproduce:
1. Open an ftp server with Dolphin
2. Check the dates of the files
3. That the ftp server's dates are actually fine as checked by e.g. terminal
Future dates of all same value
Has been reported on Debian: https://lists.debian.org/debian-qt-kde/2015/11/msg00244.html
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. 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 EOL if it remains open with a Fedora 'version'
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.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 23 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 this bug is closed as described in the policy above.
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.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.