Bug 478019

Created attachment 163834 [details]
Journal from a GNOME Boxes VM in which Plasma 5.27.80 froze after exiting full screen mode

SUMMARY

I booted the Fedora Rawhide/40 KDE Plasma live image Fedora-KDE-Live-x86_64-Rawhide-20231202.n.0.iso in GNOME Boxes QEMU/KVM VMs in a Fedora 39 KDE Plasma host. To work around the VM getting stuck on the Plasma 5.27.80 splash screen as I reported at https://bugs.kde.org/show_bug.cgi?id=477643 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.
I exited full screen mode by selecting the full screen button in the GNOME Boxes top bar. Plasma froze after exiting full screen mode. I clicked to open Dolphin and Firefox from the panel and open the Application Launcher menu, but nothing opened. I clicked to enter full screen mode again and Plasma started responding again. The programs and menu I clicked on when not in full screen mode opened.

The journal showed spice-vdagentd errors in which it appeared to be trying to connect to mutter by dbus which was odd. There were kwin_wayland errors repeated hundreds of times while Plasma was frozen like  kwin_wayland_drm: Page flip failed: No space left on device and kwin_wayland_drm: Presentation failed! No space left on device

Dec 03 20:23:29 spice-vdagent[2047]: vdagent started
Dec 03 20:23:29 systemd[1377]: app-org.kde.kgpg@autostart.service: Skipped due to 'exec-condition'.
Dec 03 20:23:29 systemd[1377]: Condition check resulted in app-org.kde.kgpg@autostart.service - KGpg being skipped.
Dec 03 20:23:29 systemd[1377]: Started app-xdg\x2duser\x2ddirs@autostart.service - User folders update.
Dec 03 20:23:29 systemd[1377]: Started app-xdg\x2duser\x2ddirs\x2dkde@autostart.service - User folders update.
Dec 03 20:23:29 kconf_update[1878]: kf.config.kconf_update: /usr/share/kconf_update/style_widgetstyle_default_breeze.upd defined Version=5 but Version=6 was expected
Dec 03 20:23:29 kconf_update[1878]: kf.config.kconf_update: /usr/share/kconf_update/webengineurlinterceptoradblock.upd defined Version=5 but Version=6 was expected
Dec 03 20:23:29 systemd[1377]: Started xdg-desktop-portal-gtk.service - Portal service (GTK/GNOME implementation).
Dec 03 20:23:29 systemd[1377]: Started xdg-desktop-portal.service - Portal service.
Dec 03 20:23:29 spice-vdagent[2047]: display: failed to call GetCurrentState from mutter over DBUS
Dec 03 20:23:29 spice-vdagent[2047]:    error message: Cannot invoke method; proxy is for the well-known name org.gnome.Mutter.DisplayConfig without an owner, and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag
Dec 03 20:23:29 systemd[1377]: Reached target xdg-desktop-autostart.target - Startup of XDG autostart applications.
Dec 03 20:23:29 spice-vdagent[2047]: No guest output map, using output index as display id
Dec 03 20:23:29 kernel: input: spice vdagent tablet as /devices/virtual/input/input7
Dec 03 20:23:29 spice-vdagentd[1694]: opening vdagent virtio channel
Dec 03 20:23:29 spice-vdagent[2047]: Received Graphics Device Info:
Dec 03 20:23:29 systemd[1377]: Started dbus-:1.2-org.freedesktop.Notifications@0.service.
Dec 03 20:23:29 spice-vdagent[2047]: card0 not found while listing DRM devices.
Dec 03 20:23:29 spice-vdagent[2047]: Unable to open file (null)
Dec 03 20:23:29 systemd[1377]: Started dbus-:1.46-org.a11y.atspi.Registry@0.service.
Dec 03 20:23:29 spice-vdagent[2047]: card0 not found while listing DRM devices.
Dec 03 20:23:29 spice-vdagent[2047]: Unable to open file (null)
Dec 03 20:23:29 spice-vdagent[2047]: channel_id: 0 monitor_id: 0 device_address: pci/0000/01.0, device_display_id: 0 xrandr output ID NOT FOUND
Dec 03 20:23:29 spice-vdagent[2047]: display: failed to call GetCurrentState from mutter over DBUS
Dec 03 20:23:29 spice-vdagent[2047]:    error message: Cannot invoke method; proxy is for the well-known name org.gnome.Mutter.DisplayConfig without an owner, and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag
Dec 03 20:23:29 spice-vdagentd[1694]: Set max clipboard: 104857600
Dec 03 20:23:29 spice-vdagent[2047]: No guest output map, using output index as display id
Dec 03 20:23:29 spice-vdagent[2047]: Received Graphics Device Info:
Dec 03 20:23:29 spice-vdagent[2047]: card0 not found while listing DRM devices.
Dec 03 20:23:29 spice-vdagent[2047]: Unable to open file (null)
Dec 03 20:23:29 spice-vdagent[2047]: card0 not found while listing DRM devices.
Dec 03 20:23:29 spice-vdagent[2047]: Unable to open file (null)
Dec 03 20:23:29 spice-vdagent[2047]: channel_id: 0 monitor_id: 0 device_address: pci/0000/01.0, device_display_id: 0 xrandr output ID NOT FOUND
Dec 03 20:23:29 spice-vdagent[2047]: display: failed to call GetCurrentState from mutter over DBUS
Dec 03 20:23:29 spice-vdagent[2047]:    error message: Cannot invoke method; proxy is for the well-known name org.gnome.Mutter.DisplayConfig without an owner, and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag
Dec 03 20:23:29 spice-vdagent[2047]: No guest output map, using output index as display id
Dec 03 20:23:29 spice-vdagent[2047]: Received Graphics Device Info:
Dec 03 20:23:29 spice-vdagent[2047]: card0 not found while listing DRM devices.
Dec 03 20:23:29 spice-vdagent[2047]: Unable to open file (null)
Dec 03 20:23:29 spice-vdagent[2047]: card0 not found while listing DRM devices.
Dec 03 20:23:29 spice-vdagent[2047]: Unable to open file (null)
Dec 03 20:23:29 spice-vdagent[2047]: channel_id: 0 monitor_id: 0 device_address: pci/0000/01.0, device_display_id: 0 xrandr output ID NOT FOUND
Dec 03 20:23:29 spice-vdagent[2047]: display: failed to call GetCurrentState from mutter over DBUS
Dec 03 20:23:29 spice-vdagent[2047]:    error message: Cannot invoke method; proxy is for the well-known name org.gnome.Mutter.DisplayConfig without an owner, and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag
Dec 03 20:23:29 spice-vdagent[2047]: No guest output map, using output index as display id
Dec 03 20:23:29 at-spi2-registryd[2063]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Dec 03 20:23:30 systemd[1377]: Started dbus-:1.2-com.redhat.imsettings@1.service.
Dec 03 20:23:30 kwin_wayland[1684]: kwin_wayland_drm: Page flip failed: No space left on device
Dec 03 20:23:30 kwin_wayland[1684]: kwin_wayland_drm: Presentation failed! No space left on device

