Any tested application based on Google Chrome / the Electron framework starts, but fails to shown an application window on Wayland with KDE Neon unstable and KDE 6. This happens on VMware Workstation 17.5. This affects, amongst other applications * Google Chrome * Microsoft Edge * Microsoft Visual Studio Code / VSCodium * Slack * Discord This reproduces for me on VMware Workstation 17.5, running on top of Microsoft Windows 11 Professional, with the following steps: * create new VM with default settings * boot from KDE Neon unstable ISO * install to virtual disk * reboot * sudo apt update & sudo apt full-upgrade * sudo apt install open-vm-tools-desktop * reboot * pkcon update * reboot * install affected software, for instance, Microsoft Visual Studio Code from https://code.visualstudio.com/download -> ".deb" -> Discover (or VSCodium from https://github.com/VSCodium/vscodium/releases) * launch the software from Konsole with "code" //exp: Software main window is shown //act: Software launches (launcher feedback), task manager entry appears, but no main window is shown journalctl -xe shows (many of) these warnings which may be relevant ``` Okt 31 06:34:22 vmware-neon kwin_wayland[1123]: kwin_core: drmPrimeHandleToFD() failed: No such file or directory Okt 31 06:34:22 vmware-neon kwin_wayland[1123]: kwin_scene_qpainter: Failed to allocate a qpainter swapchain graphics buffer Okt 31 06:34:22 vmware-neon kwin_wayland[1123]: kwin_wayland_drm: EglGbmLayerSurface::importWithCpu: failed to get a target dumb buffer ```
Created attachment 162757 [details] Visual Studio Code running, task manager preview has the right number of entries, but the content is not presented at all.
FWIW, this is a regression relative to a freshly installed KDE Neon _stable_ on the same platform (VMware Workstation 17.5)
This defect appears to be specific to Wayland sessions; on X11 (same installation of KDE Neon unstable), Chrome / Electron applications do render. Note that, historically, KDE has been working very well for me with X11 (on Fedora Linux, my real working environment). Wayland on VMware Workstation has always had challenges relative to Gnome/Mutter.
On Fedora Rawhide, with the addition of https://copr.fedorainfracloud.org/coprs/g/kdesig/kde-nightly/, application windows appear as expected. Explored with vscode and chromium, both on XWayland and natively on Wayland via passing `--enable-features=UseOzonePlatform --ozone-platform=wayland` as command-line parameters. The diagnostic output related to `drm` noted above remains. With `LIBGL_DEBUG=verbose` nothing stands out as deficient on the libdrm side. Alas, VMware Workstation open-vm-tools seem to be a bit broken on Fedora Rawhide at the moment, so test-driving the whole package with the intended configuration is not possible at the moment.
I can't reproduce the issue on bare metal, and if updating to newer packages fixed it for you in a VM, that suggests that it was caused by a code issue that's since been fixed. Thanks for reporting it anyway!