Until this is fixed, I will NOT be using "sleep" mode. I consider this BUG a huge hit to energy saving.
I run dual monitors and have them aligned left-to-right for a single desktop. Some things I observe:
Returning from sleep mode I am greeted with a black desktop within which I can move a cursor and see nothing else.
I hit Control-Alt-F2 and see no change.
I hit Control-Alt-F3 and I am presented with a terminal window and login. I execute "ps uax|grep plasma" and I see the same process ID as before I placed the system into sleep mode.
I hit Control-Alt-F1 and now see what somewhat looks like it might be two acceptable login screens using the background image I specified but the fill surrounding the background image is white, even though black was specified. They are not completely filled out compared to the original login screens, meaning the username and user's avatar image are not presented...just a black hole.
(In 24.04, Control-Alt-F1 resulted in the window where you could observe verbose boot spew, Control-Alt-F2 was the login screen and Control-Alt-F3...F6 (and maybe F7) were virtual terminals.)
I login. Recovery is glacially slow. The areas previously occupied by gkrellm (sticky bit set to cover all virtual desktops) are black and remain so indefinitely. Time and date are not displayed in the taskbar contrary to the default.
Executed "sudo journalctl -b 0 -r" and looked for "crash". Gadzillions of crash statements associated with systemd. No crash statements associated with plasma.
I run dual monitors and have them aligned left-to-right for a single desktop. Some things I observe:
Returning from sleep mode I am greeted with a black desktop within which I can move a cursor and see nothing else.
I hit Control-Alt-F2 and see no change.
I hit Control-Alt-F3 and I am presented with a terminal window and login. I execute "ps uax|grep plasma" and I see the same process ID as before I placed the system into sleep mode.
I hit Control-Alt-F1 and now see what somewhat looks like it might be two acceptable login screens using the background image I specified but the fill surrounding the background image is white, even though black was specified. They are not completely filled out compared to the original login screens, meaning the username and user's avatar image are not presented...just a black hole.
(In 24.04, Control-Alt-F1 resulted in the window where you could observe verbose boot spew, Control-Alt-F2 was the login screen and Control-Alt-F3...F6 (and maybe F7) were virtual terminals.)
I login. Recovery is glacially slow. The areas previously occupied by gkrellm (sticky bit set to cover all virtual desktops) are black and remain so indefinitely. Time and date are not displayed in the taskbar contrary to the default.
Executed "sudo journalctl -b 0 -r" and looked for "crash". Gadzillions of crash statements associated with systemd. No crash statements associated with plasma.
Code:
Sep 23 12:10:46 <hostname> systemd[6172]: drkonqi-coredump-launcher.socket: Unit needs to be started because active unit sockets.target upholds it, but not starting since we tried this too often recently. Will retry later. Sep 23 12:10:46 <hostname> systemd[6172]: drkonqi-coredump-launcher.socket - Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system). [repeat the last statement at least 16 times and the first statement once, every ten seconds]
Comment