Forum Replies Created
-
AuthorPosts
-
May 25, 2020 at 08:11 in reply to: A successful story in setting up NoMachine with Nvidia driver on AWS #27756eric-duveauParticipant
@brotech Thanks
May 22, 2020 at 07:45 in reply to: A successful story in setting up NoMachine with Nvidia driver on AWS #27732eric-duveauParticipantJust after :
> sudo apt install /tmp/nomachine_6.10.12_1_amd64.deb
Don’t forget to install the nvidia proprietary drivers
> sudo ubuntu-drivers autoinstall
eric-duveauParticipantI had this issue too, my workaround was to use lightdm instead of gdm3
eric-duveauParticipantHi since the version 6.10.12-1 of NoMachine it works well 🙂
eric-duveauParticipantHi witek
I tried to follow your advice :
ubuntu@ip-172-31-14-113:~$ sudo -i
root@ip-172-31-14-113:~# diff -u /etc/pulse/daemon.conf.ori /etc/pulse/daemon.conf.bad
— /etc/pulse/daemon.conf.ori 2020-05-11 20:50:31.514050508 +0000
+++ /etc/pulse/daemon.conf.bad 2020-05-13 21:15:11.245467189 +0000
@@ -18,11 +18,13 @@
## commenting.; daemonize = no
+daemonize = yes
; fail = yes
; allow-module-loading = yes
; allow-exit = yes
; use-pid-file = yes
; system-instance = no
+system-instance = yes
; local-server-type = user
; enable-shm = yes
; enable-memfd = yes
root@ip-172-31-14-113:~#But the Display Manager freezes after reboot and I event cannot login.
eric-duveauParticipantHi witek
I tried to follow your advice :
root@ip-172-31-14-113:~# diff -u /etc/pulse/daemon.conf.ori /etc/pulse/daemon.conf.bad
— /etc/pulse/daemon.conf.ori 2020-05-11 20:50:31.514050508 +0000+++ /etc/pulse/daemon.conf.bad 2020-05-13 21:15:11.245467189 +0000
@@ -18,11 +18,13 @@
## commenting.
; daemonize = no
+daemonize = yes
; fail = yes
; allow-module-loading = yes
; allow-exit = yes
; use-pid-file = yes
; system-instance = no
+system-instance = yes
; local-server-type = user
; enable-shm = yes
; enable-memfd = yes
root@ip-172-31-14-113:~#
But the Display Manager freezes after reboot and I event cannot login.
eric-duveauParticipantRecall of the situation: A is my desktop and B is my server.
End A: ubuntu 20.04 |—-internet —-| End B: ubuntu 18.04 / AWSOn end B: after having configured :
root@ip-172-31-14-113:/usr/NX/etc/node.cfg
root@ip-172-31-14-113:/usr/NX/etc# grep -i pulse node.cfg
# be ‘pulseaudio’, ‘alsa’ or ‘disabled’ on Linux, and ‘nxaudio’ or
AudioInterface pulseaudio
# Specify path and name of the command to start PulseAudio server.
CommandStartPulseAudio “/usr/bin/pulseaudio”
root@ip-172-31-14-113:/usr/NX/etc#I have the issue message on End B when running pavucontrol: see the image below. and no sound on end A
Could you help?
-
AuthorPosts