Bug 442667 - Desktop icons start to jump when dragged if they are right-aligned.
Summary: Desktop icons start to jump when dragged if they are right-aligned.
Status: RESOLVED DUPLICATE of bug 359783
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (show other bugs)
Version: 5.22.4
Platform: openSUSE Linux
: NOR normal
Target Milestone: 1.0
Assignee: David Edmundson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-09-18 17:45 UTC by user
Modified: 2021-09-19 10:59 UTC (History)
3 users (show)

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


Attachments
This bug happening. (1.88 MB, video/webm)
2021-09-18 17:45 UTC, user
Details

Note You need to log in before you can comment on or make changes to this bug.
Description user 2021-09-18 17:45:38 UTC
Created attachment 141683 [details]
This bug happening.

SUMMARY
Although I decided to report this bug while using 5.23.80, I can confirm that this also occurs in the plasma stable. That's why I selected "5.22.4"

In the Wayland session, if you set the icons to be arranged in columns and aligned to the right, they will start to make strange and somewhat "random" movements when dragged around the Desktop.

STEPS TO REPRODUCE
1. Right-click the desktop and hit "Configure Desktop and Wallpaper..."
2. Select the section "Icons" and in "arrangement" select "Columns", "Align right". Then click "Apply".
3. Move the icons Around, they will start to jump at random places.

OBSERVED RESULT
When you set Icons to be right-aligned, they often don't really go to the right. If you drag them, they will jump at unexpected places.
EXPECTED RESULT
Icons should be right-aligned when the user set them to be, and they should not jump at random places when dragged.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma:
Operating System: openSUSE Tumbleweed 20210915
KDE Plasma Version: 5.23.80
KDE Frameworks Version: 5.87.0
Qt Version: 5.15.2
Kernel Version: 5.14.2-1-default (64-bit)
Graphics Platform: Wayland
Comment 1 Patrick Silva 2021-09-19 10:59:20 UTC

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