Linux VMWare View 5.0 client with “USB probros”

In continuation of my previous note We are friends of Thinstation 5.0 and a VMWare View 5.0 client with a full-featured USB-redirect , for tests it was necessary to build a client version 5.0 with a “USB call” that would work in Linux. Since I know best Ubuntu - the package was collected for it. Ready package version 5.0 under the cut.

Let me explain why I had to reinvent the wheel: there is simply no “USB forwarding” in the official client from the Ubuntu partner repository, and the client version 4.6 from the installation article is not suitable for various reasons. Therefore, the official VMWare View 1.4 client for HP ThinPro series thin clients was taken. Unfortunately, dpkg completely ignored the package that I picked out, but I just didn’t want to unpack it into my system - so I took it to repack.
As a result, I collected it with such differences from the above-mentioned "original":

• the inclusion of the functionality of "USB probros" during the installation of the package;
• replacement of icons, unused discarded, necessary taken from the official client;
• client registration in the menu, among other programs installed in the system;
• left agreement and certificate in English only.

Theoretically, if you unpack the .deb package as an archive, the client should work in any popular distribution. Of the vital dependencies, I noticed only the library libssl0.9.8, which is not in the base Ubuntu 11.10 distribution. Fix this:
apt-get install libssl0.9.8

Now install the package:
dpkg -i vmware-view-client.deb

The assembled .deb package can be collected here . The mirror . Works fine, tested on several machines.
Converted by alien. Rpm package we take here . The mirror . Unfortunately, I could not check it, please, write down who can test his work.

For the test connected flash drive. Subsequently, it turned out that on the test laptop there is also a bluetooth hanging on the USB bus. Everything works, achieved the task. Below is a log.

vmware-view-usb-8007.log:

 Apr 20 19:41:48.611: vmware-usb| Log for VMware Workstation pid=8007 version=7.1.0 build=build-636740 option=Release Apr 20 19:41:48.611: vmware-usb| The process is 32-bit. Apr 20 19:41:48.611: vmware-usb| Host codepage=UTF-8 encoding=UTF-8 Apr 20 19:41:48.611: vmware-usb| Starting... Apr 20 19:41:48.612: vmware-usb| USB: Unable to open "/proc/bus/usb/devices" (No such file or directory). Apr 20 19:41:48.612: vmware-usb| USBGL: USB Sysfs found at /dev/bus/usb Apr 20 19:41:48.732: unknown| Remote USB status reported, state: available Apr 20 19:41:48.732: unknown| Device attributes: Name: ASUSTek Bluetooth Adapter, Id: vid2821(0x0b05)&pid5906(0x1712), Family: , Path: bus4,port3 Apr 20 19:41:48.732: unknown| 'ASUSTek Bluetooth Adapter' is allowed. Path: 578 Apr 20 19:41:48.733: unknown| InitDbus: Unable to connect to DBus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Apr 20 19:41:48.733: unknown| ASUSTek Bluetooth Adapter is being redirected Apr 20 19:41:49.611: vmware-usb| USBG: CONNREQ: Dequeued head request after 878 ms for [name:ASUSTek\ Bluetooth\ Adapter vid:0b05 pid:1712 path:4/2 speed:full family:other,wireless,bluetooth] Apr 20 19:41:49.613: vmware-usb| Unexpected error received 2 from USBDEVFS_CONNECTINFO Apr 20 19:41:49.869: vmware-usb| Claimed 'ASUSTek Bluetooth Adapter' device, Plug No: 1 Apr 20 19:41:49.921: vmware-usb| Sending device plug-in to desktop, plug No:1 Apr 20 19:41:49.922: vmware-usb| Sent device plug-in to desktop, plug No:1 Apr 20 19:41:49.927: unknown| Remote plug-in response, Plug No: 1, RespType: Ok, Remote Version: 3 Apr 20 19:41:49.927: unknown| Device attributes: Name: Kingston DT101 G2, Id: vid2385(0x0951)&pid5698(0x1642), Family: storage, Path: bus1,port4 Apr 20 19:41:49.927: unknown| 'Kingston DT101 G2' is allowed. Path: 786 Apr 20 19:41:49.928: unknown| InitDbus: Unable to connect to DBus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Apr 20 19:41:49.928: unknown| Kingston DT101 G2 is being redirected Apr 20 19:41:49.929: vmware-usb| Device doesn't have a product string. Apr 20 19:41:49.929: vmware-usb| USBG: CONNREQ: Dequeued head request after 1 ms for [name:Kingston\ DT101\ G2 vid:0951 pid:1642 path:1/3 speed:high family:storage] Apr 20 19:41:49.986: vmware-usb| Claimed 'Kingston DT101 G2' device, Plug No: 2 Apr 20 19:41:49.988: vmware-usb| Sending device plug-in to desktop, plug No:2 Apr 20 19:41:49.988: vmware-usb| Sent device plug-in to desktop, plug No:2 Apr 20 19:41:50.199: unknown| Remote plug-in response, Plug No: 2, RespType: Ok, Remote Version: 3 Apr 20 19:41:50.650: vmware-usb| USBGL: SETCONFIGURATION=1 failed -1:16:Device or resource busy, work around triggered Apr 20 19:42:05.776: vmware-usb| Disconnecting all devices Apr 20 19:42:06.119: vmware-usb| USBGL: RELEASEINTERFACE=0 failed -1:22:Invalid argument Apr 20 19:42:06.119: vmware-usb| USBGL: USBDEVFS_CONNECT(0) failed -1:16:Device or resource busy Apr 20 19:42:06.119: vmware-usb| USBGL: RELEASEINTERFACE=1 failed -1:22:Invalid argument Apr 20 19:42:06.119: vmware-usb| USBGL: USBDEVFS_CONNECT(1) failed -1:16:Device or resource busy Apr 20 19:42:06.119: vmware-usb| USBGL: RELEASEINTERFACE=2 failed -1:22:Invalid argument Apr 20 19:42:06.119: vmware-usb| Released device, Plug No: 1 Apr 20 19:42:06.370: vmware-usb| USBGL: RELEASEINTERFACE=0 failed -1:22:Invalid argument Apr 20 19:42:06.370: vmware-usb| USBGL: USBDEVFS_CONNECT(0) failed -1:16:Device or resource busy Apr 20 19:42:06.370: vmware-usb| Released device, Plug No: 2 Apr 20 19:42:06.370: vmware-usb| Disconnecting all devices completed Apr 20 19:42:06.370: vmware-usb| Exiting.