Forum Replies Created
even though pipewire-pulseaudio (specially the latest release) implements a lot of components of Pulse Audio, it still misses some important components to fully support all features that NoMachine achieves using Pulse Audio.
As mentioned in the article you can just switch to Pulse Audio in the meantime.
kextstat output shows that it is loaded also, kextutil output would be different if you didn’t approve it, so you have done it already.
You should have 2 NoMachine audio device.
Can you attach audio MIDI setup’s screens (during the session, while you are connected to your mac)?
1. let’s load nxaudio kext manually:
sudo kextutil -vvv /System/Library/Extensions/nxaudio.kext/
2. if you did not approve it, do::
Access System Preferences -> Security&Privacy -> General panel. Click on the “Allow” button
3. if it finished without any error, check if it’s loaded properly:
kextstat | grep nxau
you should get similar output:
180 0 0xffffff7f83d9c000 0x5000 0x5000 com.nomachine.driver.nxau (4.1.b2) 78172556-B6A4-3112-BA41-E79D18108476 <93 6 5 3 1>
4. restart NoMachine server:
sudo /etc/NX/nxserver --restart
If audio still does not work, please send us the output of kextutil command (point 1) in your reply.
these messages seem ok for disk forwarding, network agent extension shouldn’t do anything with disks.
From previously reply, I see that when you try to forward disk nxfs loading, but to be sure we don’t miss something, can you do the following:
– open the console app on Mac.
– enable/start log messages.
– connect again from Windows and try to forward disk.
– when you reproduce the same behavior, you can stop logging in console app.
– filler log messages with nxfs.
– check if there is some unusual message or error/warning for it.
– if it’s possible, copy all of them and I’ll check too.
I tried many times but was never able to reproduce that issue (with the same setup, same versions), can you check while you getting this behavior, if there are some crashes related to nxnode?
If yes, please upload the corresponding crash report(s).
when you mention that Mac starts hanging, do you mean NX session (do you use terminal in session or are you checking it on actual machine) or actual system starts hanging?
When you press connect button, does it show up permission asking widget for nxfs? or does it show that it is blocked?
https://knowledgebase.nomachine.com/AR01P00962 even if you already allowed it? Can you check does it actually blocked?
Also, can you run again this command while you are forwarding disk and when it fails after too:
After forwarding fails, can you click again on disk (it will show red exclamation mark on it) and check does it show some error message above “export this disk at session startup” option?
to help and to be more clear, can you tell me:
1. What are you doing exactly? When you connect from the Windows client to the Mac server, do you forward Mac’s disk on Win or Win’s disk on Mac?
2. Does it succeed or not? If not, what do you get as an error?
3. What are the client and server NoMachine versions?
4. What are the Mac and Windows versions?
5. When does the Mac hanging starts? While trying to forward disk or after also when if it succeeded?
6. What is the output of the command below on Mac?
glad to hear that it helped.
In general, NM connects always to the physical session, but the physical session should exist on the system, NM just detects and connects to it, if on the system the physical session is not detected NM creates a virtual session, to be sure that you will be able to use it (that’s happening in your case, a possible reason can be that system is slowly booting).
And also, please check /usr/NX/etc/server.cfg file and if CreateDisplay key is set to 1, set it to 0 and restart NM:
sudo /etc/NX/nxserver --restart
glad to hear that your problem is solved now.
Hi Paai again, received your logs.
So according to the logs you are using NoMachine virtual session and “mute server” option is only available for NoMachine physical session (there is no problem in virtual session logs).
One PA instance which was invoked by nxserver is for virtual session, but your logs shows that you are using physical session. Are you using virtual NoMachine session on the host machine?
According to the logs and output of pactl commands, you should have audio output, or there is something wrong on system or some PA configs are messed up.
Hi Paal again.
after you enable logs on the machine, please restart nxserver (if not it miss some essential logs):
sudo /etc/NX/nxserver --restart
and after this connect to the machine using NM and collect logs again.
According to pactl output our sinks/sources are loaded how it should but indeed not see hardware sink/source is weird.
Can you give use to the same pact commands on host machine (directly on it without using NM) and can you confirm that it is happening only during the session or after NM installation it disappears?
pavucontol screens would be helpful too.
even they are important modules, I tested it and sound loading should still work (I used Ubuntu 18.04 too), so let’s comment them again and restart pulseaudio.
In the previous reply where I asked you output for
ps aux|grep pulse
your output shows that PA is running twice for your user and probably that is the problem.
let’s check which commands are invoking both instances:
run again previous ps command and for both PA instance pid (second column is pid) run:
systemctl status PID_VALUE #replace pid number
It will get info which process started PA, one should be systemd and let’s check what is second one.
got your email and your config file.
Why did you disable to load
They are important modules.
uncomment them and restart pulseaudio:
Then try again and check, if you can see our sink/sources and if you get sound during NoMachine session.
so you mean that you don’t get audio in amplifier during NoMachine session, yes? or it stops working just after installing NoMachine , without using NoMachine session?
NoMachine doesn’t “kill/stop” default sinks/source that’s why NoMachine use its own sink/sources.
Please upload logs (instruction is the same how I advised Dan)
Just while you will be connected to the host machine using NoMachine, please try to check/uncheck “mute audio on server” option a few times.
Also provide output of commands of pactl on host machine before you connect using NoMachine and upload screen of pavucontrol output device tab.