Those kwin_wayland errors were also shown with when Plasma remained on the splash screen as at https://bugs.kde.org/show_bug.cgi?id=477643 I'm attaching the journal.

I stopped spice-vdagent with 
sudo systemctl stop spice-vdagentd.service 
sudo systemctl stop spice-vdagentd.socket

After that exiting full screen mode didn't make Plasma freeze and those errors didn't occur. spice-vdagent crashed when I stopped it. 


STEPS TO REPRODUCE
1. Boot a Fedora 39 KDE Plasma installation updated to 2023-12-3 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-20231202.n.0.iso from https://koji.fedoraproject.org/koji/buildinfo?buildID=2326954
6. Start GNOME Boxes
7. Boot Fedora-KDE-Live-x86_64-Rawhide-20231202.n.0.iso in a GNOME Boxes QEMU/KVM VM with 3 GiB RAM, UEFI enabled, and 3D acceleration disabled or enabled
8. Select full screen mode in GNOME Boxes
9. To work around https://bugs.kde.org/show_bug.cgi?id=477643, switch to VT2 in GNOME boxes via the keyboard menu Ctrl+Alt+F2 and back to VT1 with Ctrl+Alt+F1
10. Exit full screen mode in GNOME Boxes
11. Try to open menus or programs in the panel.

OBSERVED RESULT
Plasma froze after exiting full screen mode in GNOME Boxes QEMU/KVM VMs started in full screen mode

EXPECTED RESULT
Plasma shouldn't have froze.

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.1

ADDITIONAL INFORMATION

This problem didn't happen if I didn't select full screen mode in GNOME Boxes before Plasma started. Plasma didn't freeze in this way when using virt-manager QEMU/KVM VMs with the same image and settings. This problem didn't happen with Plasma 5.27.9 when doing the same things. The problem might've involved how Plasma 5.27.80 interacted with spice-vdagent in GNOME Boxes specifically.