Bug 379129 - Duplicate recent document opened
Summary: Duplicate recent document opened
Status: RESOLVED FIXED
Alias: None
Product: frameworks-kio
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: David Faure
URL:
Keywords: usability
Depends on:
Blocks:
 
Reported: 2017-04-23 17:19 UTC by danjaredg
Modified: 2018-08-16 22:02 UTC (History)
6 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
application launcher with recent documents duplicated (44.40 KB, image/jpeg)
2017-04-23 17:19 UTC, danjaredg
Details
krunner with recent documents duplicated (22.01 KB, image/jpeg)
2017-04-23 17:21 UTC, danjaredg
Details

Note You need to log in before you can comment on or make changes to this bug.
Description danjaredg 2017-04-23 17:19:08 UTC
Created attachment 105162 [details]
application launcher with recent documents duplicated

the recent documents opened appear duplicates

To reproduce: Open a file many times, and this files appear duplicate many times in krunner and laucher menu.
Comment 1 danjaredg 2017-04-23 17:21:07 UTC
Created attachment 105163 [details]
krunner with recent documents duplicated
Comment 2 Michael D 2017-05-28 06:57:03 UTC
On my system (KDE Neon, Plasma 5.9.5) the application launcher is not showing duplicates, but krunner is.
Comment 3 Kai Uwe Broulik 2017-05-29 12:11:10 UTC
Did you perhaps open the same file in different applications? When I open the same file in Kate and Kwrite for instance I get it in KRunner twice. Agreed, it should probably strip duplicates.

KRecentDocument::recentDocuments() probably shouldn't contain duplicates.
Comment 4 Michael D 2017-05-29 17:46:08 UTC
It definitely should not unless the entries remember which application it was opened in and displays this info in the recents list. But even still duplicates don't make sense.
Comment 5 Nate Graham 2018-06-29 23:07:39 UTC
Here, have a patch: https://phabricator.kde.org/D13804
Comment 6 Nate Graham 2018-08-16 22:02:43 UTC
It turns out that the bug was already fixed somewhere along the way, so my patch was unnecessary!