Forum Replies Created
-
AuthorPosts
-
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