search

mkubecek / vmware-host-modules

Patches needed to build VMware (Player and Workstation) host modules against recent kernels
GNU General Public License v2.0
2.27k stars 366 forks source link

vmplayer 12.5.9 segfault #196

Closed cxrodgers closed 1 year ago

cxrodgers commented 1 year ago

Hello, I have been using this repository successfully for a long time, thank you for supporting this. Recently I have encountered a segfault that I haven't been able to address.

I am using this version of vmplayer: VMware Player 12.5.9 build-7535481 I have this kernel: 5.15.0-69-generic

I have followed the installation instructions as I always do, using the branch player-12.5.9. The make and make install complete without any problems. I also did make tarballs and copied vmmon.tar and vmnet.tar into /usr/lib/vmware/modules/source.

However, whenever I start vmplayer, I get this segfault:

Gtk-Message: Failed to load module "atk-bridge": /lib/x86_64-linux-gnu/libatspi.so.0: undefined symbol: g_type_add_instance_private

(vmware-modconfig:5123): Gtk-WARNING **: Unable to locate theme engine in module_path: "adwaita",
/usr/share/themes/Mint-Y-Pink/gtk-2.0/main.rc:1045: error: unexpected identifier `direction', expected character `}'

(vmware-modconfig:5123): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",

(vmware-modconfig:5123): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",

(vmware-modconfig:5123): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",

(vmware-modconfig:5123): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",

(vmware-modconfig:5123): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
/usr/bin/vmplayer: line 106:  5123 Segmentation fault      "$BINDIR"/vmware-modconfig --appname="VMware Player" --icon="vmware-player"

I think most of the Gtk warning can be ignored. Not sure how to address the last one. Thanks for any advice!

mkubecek commented 1 year ago

This is a userspace issue with a closed source application, i.e. something I can hardly do anything with. You can work around it by building and installing the modules directly (just make and make install, without vmware-modconfig).