SUMMARY Randomly whenever the display turns off to go to sleep, I turn it back on to see that the Task Manager has moved to the top. When I try to move it down by right clicking, only right clicking on the bottom where the Task Manager should be opens the edit option. Additionally, when I tried to move it back down, the only options are up, left and right. I have to move it up and then down again to get it to go back to where I want it to be. I can't find any way to reliably reproduce it because it just happens randomly when the display goes to sleep. I tried "systemctl suspend" to see if this could reproduce it, but it doesn't work. OBSERVED RESULT Task Manager on top of screen when it should be on the bottom. Fully interactible, but I can't right click it unless I go to the bottom where it should be. EXPECTED RESULT Task Manager staying on bottom of screen where it should be. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION Running on X11
OKAY, so I found out how to reproduce it, and found something new. So whenever I idle and the screen turns off, I move my mouse or hit my keyboard to turn the screen back on. When I do, not only is the task manager on the top, but the screen is stuck at 640x480 until I turn my monitor off and on again. Even after it turns on again, I have to manually move the task manager as described in the initial post. I also forgot to mention that my GPU is an Nvidia 1050 ti, and while that may explain the resolution issue, it doesn't explain the task manager.
Sounds a *bit* like Bug 483275, maybe a similar issue. I suspect the panel moving is a symptom of the resolution change problem, and fixing that will fix the panel issue too. What physical port is the monitor plugged into? Does the issue happen if you plug it into a different port?
The 640x480 issue does sound like bug 483275. If you can trigger it again, please follow up on that in there with the drm_info output as mentioned in bug 483275.
*** This bug has been marked as a duplicate of bug 483275 ***