NoMachine on Chromebook is messed up

[ukscone]

I had NoMachine working on a beta channel v90 running Chromebook perfectly however tonight I ended up updating both ChromeOS & NoMachine and now the GUI is well and truly borked.

http://russelldavis.org/screenshots/Screenshot%202021-04-23%2010.44.36%20PM.png

http://russelldavis.org/screenshots/Screenshot%202021-04-23%2010.44.45%20PM.png

http://russelldavis.org/screenshots/Screenshot%202021-04-23%2010.45.22%20PM.png

http://russelldavis.org/screenshots/Screenshot%202021-04-23%2010.45.36%20PM.png

http://russelldavis.org/screenshots/Screenshot%202021-04-23%2010.46.01%20PM.png

http://russelldavis.org/screenshots/Screenshot%202021-04-23%2010.47.30%20PM.png

All the shared libs and everything seem to be ok

Anyone seen anything like this before, know the immediate fix or know how to start debugging, tracking down the problem and how to fix as I really need to get this working again as I use it for accessing all my Pi’s and Windows machines on my network as NoMachine works better than [removed] or [removed] for my needs.

thanks

 

[Carin]

Hi ukscone,

Can you please let us know if you’re using the Linux version of the NoMachine client on your Chromebook?

[ukscone]

Yes, I’m using the Linux version of NoMachine however it actually seems to be a now known problem with ChromeOS that they introduced in their latest update. They are working on a proper fix but for others who might be in the same situation as me a temporary fix is adding the line: Environment="VIRGL_DEBUG=noemubgra" to the file /etc/systemd/user/sommelier-x@0.service/cros-sommelier-x-override.conf

 

 

[Author]

Posts