Results 1 to 12 of 12

Thread: VMWare tools not working completely on kernel 3.18

  1. #1
    Join Date
    2013-Mar
    Location
    Brazil
    Posts
    52

    VMWare tools not working completely on kernel 3.18

    Today is a great day: the kernel was upgraded from 3.14 to 3.18.
    But we have an issue: VMWares tools, most specifically HGFS (Host-Guest File System) were unable to compile and it is not working. So, if you use vmware feature to share folders between host and guest, I suggest you to wait for a solution and stay on 3.14.

    If anyone has a solution, please, report bellow.

  2. #2
    Join Date
    2013-May
    Location
    indonesia
    Posts
    20
    first you must install your linux headers on kernel 3.18:
    sudo apt-get install linux-headers-`uname -r`

    then reinstall vmware tools ...
    i've done ..
    [-] INDONESIA [-]

  3. #3
    Join Date
    2013-Mar
    Location
    Brazil
    Posts
    52
    Thanks for the tip!
    I've done it before and didn't work.

    Now, at 2015-02-03 12:57 UTC, I can't find kernel 3.18 on repositories. Have these kernel (3.18) removed from the repositories? Can someone confirm?

  4. #4
    Join Date
    2013-Mar
    Location
    Brazil
    Posts
    52
    Ok, at 2015-02-03 20-04 UTC, I've noticed the responsible team has put back into the repositories the 3.18 kernel again. And again, the HGFS is not working.

    I've taken the steps bellow:
    - uninstall vmware using vmware-uninstall-tools.pl
    - reboot
    - apt-get update
    - apt-get upgrade, then comes 3.18
    - apt-get dist-upgrade, then comes more 3.18
    - reboot
    - apt-get install linux-headers-$(uname -r)
    - reboot
    - then finally, vmware-install.pl

    The "uname -a" of this new kernel is "Linux kali 3.18.0-kali1-686-pae #1 SMP Debian 3.18.3-1~kali4 (2015-01-22) i686 GNU/Linux".


    The error message that appear is:

    Before you can compile modules, you need to have the following installed...

    make
    gcc
    kernel headers of the running kernel


    Searching for GCC...
    Detected GCC binary at "/usr/bin/gcc".
    The path "/usr/bin/gcc" appears to be a valid path to the gcc binary.
    Would you like to change it? [no]

    Searching for a valid kernel header path...
    Detected the kernel headers at
    "/lib/modules/3.18.0-kali1-686-pae/build/include".
    The path "/lib/modules/3.18.0-kali1-686-pae/build/include" appears to be a
    valid path to the 3.18.0-kali1-686-pae kernel headers.
    Would you like to change it? [no]

    Using kernel build system.
    make: Entrando no diretório `/tmp/modconfig-JvObjh/vmhgfs-only'
    /usr/bin/make -C /lib/modules/3.18.0-kali1-686-pae/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= modules
    make[1]: Entrando no diretório `/usr/src/linux-headers-3.18.0-kali1-686-pae'
    CC [M] /tmp/modconfig-JvObjh/vmhgfs-only/backdoor.o
    CC [M] /tmp/modconfig-JvObjh/vmhgfs-only/backdoorGcc32.o
    CC [M] /tmp/modconfig-JvObjh/vmhgfs-only/bdhandler.o
    CC [M] /tmp/modconfig-JvObjh/vmhgfs-only/cpName.o
    CC [M] /tmp/modconfig-JvObjh/vmhgfs-only/cpNameLinux.o
    CC [M] /tmp/modconfig-JvObjh/vmhgfs-only/cpNameLite.o
    CC [M] /tmp/modconfig-JvObjh/vmhgfs-only/dentry.o
    CC [M] /tmp/modconfig-JvObjh/vmhgfs-only/dir.o
    CC [M] /tmp/modconfig-JvObjh/vmhgfs-only/file.o
    CC [M] /tmp/modconfig-JvObjh/vmhgfs-only/filesystem.o
    CC [M] /tmp/modconfig-JvObjh/vmhgfs-only/fsutil.o
    CC [M] /tmp/modconfig-JvObjh/vmhgfs-only/hgfsBd.o
    CC [M] /tmp/modconfig-JvObjh/vmhgfs-only/hgfsEscape.o
    CC [M] /tmp/modconfig-JvObjh/vmhgfs-only/hgfsUtil.o
    CC [M] /tmp/modconfig-JvObjh/vmhgfs-only/inode.o
    CC [M] /tmp/modconfig-JvObjh/vmhgfs-only/link.o
    CC [M] /tmp/modconfig-JvObjh/vmhgfs-only/message.o
    CC [M] /tmp/modconfig-JvObjh/vmhgfs-only/module.o
    /tmp/modconfig-JvObjh/vmhgfs-only/inode.c: In function ‘HgfsPermission’:
    /tmp/modconfig-JvObjh/vmhgfs-only/inode.c:1920:7: error: ‘struct dentry’ has no member named ‘d_alias’
    /tmp/modconfig-JvObjh/vmhgfs-only/inode.c:1920:7: warning: initialization from incompatible pointer type [enabled by default]
    /tmp/modconfig-JvObjh/vmhgfs-only/inode.c:1920:7: error: ‘struct dentry’ has no member named ‘d_alias’
    /tmp/modconfig-JvObjh/vmhgfs-only/inode.c:1920:7: error: ‘struct dentry’ has no member named ‘d_alias’
    /tmp/modconfig-JvObjh/vmhgfs-only/inode.c:1920:7: error: ‘struct dentry’ has no member named ‘d_alias’
    /tmp/modconfig-JvObjh/vmhgfs-only/inode.c:1920:7: error: ‘struct dentry’ has no member named ‘d_alias’
    /tmp/modconfig-JvObjh/vmhgfs-only/inode.c:1920:7: warning: initialization makes pointer from integer without a cast [enabled by default]
    /tmp/modconfig-JvObjh/vmhgfs-only/inode.c:1920:7: error: ‘struct dentry’ has no member named ‘d_alias’
    make[4]: ** [/tmp/modconfig-JvObjh/vmhgfs-only/inode.o] Erro 1
    make[4]: ** Esperando que outros processos terminem.
    make[3]: ** [_module_/tmp/modconfig-JvObjh/vmhgfs-only] Erro 2
    make[2]: ** [sub-make] Erro 2
    make[1]: ** [all] Erro 2
    make[1]: Saindo do diretório `/usr/src/linux-headers-3.18.0-kali1-686-pae'
    make: ** [vmhgfs.ko] Erro 2
    make: Saindo do diretório `/tmp/modconfig-JvObjh/vmhgfs-only'

    The filesystem driver (vmhgfs module) is used only for the shared folder
    feature. The rest of the software provided by VMware Tools is designed to work
    independently of this feature.

    If you wish to have the shared folders feature, you can install the driver by
    running vmware-config-tools.pl again after making sure that gcc, binutils, make
    and the kernel sources for your running kernel are installed on your machine.
    These packages are available on your distribution's installation CD.
    [ Press Enter key to continue ]


    Really anoying! This way it is not possible to use VMWare HGFS with Kali kernel 3.18.

    Anyone with a solution is welcome.

    PS: Before somenone ask: make, gcc and linux kernels are all installed.

  5. #5
    Join Date
    2013-Mar
    Location
    Brazil
    Posts
    52
    Solution found. I hope VMWare release a official solution soon, until this moment arrive, it is possible to use this:
    http://docs.kali.org/general-use/ins...ols-kali-guest

  6. #6
    PePeLeGal,

    I am having the same issue and I went to http://docs.kali.org/general-use/ins...ols-kali-guest

    At the command:
    apt-get install git gcc make linux-headers-$(uname -r)
    It says: it is unable to locate package linux-headers-3.12-kali-amd64
    And : couldn't find any package by regx 'liniux-headers-3.12-kali-amd64'

    Any suggestions?

  7. #7
    Join Date
    2015-Feb
    Posts
    9
    Tried to install the VMware Tools Patches https://github.com/rasa/vmware-tools-patches as explained here
    but it still fails to patch hgfs modules and shared folders do not work.
    Running VMware WS 10.0.4 and VMwareTools-9.6.2-1688356.tar.gz (which is supposed to work) under Linux kali 3.18.0-kali1-amd64

    Any hint?
    Thanks a lot

  8. #8
    Join Date
    2015-Feb
    Posts
    9
    I paste here some messages from the untar-and-patch-and-compile.sh

    ....
    *** Applying vsock/vsock-sk_data_ready-kernel-3.15-tools-9.6.2.patch ...
    patching file linux/notify.c
    patching file linux/notifyQState.c
    *** Applying vmci/vmware9.k3.8rc4.patch ...
    patching file linux/driver.c
    Reversed (or previously applied) patch detected! Assuming -R.
    Hunk #1 succeeded at 128 with fuzz 1 (offset 4 lines).
    Hunk #2 succeeded at 1747 (offset -3 lines).
    Hunk #3 succeeded at 1975 (offset -3 lines).
    *** Applying vmhgfs/vmhgfs-vfs_readlink-kernel-3.16-tools-9.6.2.patch ...
    patching file file.c
    patching file link.c
    patching file shared/compat_fs.h
    *** Applying vmhgfs/vmhgfs-wait_on_bit-kernel-3.17-tools-9.6.2.patch ...
    patching file page.c
    *** Applying vmhgfs/vmhgfs-smp_mb_before_clear_bit-3.18-tools-9.9.0.patch ...
    patching file page.c
    Hunk #1 succeeded at 1456 (offset -222 lines).
    *** Applying vmhgfs/vmhgfs-rename_deprecated-kernel-3.18.1-tools-9.6.1.patch ...
    patching file shared/vm_assert.h
    *** Skipping vmhgfs/vmhgfs-uid-gid-kernel-3.12-tools-9.6.1.patch: did not apply cleanly
    *** Skipping vmhgfs/vmware9.compat_mm.patch: did not apply cleanly
    *** Applying vmhgfs/compat_dcache.h.patch ...
    patching file shared/compat_dcache.h
    *** Skipping vmhgfs/vmhgfs-d_set_type-kernel-3.18.1-tools-9.6.1.patch: did not apply cleanly
    *** Skipping vmhgfs/vmhgfs-d_count-kernel-3.11-tools-9.6.0.patch: did not apply cleanly
    *** Skipping vmhgfs/vmhgfs-d_alias-kernel-3.17.7-tools-9.9.0.patch: did not apply cleanly
    *** Applying vmhgfs/vmhgfs-3.15-vfs_readlink.patch ...
    patching file link.c
    Hunk #2 succeeded at 193 (offset 4 lines).
    *** Skipping vmhgfs/patch_inode.c.patch: did not apply cleanly
    *** Applying vmblock/vmblock.3.10.patch ...
    patching file linux/control.c
    *** Applying vmblock/vmblock.3.11.patch ...
    patching file linux/file.c
    *** Applying vmblock/vmblock-vfs_readlink-kernel-3.15-tools-9.6.2.patch ...
    patching file linux/inode.c
    Hunk #1 succeeded at 177 (offset -1 lines).
    .....
    ...
    The VMware Host-Guest Filesystem allows for shared folders between the host OS
    and the guest OS in a Fusion or Workstation virtual environment. Do you wish
    to enable this feature? [yes]

    The module vmhgfs has already been installed on this system by another package
    but has been marked for clobbering and will be overridden.

    Using 2.6.x kernel build system.
    make: Entering directory `/tmp/modconfig-qQT7gg/vmhgfs-only'
    /usr/bin/make -C /lib/modules/3.18.0-kali1-amd64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= modules
    make[1]: Entering directory `/usr/src/linux-headers-3.18.0-kali1-amd64'
    CC [M] /tmp/modconfig-qQT7gg/vmhgfs-only/backdoorGcc64.o
    CC [M] /tmp/modconfig-qQT7gg/vmhgfs-only/backdoor.o
    CC [M] /tmp/modconfig-qQT7gg/vmhgfs-only/cpName.o
    CC [M] /tmp/modconfig-qQT7gg/vmhgfs-only/bdhandler.o
    CC [M] /tmp/modconfig-qQT7gg/vmhgfs-only/cpNameLinux.o
    CC [M] /tmp/modconfig-qQT7gg/vmhgfs-only/cpNameLite.o
    CC [M] /tmp/modconfig-qQT7gg/vmhgfs-only/dentry.o
    CC [M] /tmp/modconfig-qQT7gg/vmhgfs-only/dir.o
    CC [M] /tmp/modconfig-qQT7gg/vmhgfs-only/file.o
    CC [M] /tmp/modconfig-qQT7gg/vmhgfs-only/filesystem.o
    CC [M] /tmp/modconfig-qQT7gg/vmhgfs-only/fsutil.o
    CC [M] /tmp/modconfig-qQT7gg/vmhgfs-only/hgfsBd.o
    CC [M] /tmp/modconfig-qQT7gg/vmhgfs-only/hgfsEscape.o
    CC [M] /tmp/modconfig-qQT7gg/vmhgfs-only/hgfsUtil.o
    CC [M] /tmp/modconfig-qQT7gg/vmhgfs-only/inode.o
    CC [M] /tmp/modconfig-qQT7gg/vmhgfs-only/link.o
    /tmp/modconfig-qQT7gg/vmhgfs-only/inode.c: In function ‘HgfsPermission’:
    /tmp/modconfig-qQT7gg/vmhgfs-only/inode.c:1898:7: error: ‘struct dentry’ has no member named ‘d_alias’
    /tmp/modconfig-qQT7gg/vmhgfs-only/inode.c:1898:7: warning: initialization from incompatible pointer type [enabled by default]
    /tmp/modconfig-qQT7gg/vmhgfs-only/inode.c:1898:7: error: ‘struct dentry’ has no member named ‘d_alias’
    /tmp/modconfig-qQT7gg/vmhgfs-only/inode.c:1898:7: error: ‘struct dentry’ has no member named ‘d_alias’
    /tmp/modconfig-qQT7gg/vmhgfs-only/inode.c:1898:7: error: ‘struct dentry’ has no member named ‘d_alias’
    /tmp/modconfig-qQT7gg/vmhgfs-only/inode.c:1898:7: error: ‘struct dentry’ has no member named ‘d_alias’
    /tmp/modconfig-qQT7gg/vmhgfs-only/inode.c:1898:7: warning: initialization makes pointer from integer without a cast [enabled by default]
    /tmp/modconfig-qQT7gg/vmhgfs-only/inode.c:1898:7: error: ‘struct dentry’ has no member named ‘d_alias’
    make[4]: *** [/tmp/modconfig-qQT7gg/vmhgfs-only/inode.o] Error 1
    make[4]: *** Waiting for unfinished jobs....
    make[3]: *** [_module_/tmp/modconfig-qQT7gg/vmhgfs-only] Error 2
    make[2]: *** [sub-make] Error 2
    make[1]: *** [all] Error 2
    make[1]: Leaving directory `/usr/src/linux-headers-3.18.0-kali1-amd64'
    make: *** [vmhgfs.ko] Error 2
    make: Leaving directory `/tmp/modconfig-qQT7gg/vmhgfs-only'

    The filesystem driver (vmhgfs module) is used only for the shared folder
    feature. The rest of the software provided by VMware Tools is designed to work
    independently of this feature.

    If you wish to have the shared folders feature, you can install the driver by
    running vmware-config-tools.pl again after making sure that gcc, binutils, make
    and the kernel sources for your running kernel are installed on your machine.
    These packages are available on your distribution's installation CD.
    [ Press Enter key to continue ]
    ...
    I uninstalled previous vmwaretools version using vmware-uninstall-tools.pl

    Could you kindly point me to a working solution?
    I really need shared folders within my Lab setup.

    Thanks a lot

  9. #9

    A Solution for shared folders but not vmware tools

    I am still having trouble with shared folders with vm-tools but another solution is to use winscp from a windows vm to the kali vm or set up a mount in kali and have your host machine connect to it.

  10. #10
    Join Date
    2015-Feb
    Posts
    9
    Fixed for me upgrading to VMwareTools-9.9.0-2304977.tar.gz

  11. #11
    Join Date
    2015-Mar
    Posts
    1
    Help me plz Guys!

    i want install vmware , but i have error in Kenrnal Module Updeter

    2015-03-02T17:27:05.665-05:00| appLoader| I120: Log for VMware Workstation pid=7405 version=9.0.2 build=build-1031769 option=Release
    2015-03-02T17:27:05.665-05:00| appLoader| I120: The process is 32-bit.
    2015-03-02T17:27:05.665-05:00| appLoader| I120: Host codepage=UTF-8 encoding=UTF-8
    2015-03-02T17:27:05.665-05:00| appLoader| I120: Host is Linux 3.18.0-kali1-686-pae Kali GNU/Linux 1.1.0
    2015-03-02T17:27:05.691-05:00| appLoader| I120: Invocation: "/usr/lib/vmware/bin/vmware-modconfig --launcher=/usr/bin/vmware-modconfig --appname=VMware Workstation --icon=vmware-workstation"
    2015-03-02T17:27:05.691-05:00| appLoader| I120: Calling: "/usr/lib/vmware/bin/vmware-modconfig --launcher=/usr/bin/vmware-modconfig --appname=VMware Workstation --icon=vmware-workstation"
    2015-03-02T17:27:05.691-05:00| appLoader| I120: VMDEVEL not set.
    2015-03-02T17:27:05.691-05:00| appLoader| I120: VMWARE_SHIPPED_LIBS_LIST is not set.
    2015-03-02T17:27:05.691-05:00| appLoader| I120: VMWARE_SYSTEM_LIBS_LIST is not set.
    2015-03-02T17:27:05.691-05:00| appLoader| I120: VMWARE_USE_SHIPPED_LIBS is not set.
    2015-03-02T17:27:05.691-05:00| appLoader| I120: VMWARE_USE_SYSTEM_LIBS is not set.
    2015-03-02T17:27:05.691-05:00| appLoader| I120: Using configuration file /etc/vmware/config.
    2015-03-02T17:27:05.691-05:00| appLoader| I120: Using library directory: /usr/lib/vmware.
    2015-03-02T17:27:05.692-05:00| appLoader| I120: Shipped glib version is 2.24
    2015-03-02T17:27:05.692-05:00| appLoader| I120: System glib version is 2.32
    2015-03-02T17:27:05.692-05:00| appLoader| I120: Using system version of glib.
    2015-03-02T17:27:05.692-05:00| appLoader| I120: Detected VMware library libvmware-modconfig.so.
    2015-03-02T17:27:05.692-05:00| appLoader| I120: Marking libvmware-modconfig.so node as SHIPPED.
    2015-03-02T17:27:05.692-05:00| appLoader| I120: Marking libgcc_s.so.1 node as INVALID.
    2015-03-02T17:27:05.692-05:00| appLoader| I120: Detected VMware library libvmwarebase.so.0.
    2015-03-02T17:27:05.692-05:00| appLoader| I120: Marking libvmwarebase.so.0 node as SHIPPED.
    2015-03-02T17:27:05.692-05:00| appLoader| I120: Marking libgvmomi.so.0 node as INVALID.
    2015-03-02T17:27:05.692-05:00| appLoader| I120: Marking libcds.so node as INVALID.
    2015-03-02T17:27:05.692-05:00| appLoader| I120: Detected VMware library libvmwareui.so.0.
    2015-03-02T17:27:05.692-05:00| appLoader| I120: Marking libvmwareui.so.0 node as SHIPPED.
    2015-03-02T17:27:05.692-05:00| appLoader| I120: Marking libpng12.so.0 node as INVALID.
    2015-03-02T17:27:05.692-05:00| appLoader| I120: Marking libcairomm-1.0.so.1 node as INVALID.
    2015-03-02T17:27:05.692-05:00| appLoader| I120: Marking libcairo.so.2 node as INVALID.
    2015-03-02T17:27:05.692-05:00| appLoader| I120: Marking libpangocairo-1.0.so.0 node as INVALID.
    2015-03-02T17:27:05.692-05:00| appLoader| I120: Marking libpixman-1.so.0 node as INVALID.
    2015-03-02T17:27:05.693-05:00| appLoader| I120: Marking libXfixes.so.3 node as INVALID.
    2015-03-02T17:27:05.693-05:00| appLoader| I120: Marking libXdmcp.so.6 node as INVALID.
    2015-03-02T17:27:05.693-05:00| appLoader| I120: Marking libz.so.1 node as INVALID.
    2015-03-02T17:27:05.693-05:00| appLoader| I120: Marking libview.so.3 node as INVALID.
    2015-03-02T17:27:05.693-05:00| appLoader| I120: Marking librsvg-2.so.2 node as INVALID.
    2015-03-02T17:27:05.693-05:00| appLoader| I120: Marking libxml2.so.2 node as INVALID.
    2015-03-02T17:27:05.693-05:00| appLoader| I120: Marking libart_lgpl_2.so.2 node as INVALID.
    2015-03-02T17:27:05.693-05:00| appLoader| I120: Marking libgtkmm-2.4.so.1 node as INVALID.
    2015-03-02T17:27:05.693-05:00| appLoader| I120: Marking libgdkmm-2.4.so.1 node as INVALID.
    2015-03-02T17:27:05.693-05:00| appLoader| I120: Marking libpangomm-1.4.so.1 node as INVALID.
    2015-03-02T17:27:05.693-05:00| appLoader| I120: Marking libatkmm-1.6.so.1 node as INVALID.
    2015-03-02T17:27:05.693-05:00| appLoader| I120: Marking libglibmm_generate_extra_defs-2.4.so.1 node as INVALID.
    2015-03-02T17:27:05.693-05:00| appLoader| I120: Marking libglibmm-2.4.so.1 node as INVALID.
    2015-03-02T17:27:05.693-05:00| appLoader| I120: Marking libgiomm-2.4.so.1 node as INVALID.
    2015-03-02T17:27:05.693-05:00| appLoader| I120: Marking libsigc-2.0.so.0 node as INVALID.
    2015-03-02T17:27:05.693-05:00| appLoader| I120: Marking libgtk-x11-2.0.so.0 node as INVALID.
    2015-03-02T17:27:05.693-05:00| appLoader| I120: Marking libgdk_pixbuf-2.0.so.0 node as INVALID.
    2015-03-02T17:27:05.693-05:00| appLoader| I120: Marking libgdk-x11-2.0.so.0 node as INVALID.
    2015-03-02T17:27:05.693-05:00| appLoader| I120: Marking libpangox-1.0.so.0 node as INVALID.
    2015-03-02T17:27:05.693-05:00| appLoader| I120: Marking libpangoxft-1.0.so.0 node as INVALID.
    2015-03-02T17:27:05.693-05:00| appLoader| I120: Marking libpangoft2-1.0.so.0 node as INVALID.
    2015-03-02T17:27:05.693-05:00| appLoader| I120: Marking libpango-1.0.so.0 node as INVALID.
    2015-03-02T17:27:05.693-05:00| appLoader| I120: Marking libatk-1.0.so.0 node as INVALID.
    2015-03-02T17:27:05.693-05:00| appLoader| I120: Marking libgthread-2.0.so.0 node as INVALID.
    2015-03-02T17:27:05.693-05:00| appLoader| I120: Marking libgobject-2.0.so.0 node as INVALID.
    2015-03-02T17:27:05.693-05:00| appLoader| I120: Marking libgmodule-2.0.so.0 node as INVALID.
    2015-03-02T17:27:05.693-05:00| appLoader| I120: Marking libglib-2.0.so.0 node as INVALID.
    2015-03-02T17:27:05.693-05:00| appLoader| I120: Marking libgio-2.0.so.0 node as INVALID.
    2015-03-02T17:27:05.693-05:00| appLoader| I120: Marking libgcrypt.so.11 node as INVALID.
    2015-03-02T17:27:05.693-05:00| appLoader| I120: Marking libgpg-error.so.0 node as INVALID.
    2015-03-02T17:27:05.693-05:00| appLoader| I120: Marking libgcr.so.0 node as INVALID.
    2015-03-02T17:27:05.693-05:00| appLoader| I120: Marking libgck.so.0 node as INVALID.
    2015-03-02T17:27:05.693-05:00| appLoader| I120: Marking libXft.so.2 node as INVALID.
    2015-03-02T17:27:05.693-05:00| appLoader| I120: Marking libXrender.so.1 node as INVALID.
    2015-03-02T17:27:05.693-05:00| appLoader| I120: Marking libfreetype.so.6 node as INVALID.
    2015-03-02T17:27:05.693-05:00| appLoader| I120: Marking libfontconfig.so.1 node as INVALID.
    2015-03-02T17:27:05.693-05:00| appLoader| I120: Marking libexpat.so.0 node as INVALID.
    2015-03-02T17:27:05.693-05:00| appLoader| I120: Marking libXrandr.so.2 node as INVALID.
    2015-03-02T17:27:05.693-05:00| appLoader| I120: Marking libXcursor.so.1 node as INVALID.
    2015-03-02T17:27:05.693-05:00| appLoader| I120: Marking libXau.so.6 node as INVALID.
    2015-03-02T17:27:05.693-05:00| appLoader| I120: Marking libXinerama.so.1 node as INVALID.
    2015-03-02T17:27:05.693-05:00| appLoader| I120: Marking libstdc++.so.6 node as INVALID.
    2015-03-02T17:27:05.695-05:00| appLoader| I120: Marking libXdamage.so.1 node as INVALID.
    2015-03-02T17:27:05.695-05:00| appLoader| I120: Marking libXcomposite.so.1 node as INVALID.
    2015-03-02T17:27:05.860-05:00| appLoader| I120: Marking libcurl.so.4 node as INVALID.
    2015-03-02T17:27:05.860-05:00| appLoader| I120: Marking libglade-2.0.so.0 node as INVALID.
    2015-03-02T17:27:06.037-05:00| appLoader| I120: Marking libcrypto.so.0.9.8 node as INVALID.
    2015-03-02T17:27:06.037-05:00| appLoader| I120: Marking libssl.so.0.9.8 node as INVALID.
    2015-03-02T17:27:06.039-05:00| appLoader| I120: Created dependency tree.
    2015-03-02T17:27:06.039-05:00| appLoader| I120: -- Processing libgtkmm-2.4.so.1 --
    2015-03-02T17:27:06.285-05:00| appLoader| I120: libgtkmm-2.4.so.1 validator returned true.
    2015-03-02T17:27:06.285-05:00| appLoader| I120: Marking libgtkmm-2.4.so.1 node as SYSTEM.
    2015-03-02T17:27:06.285-05:00| appLoader| I120: -- Finished processing libgtkmm-2.4.so.1 --
    2015-03-02T17:27:06.293-05:00| appLoader| I120: Accessibility is not enabled.
    2015-03-02T17:27:06.301-05:00| appLoader| I120: Accessibility is not enabled.
    2015-03-02T17:27:06.302-05:00| appLoader| I120: -- Processing libgtk-x11-2.0.so.0 --
    2015-03-02T17:27:06.303-05:00| appLoader| I120: GTK: gtk_major_version: Comparing 2 with 2
    2015-03-02T17:27:06.303-05:00| appLoader| I120: GTK: gtk_minor_version: Comparing 24 with 20
    2015-03-02T17:27:06.303-05:00| appLoader| I120: libgtk-x11-2.0.so.0 validator returned true.
    2015-03-02T17:27:06.303-05:00| appLoader| I120: Marking libgtk-x11-2.0.so.0 node as SYSTEM.
    2015-03-02T17:27:06.303-05:00| appLoader| I120: -- Finished processing libgtk-x11-2.0.so.0 --
    2015-03-02T17:27:06.303-05:00| appLoader| I120: -- Processing libglib-2.0.so.0 --
    2015-03-02T17:27:06.303-05:00| appLoader| I120: GLib: glib_major_version: Comparing 2 with 2
    2015-03-02T17:27:06.303-05:00| appLoader| I120: GLib: glib_minor_version: Comparing 32 with 32
    2015-03-02T17:27:06.303-05:00| appLoader| I120: libglib-2.0.so.0 validator returned true.
    2015-03-02T17:27:06.303-05:00| appLoader| I120: Marking libglib-2.0.so.0 node as SYSTEM.
    2015-03-02T17:27:06.303-05:00| appLoader| I120: -- Finished processing libglib-2.0.so.0 --
    2015-03-02T17:27:06.303-05:00| appLoader| I120: Marking libstdc++.so.6 node as SYSTEM.
    2015-03-02T17:27:06.303-05:00| appLoader| I120: Marking libgcc_s.so.1 node as SYSTEM.
    2015-03-02T17:27:06.303-05:00| appLoader| I120: Marking libXinerama.so.1 node as SYSTEM.
    2015-03-02T17:27:06.303-05:00| appLoader| I120: Marking libXau.so.6 node as SYSTEM.
    2015-03-02T17:27:06.303-05:00| appLoader| I120: Marking libXcursor.so.1 node as SYSTEM.
    2015-03-02T17:27:06.303-05:00| appLoader| I120: Marking libXrender.so.1 node as SYSTEM.
    2015-03-02T17:27:06.303-05:00| appLoader| I120: Marking libXfixes.so.3 node as SYSTEM.
    2015-03-02T17:27:06.303-05:00| appLoader| I120: Marking libXrandr.so.2 node as SYSTEM.
    2015-03-02T17:27:06.303-05:00| appLoader| I120: Marking libexpat.so.0 node as SHIPPED.
    2015-03-02T17:27:06.303-05:00| appLoader| I120: Marking libfontconfig.so.1 node as SYSTEM.
    ---//--

    Thanks!

  12. #12
    Join Date
    2015-May
    Posts
    2
    I was running into the same issue with vmware, when I ran the command uname -r it displayed my kernel as 3.14.0, but when I click on the vmware GUI menu browse button the pop window show I have 3.18.0
    I came across this http://www.blackmoreops.com/2013/10/...-repositories/,
    I did dist upgrade and reboot my vmware worked like a charm.
    Hope this might help.

Similar Threads

  1. Replies: 1
    Last Post: 2016-05-06, 13:33
  2. kali linux 2016.1 vmware tools not working
    By cassidyc in forum TroubleShooting Archive
    Replies: 1
    Last Post: 2016-02-09, 22:21
  3. VMware Tools failed after updating Linux Kernel Headers
    By altjx in forum TroubleShooting Archive
    Replies: 1
    Last Post: 2013-06-05, 08:53

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •