No sound from Ubuntu 18.04 / AWS

[eric-duveau]

End A: ubuntu 20.04 |----internet ----| End B: ubuntu 18.04 / AWS

On end B: after having configured :

.`/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: see the image below.

and no sound on end A

Could you help?

Attachments:

1. 

   Capture-d’écran-du-2020-05-06-23-43-51.png
   

[eric-duveau]

Recall of the situation: A is my desktop and B is my server.

End A: ubuntu 20.04 |—-internet —-| End B: ubuntu 18.04 / AWS

On 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?

[witek]

Hi,

Are you trying to set up PulseAudio via root?

By default PulseAudio is not intended to be run as root but you can try to use it in a system-wide mode.

Edit the following variables in /etc/pulse/daemon.conf:

– change daemonize = no to daemonize = yes

– change system-instance = no to system-instance = yes

Remember to remove ‘#’ or ‘;’ sign to uncomment line.

After that reboot system and try to access pavucontrol.

Please note that in some cases running PulseAudio in system-wide mode is not recommended.

More information you can find here:

https://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/SystemWide/

https://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/WhatIsWrongWithSystemWide/

[eric-duveau]

Hi 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-duveau]

Hi 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-duveau]

Hi since the version 6.10.12-1 of NoMachine it works well 🙂

[Britgirl]

Thanks for letting us know.

[Author]

Posts