Problems with Wayland found after Kubuntu 25.04 install, not problems in X11

I installed Kubuntu 25.04 because of plasma stability issues in Kubuntu 24.04. I will very likely file a bug report but wanted to bring this to your attention.

I have witnessed the following problems with Wayland in Kubuntu 25.04.
These are not problems with X11 in Kubuntu 25.04.

  1. I run multiple instances of Konsole. Inside each Konsole I run multiple tabs. When I login with Wayland, I now see only one instance of Konsole regardless of the pre-logout greater than 1 Konsole quantity and that Konsole is not showing any tabs, nor does it show any directory location I had been working in prior to logout. This is not an issue in X11.
  2. I place my system into sleep mode. Waking from sleep mode is glacially slow and does not fully recover. 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 hit Control-Alt-F1 and now see two login screens using the background image I specified. The login screens are not completely filled out compared to the original login screens, meaning the username and user avatar image are not presented…just a black hole. Clearly, waking from sleep mode should either move to the Control-Alt-F1 screen instead of the Control-Alt-F2 screen, or Wayland should default to use Control-Alt-F2 instead of Control-Alt-F1 for login, similar to X11.
    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. This is not an issue with X11.

Sep 23 12:10:46 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 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, and do so every ten seconds]

  1. Running “emacs -fg yellow -bg black -cr red -geometry 80x48 $@ &” (emacs-pgtk) inside a shellscript. I cannot change the size of the resulting window by placing my mouse cursor on any border or lower or upper corners since the resulting motion is limited to a “smidgen”…a highly technical term. This is not an issue with X11.

Hardware:

CPU: AMD Ryzen 9 9900X
GPU: NVIDIA GeForce RTX 5070
Mboard: MSI PRO B650-VC WIFI III
RAM: 32 GB DDR5
2 x 2 TB SSD WD_BLACK SN850X HS 2000GB w/ heatsink
Dual identical resolution monitors used side-by-side forming single desktop.