| Summary: | No app window shown - vscode / Chrome/ Electron - Wayland, KDE6 | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Stefan Hoffmeister <stefan.hoffmeister> |
| Component: | wayland-generic | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | major | CC: | nate, xaver.hugl |
| Priority: | NOR | Keywords: | wayland-only |
| Version First Reported In: | git master | ||
| Target Milestone: | --- | ||
| Platform: | Neon | ||
| OS: | Other | ||
| See Also: | https://bugs.kde.org/show_bug.cgi?id=473887 | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | Visual Studio Code running, task manager preview has the right number of entries, but the content is not presented at all. | ||
|
Description
Stefan Hoffmeister
2023-10-31 05:39:35 UTC
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! |