Peter76

[Peter76]

There is a Trouble Report on this issue which you can see here:

https://www.nomachine.com/TR04N06752

Users can follow the link to the Trouble Report and use the ‘notify me’ feature to know when a patch has been released.

[Peter76]

Hi, thanks for replying. Those logs would contain additional information about system and files calls which would be useful for the investigation. We’re investigating and will update the post once we have some feedback on the issue.

[Peter76]

There is a Trouble Report on this issue which you can see here:

https://www.nomachine.com/TR03N06660

Users can follow the link to the Trouble Report and use the ‘notify me’ feature to know when a patch has been released.

[Peter76]

Hi, thanks for reporting and logs. Please check, if file /var/log/audit/audit.log exists. If it does, please send it to us (forum[at]nomachine[dot]com or attach here)

[Peter76]

Hi,

thanks for reporting. We’re investigating and will update the post once we have some feedback on the issue.

[Peter76]

Hi,

There is a Trouble Report on this issue which you can see here:

https://www.nomachine.com/TR01N06360

There is also a workaround documented. The workaround works only for Mac OS X versions included in file (/Applications/NoMachine.app/Contents/Framework/scripts/restricted/nxusb.sh.

OS X 10.11 will be added as soon as issues regarding USB forwarding are solved for this version (https://www.nomachine.com/TR09M06042)

Please use the notify me to know when fixes have been released.

Attachments:

1. 

   11.jpg
   

2. 

   21.jpg
   

3. 

   31.jpg
   

4. 

   4.jpg
   

[Peter76]

Hi,

referring to the last post, we can confirm that the problem occurs. This problem is caused by the USB driver that uses NoMachine and VirtualBox. We are currently working on a solution.

Until then, we suggest you uninstall the USB drivers without having to remove NoMachine:

1) Run the CMD console with administrator rights:

right click on the bottom left corner on Windows Desktop -> choose Command Prompt (Admin)

2) Move to <NoMachine>/bin directory

where <NoMachine> is the directory where you installed the NoMachine software

4) Remove USB drivers and devices by executing from console:

nxservice64 –uninstall nxusb

or, if you are on a 32.bit machine:

nxservice32 –uninstall nxusb

5) USB service will be in ‘Marked to delete’ status until next reboot.

nxservice64 –status nxusb

6) change entry in node.cfg (than after reboot the Windows driver will not be loaded):

run the Notepad (or other text editor) as administrator

open file <NoMachine>/etc/node.cfg

change entry
#EnableUSBSharing both
to
EnableUSBSharing none

7) Reboot the Windows.

If you want to check status of USB service, you can run from console:

nxservice64 –status nxusb

it should be: Not installed

[Peter76]

Hi,

thanks for reporting. We’re investigating and will update the post once we have some feedback on the issue.

[Peter76]

Hi,

to help you, we need more information.

Please reproduce the issue on server side under NoMachine and pulseaudio debug level.

To do this go to:
/usr/NX/etc/node.cfg
/usr/NX/etc/server.cfg

and change variable:
SessionLogLevel to 8

In pulseaudio, change the following in /etc/pulse/daemon.conf:
log-level=debug

Logs from pulseaudio will go to /var/log/syslog

Then restart nxserver, start a new session and collect all logs from nx and
pulseaudio and put them on forum.

To retrieve the NoMachine logs, see this guideline:

How to gather debug logs for Support requests
https://www.nomachine.com/DT04M00076

Send to forum[at]nomachine[dot]com.

Additionally, please collect also all results from these two commands and put them too:
pulseaudio -v –log-target=stderr

pacmd
>>> list-sinks

[Peter76]

Hello,

We enable USB subsystem only on well tested OSX releases.

We tested already 10.10.4 and users can enable it safely.

We will do it in the next release, but you can add the new MAC OS (10.10.4) to nxusb.sh:

1. change the curent directory:

cd /Applications/NoMachine.app/Contents/Frameworks/scripts/restricted

2. open the file nxusb.sh:

sudo vim nxusb.sh

3. add the new system in line 329 after “$systemVersion” == “10.10.3″:

|| “$systemVersion” == “10.10.4″

4. save the changes:

Esc + :wq

5. restart nxusb.sh:

sudo ./nxusb.sh –restart

[Peter76]

Hello,

Problem is fixed in the version NoMachine 4.5.0. Please install this newest version.

[Peter76]

Hello,

you have to add the new MAC OS (10.10.3) to nxusb.sh:

1. change the curent directory:

cd /Applications/NoMachine.app/Contents/Frameworks/scripts/restricted

2. open the file nxusb.sh:

sudo vim nxusb.sh

3. add the new system in line 328 after “$systemVersion” == “10.10.2”:

|| “$systemVersion” == “10.10.3”

4. save the changes:

Esc + :wq

5. restart nxusb.sh:

sudo ./nxusb.sh –restart

[Peter76]

Hi,

Please install pavucontrol on your Linux Fedora:

sudo yum install pavucontrol

then launch it. You will be able to change additional audio settings after connection (also NoMachine). Let us know if the problem persists.

[Peter76]

Hi,

this problem appears in version NoMachine 4.4.12 and a patch will be made available in the next release which has been scheduled for next week. If the problem persists after update, please let us know.

 

 

[Peter76]

Hi,

this problem appears in version NoMachine 4.4.12 and a patch will be made available in the next release which has been scheduled for next week. If the problem persists after update, please let us know.

[Author]

Posts