Bug 477643

Summary:	Plasma 5.27.80 got stuck on the splash screen in VMs with kwin_wayland errors
Product:	[Plasma] kwin	Reporter:	Matt Fagnani <matt.fagnani>
Component:	wayland-generic	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED FIXED
Severity:	normal	CC:	nate, vlad.zahorodnii, xaver.hugl
Priority:	NOR	Keywords:	qt6
Version First Reported In:	5.27.80
Target Milestone:	---
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	Journal for a boot when Plasma 5.27.80 got stuck on the splash screen in a VM using the llvmpipe driver

Description Matt Fagnani 2023-11-27 22:37:55 UTC

Created attachment 163555 [details]
Journal for a boot when Plasma 5.27.80 got stuck on the splash screen in a VM using the llvmpipe driver

SUMMARY

I booted the Fedora Rawhide/40 KDE Plasma live image Fedora-KDE-Live-x86_64-Rawhide-20231127.n.0.iso in GNOME Boxes QEMU/KVM VMs in a Fedora 39 KDE Plasma host. Fedora-KDE-Live-x86_64-Rawhide-20231127.n.0.iso is the first Fedora Rawhide image using Plasma 5.27.80. Plasma 5.27.80 got stuck on the splash screen which was shown for at least 2 minutes. The cursor was still movable on the splash screen, and it changed to a hand shape when it was over the centre of the screen in some places where Plasma Welcome was later shown. When the VM had 3D acceleration disabled using the llvmpipe mesa 23.3.0-rc2 driver, the spinner on the splash screen spun for a few seconds then froze. When the VM had 3D acceleration enabled using the virgl mesa driver, the spinner on the splash screen spun for 2 seconds then disappeared.

I changed to VT2 using the keyboard menu in the top bar of GNOME Boxes and selecting Ctrl+Alt+F2. When I changed back to VT1, Plasma was shown with the Plasma Welcome program open. There were some kwin_wayland errors in the journal when it was starting.

