Britgirl

[Britgirl]

Which distribution of Linux and its version do you use?
You can submit logs to forum[at]nomachine[dot]com using the title of this topic as the subject of your email. Thanks.

Desktop environment is also useful to know.

[Britgirl]

I understand you are connecting to localhost. Can you send us the logs? See here for instructions and send them to forum[at]nomachine[dot]com. Please use the title of your topic in the subject of the email.

https://kb.nomachine.com/DT07S00243

[Britgirl]

We have reproduced it! A Trouble Report will be opened and queued up for fixing. Thanks for reporting.

[Britgirl]

Not sure what to make of your response, Britgirl, but I emailed the file as an attachment to the specified email address with the number (#46174) of the post it should be attached to.

I was referring to your attachment which didn’t attach 🙂
You previously wrote ” I ran xev on the client machine and included the results in the “keys.txt” attached file.” and it wasn’t attached.  So I asked for you to send it. But you’re all set now anyway.

About your comment on attachments, we’ll make a point of adding what types of attachment are permitted so that users know. Right now only the size is stated. That said, some attachments don’t pass the spam filter because of unusual characters within. We’ll get this checked out. Thanks again for your feedback.

Happy nomachining!

[Britgirl]

Quite a lot of information is missing. Please provide:

– NoMachine product and version on local and remote machine (free version, Workstation, etc).

– Whether the problem arises connecting to a physical or a virtual display.

– Remote and local Windows/Mac/Linux version (Windows XP/7/8, OS X 10.x, Ubuntu xyz, Mint x.y, etc.).

– If on Linux, desktop version (GNOME. KDE, whatever) on client and on server.

– Are you using Pulse Audio or Pipewire

– Precise steps to reproduce the issue.

 

[Britgirl]

Hi, a quick update. We were unable to reproduce the problem. Can you update to the latest version, 8.10, both sides and let us know if anything has changed?

[Britgirl]

Submit a report to Wacom or HP by all means. We will investigate from our side what needs to be done.

[Britgirl]

Ok thanks for letting us know.

[Britgirl]

Hi, your attachment didn’t attach. Can you submit any attachments to forum[at]nomachine[dot]com? Thanks!

[Britgirl]

Everyone, please follow the workaround posted in another issue, but related:

How to speed up NM server startup at boot

Thanks!

[Britgirl]

Thanks for submitting the tip about disabling animations. We’ll certainly check that out.

Some tips if it happens again:

– disable hardware decoding on the device you are connecting from (if you can bring the connection menu up you can do it in the Display settings panel, or do it in the player.cfg file. Follow the instructions here https://kb.nomachine.com/AR07U01202)

–  and/or disable hardware encoding to exclude any problem with drivers (server settings -> server performance -> uncheck “Use hardware encoding”)

– If the server is headless, try to attach a monitor

– If nothing helps, collect logs and send to us https://kb.nomachine.com/DT07S00243

[Britgirl]

Hi, can we see the player logs (the Windows machine you are connecting from)? Please see the instructions here:
https://kb.nomachine.com/DT07S00243, section “Fourth Step: Collect Client Side Logs”.

 

[Britgirl]

Hi, this

connects to the physical desktop, the screens turn black and then slowly begin fading between gray and black,

is because you activated screen-blanking and have the screen shading effect enabled. If you don’t want the fading affect, you can disable this. Go to server settings on the machine you are connecting to -> Server -> Security -> tick the second checkbox “Disable the screen shading effect….”.

punctuated by a split-second flash of the actual desktop. Some of the keys don’t work.

This is not normal, and we are trying to reproduce.

[Britgirl]

What I forgot to ask is for the logs, so we can verify that it is the same problem I mentioned. It would be useful to have the logs from the Ubuntu host; you can extract them using the instructions here: https://kb.nomachine.com/DT07S00243 and then submit them directly to forum[at]nomachine[dot]com.

Can you also show us the output of the following:

sudo netstat -anlp | grep egl

if the output is empty, then send the output of

sudo /usr/NX/bin/nxserver --eglcapture yes and sudo getcap /usr/bin/gnome-shell

Thanks!

[Britgirl]

A workaround that you can try is adding graphical.target to nxserver.service in After=.

nxserver.service can be in one of these paths:

/lib/systemd/system/nxserver.service
/usr/lib/systemd/system/nxserver.service

with root permissions you should add graphical.target to the following line:

After = syslog.target network.target network-online.target sshd.service http-daemon.target.service htd.service

to look like this

After = syslog.target network.target network-online.target sshd.service http-daemon.target.service htd.service graphical.target

Then, still as root

systemctl daemon-reload

and

systemctl restart nxserver.service

Does this change anything?

[Author]

Posts