https://bugs.kde.org/show_bug.cgi?id=365855
Bug ID: 365855
Summary: Krunner's "Recent documents" results still there after
"forgetting" recent docs in appdashboard
Product: krunner
Version: 5.7.1
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: NOR
Component: general
Assignee: [email protected]
Reporter: [email protected]
[Please note: in this report all strings marked with (*) are backtranslated
from Polish l10n; they might be slightly different in the the English
original.]
When I clear (i.e. "forget") Recent Documents(*) in appdashboard, these
documents can still be found by typing part of a filename in Krunner. They
display in a group labelled "Recent documents(*)".
Additionally there doesn't seem to be ANY way to clear recent documents history
remembered by Krunner. The whole endeavour of covering one's tracks is thus
completely defeated. Whenever someone is sitting beside who I don't want to be
privy to my recent activity, I must remember not to use Krunner at all because
something I don't want that person to see might show in the results.
Disabling recent history search in Krunner is not an acceptable workaround. I
want to have the feature AND have control over it, rather than not have the
feature.
Reproducible: Always
Steps to Reproduce:
1. Open a document, e.g. a spreadsheet
2. Clear recent files in the program you used to open the document (just to
eliminate this variable)
3. In appdashboard, right click "Recent documents(*)" and choose "Forget about
all documents(*)"
4. Activate Krunner and type a sufficiently long part of the filename of the
document you opened in step 1
Actual Results:
The file is shown in Krunner search results in a section named "Recent
documents(*)", even though the appdashboard "Recent documents(*)" tab is empty.
Expected Results:
The file should NOT be located by Krunner, at least not in the "Recent
documents(*)" section.
I believe that the ability to erase tracks of recent activity is a major
feature, and I believe that this feature is broken by this bug. Therefore I
chose severity "Major: A major feature is broken".
--
You are receiving this mail because:
You are watching all bug changes.
