Britgirl

[Britgirl]

Thanks for the feedback on the issues you’ve encountered with 18.04. They’ll be passed on to the testers 😉

[Britgirl]

OK, thanks for the update. If it happens again, please open a new topic.

[Britgirl]

Can you send us the complete logs and backtrace? Send everything to forum[at]nomachine[dot]com.

Instructions for extracting logs (server side) are here: https://www.nomachine.com/AR07K00677
Backtrace here: https://www.nomachine.com/AR09L00810

Thanks!

[Britgirl]

Since the last exchange, a new version has been released, so we recommend you update the software and open a new topic if the problem persists.

[Britgirl]

Although we haven’t yet added it to our official list in the download section, NoMachine runs on Debian Stretch without any problems provided you are not using Wayland protocol. Wayland will be supported in an upcoming maintenance: https://www.nomachine.com/FR10N03221.

[Britgirl]

To check what’s being used in your session, you can look in the C-*/session logs.

If you get:

Info: Using H.264 software encoder.

the encoding is done by the CPU, otherwise you’ll get “hardware encoder” if it is done by the GPU.

If there is no H.264 encoding available on the server, it will fall back to VP8 and in the panel you mention, you will see VP8, not H.264.

More info about H.264 is here:

Enabling the H.264 codec on the NoMachine client host https://www.nomachine.com/AR10K00696

What do I need to do to allow NoMachine software to use H.264? – https://www.nomachine.com/AR10K00696

[Britgirl]

Can you confirm what NoMachine packages and version you ‘ve installed on the Ubuntu host. And also, what NoMachine version do you have on the connecting client?

[Britgirl]

Hi, yes we received them. We’ll reply soon 🙂

[Britgirl]

We’re late, we know! Be patient just a little bit more. I’m sure you won’t regret it. 🙂

[Britgirl]

Hi, the logs didn’t help us to identify the problem, so we’ve just sent you a debug package which will help us to narrow down the issue. Please install on the server side, reproduce the problem and send us the logs 🙂

[Britgirl]

Hi, the backtrace doesn’t seem to have attached. Can you send direct to forum[at]nomachine[dot]com? Thanks!

[Britgirl]

We aren’t able to reproduce this problem at all.

Are there any .xsession-errors in the Home directory?

By all means send in the logs that you have, you can either attach them here or submit them to forum[at]nomachine[dot]com.

[Britgirl]

Yes it is 🙂  Apologies for not replying sooner. Your Feature Request is under evaluation and we’ll update this space with more information soon.

[Britgirl]

 

@Zardoc, thanks for the feedback, and we’re pleased to know that you can now connect 🙂

We would like to know exactly what characters are causing the problems and if this is indeed related to the multiple processes appearing. To investigate thoroughly we would need to see the logs with debug enabled.

If possible, can you enable logs on Windows server side, reproduce the issue (so you’d have to go back to using the unusual character in the usernames) and zip up the logs? I’ll write the instructions here:

– Go to the installation folder of NoMachine, for example: C:\Program Files\NoMachine\etc and locate the server.cfg file.

– Right-click the server.cfg and open it with a text editor such as Wordpad or Notepad.

– Locate #SessionLogLevel 6 and change it to: SessionLogLevel 7.

– And restart the server. You can restart from the GUI (see image).

– Reproduce the problem. The logs will then capture any errors being produced.

– The logs are located on Windows here: %PROGRAMDATA%/NoMachine/var/log . You can locate it quickly by opening up the ‘Run’ app and pasting that path in the appropriate field.

– Zip up the folder by right-clicking the file or folder, point to Send To, and then click Compressed (zipped) Folder.

The logs would also allow us to check out the warnings about the server not shutting down properly 🙂

[Britgirl]

By the way, since they’re only PNG files you can replace them 🙂

[Author]

Posts