https://bugs.kde.org/show_bug.cgi?id=477985
Bug ID: 477985
Summary: Regression on VMware setting screen resolution
(Wayland)
Classification: Plasma
Product: kwin
Version: git master
Platform: Other
OS: Other
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: kwin-bugs-n...@kde.org
Reporter: stefan.hoffmeis...@econos.de
Target Milestone: ---
SUMMARY
Setting the screen resolution of a virtualized Fedora Rawhide / Plasma 6.0 dev
master via VMware Workstation / Player tooling fails to update the screen
resolution of the KDE 6 desktop, on Wayland.
This breaks, for instance, "full screen" support in VMware Workstation.
This is a regression relative to Fedora Linux 39 with KDE 5.27.x on Wayland.
This seems to work fine on X11.
STEPS TO REPRODUCE
1. have VMware Workstation or VMware Player running as a virtualization
solution
2. install and up-to-date Fedora Rawhide (which includes Plasma 6.0 dev master)
as a fresh VM
// no additional steps are required to get VMware tools in - Fedora Rawhide
does this out of the box
// observe that this generally works
3. `sudo vmwgfxctrl --set-topology 1920x1080+0+0`
OBSERVED RESULT
Nothing happens
EXPECTED RESULT
Virtual screen gets resized to 1920x1080.
This applies to setting any screen resolution; above I am using `vmwgfxctrl`
for the sake of simplicity, but the same code path (on the VMware side? Linux
kernel side?) is most likely taken by
* resizing the host virtualized window with "Autofit Guest" feature enabled
* putting the VM into full-screen mode (or back)
In all cases, the "virtual" screen resolution never changes.
Note that setting the screen resolution from _within_ KDE, via "Display
Configuration" works (almost always - have not found a reliable way to repro).
The drawback of doing that, though, is that this does not allow enabling the
peculiar (good) behaviour of "Full-screen mode" in VMware Workstation, where
all input is redirected into the VM. The regression therefore does hurt quite a
bit in real use of the KDE desktop environment.
I do not see any log output, neither in journalctl nor in dmesg, which seem to
apply to this scenario.
--
You are receiving this mail because:
You are watching all bug changes.
