[Bug 263571] New: KDE Find Files / Folders Dialog / Properties Tab / Find All Files created or modified between

foxbearmouse at yahoo.ca foxbearmouse at yahoo.ca
Tue Jan 18 18:40:46 GMT 2011


https://bugs.kde.org/show_bug.cgi?id=263571

           Summary: KDE Find Files / Folders Dialog / Properties Tab /
                    Find All Files created or modified between
           Product: kde
           Version: 4.5
          Platform: Gentoo Packages
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: unassigned-bugs at kde.org
        ReportedBy: foxbearmouse at yahoo.ca


Created an attachment (id=56171)
 --> (http://bugs.kde.org/attachment.cgi?id=56171)
It seems impossible to specify a date search interval between and after year
2000.

Version:           4.5 (using KDE 4.5.4) 
OS:                Linux

It seems impossible to use the KDE Find Files dialog to locate files created or
modified between dates within the interval of today's date and any dtes prior
to the year 2000.  USers get a KFind invalid date range message box alert
followed by another message saying: "Please specify an absolute path in the
"Look in" box, though a legitimate absolute path is already specified.  The
KFind dialog reverts to the year '20XX' even when specifying the year '19XX'.

Reproducible: Always

Steps to Reproduce:
Launch the KFind application, specify an absolute path ( i.e. directory
containing valid files ).  Click on the Properties tab of the KFind dialog and
enter a date range before 2000 and after year 2000.

Actual Results:  
Error.  Seems to force a legitimate date to another value.  For example 1999
become the year 2099.

Expected Results:  
Should produce a list of any files matching created or modified dates within
the specified date range.

Not sure if this bug applies to current or older versions of KFind.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the Unassigned-bugs mailing list