Bug 456504

Summary: When using the "double click to open files" setting, you need to click extremely fast on the deskop
Product: [Plasma] plasmashell Reporter: Marcel Hentschel <marcelhentschel580>
Component: FolderAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal CC: hein, nate, plasma-bugs, zrenfire
Priority: NOR    
Version: 5.18.8   
Target Milestone: 1.0   
Platform: Debian stable   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Marcel Hentschel 2022-07-09 08:38:10 UTC 
STEPS TO REPRODUCE
1. Use a high frame rate Monitor (144hz in my case)
2. Activate double click to open files and folders in the "General Behaviour"-Settings

OBSERVED RESULT
You need to double click extremly fast with files located on the desktop.  (the higher the refresh rate, the faster you have to double click)

EXPECTED RESULT
The same click speed as on Dolphin.

SOFTWARE/OS VERSIONS
Operating System: Debian GNU/Linux 11
KDE Plasma Version: 5.20.5
KDE Frameworks Version: 5.78.0
Qt Version: 5.15.2
Kernel Version: 5.10.0-15-amd64
OS Type: 64-bit
Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor
Memory: 15.6 GiB of RAM
Graphics Processor: NVIDIA GeForce GT 1030/PCIe/SSE2
Comment 1 Chris Holland 2022-07-09 16:52:38 UTC 
If you have trouble finding out which product/category, this might help: https://zren.github.io/kde/repos/#desktop-folder-view

The existing Folder View bugs are at:
https://bugs.kde.org/buglist.cgi?component=Folder&list_id=2110597&order=bug_id%20DESC&product=plasmashell&query_format=advanced

Possibly related bug?
https://bugs.kde.org/show_bug.cgi?id=428978 Double clicking desktop items does not open selected items (Plasma 5.20.4)

You're using Debian 11 with Plasma 5.20. Unless debian is backporting fixes, you're unlikely to get a bugfix since 5.20 isn't an LTS release. There is debian 12 with Plasma 5.24.
https://repology.org/project/plasma-desktop/versions#debian_11
Comment 2 Nate Graham 2022-07-13 18:55:31 UTC 

*** This bug has been marked as a duplicate of bug 419421 ***