SUMMARY After boot I've got bottom part of the screen black. It's a secondary screen and it's rotated 90°. I think this is the culprit because wallpaper looks like it if were applied to horizontally oriented screen. Maybe some kind of data race, where display code can be applied after shell initializes environment. And doesn't check later if it's changed. STEPS TO REPRODUCE 1. Boot OBSERVED RESULT Screenshot in attachment. Black half hides drag selection but cursor and windows go over it. Wallpaper seem to be correct but cropped as if screen weren't rotated at all. EXPECTED RESULT Correctly oriented screen. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.3.5 KDE Frameworks Version: 6.14.0 Qt Version: 6.9.0 Kernel Version: 6.14.6-arch1-1 (64-bit) Graphics Platform: X11 Graphics Processor 1: AMD Radeon RX Vega M GL Graphics Graphics Processor 2: Mesa Intel® HD Graphics 630
Created attachment 181594 [details] secondary screen
Can you open Display & Monitor section in System Settings and check the orientation setting for your monitor? Switch it to vertical. Is this your first boot or was it working before and got switched to horizontal?
Some questions: 1. Is *anything* shown on the secondary screen that's black? Part of the wallpaper from another screen, for example? 2. If you right-click on the black area, do you see a context menu? 3. If you drag a window over to the black area, does it remain visible and interactive? 4. Does any of this happen if you log into a Wayland session on the same machine? Or does it only happen in an X11 session?
(In reply to Filip from comment #2) > Can you open Display & Monitor section in System Settings and check the > orientation setting for your monitor? Switch it to vertical. It is switched to vertical (and was before too). (In reply to Filip from comment #2) > Is this your first boot or was it working before and got switched to > horizontal? Not the first. It's working system that I use on a regular basis. It's not switched to horizontal, it is vertical. But wallpaper and some other stuff (like box selection) thinks it's horizontal. (In reply to Nate Graham from comment #3) > Some questions: > 1. Is *anything* shown on the secondary screen that's black? Part of the > wallpaper from another screen, for example? > 2. If you right-click on the black area, do you see a context menu? > 3. If you drag a window over to the black area, does it remain visible and > interactive? > 4. Does any of this happen if you log into a Wayland session on the same > machine? Or does it only happen in an X11 session? 1. Don't really understand the question. I see what's shown on screenshot. Top part shows wallpaper, bottom part is black. 2. No 3. Yes, it does 4. Can't say, don't use wayland as it has issues more severe than this one
On X11, if you restart plasmashell with `systemctl restart --user plasma-plasmashell.service`, does the issue disappear? Can you try the Wayland session for debugging purposes, to see if the issue is there as well?
(In reply to Nate Graham from comment #5) > On X11, if you restart plasmashell with `systemctl restart --user > plasma-plasmashell.service`, does the issue disappear? Sadly I already turned off PC at this point. After boot there's no issue so I think restarting plasmashell would've helped too. However, this isn't first time I see this. It looks like code responsible for configuring layouts and plasmashell code that uses layout information are not in sync with each other. And in very rare occasions layout configuration (rotation in my case) happens after plasmashell configured desktop containment.
(In reply to Nate Graham from comment #5) > Can you try the Wayland session for debugging purposes, to see if the issue > is there as well? If it is indeed some sort of data race (because after reboot everything is fine), the fact that issue isn't present at the moment doesn't tell anything useful. I'll try to change session when I see this again but what'd happen is likely just the fact of changing session (either to wayland or back to x11) would fix issue on its own.
I asked because I strongly suspect it never happens on Wayland, because the Wayland and X11 sessions handle mixed-DPI multi-monitor setups very differently. Mostly, on Wayland they're handled well and on X11 they're handled badly. :)
(In reply to Nate Graham from comment #8) > I asked because I strongly suspect it never happens on Wayland, because the > Wayland and X11 sessions handle mixed-DPI multi-monitor setups very > differently. Mostly, on Wayland they're handled well and on X11 they're > handled badly. :) I understand that. But since it happens only from time to time, makes this kind of test inconclusive. For what it worth, I use same DPI on X11 (not sure if it's even possible to change scale per monitor on X11 though). Layout changes include scale (125%) and secondary screen rotation.
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone!
Haven't had this issue yet, so can't really check it on both sessions.
(In reply to Nate Graham from comment #5) > Can you try the Wayland session for debugging purposes, to see if the issue is there as well? Caught this bug again today and tried to login into wayland session right after that. Screen is okay as expected but there's huge BUT: When I re-login into X11 back, it's all good again too. So from my side it's impossible to say whether or not it's X11 only because it is random and lasts until plasma restart. > On X11, if you restart plasmashell with `systemctl restart --user plasma-plasmashell.service`, does the issue disappear? Haven't tried this one yet.
Do you use multiple Activities on your device, by chance? The end result of this issue sounds like the result of https://bugs.kde.org/show_bug.cgi?id=495762 , so I figured it was worth a check if there was a connection. Thanks!
(In reply to John Kizer from comment #13) > Do you use multiple Activities on your device, by chance? I do
Thanks - when this issue occurs, does it occur on all Activities, or is the default Activity OK? Trying to figure out if this is actually the same underlying issue as https://bugs.kde.org/show_bug.cgi?id=495762 :-)
(In reply to John Kizer from comment #15) > when this issue occurs, does it occur on all Activities, or is the default Activity OK? Not OK, every activity is broken the same way until re-login.
Can't really add anything new to what's already here.
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.