https://bugs.kde.org/show_bug.cgi?id=475605
--- Comment #37 from Victor Ryzhykh <victorr2...@yandex.ru> --- (In reply to holyzolly from comment #35) > I too have been affected by a probably different bug (no signal too monitor). > As a result, I changed from auto hybrid-sleep to auto hibernate. Dunno maybe > btrfs issue, but I'm using a swap partition. > So below is now after hibernate but used to be after sleep mode too: > > Ok ok so I too have possibly been affected by this bug as well. > 0. I however see the log screen where I use a slideshow of pictures as > background. These pictures are seen but in the middle password field or my > username don't show. Cursor however is active and in the middle where the pw > field is supposed to show, the arrow of the cursor changed to a pipe so I > know where to activate the not-shown pw field. So I left click there, type > my pw and hit enter. That way I know I have unlocked the session which > however is still visually covered with the lock screen. In the middle the > cursor arrow does not change to pipe now. > My workaround then is: > 1./0b. Wait a few minutes, up to 6-7. > or which I mostly after 0. > 2. Change into TTY3 and back. If I get the black screen with only cursor > like the OP: > 2b. Change into TTY3 and log into it and look at htop, hit Q to quit it, > look at nvtop (not installed by default) and hit Q and then I switch back to > graphical interface from TTY3 (CTRL+ALT+F2). In either of the monitors shown > in TTY you see the lockscreen process or plasmashell above 80%. For me this > eventually changes after waiting a while. If I still get the black screen > with only cursor like the OP. > 2c. Repeat 2b > > Might be the switching to TTY and back triggers the graphics to be restarted > faster. > At least I get my session back and the info message in systray: Your > graphics had to be restarted due to a graphical issue (or a wording the > like). And here everything works again as expected, full GUI. (Apart from > some screen tearing when switching between Activities or in FF Yt videos, > which is why I usually log out and back in in these restored/unlocked > sessions). > > Everyone is welcome to translate my complicatedly described workaround into > fewer, better organized sentences :) In general, sometimes simply turning off and turning on the monitor using the monitor's power button helps. -- You are receiving this mail because: You are watching all bug changes.