Nov 27 16:54:38 kwin_wayland[1683]: kwin_wayland_drm: Atomic Mode Setting disabled on GPU /dev/dri/card1 because of cursor offset issues in virtual machines
Nov 27 16:54:39 kwin_wayland[1683]: kwin_core: Parse error in tiles configuration for monitor "92e842d7-5928-5c43-884a-4912e7cc82ed" : "illegal value" Creating default setup
Nov 27 16:54:41 kwin_wayland[1683]: OpenGL vendor string:                   Mesa
Nov 27 16:54:41 kwin_wayland[1683]: OpenGL renderer string:                 llvmpipe (LLVM 17.0.4, 256 bits)
Nov 27 16:54:41 kwin_wayland[1683]: OpenGL version string:                  4.5 (Core Profile) Mesa 23.3.0-rc2
Nov 27 16:54:41 kwin_wayland[1683]: OpenGL shading language version string: 4.50
Nov 27 16:54:41 kwin_wayland[1683]: Driver:                                 LLVMpipe
Nov 27 16:54:41 kwin_wayland[1683]: GPU class:                              Unknown
Nov 27 16:54:41 kwin_wayland[1683]: OpenGL version:                         4.5
Nov 27 16:54:41 kwin_wayland[1683]: GLSL version:                           4.50
Nov 27 16:54:41 kwin_wayland[1683]: Mesa version:                           23.3
Nov 27 16:54:41 kwin_wayland[1683]: Requires strict binding:                no
Nov 27 16:54:41 kwin_wayland[1683]: Virtual Machine:                        no
Nov 27 16:54:41 kwin_wayland[1683]: Timer query support:                    yes
Nov 27 16:54:41 kwin_wayland[1683]: kwin_core: Parse error in tiles configuration for monitor "4d031bd2-ddeb-57b0-97bb-ac4d7cdf2819" : "illegal value" Creating default setup
Nov 27 16:54:42 kwin_wayland[1683]: kwin_wayland_drm: Setting gamma failed! Function not implemented
Nov 27 16:54:43 ksplashqml[1691]: libEGL warning: egl: failed to create dri2 screen
Nov 27 16:54:43 kwin_wayland_wrapper[1775]: (WW) Option "-listen" for file descriptors is deprecated
Nov 27 16:54:43 kwin_wayland_wrapper[1775]: Please use "-listenfd" instead.
Nov 27 16:54:43 kwin_wayland_wrapper[1775]: (WW) Option "-listen" for file descriptors is deprecated
Nov 27 16:54:43 kwin_wayland_wrapper[1775]: Please use "-listenfd" instead.
Nov 27 16:54:43 kwin_wayland_wrapper[1775]: libEGL warning: egl: failed to create dri2 screen
Nov 27 16:54:43 kwin_wayland_wrapper[1775]: libEGL warning: egl: failed to create dri2 screen
Nov 27 16:54:43 kwin_wayland_wrapper[1775]: libEGL warning: NEEDS EXTENSION: falling back to kms_swrast
Nov 27 16:54:43 kwin_wayland_wrapper[1775]: Refusing to try glamor on llvmpipe
Nov 27 16:54:43 kwin_wayland_wrapper[1775]: EGL setup failed, disabling glamor
Nov 27 16:54:43 kwin_wayland_wrapper[1775]: Failed to initialize glamor, falling back to sw
Nov 27 16:54:43 kwin_wayland_wrapper[1785]: The XKEYBOARD keymap compiler (xkbcomp) reports:
Nov 27 16:54:43 kwin_wayland_wrapper[1785]: > Warning:          Could not resolve keysym XF86CameraAccessEnable
Nov 27 16:54:43 kwin_wayland_wrapper[1785]: > Warning:          Could not resolve keysym XF86CameraAccessDisable
Nov 27 16:54:43 kwin_wayland_wrapper[1785]: > Warning:          Could not resolve keysym XF86CameraAccessToggle
Nov 27 16:54:43 kwin_wayland_wrapper[1785]: > Warning:          Could not resolve keysym XF86NextElement
Nov 27 16:54:43 kwin_wayland_wrapper[1785]: > Warning:          Could not resolve keysym XF86PreviousElement
Nov 27 16:54:43 kwin_wayland_wrapper[1785]: > Warning:          Could not resolve keysym XF86AutopilotEngageToggle
Nov 27 16:54:43 kwin_wayland_wrapper[1785]: > Warning:          Could not resolve keysym XF86MarkWaypoint
Nov 27 16:54:43 kwin_wayland_wrapper[1785]: > Warning:          Could not resolve keysym XF86Sos
Nov 27 16:54:43 kwin_wayland_wrapper[1785]: > Warning:          Could not resolve keysym XF86NavChart
Nov 27 16:54:43 kwin_wayland_wrapper[1785]: > Warning:          Could not resolve keysym XF86FishingChart
Nov 27 16:54:43 kwin_wayland_wrapper[1785]: > Warning:          Could not resolve keysym XF86SingleRangeRadar
Nov 27 16:54:43 kwin_wayland_wrapper[1785]: > Warning:          Could not resolve keysym XF86DualRangeRadar
Nov 27 16:54:43 kwin_wayland_wrapper[1785]: > Warning:          Could not resolve keysym XF86RadarOverlay
Nov 27 16:54:43 kwin_wayland_wrapper[1785]: > Warning:          Could not resolve keysym XF86TraditionalSonar
Nov 27 16:54:43 kwin_wayland_wrapper[1785]: > Warning:          Could not resolve keysym XF86ClearvuSonar
Nov 27 16:54:43 kwin_wayland_wrapper[1785]: > Warning:          Could not resolve keysym XF86SidevuSonar
Nov 27 16:54:43 kwin_wayland_wrapper[1785]: > Warning:          Could not resolve keysym XF86NavInfo
Nov 27 16:54:43 kwin_wayland_wrapper[1785]: Errors from xkbcomp are not fatal to the X server
Nov 27 16:54:43 kwin_wayland[1683]: kf.windowsystem: static bool KX11Extras::mapViewport() may only be used on X11
Nov 27 16:54:43 kwin_wayland_wrapper[1789]: The XKEYBOARD keymap compiler (xkbcomp) reports:
Nov 27 16:54:43 kwin_wayland_wrapper[1789]: > Warning:          Unsupported maximum keycode 708, clipping.
Nov 27 16:54:43 kwin_wayland_wrapper[1789]: >                   X11 cannot support keycodes above 255.
Nov 27 16:54:43 kwin_wayland_wrapper[1789]: > Warning:          Could not resolve keysym XF86CameraAccessEnable
Nov 27 16:54:43 kwin_wayland_wrapper[1789]: > Warning:          Could not resolve keysym XF86CameraAccessDisable
Nov 27 16:54:43 kwin_wayland_wrapper[1789]: > Warning:          Could not resolve keysym XF86CameraAccessToggle
Nov 27 16:54:43 kwin_wayland_wrapper[1789]: > Warning:          Could not resolve keysym XF86NextElement
Nov 27 16:54:43 kwin_wayland_wrapper[1789]: > Warning:          Could not resolve keysym XF86PreviousElement
Nov 27 16:54:43 kwin_wayland_wrapper[1789]: > Warning:          Could not resolve keysym XF86AutopilotEngageToggle
Nov 27 16:54:43 kwin_wayland_wrapper[1789]: > Warning:          Could not resolve keysym XF86MarkWaypoint
Nov 27 16:54:43 kwin_wayland_wrapper[1789]: > Warning:          Could not resolve keysym XF86Sos
Nov 27 16:54:43 kwin_wayland_wrapper[1789]: > Warning:          Could not resolve keysym XF86NavChart
Nov 27 16:54:43 kwin_wayland_wrapper[1789]: > Warning:          Could not resolve keysym XF86FishingChart
Nov 27 16:54:43 kwin_wayland_wrapper[1789]: > Warning:          Could not resolve keysym XF86SingleRangeRadar
Nov 27 16:54:43 kwin_wayland_wrapper[1789]: > Warning:          Could not resolve keysym XF86DualRangeRadar
Nov 27 16:54:43 kwin_wayland_wrapper[1789]: > Warning:          Could not resolve keysym XF86RadarOverlay
Nov 27 16:54:43 kwin_wayland_wrapper[1789]: > Warning:          Could not resolve keysym XF86TraditionalSonar
Nov 27 16:54:43 kwin_wayland_wrapper[1789]: > Warning:          Could not resolve keysym XF86ClearvuSonar
Nov 27 16:54:43 kwin_wayland_wrapper[1789]: > Warning:          Could not resolve keysym XF86SidevuSonar
Nov 27 16:54:43 kwin_wayland_wrapper[1789]: > Warning:          Could not resolve keysym XF86NavInfo
Nov 27 16:54:43 kwin_wayland_wrapper[1789]: Errors from xkbcomp are not fatal to the X server
Nov 27 16:54:44 systemd[1411]: Started plasma-kcminit.service - KDE Config Module Initialization.
Nov 27 16:54:44 systemd[1411]: Starting plasma-ksmserver.service - KDE Session Management Server...
Nov 27 16:54:44 systemd[1411]: Started plasma-kwallet-pam.service - Unlock kwallet from pam credentials.
Nov 27 16:54:44 systemd[1411]: Starting plasma-kded6.service - KDE Daemon 6...
Nov 27 16:54:44 kded6[1804]: libEGL warning: egl: failed to create dri2 screen
Nov 27 16:54:44 ksplashqml[1691]: MESA: error: ZINK: failed to choose pdev
Nov 27 16:54:44 ksplashqml[1691]: libEGL warning: egl: failed to create dri2 screen
Nov 27 16:54:44 kded6[1804]: MESA: error: ZINK: failed to choose pdev
Nov 27 16:54:44 kded6[1804]: libEGL warning: egl: failed to create dri2 screen
Nov 27 16:54:45 ksmserver[1802]: MESA: error: ZINK: failed to choose pdev
Nov 27 16:54:45 ksmserver[1802]: glx: failed to create drisw screen
Nov 27 16:54:45 ksmserver[1802]: failed to load driver: zink

