tom___'s Posts

> the current state under Wayland is, how it should be What do you mean? This problem still exists for me even under workstation 16. Has anyone figured out a way to get workstation to properly rout... See more...
> the current state under Wayland is, how it should be What do you mean? This problem still exists for me even under workstation 16. Has anyone figured out a way to get workstation to properly route all keys to a guest on wayland? I know it works on Xorg, but VMWare claims support for wayland, and I would argue this problem makes workstation unusable.
also see this thread regarding the previous kernel upgrade: Workstation 12.1 does not compile on kernel 4.6.0-1
from the vmware-installer log: [2016-08-17 15:34:04,801] Installer running. [2016-08-17 15:34:04,801] Command Line Arguments: [2016-08-17 15:34:04,801] ['/usr/lib/vmware-installer/2.1.0/... See more...
from the vmware-installer log: [2016-08-17 15:34:04,801] Installer running. [2016-08-17 15:34:04,801] Command Line Arguments: [2016-08-17 15:34:04,801] ['/usr/lib/vmware-installer/2.1.0/vmware-installer.py', '-t', '--console'] [2016-08-17 15:34:04,802] UI Initialization failed. Traceback (most recent call last):   File "/usr/lib/vmware-installer/2.1.0/vmware-installer.py", line 288, in main     ui.Initialize(options.ui)   File "/usr/lib/vmware-installer/2.1.0/vmis/ui/__init__.py", line 83, in Initialize     exec 'from vmis.ui.null import *' in globals()   File "<string>", line 1, in <module>   File "/usr/lib/vmware-installer/2.1.0/vmis/ui/null.py", line 13, in <module>     from vmis.ui import console   File "/usr/lib/vmware-installer/2.1.0/vmis/ui/console.py", line 9, in <module>     import curses   File "/usr/lib/vmware-installer/2.1.0/python/lib/curses/__init__.py", line 15, in <module>     from _curses import * ImportError: libncursesw.so.5: cannot open shared object file: No such file or directory I have two python versions installed, 3.5.2 and 2.7.12 and both can import curses, so I assume this is with the VMWare provided python which is linked to ncurses 5 (my system has only ncurses 6 installed). I am also not sure why it is trying to run the console version at all, as this is being triggered from the GUI after it downloaded the vmware tools update. Shouldn't it be launching the --gtk version (which does appear to work if I run it manually from the command line)?
I use Arch Linux and several times have had the same problem. Here's what was happening to me, and I assume you as well: Your kernel version upgraded. VMWare when launched noticed this and tri... See more...
I use Arch Linux and several times have had the same problem. Here's what was happening to me, and I assume you as well: Your kernel version upgraded. VMWare when launched noticed this and tried to recompile its kernel modules for your new version. Some kernel function, struct element, variable name, etc has changed in the kernel source and the build fails. VMWare cannot load the required module(s) because it couldn't be compiled. The solution is to manually patch vmware's kernel module source code so that they all build, and repackage that code in the place that Workstation will look for it next time it runs. Here's a brief summary of that process if you want to try it: https://wiki.archlinux.org/index.php/VMware#Kernel_modules_fail_to_build_after_Linux_4.7
This doesn't solve the original problem (or my problem) because it won't help on OSes without vmtools or on any system prior to tools startup (during boot). In VirtualBox I can just drag the wind... See more...
This doesn't solve the original problem (or my problem) because it won't help on OSes without vmtools or on any system prior to tools startup (during boot). In VirtualBox I can just drag the window larger and it scales perfectly... I'm also on a Yoga 2 Pro (3200x1800) using WS12, but on a Linux host (Arch 64 bit).