Were any of you guys able to make VMplayer use the proper GTK3 theme and icons under KDE (more specifically, Breeze-Dark and Papirus-Dark)? I swear to God. Theming in version 14 didn't work at all for me, but after the 15.0 update, it started to work flawlessly. But then I decided to do a clean install of Arch yesterday, so I installed VMware, but now it doesn't pick up the proper theme and icons, again. I don't get it, it's only happening with VMware amongst all GTK3-based programs. I've tried using VMWARE_USE_SHIPPED_LIBS=1, but it did nothing either. Does anyone have any ideia of what is causing this? VMware always picks up the dark Adwaita theme.
Search Criteria
Package Details: vmware-workstation 17.6.3-3
Package Actions
Git Clone URL: | https://aur.archlinux.org/vmware-workstation.git (read-only, click to copy) |
---|---|
Package Base: | vmware-workstation |
Description: | The industry standard for running multiple operating systems as virtual machines on a single Linux PC. |
Upstream URL: | https://www.vmware.com/products/workstation-for-linux.html |
Keywords: | dkms ovftool player vmplayer vmware workstation |
Licenses: | custom |
Conflicts: | vmware-modules-dkms, vmware-ovftool, vmware-patch, vmware-systemd-services |
Provides: | vmware-ovftool |
Submitter: | synthead |
Maintainer: | JulianXhokaxhiu |
Last Packager: | JulianXhokaxhiu |
Votes: | 212 |
Popularity: | 3.26 |
First Submitted: | 2017-02-10 19:04 (UTC) |
Last Updated: | 2025-04-03 21:57 (UTC) |
Dependencies (15)
- dkms (dkms-gitAUR)
- fuse2
- gcr
- gtk3 (gtk3-no_deadkeys_underlineAUR, gtk3-classic-xfceAUR, gtk3-patched-filechooser-icon-viewAUR, gtk3-classicAUR)
- gtkmm3
- hicolor-icon-theme (hicolor-icon-theme-gitAUR)
- libaio (libaio-gitAUR)
- libcanberra
- libxcrypt-compat
- pcsclite (pcsclite-gitAUR)
- 7zip (make)
- python (python37AUR, python311AUR, python310AUR) (make)
- sqlite (sqlite-fossilAUR) (make)
- uefitoolAUR (uefitool-gitAUR, uefitool-binAUR) (make)
- linux-headers (optional) – build modules against Arch kernel
Required by (6)
Sources (25)
- config
- configure-initscript.sh
- dkms.conf.in
- efi-patches.txt
- https://softwareupdate-dev.broadcom.com/cds/vmw-desktop/ws/17.5.2/23775571/linux/packages/vmware-tools-linux-12.4.0-23259341.x86_64.component.tar
- https://softwareupdate-dev.broadcom.com/cds/vmw-desktop/ws/17.5.2/23775571/linux/packages/vmware-tools-linuxPreGlibc25-12.4.0-23259341.x86_64.component.tar
- https://softwareupdate-dev.broadcom.com/cds/vmw-desktop/ws/17.5.2/23775571/linux/packages/vmware-tools-netware-12.4.0-23259341.x86_64.component.tar
- https://softwareupdate-dev.broadcom.com/cds/vmw-desktop/ws/17.5.2/23775571/linux/packages/vmware-tools-solaris-12.4.0-23259341.x86_64.component.tar
- https://softwareupdate-dev.broadcom.com/cds/vmw-desktop/ws/17.5.2/23775571/linux/packages/vmware-tools-winPre2k-12.4.0-23259341.x86_64.component.tar
- https://softwareupdate-dev.broadcom.com/cds/vmw-desktop/ws/17.5.2/23775571/linux/packages/vmware-tools-winPreVista-12.4.0-23259341.x86_64.component.tar
- https://softwareupdate-dev.broadcom.com/cds/vmw-desktop/ws/17.6.3/24583834/linux/core/VMware-Workstation-17.6.3-24583834.x86_64.bundle.tar
- Makefile
- unlocker.py
- vmmon.patch
- vmnet.patch
- vmware-bootstrap
- vmware-environment.sh
- VMware-Fusion-13.5.2-23775688_universal.zip.tar
- vmware-networks-configuration.service
- vmware-networks.path
- vmware-networks.service
- vmware-tools-windows-12.5.0-24276846-17.6.3.x86_64.component.tar
- vmware-usbarbitrator.path
- vmware-usbarbitrator.service
- vmware-vix-bootstrap
Latest Comments
« First ‹ Previous 1 .. 47 48 49 50 51 52 53 54 55 56 57 .. 71 Next › Last »
gbr commented on 2018-10-06 14:14 (UTC) (edited on 2018-10-06 14:15 (UTC) by gbr)
jihem commented on 2018-09-30 07:50 (UTC)
vmAutoStart.xml file is automatically created by VMware if it doesn't exist. On this release, I've added this file in the package, that's why you had this conflict. Deleting this file before upgrading is the right thing to do.
king007 commented on 2018-09-30 06:18 (UTC)
@jihem
Thank you for quick upgrade.
I have got new "updates available" notification from the package manager as I was using version 14. I tried upgrading it and after the build process i got the error "conflicting files : /etc/vmware/hostd/vmAutoStart.xml" (https://imgur.com/a/rV6kJ4y). I then removed version 14 and tried to do fresh install of version 15 and I still got the same error.
Finally I have deleted the file manually and restarted the build process, installation was successful and everything seems to be fine so far.
Regards
jihem commented on 2018-09-29 14:26 (UTC)
Hi,
I've just updated the package for version 15.0.0. Tell me if you see some bugs. I've not tested the new REST API because I don't know what it is exactly and how to test it, so feedback are welcome.
I've created vmware-workstation14 package for people who want to stay on version 14.
strayArch commented on 2018-09-26 15:58 (UTC) (edited on 2018-09-26 15:59 (UTC) by strayArch)
jihem's version worked for me. I think the new thumbnails might not be updated properly. Thanks a ton!
buzo commented on 2018-09-26 14:57 (UTC)
sajmonella9: May I suggest to continue this discussion with jihem via e-mail?
jihem commented on 2018-09-26 14:19 (UTC)
@sajmonella9 The link I provide does not contain the package but the sources to create it; extract the archive, create the package with makepkg and install it with pacman. Or be patient, because there is some bugs with this PKGBUILD.
sajmonella9 commented on 2018-09-26 10:50 (UTC)
@jihem you'r new PKGBUILD send me this output :
sudo pacman -U vmware-workstation.tar.xz loading packages... error: missing package metadata in vmware-workstation.tar.xz error: 'vmware-workstation.tar.xz': invalid or corrupted package
CaskAle13c commented on 2018-09-25 23:43 (UTC)
@jihem Thank you. I will compare this against mine to learn why my work would not build.
jihem commented on 2018-09-25 23:00 (UTC) (edited on 2018-09-29 14:15 (UTC) by jihem)
@CaskAle13c Actually, I already made a PKGBUILD. If you really want it now, you can download it here: (EDIT: this link is not useful anymore)
But I didn't test it well, so you could see some bugs or missing functionalities.
Pinned Comments
jihem commented on 2020-02-10 17:29 (UTC) (edited on 2021-06-19 13:19 (UTC) by jihem)
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