The journal showed the following kwin_wayland errors repeated many times while the splash screen was shown.

Nov 27 16:54:50 kwin_wayland[1683]: kwin_wayland_drm: Page flip failed: No space left on device
Nov 27 16:54:50 kwin_wayland[1683]: kwin_wayland_drm: Presentation failed! No space left on device

There were various other errors shown in the journal. I'm attaching the journal for a VM boot with the llvmpipe driver.

This problem happened 4/4 times when I booted Fedora-KDE-Live-x86_64-Rawhide-20231127.n.0.iso in VMs with the llvmpipe and virgl drivers. This problem didn't happen when I booted this image on bare metal from a flash drive. The radeonsi mesa driver and amdgpu kernel driver were used in that case. This problem didn't happen when booting previous Fedora Rawhide images with Plasma 5.27.9 in VMs. The problem might be related to the Plasma 5.27.80 update.

STEPS TO REPRODUCE
1. Boot a Fedora 39 KDE Plasma installation updated to 2023-11-27 with updates-testing enabled
2. Log in to Plasma 5.27.9 on Wayland
3. Start Konsole
4. Install GNOME Boxes if it isn't already with sudo dnf install gnome-boxes
5. Download Fedora-KDE-Live-x86_64-Rawhide-20231127.n.0.iso from https://koji.fedoraproject.org/koji/buildinfo?buildID=2324914
6. Start GNOME Boxes
7. Boot Fedora-KDE-Live-x86_64-Rawhide-20231127.n.0.iso in a GNOME Boxes QEMU/KVM VM with 3 GiB RAM, and 3D acceleration disabled or enabled

