Arch Linux User Repository

After the first installation, please:

1) install the appropriate headers package(s) for your installed kernel(s): linux-headers for default kernel, linux-lts-headers for LTS kernel...

2) reboot or load vmw_vmci and vmmon kernel modules (modprobe -a vmw_vmci vmmon)

3) Enable the services you need (using .service units to activate them during boot or .path units to activate them when a VM is started) :

• vmware-networks: to have network access inside VMs

• vmware-usbarbitrator: to connect USB devices inside VMs

when the bundle tries to install

The bundle should never try to install anything. You shouldn't manually start the bundle if you want to install VMware from this AUR package, and the PKGBUILD only extracts the files from the bundle to install them using its own script (it doesn't start the bundle installation).

Unfortunately, IDK how to force the aur helper (trizen) to write on the root partition. AFAIK trizen can not be run as sudo.

After re-reading your first comment, I think you don't understand how AUR works. To install this package, you should only start the command trizen -S vmware-workstation (or something similar, I don't know trizen syntax). Then trizen downloads the PKGBUILD in a directory, starts makepkg in this direcory and when the package is built, trizen uses pacman to install the package. Only pacman needs root privileges and is able to write files anywhere on the filesystem (I guess trizen uses sudo pacman -U, makepkg -i or something like that to run pacman with root privileges).

If you are sure to use trizen correctly, then maybe this is a trizen bug, so try with the manual method: https://wiki.archlinux.org/title/Arch_User_Repository#Installing_and_upgrading_packages

rado84, Are you using any other AUR packages that maybe in conflict, because your issue doesn't happen with my systems.

@jihem, yes and I deleted them manually one by one, thus cleaning the system from everything vmware related. And then at the end of the installation the story repeats itself. So I backed up the current system, installed a fresh Arch with nothing else but the desktop and video driver and tried installing VMWare again - same thing: at the end of the installation "these files exist in the filesystem". Clearly one of the other files in the above list provides these files prematurely and when the bundle tries to install, it can't because of these conflicts. It's pointless, I'll use vbox. VMWare has become (to me) the same thing Skype did ever since MS bought it - something not to touch, if I wanna keep my sanity intact.

@ihipop No, the only language available is english.

@rado84 As yurikoles said, these files were created when you tried to install the bundle, even if the bundle was unable to finish the installation.

You can remove these files using this process: https://wiki.archlinux.org/title/VMware#Removal but if the installation was not finished, I am not sure it will work.

Otherwise, you can remove most of the files with the command rm -r /etc/vmware-installer /usr/lib/vmware-installer and force installing the package using the command given in yurikoles link: pacman -U --overwrite \* vmware-workstation-17.5.2-1-x86_64.pkg.tar.zst

Any way to change the localization language?

I see file conflicts in the rado84's pastebin, so you definitely installed VMware Workstation from bundle before installing this package.

Any AUR helper, including trizen, don't write system files directly, they delegate this to the pacman. So if you have these files in the system but pacman doesn't know about them, this means they didn't came from this package.

That's not a fault of package author, nor trizen nor pacman or Arch Linux, but the user who installed files to the system without leveraging package manager.

Please consult with Arch Wiki about pacman file conflicts

@jihem, yeah, I tested it and it didn't cry about GCC version but something else happened. Just at the end of the installation it showed a bunch of errors unable to write ANYTHING in the root partition (ALL of the vmware packages, icons, files, etc) and the installation was terminated. Unfortunately, IDK how to force the aur helper (trizen) to write on the root partition. AFAIK trizen can not be run as sudo.

Up until the moment it asks whether I wanna install vmware-workstation (Yes/No) - it's ok. If I type "Y" and press enter, then the nightmare begins. I created a pastebin for you to see it. Keep in mind that that's on a system which didn't have vmware before and all of these files came from the AUR package. Now I'll have to delete each one manually...

https://pastebin.com/qsDfp8yU

If it can't be fixed - f*ck it, I can live without VMWare. I needed it to test something but I guess I won't.

@rado84 I don't understand exactly what happens for you with the bundle, but this package works with GCC 14 without any problem.

I downloaded the bundle (17.5.2) from Broadcom and it cried about gcc 13.2.1 (and I have 14.something installed). Does this package here cry about the same?