Bug 172296
Summary: | Date (year) incorrect when browsing ftp | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Hans Kristian <hk> |
Component: | firefox | Assignee: | Christopher Aillon <caillon> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4 | CC: | frank, mcepl, mcepl, wtogami |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
URL: | ftp://mirrors.kernel.org/fedora/core/updates/testing/4/i386/ | ||
Whiteboard: | |||
Fixed In Version: | 1.5.0.7-7.fc6 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-07-19 06:22:29 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Hans Kristian
2005-11-02 14:59:39 UTC
Let me do some triaging... 1. Rawhide (firefox-1.5-0.5.0.beta2) doesn't show this anymore. 2. Related mozilla bug is https://bugzilla.mozilla.org/show_bug.cgi?id=236365 This report targets the FC3 or FC4 products, which have now been EOL'd. Could you please check that it still applies to a current Fedora release, and either update the target product or close it ? Thanks. Distribution against which this bug was reported is no longer supported; could you please reproduce this with the updated version of the currently supported distribution (Fedora Core 6, or Fedora 7, or Rawhide)? If this issue turns out to still be reproducible, please let us know in this bug report. If after a month's time we have not heard back from you, we will have to close this bug as CANTFIX. Setting status to NEEDINFO, and awaiting information from the reporter. Thanks in advance. This got fixed upstream one and a half years ago. See comment #2 for mozilla bug reference. I've checked firefox-1.5.0.7-7.fc6 sources, and it's definitly fixed there. So later versions should be fine, too. I just close this bug before someone wastes more time with triaging... |