# Anyone succuessfully run Vision 8.1 on a chrome book, chrome os? **URL:** \ **Category:** Ignition\ **Tags:** ignition81, vision\ **Created:** [April 15, 2024, 4:47pm UTC](https://forum.inductiveautomation.com/t/anyone-succuessfully-run-vision-8-1-on-a-chrome-book-chrome-os/88836 "2024-04-15T16:47:55Z")\ **Posts on this page:** 1\ **Showing post:** 4
**Author:** ![Paul\_Clearfire](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul_clearfire/32/71718_2.png) [@Paul\_Clearfire](https://forum.inductiveautomation.com/u/Paul_Clearfire)\ **Post date:** [February 15, 2025, 1:15am UTC](https://forum.inductiveautomation.com/t/anyone-succuessfully-run-vision-8-1-on-a-chrome-book-chrome-os/88836/4 "2025-02-15T01:15:01Z")
OK - Here are my fully fleshed out and tested instructions: ## Installing Vision Client on ChromeOS and Chrome OS Flex ### Prerequisites 1. The machine should be running either ChromeOS or ChromeOS Flex 2. Enable the Linux Developer Environment: - The following instructions are taken from [this Google article](https://support.google.com/chromebook/answer/9145439?hl=en), which also has tips for troubleshooting and installing other linux apps. - On ChromeOS/Flex, at the bottom right, select the time. - Select Settings ![](https://us1.discourse-cdn.com/inductiveautomation/original/3X/3/7/370fff8d6c65ba090549bb4031d1fe55f8b12767.png) ![and then](https://us1.discourse-cdn.com/inductiveautomation/original/3X/7/1/7125bf051c3ca651f9ee19f396b118bccda4e9af.png) About ChromeOS ![and then](https://us1.discourse-cdn.com/inductiveautomation/original/3X/7/1/7125bf051c3ca651f9ee19f396b118bccda4e9af.png) Developers. - Next to "Linux development environment," select Set up. - Follow the on-screen instructions. Setup can take 10 minutes or more - A terminal window opens to a Debian environment. You can run Linux commands, install more tools using the APT package manager, and customize your shell. - Some notes about the Linux Developer Environment. - Enabling this in ChromeOS creates a “virtual machine” that runs a limited version of LinuxOS Debian (called crostini) alongside ChromeOS. It is capable of running most of what is available in a typical Debian Linux installation, but not everything. - The virtual machine is named “Penguin” by default. So, when you run a terminal session, you will be `username@penguin`. - You can start a linux terminal session from the applications menu in Chrome OS (available via the little circle at the bottom left of the screen). The icon looks like… a penguin… sort of. 1. Install Java Runtime Environment (JRE) for Debian - From the wiki at debian dot org: - From the terminal run: ```sh sudo apt update ``` Then run: ```sh sudo apt-get install default-jre ``` ## Install Vision Client Launcher 1. Navigate to your Vision gateway and download the installer for Linux. The installer is compressed in a .tar package named `visionclientlauncher.tar.gz` 2. Download the installer to the “Linux Files” directory in ChromeOS or move it there after you download it (use the ChromeOS “FIles” app to find it at My Files/Linux Files, or use the `mv` command from the Linux terminal to move it to your home directory). The next few steps are based on the threads from [this post at the Inductive Automation Users Forum](https://forum.inductiveautomation.com/t/install-vision-client-launcher-for-linux/45024/8?page=2): 1. Unpack the `visionclientlauncher.tar` package: 2. Move the unpacked `visonclientlauncher/` folder to the appropriate location, depending on if you’re installing for all users or just one: 3. Change the permissions visionclientlauncher folder: 4. Within visionclientlauncher/app, change the visionclientlauncher.sh and the launcher-vision-client-linux.jar file to be executable - 5. Using Nano, vi, or your preferred text editor, edit the copied version of the `visionclientlauncher.desktop` file that you copied in step 3 above to change the paths accordingly (see below). Note that because these directories are protected, you'll need to invoke your text editor as sudo. 6. You should now be able to load the Vision Client Launcher from the Applications pane (access from the circle icon at the bottom left of the screen) 7. Add the icon shortcut to the taskbar. ## Example edits for the visionclientlauncher.desktop file The `visionclientlauncher.desktop` file is very important, as it provides the OS with the information needed to open the Vision Client Launcher when a user clicks on the icon in the applications folder in the Chrome OS GUI. Thus, if you don’t get this right, the application simply won’t load. The reference to the icon tells the GUI what icon to use in the applications folder and other locations. If you get this wrong then the GUI will simply choose the default “linux app” penguin icon. I was using a shared machine, and needed the Vision program to be available just to me. So I moved the `visionclientlauncher/` folder to the root level of my home directory at `/home/paulc/`. Then I edited the `visionclientlauncher.desktop` file to look like this: ```python [Desktop Entry] Encoding=UTF-8 Version=1.1 Type=Application Terminal=False Icon=/home/paulc/visionclientlauncher/app/launcher.png Name=Vision Client Launcher Exec=/home/paulc/visionclientlauncher/app/visionclientlauncher.sh -Dapp.h Path=/home/paulc/visionclientlauncher/app/ ``` If you’re installing for all users, and you’ve saved to `/usr/local/` then your `visionclientlauncher.desktop` file should look like this: ```python [Desktop Entry] Encoding=UTF-8 Version=1.1 Type=Application Terminal=False Icon=/usr/local/visionclientlauncher/app/launcher.png Name=Vision Client Launcher Exec=/usr/local/visionclientlauncher/app/visionclientlauncher.sh -Dapp.h Path=/usr/local/visionclientlauncher/app/ ``` You get the idea. The paths for Icon, Exec and Path just need to match whatever location you’ve chosen. Good luck! --- _[View the full topic](https://forum.inductiveautomation.com/t/anyone-succuessfully-run-vision-8-1-on-a-chrome-book-chrome-os/88836)._