gclayburg's Posts

This worked for me as well.  In  my case, I upgraded ubuntu to 22.04 and ran into this issue when I tried to launch vmware player.  I was running version 16.2.1 of vmware player before the ubuntu upg... See more...
This worked for me as well.  In  my case, I upgraded ubuntu to 22.04 and ran into this issue when I tried to launch vmware player.  I was running version 16.2.1 of vmware player before the ubuntu upgrade.  After the ubuntu upgrade, vmware player would launch, but complain about missing kernel modules.  There is a button to click in the gui to recompile, but that failed.  The fix described in this thread worked!  I can at least launch vmware player without the show stopping error.  Of course, once I launch vmware player, it prompts me to upgrade to the latest 16.2.5.  A quick check of the release notes shows that the error of compiling kernel modules for ubuntu 22.04 has been fixed with version 16.2.4. yay!  So maybe if you were to upgrade to vmware player 16.2.4 or later BEFORE upgrading to ubuntu 22.04 you wouldn't run into this issue?  For the rest of us, we need to do this manual install of the kernel modules as documented here: https://github.com/mkubecek/vmware-host-modules/blob/master/INSTALL From the release notes of vmware player 16.2.4: ``` Workstation Player fails to launch on Ubuntu 22.04 host operating system After you install Workstation Player on an Ubuntu 22.04 host operating system, the application fails to launch because of a compilation error in building the vmmon and vmnet kernel module.  This issue is now resolved. ```
I am running VMware player 16.1.0 on Ubuntu linux 18.04.   Running VMware player will corrupt my keyboard on the host once any guest OS has started.  This issue is not about trying to configure the k... See more...
I am running VMware player 16.1.0 on Ubuntu linux 18.04.   Running VMware player will corrupt my keyboard on the host once any guest OS has started.  This issue is not about trying to configure the keyboard mapping in the guest OS.  This is about being able to run VMware player without it putting the keyboard into an unusable state on the host.  Here are the steps to reproduce the issue. 1. Map the caps lock key on the host to act as a extra control key on the host: $ gsettings set org.gnome.desktop.input-sources xkb-options "['caps:ctrl_modifier']" 2. Launch VMware player and start a guest.  I've been testing with a Ubuntu 20.04 guest, but I don't think it matters which guest is used.  You don't even need to log into the guest to see the problem. 3.  Click somewhere within the login window of the guest. 4. Now move the mouse out of the window and attempt to use an application such as the terminal. This is enough to show this problem.  For me, many modifier keys are corrupt in weird ways.  For example, the left shift key works, but the right shift key does not.  You can also see this with the output of xmodmap: $ xmodmap xmodmap: up to 0 keys per modifier, (keycodes in parentheses): shift lock control mod1 mod2 mod3 mod4 mod5   This output shows nothing mapped for these modifier keys.  It should show much more. There are several workarounds to this problem, but none are ideal.  It just looks like VMware is not able to honor the setting to map the caps lock as an additional crontrol on the host.  VMware bug?