https://bugs.kde.org/show_bug.cgi?id=496926
--- Comment #67 from Guido <guido.iod...@gmail.com> --- (In reply to evgeniyharchenko.dev from comment #64) > (In reply to Guido from comment #61) > > Created attachment 183517 [details] > > fix plashashell blackouts after resume or output order change > > Thank you very much for your work! If you'd like, I can create a merge > request and credit you as the author of the fix. However, I will need a > detailed description of the patch in order to include it in the commit > message. Unfortunately, I haven't fully understood the root cause of the bug > yet. I honestly think that this and other bugs stem from kscreen. However, it is not prudent to change it, could cause even greater problems in other cases. It is more prudent, at least for now, to intervene downstream. Here is a description of the patch. Bear in mind that I am not a native English speaker, so if something sounds strange feel free to correct it! screenpool: avoid empty outputOrder and restore focus after screen changes 1. Prevents ScreenPool from applying an empty outputOrder, which may occur on outputOrderChanged() during display suspend/resume. Ignoring the empty list avoids losing screen associations and helps prevent plasmashell from disappearing when the screen wakes up. 2. After screen changes (e.g. when one monitor is switched off and another is switched on), plasmashell may appear on the new screen but not receive input focus or mouse cursor, thus appearing "frozen". This patch imposes the focus and repositions the cursor to the center of the primary screen, resolving the "frozen" desktop state. Both fixes apply only to X11, and are guarded by both 'if HAVE_X11' directive and 'KWindowSystem::isPlatformX11()=true' control condition. -- You are receiving this mail because: You are watching all bug changes.
