Changes between Version 8 and Version 9 of WebKitGTK/Chroot

Timestamp:

Feb 20, 2014, 3:15:24 PM (11 years ago)

Author:

Andres Gomez

Comment:

Resorted pulse audio connection methods from a chroot

WebKitGTK/Chroot

@@ -93 +93 @@
 There are different ways of overcoming this limitation.
 
+==== Fix through tcp connection ====
+
 One of the simplest ones would be to set the local server to listen for TCP connections in the loopback interface, allowing any connection, and the Pulse client processes running in the chroot to connect to the server listening in the loopback interface. This can be sent system-wide, to all the users in the local host and the chroot or just per user. 
 
@@ -119 +121 @@
 }}}
 
-=== Pulse running system-wide ===
+==== Fix through unix connection ====
 
-The complete information about this can be found at http://www.freedesktop.org/wiki/Software/PulseAudio/FAQ/#index36h3
+This was a way of making a working connection to the pulse audio server running in the host while a soft link to the /tmp/pulse-XXXX working directory was stored at $HOME/.pulse/ .
 
-As this is not the default running mode for pulse, you will have to set the proper setting:
-{{{
-#!sh
-$ cat /etc/pulse/daemon.conf 
-...
-system-instance = yes
-...
-}}}
+This is not like this any more so '''this method is not working any more'''. You are free to correct this method for a way that would actually work.
 
-==== Pulse Ubuntu ====
+This were the steps to follow, though ...
 
 First, we have to make work `/dev/shm` (in some distributions, this is actually a soft link to `/run/shm`) following the instructions [wiki:WebKitGTK/Chroot#SHM_Ubuntu above].
@@ -161 +156 @@
 /home/user/.pulse /home/user/.pulse none rw,bind        0       0
 }}}
+
+=== Pulse running system-wide ===
+
+In system-wide mode any client process can connect to the running pulse audio instance.
+
+The complete information about this can be found at http://www.freedesktop.org/wiki/Software/PulseAudio/FAQ/#index36h3
+
+As this is not the default running mode for pulse, you will have to set the proper setting:
+{{{
+#!sh
+$ cat /etc/pulse/daemon.conf 
+...
+system-instance = yes
+...
+}}}