Bug 510139 - File selector in the pop-up windows on Desktop is broken
Summary: File selector in the pop-up windows on Desktop is broken
Status: RESOLVED DUPLICATE of bug 468359
Alias: None
Product: plasmashell
Classification: Plasma
Component: Desktop icons & Folder View widget (other bugs)
Version First Reported In: 6.4.5
Platform: EndeavourOS Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-10-01 20:00 UTC by Alex Sh
Modified: 2025-10-02 08:46 UTC (History)
3 users (show)

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

Attachments
Bug showcase (1.54 MB, video/mp4)
2025-10-01 20:00 UTC, Alex Sh 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Alex Sh 2025-10-01 20:00:42 UTC 
Created attachment 185432 [details]
Bug showcase

SUMMARY
File selector (Ig it's called 'the rubberband selector' in the pop-up windows for Folders on Desktop (Folder View mode) is broken: selector is showing near the scroll bar, and it's impossible to select something

STEPS TO REPRODUCE
1. Create a folder in Desktop directory
2. Add some files there
3. Enable the «Folder View» mode in Desktop Settings
4. Go to Desktop and find the folder; click on the arrow/plus icon 

OBSERVED RESULT
We can't select files in pop-up using rubberband selector and it's shown near the scrollbar

EXPECTED RESULT
We can select files in pop-up using rubberband selector that is shown in the right place

SOFTWARE/OS VERSIONS

Linux/KDE Plasma: 

Operating System: EndeavourOS 
KDE Plasma Version: 6.4.5
KDE Frameworks Version: 6.18.0
Qt Version: 6.9.2
Kernel Version: 6.16.8-arch3-1 (64-bit)
Graphics Platform: X11
Processors: 12 × 12th Gen Intel® Core™ i5-12450H
Memory: 8 GiB of RAM (7.5 GiB usable)
Graphics Processor: Intel® Graphics
Manufacturer: HONOR
Product Name: BRN-FXXC
System Version: M1040

ADDITIONAL INFORMATION
Screen recording is attached
Comment 1 Akseli Lahtinen 2025-10-02 08:46:10 UTC 

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