OBSERVED RESULT
Plasma 5.27.80 got stuck on the splash screen in VMs with kwin_wayland errors

EXPECTED RESULT
Plasma 5.27.80 would start normally in VMs

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora Rawhide/40
(available in About System)
KDE Plasma Version: 5.27.80
KDE Frameworks Version: 5.245.0
Qt Version: 6.6.0

ADDITIONAL INFORMATION

Comment 1 Matt Fagnani 2023-12-01 05:44:29 UTC

When I selected full-screen mode from the top menu in GNOME Boxes QEMU/KVM VMs using Plasma 5.27.80 on Wayland with Fedora-KDE-Live-x86_64-Rawhide-20231127.n.0.iso and Fedora-KDE-Live-x86_64-Rawhide-20231129.n.0.iso, and then I exited full-screen mode, Plasma froze. The journal when Plasma froze in this way repeatedly showed the same errors "kwin_wayland_drm: Page flip failed: No space left on device" and "kwin_wayland_drm: Presentation failed! No space left on device". When I selected full-screen mode again, Plasma wasn't frozen any longer and programs I had clicked on while it was frozen changed or appeared. df showed what appears to be enough free space on the VM's partitions.

This problem didn't happen when I booted those images in virt-manager QEMU/KVM VMs with the same settings. In GNOME Boxes QEMU/KVM VMs using Plasma 5.27.9 on Wayland with Fedora-KDE-Live-x86_64-Rawhide-20231125.n.0.iso and earlier, the resolution of Plasma appeared to change automatically to fit the window when Plasma appeared right after the splash screen disappeared. There might be some problem with the way Plasma 5.27.80's resolution changed in the GNOME Boxes VMs which didn't happen in virt-manager.

Comment 2 Matt Fagnani 2023-12-26 22:26:13 UTC

Plasma 5.91.0 doesn't have this problem in Fedora-KDE-Live-x86_64-Rawhide-20231226.n.0.iso. The resolution seems to be changed automatically, as the splash screen icon like ...> moves left and right. The desktop appeared normally.