xf86-video-vmware-13.3.0-4 VM autofit

PeterUpfold · 2022-08-21 20:53:30

I have Arch running as a guest within VMware Workstation 16.2.4 build-20089737.

The guest is running linux 5.19.2-arch1-1.

Following the update to xf86-video-vmware-13.3.0-4 from 13.3.0-3, autofit for the VM window resolution no longer functions. I am able to manually change resolution with xrandr without problems, but dragging the window to increase or decrease the VM window size does not update the guest resolution as it did before.

I have rolled back to xf86-video-vmware-13.3.0-3 and the issue is resolved. There were no other pertinent changes to video config -- just rolling back this one package fixes it.

My reading is that it doesn't appear that there were any upstream changes, and this is just an Arch packaging difference.

It sounds like, then, I should open an Arch bug...?

Can anyone provide any pointers on the kind of information I should include in a bug report in this case, and if this does indeed sound like it would be an Arch-specific issue, given the upstream .tar.bz2 that the PKGBUILD pulls has not changed?

Lone_Wolf · 2022-08-22 12:07:27

The log shows that there were 2 changes :
- the package is now build with debug symbols (they go in a spearate package)
- a new patch is applied to the source

If you check the bugreport (FS#75367 ) mentioned in the commit message you'll notice the patch does come from upstream.

The first is an archlinux packaging change, the 2nd is an upstream change*

You could try to build 13.3.0-4 with 'debug' removed from the PKGBUILD to verify which of those 2 changes causes your issue.

* that change is already merged to master so should be included in the next relase of xf86-video-vmware .

Last edited by Lone_Wolf (2022-08-22 12:08:13)

PeterUpfold · 2022-08-22 21:15:13

Interestingly, I appear to have no problems when building the package myself, even with no changes, but the binary downloaded from the mirrors exhibits the problem. I have swapped the mirror's package to my own build and back and it appears to be consistent.

I'm struggling to understand this, as one would imagine this should not have any material impact on the produced binary. But on multiple guests, which consistently have not supported the autofit resize since 13.3.0-4, my own pkgbuilt version of the same source fixes this problem.

I have solved my immediate problem, in that it now works for me, but I'm not sure if there is any mileage still in trying to figure out what is happening here?

Lone_Wolf · 2022-08-24 13:19:07

I do think it's worth investigating.

There are (atleast) 2 possible causes for the issue :
- build system where the repo binary was created on has issues
- difference between your build environment and the env used for the repo.

Archlinux repo packages are build in a clean chroot, user built packages often in their everyday running environmnet .
While rare, there have been some cases where clean chroot building missed a feature due to not detecting a library needed for the feature.

https://wiki.archlinux.org/title/Develo … ean_chroot
install devtools, then run extra-x86_64-build from the folder where the PKGBUILD for xf86-video-vmware resides.
Test with the resulting binary.

If it has the same behavior as the repo binary, the PKGBUILD may be missing a needed dependency.

PeterUpfold · 2023-01-28 10:59:15

I have come back to this after a long time (sorry!), as a recent update to 13.4.0 exhibits the same problem.

I did the following to build in a chroot, and, again, my package seems to work fine with the resizing of the guest resolution, but the stock package does not resize the guest resolution when you drag to resize the VM window.

I am not at all sure what could be different about the package I have built and the one in the repo.

Here are the steps I took:

    mkdir stock-13.4.0
    cd stock-13.4.0
    wget https://raw.githubusercontent.com/archlinux/svntogit-packages/packages/xf86-video-vmware/trunk/PKGBUILD
    mkdir -p keys/pgp
    cd keys/pgp
    wget https://raw.githubusercontent.com/archlinux/svntogit-packages/packages/xf86-video-vmware/trunk/keys/pgp/3C2C43D9447D5938EF4551EBE23B7E70B467F0BF.asc
    wget https://raw.githubusercontent.com/archlinux/svntogit-packages/packages/xf86-video-vmware/trunk/keys/pgp/90D027AEAF33CBABC140735BC1F5D3CDF5176580.asc

Install devtools dependencies

sudo pacman -S devtools

Create a chroot. Cannot be in a dir with spaces

    cd ~/build
    mkdir chroot
    export CHROOT=$PWD/chroot
    mkarchroot $CHROOT/root base-devel

Now try and build the package in the chroot. (I know I should not do --skippgpcheck, but I did not yet look up how to get the correct public keys imported into the chroot):

cd /path/to/stock-13.4.0
makechrootpkg -r $CHROOT -- --skippgpcheck

Now we have a package -- let's try it.

Copy to the VM. In the VM:

pacman -U xf86-video-vmware-13.4.0-1-x86_64.pkg.tar.zst

And my package works -- the one recently upgraded via pacman -Syu does not.

Although I can solve my problem by just building this myself, transferring to my guests and "re-installing" with the package I have built, any insight on what is going on here is most welcome!

Lone_Wolf · 2023-01-31 12:06:27

I'm not sure what mkarchroot uses by default for makepkg.conf & pacman.conf , but I expect it to be those files in the pacman package .

extra-x86_64-build uses different files though, taken from /usr/share/devtools .
I stronlgy suggest you build that way and verify if it makes a difference .

(extra-x86_64-build should be able to use the keys yoiu downloaded)

Arch Linux

#1 2022-08-21 20:53:30

xf86-video-vmware-13.3.0-4 VM autofit

#2 2022-08-22 12:07:27

Re: xf86-video-vmware-13.3.0-4 VM autofit

#3 2022-08-22 21:15:13

Re: xf86-video-vmware-13.3.0-4 VM autofit

#4 2022-08-24 13:19:07

Re: xf86-video-vmware-13.3.0-4 VM autofit

#5 2023-01-28 10:59:15

Re: xf86-video-vmware-13.3.0-4 VM autofit

#6 2023-01-31 12:06:27

Re: xf86-video-vmware-13.3.0-4 VM autofit

Board footer