Bug 490516 - Corrupted image of folder area if a drag-drop performed
Summary: Corrupted image of folder area if a drag-drop performed
Status: RESOLVED DUPLICATE of bug 490183
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 24.05.2
Platform: Neon Linux
: NOR grave
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-07-19 17:58 UTC by Dm
Modified: 2024-07-19 19:20 UTC (History)
1 user (show)

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


Attachments
broken image in files area (34.48 KB, image/webp)
2024-07-19 17:58 UTC, Dm
Details
broken image in files area 2 (70.01 KB, image/webp)
2024-07-19 17:58 UTC, Dm
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Dm 2024-07-19 17:58:41 UTC
Created attachment 171796 [details]
broken image in files area

SUMMARY
If there are multiple tabs in Dolphin and a file is moved to antoher tab, the image "braeks" after scroll
If a file is dragged to another window, "reciever" window also is buggy
If a file is dragged to a falder in sidebar with bookmarks, the area will be buggy
If any tab is closed after bug appears, Dolphin is also closed

STEPS TO REPRODUCE
1. Open Dolphin
2. Make 2 tabsor more
3. Move a file to another tab
4. Scroll

SOFTWARE/OS VERSIONS
Operating System: KDE neon 6.0
KDE Plasma Version: 6.1.3
KDE Frameworks Version: 6.4.0
Qt Version: 6.7.0
Kernel Version: 6.5.0-44-generic (64-bit)
Graphics Platform: Wayland
Processors: 6 × Intel® Core™ i7-8750H CPU @ 2.20GHz
Memory: 15.3 ГиБ of RAM
Graphics Processor: Mesa Intel® UHD Graphics 630
Manufacturer: Dell Inc.
Product Name: XPS 15 9570
Comment 1 Dm 2024-07-19 17:58:59 UTC
Created attachment 171797 [details]
broken image in files area 2
Comment 2 Dm 2024-07-19 18:02:37 UTC
Every attempt to drag-drop a file causes the bug
Comment 3 Dm 2024-07-19 18:08:29 UTC
Checked for x11, the bug is only in Wayland session
Comment 4 Antonio Rojas 2024-07-19 19:20:51 UTC

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