This guide demonstrates the installation process using the Ubuntu 22.04.3LTS system as an example.
Method 1: Snap Method
- Install snap: - sudo apt install snapd- Refer to the link for installing snap on other Linux systems: Reference 
- Install OneKey App in two ways: - Open the link: https://snapcraft.io/onekey-wallet and install it directly from the snap store. 
- Install it using the command line: - sudo snap install onekey-wallet
 
- Download and install bridge (Download link) 
- After downloading, switch to the directory where the bridge is located and execute the following command to install: - sudo dpkg -i onekey-bridge-2.2.0-amd64.deb
- Access the address http://127.0.0.1:21320/status/ in your browser to ensure the page opens and shows "Connected devices: 1". 
- Complete the installation. Open OneKey App and select "Connect Hardware Wallet". 
Method 2: Directly Download and Run AppImage
- Download the AppImage file. 
- Install the necessary dependencies with the command: - sudo apt-get install fuse libfuse. (Refer to the link for more about dependencies and their installation on different systems)
- Switch to the directory where the AppImage file is located and give the file executable permissions: - chmod +x OneKey-Wallet-4.18.0-linux-x86_64.AppImage
- Install using the current user (non-root): - ./OneKey-Wallet-4.18.0-linux-x86_64.AppImage
If you encounter the error "Missing X Server or $DISPLAY" during execution, please install the related graphical environment components. For Ubuntu or Debian systems, you can install xorg.
Solution for when Linux Mint cannot detect hardware devices
When using a OneKey hardware wallet on a Linux Mint system, you need to install UDEV rules so the application can connect to the device correctly.
1.Go to https://data.onekey.so/onekey.rules and copy the UDEV rules.
2.Create a new file at /etc/udev/rules.d/99-onekey.rules and paste the rules above, then save it.
3.After completing the above, enter the following in the terminal:
sudo udevadm control --reload-rules
Do not manually change the permissions of device files under /dev, such as using chmod or chown.
Such changes are temporary and will not persist after a reboot or re-plugging the device, and loosening permissions may introduce security risks.



