[kde] [Bug 509849] New: Problems with Wayland found after Kubuntu 25.04 install, not problems in X11

[bugzilla_noreply at kde.org]

https://bugs.kde.org/show_bug.cgi?id=509849

            Bug ID: 509849
           Summary: Problems with Wayland found after Kubuntu 25.04
                    install, not problems in X11
    Classification: I don't know
           Product: kde
      Version First unspecified
       Reported In:
          Platform: Kubuntu
                OS: Linux
            Status: REPORTED
          Severity: major
          Priority: NOR
         Component: general
          Assignee: unassigned-bugs at kde.org
          Reporter: steve_garnier at yahoo.com
  Target Milestone: ---

SUMMARY

I have found poor behavior of Wayland when compared to X11 in the areas of
post-sleep wakeup restoration, saving Konsole tab behavior between login
sessions, and the inability to resize emacs windows.

STEPS TO REPRODUCE

System should be a fresh install that has never run X11.  

1.  Problem with respect to Konsole usage. 
1.a.  Ensure that System Settings > Session > "On login, launch apps that were
open: [*] On last logout" is selected.  
1.b.  Now start multiple instances of Konsole and force multiple tabs in each
Konsole window by using Control-Shift-T.  
1.c.  Within each tab in Konsole, "cd <different directory of choice>".  
1.d.  Now logout of Wayland and then login with Wayland.  When I do this 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.  
Expected Result:  Multiple instances of Konsole should be observed and each
Konsole should contain multiple tabs at directory positions that were
previously set.  This is not an issue with X11.  

2.  Problem with respect to Wayland sleep and awakening. 
2.a.  Before I run what follows, I go to System Settings > Appearance & Style >
Colors & Themes > Login Screen (SDDM) and I choose "Kubuntu" and enter whatever
image I want into "Change Background".  
2.b.  I also start gkrellm and set the sticky bit.  (This is done by
right-clicking on the gkrellm titlebar, and in the resulting popup selecting
"General", the "Properties" tab and then selecting "Set sticky state", then
click "Apply" or "OK".)  Leave gkrellm running on the display.  
2.c.  Next place the system running Wayland into sleep mode.  
2.d.  Wake from sleep mode.  
Observations: 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 virtual 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 instead of an avatar image.  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. 
2.e.  Login. 
Observations:  Recovery of the desktop display 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.  I opened Konsole and executed “sudo
journalctl -b 0 -r” and looked for “crash”. Gadzillions of crash statements
associated with systemd. This is not an issue with X11.
>From the journalctl output: 
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).
[repeats the last statement at least 16 times and the first statement once, and
does so every ten seconds] 
Expected Result: Very fast waking and recovery from sleep mode.  This is not an
issue with X11. 

3.  Problem with respect to emacs window resizing. 
3.a.  Within Wayland, open a Konsole terminal and enter "emacs -fg yellow -bg
black -cr red -geometry 80x40 $@ &".  This is using the emacs-pgtk package.  
3.b.  Attempt to change the size of the resulting window by placing the mouse
cursor on any border or corner.  Attempt this several times from multiple
borders and corners.  
Observation:  The resulting motion is limited to a "smidgen"...a highly
technical term. ;-)  
Expected Result:  The emacs window should easily resize in all directions
dictated by mouse manipulation.  This is not an issue with X11.  

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Kubuntu 25.04, Linux  6.14.0-32-generic #32-Ubuntu SMP
PREEMPT_DYNAMIC 
KDE Plasma Version: 6.3.4
KDE Frameworks Version: 6.12.0 
Qt Version: 6.8.3

ADDITIONAL INFORMATION
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.

-- 
You are receiving this mail because:
You are the assignee for the bug.