Bug 492003

Summary: Desktop icons sometimes get scrambled on plasmashell startup
Product: [Plasma] plasmashell Reporter: EpicTux123 <EpicTux123>
Component: FolderAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED DUPLICATE    
Severity: major CC: hein, idarktemplar, justin, kde, linux, nate, notmart
Priority: NOR    
Version: 6.2.0   
Target Milestone: 1.0   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description EpicTux123 2024-08-21 20:10:32 UTC
This is the same issue as other issues (see "See Also"). The other issues were closed as fixed or duplicate, but the bug still exists.
Comment 1 EpicTux123 2024-08-24 19:08:34 UTC
Relevant information from my system:

Fedora Linux 40
KDE Plasma 6.1.4
KDE Frameworks 6.5.0
Qt 6.7.2
Kernel: 6.10.6-200.fc40.x86_64 (64-bit)
X11

NVIDIA proprietary drivers 555.58.02

This has been happening since KDE version 5 (before Fedora upgraded to 6 in version 40). This has also been happening with prior versions of everything (kernel, Qt etc.). I don't use Wayland due to some missing features ATM, so I cannot say if this also happens on Wayland.

Sometimes when I boot up my PC the screen on SDDM or afterwards on plasmashell is blurry or has black bars. Turning off the monitor and turning it back on fixes the issue (I believe this is an X11 issue, as it has not happened for me on Wayland the few times I used it).

One thing I noticed is that when desktop icons get scrambled for a brief moment, sometimes, the horizontal scroll at the bottom of the screen appears (to scroll the desktop to see further icons). I believe that if this option was disabled maybe the problem related to icons scrambling would be fixed, because visually it seems the icons try to expand to the other side of the desktop (scrollbar) as if there was more than one monitor or as if I had put the icons further way to make the scrollbar appear.
Comment 2 Akseli Lahtinen 2024-08-30 12:03:33 UTC
*** Bug 492402 has been marked as a duplicate of this bug. ***
Comment 3 Justin Zobel 2024-09-02 12:33:40 UTC
Does the icon scrambling also occur on Wayland?
Comment 4 EpicTux123 2024-09-02 16:29:46 UTC
I don't use Wayland, so I don't know.

Even on X11, the bug is not consistent/reproducible all the time. Occurs randomly.
Comment 5 Marco Martin 2024-09-30 14:41:54 UTC
*** Bug 468546 has been marked as a duplicate of this bug. ***
Comment 6 Marco Martin 2024-09-30 14:44:12 UTC

*** This bug has been marked as a duplicate of bug 468546 ***
Comment 7 EpicTux123 2024-10-14 16:08:00 UTC
Reopening because https://bugs.kde.org/show_bug.cgi?id=468546 was closed.

Bug still persists in Plasma 6.2.0.
Comment 8 EpicTux123 2024-10-17 19:34:52 UTC
I would say that after the fix in Plasma 6.2.0 I am having this bug more frequently, but I am not sure.
Comment 9 Nate Graham 2024-10-22 16:21:11 UTC
I need you to describe the issue you're seeing in precise technical terms. "This is the same issue as other issues" is not helpful because those bug reports are each about subtly different things. Can you please describe *exactly* the icon positioning but that *you* are experiencing? Thanks!
Comment 10 EpicTux123 2024-10-22 17:05:50 UTC
For me, what happens is that icons are, well, scrambled on plasmashell start-up. They appear in random places instead of being in the last location. The entire desktop is scrambled.

Normally, when it happens, I can see the scroll bar in the bottom for a brief second (as if I was trying to put icons beyond the desktop limit).
It seems that, for what I can tell, it struggles to correctly calculate the space needed for the icons after plasma shell (the task bar) is spawned, so it (re-)uses previous values and ends up being wrong.

I think that it gets the info from the desktop icons' positions before plasmashell starts, and results in the icons being in the wrong place.
Comment 11 Nate Graham 2024-10-22 18:17:45 UTC
Aha, yes, that makes sense. It meant this is Bug 458007, which is actually not really a bug per se, but rather the lack of a feature to consider this exact situation. We'll get it fixed eventually.

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