Forum Replies Created
-
AuthorPosts
-
mckaygerhard
ParticipantThere is no sense in your petition but I send both attached in this message.. both installed nomachine 9.0.188 client side has log level to 9.. server side makes no sense cos already sens the audio as must be cos i tested client side nomachine 6, 7, inclusive (with server side using 9.X ) and sound is working perfectly
No matter if you raise the level to 9 debug, the only log i found in session part of Client is:
Info: Slave server running with pid 1097.
Info: Listening to slave connections on port 25001.
Info: Starting NoMachine Monitor version ‘9.0.188’.
Info: Loaded translation files for ‘English’.
1089 1089 2025-07-21 14:20:42 630.524 OsDetect: Setting os type to ‘Debian’.
1089 1089 2025-07-21 14:20:42 630.548 Main: Creating a new connection monitor.
1089 1127 2025-07-21 14:20:42 754.355 AudioIoPulseaudioServer: WARNING! Cannot connect to PulseAudio server.
1089 1127 2025-07-21 14:20:42 754.378 AudioIoPulseaudioServer: Failed to get devices list.
1089 1089 2025-07-21 14:20:43 248.538 MonitorService: Enabled drag and drop feature.Attachments:
mckaygerhard
ParticipantI attached the two sides.. Client logs and server logs
I must remembered to all that the problem is at the client side on Linux .. error reports no connection to pulseaudio but pulseaudio is running and all the rest of the apps are working
I downgrade at the client side the NoMachine to my older binary and audio reception is working
Attachments:
mckaygerhard
ParticipantStill no sound in NoMachine 9 I installed NoMachine 8.16 and worked
mckaygerhard
ParticipantHi there is no need of send logs. NoMachine team just have to check changes in how pulseaudio its detected no matter if pipewire or pulseaudio case..
This affects all NoMachine 9 and last NoMachine 8.16, older NoMachine version just works without problem
- pipewire with pulseaudio emulation
- and pulseaudio
by example in this clien log line we got:
AudioIoPulseaudioServer: WARNING! Cannot connect to PulseAudio server.
AudioIoPulseaudioServer: Failed to get devices list.This line will be present in all your connections if you use NoMachine 9 but not if you use NoMachine 8 as client
I tested NoMachine 9 in older Debians, older Arch and newer ones and always same problem.. failed to get device list where pulseaudio setup is assumed.
August 2, 2019 at 07:38 in reply to: Connection from Debian amd64 to i386 makes high load on CPU? #23141mckaygerhard
ParticipantDesktop of the jessie are openbox. Desktop in debian 10 are mate or lxde.
Occurs as soon as i connect
Important lines of top as you can see nxbin are almost in top.
32422 remoto 0 -20 395324 123600 62504 S 15,3 3,1 13:37.09 nxnode.bin
5043 remoto 20 0 741600 236876 39916 S 6,3 5,9 141:55.71 chromium
12621 remoto 20 0 109476 5592 1220 S 6,3 0,1 0:02.83 caja
19509 remoto 20 0 1103380 442008 89616 S 6,3 11,0 1:51.10 palemoon
19962 remoto 20 0 5132 2708 2332 R 6,3 0,1 0:00.01 top
1 root 20 0 27744 3660 2656 S 0,0 0,1 0:10.03 systemd -
AuthorPosts