SUMMARY Hello. I'm using Fedora 38 + KDE 5.27.4. I am coding in full screen. Sometimes when I come to the desktop, the icons are fine as in the 1st picture. Sometimes the icons are lined up to the left as in the 2nd picture. I couldn't catch any error log because I don't know what time this error occurred while writing code STEPS TO REPRODUCE 1. Use any app full screen 2. Error occurs or not SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 38 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 IMAGES https://cdn.mtaha.dev/1.png https://cdn.mtaha.dev/2.png
The same problem reoccurred today and I got journalctl output https://cdn.mtaha.dev/log2.txt
A few questions: 1. Do you have your icons configured to arrange "top-to-bottom" and "align left"? 2. Is there any chance that any of the full screen apps you're using are changing the resolution of the screen? 3. If you make your panel auto-hide for a while for testing purposes, does the problem stop happening?
(In reply to Nate Graham from comment #2) > A few questions: > 1. Do you have your icons configured to arrange "top-to-bottom" and "align > left"? > 2. Is there any chance that any of the full screen apps you're using are > changing the resolution of the screen? > 3. If you make your panel auto-hide for a while for testing purposes, does > the problem stop happening? 1- Yes. The same error occurs in both types 2- No 3- No
I got the kde 5.27.5 update a while ago, but the same problem persists.
Thanks. Does the issue stop occurring if you change the arrangement setting from "Top to bottom" to "Left to right"?
(In reply to Nate Graham from comment #5) > Thanks. Does the issue stop occurring if you change the arrangement setting > from "Top to bottom" to "Left to right"? No, the icons are lined up from left to right (in a random time)
Darn.
Lowering priority for now since unfortunately this isn't actionable at the moment. We need to schedule a rewrite of some of the flaky code here.
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 ***