Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: The display resolution of a VMware virtual machine can be indeterminate, apparently depending in the order in which vmtoolsd finishes starting and the display manager starts. Background: /usr/bin/vmtoolsd provides an enhanced choice of display resolutions. /usr/libexec/Xorg is started by the display manager. e.g. /usr/bin/lightdm . Version-Release number of selected component: open-vm-tools-13.0.10-2.fc43 How reproducible: Seems roughly a 50/50 chance which resolution of the two mentioned below is used. Steps to Reproduce: (Perhaps not really needed, since the patch offered below seems quite logical.) VMware should be in full screen mode. My physical display is 16:10, so 2048x1152 (16:9) has black bands top and bottom, whereas 2048x1280 fills the physical display. On the virtual machine: 1. In System/Preferences/Hardware/Displays, choose 2048x1152 . (In my testing, this would mysteriously result in 2048x1280 for the current session, which is what I actually wanted, but that choice was not in the menu.) 2. Click "Apply" and accept the change. 3. Click "Apply system-wide". 4. Reboot the virtual machine and log in, repeatedly. Actual results: Resolution is sometimes 2048x1152, sometimes 2048x1280 . Expected results: Always 2048x1280 . FIX: This problem has all the earmarks of a race, and seems to be fixed by the following addition to /usr/lib/systemd/system/vmtoolsd.service : [Unit] Description=Service for virtual machines hosted on VMware Documentation=http://github.com/vmware/open-vm-tools ConditionVirtualization=vmware Requires=vgauthd.service After=vgauthd.service Add >>> Before=display-manager.service [Service] ExecStart=/usr/bin/vmtoolsd TimeoutStopSec=5 [Install] WantedBy=multi-user.target Also=vgauthd.service That seems to ensure that the resolutions provided by vmtoolsd are available when the display manager starts. I have not experienced the problem with this patched version.
FEDORA-2026-5674adc0a5 (open-vm-tools-13.1.0-2.fc44) has been submitted as an update to Fedora 44. https://bodhi.fedoraproject.org/updates/FEDORA-2026-5674adc0a5
FEDORA-2026-d3f7081ad6 (open-vm-tools-13.1.0-2.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2026-d3f7081ad6
FEDORA-2026-d3f7081ad6 has been pushed to the Fedora 43 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-d3f7081ad6` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-d3f7081ad6 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2026-5674adc0a5 has been pushed to the Fedora 44 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-5674adc0a5` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-5674adc0a5 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2026-5674adc0a5 (open-vm-tools-13.1.0-2.fc44) has been pushed to the Fedora 44 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2026-d3f7081ad6 (open-vm-tools-13.1.0-2.fc43) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report.