Summary: | Desktop icons being mixed sometimes after a reboot | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | Dimitri <dimitri.code> |
Component: | Desktop icons & Folder View widget | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | dimitri.code, hein, kdedev, n2thew, nate |
Priority: | NOR | ||
Version: | master | ||
Target Milestone: | 1.0 | ||
Platform: | Neon | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
Desktop before one of the bad reboot
Desktop after one of the bad reboot, mixed icons |
Description
Dimitri
2024-05-03 20:03:30 UTC
Created attachment 169157 [details]
Desktop before one of the bad reboot
As the bug started annoying my with all the time it had happen to me, I wanted to show it clearly.
I have prepared my desktop for this bug by putting colored folder in a clear layout. With that layout, the way icons are moved would (I was thinking) be more understandable.
It remained like this for a week without any display change (no screen plug or unplugged from the laptop, no display setting changed, and even no icons being added to the desktop) until the bug appeared.
Created attachment 169159 [details]
Desktop after one of the bad reboot, mixed icons
Here is what I got after one week : icons mixed.
I am not really sure if a small update happen just before that but if it was the case it was an extremely small update (I know it's less than 5 system packets).
I have used, boot and shutdown, my computer every days. Nothing has suggested that it was this day that the bug reappeared.
It may be hard to fix. Sorry for that. But I thought it was better to report it anyway. Unfortunately this is a known issue at this point in time. The positioning code is just super buggy and probably needs a total rewrite, with all behaviors guarded by autotests. (In reply to Nate Graham from comment #4) > Unfortunately this is a known issue at this point in time. The positioning > code is just super buggy and probably needs a total rewrite, with all > behaviors guarded by autotests. Ok, thanks for the precision. There are multiple bug reports about this behavior. I'm using 468546 as the main bug report. *** This bug has been marked as a duplicate of bug 468546 *** |