Refresh artifacts on ChromeOS Linux client

Forums / NoMachine for Linux / Refresh artifacts on ChromeOS Linux client

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
  • #27122

    I’ve read on here where others have gotten NoMachine to work from a Chromebook well, but I am having a bad issue that makes it unusable until I can resolve it.
    It is best described as failure to refresh a changed portion of the screen. The mouse controls the server, but I see black square areas where things have changed on the server’s display, but not on the client’s window of it. This occurs whether a physical display is connected or headless with an emulated display dongle on the server. The black boxes sometimes refresh if I do a window resize. But then they return if something else changes.
    I have attached some client screenshots of the issue, sometimes I just get black screen on the client.

    NoMachine Free 6.9.2 on client and server.
    My server:
    Ryzen 5 2400G (so it has an integrated APU, no separate GPU card)
    Zorin 15.2 (based on Ubuntu 18.04 LTS)
    Zorin running Xorg, not Wayland, and Gnome desktop

    Connected over my local network to my Client:
    Chromebox with Intel I7
    Play store says the NoMachine Android client is not compatible with my device, so, I have installed the NoMachine Lunux client on ChromeOS’s Debian implementation (Buster, Kernel 4.19)

    Previous posts suggest display dongle and restarting the nxserver and I’ve done those; is there a setting that Chromebooks/Boxes need for the Linux client to run right?


    Hi. There seem to be an issue with the GPU acceleration in the Linux container. You can try this to work around it, by hoping next Chrome OS version will include a fix (this was not happening in Chrome OS 76, for example):

    1. Open Chrome
    2. In the address bar type chrome://flags/#crostini-gpu-support
    3. In the opening page change the combo from “Default” to “Disabled”
    4. Reboot by clicking “Restart now”

    As for supporting Chromebox, the reason why you see the app as not compatible should be due to the requirement of a touch interface on the device. This requirement should no longer be needed because the NoMachine app works equally well with touch and mouse input, so we’ll remove it and verify if it is enough.


    Wow, disabling the GPU works great, thanks!

    I’m up and running on the Linux app.

    I’ll try the Android app again when I see it appear in the store, but all’s well for now.


Viewing 3 posts - 1 through 3 (of 3 total)

This topic was marked as solved, you can't post.