Mageia forum

This one has been messing with my head for months but I think I have narrowed down the issues to what you will see in this fresh session statrtup sequence. The server is MGA4 fully maintained and freshly booted to a terminal. The client is MGA3.

Code: Select all

Oct  7 21:55:48 Gardenshed sshd[2198]: Accepted publickey for richard from XX.XX.XX.XX port 33878 ssh2
Oct  7 21:55:51 Gardenshed /usr/bin/x2gostartagent: successfully started X2Go agent session with ID richard-96-1412715349_stDLXDE_dp24
Oct  7 21:55:52 Gardenshed sshd[2447]: Accepted publickey for richard from XX.XX.XX.XX  port 33882 ssh2
Oct  7 21:55:53 Gardenshed /usr/bin/x2goruncommand: launching session with Xsession-x2go mechanism, using STARTUP="startlxde"
Oct  7 21:55:57 Gardenshed net_applet[2629]: ### Program is starting ###
Oct  7 21:56:05 Gardenshed kernel: [ 1727.236259] fuse init (API version 7.22)
Oct  7 21:55:58 Gardenshed mgaapplet[2661]: ### Program is starting ###
Oct  7 21:56:00 Gardenshed pulseaudio[2646]: [pulseaudio] main.c: User-configured server at localhost:30140, refusing to start/autospawn.
Oct  7 21:56:00 Gardenshed dbus[1353]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service'
Oct  7 21:56:01 Gardenshed polkitd[2678]: Started polkitd version 0.112
Oct  7 21:56:03 Gardenshed dbus[1353]: [system] Activating via systemd: service name='org.freedesktop.UDisks2' unit='udisks2.service'
Oct  7 21:56:03 Gardenshed udisksd[2708]: udisks daemon version 2.1.1 starting
Oct  7 21:56:05 Gardenshed dbus[1353]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
Oct  7 21:56:05 Gardenshed dbus[1353]: [system] Successfully activated service 'org.freedesktop.UDisks2'
Oct  7 21:56:05 Gardenshed udisksd[2708]: Acquired the name org.freedesktop.UDisks2 on the system message bus
Oct  7 21:56:09 Gardenshed dbus[1353]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.26" (uid=501 pid=2629 comm="/usr/bin/perl /usr/bin/net_applet ") interface="org.freedesktop.DBus.Introspectable" member="Introspect" error name="(unset)" requested_reply="0" destination="org.mageia.monitoring" (uid=0 pid=1354 comm="/usr/sbin/mandi -d ")
Oct  7 21:56:09 Gardenshed dbus[1353]: [system] Rejected send message, 3 matched rules; type="method_call", sender=":1.26" (uid=501 pid=2629 comm="/usr/bin/perl /usr/bin/net_applet ") interface="org.mageia.monitoring.ifw" member="GetMode" error name="(unset)" requested_reply="0" destination="org.mageia.monitoring" (uid=0 pid=1354 comm="/usr/sbin/mandi -d ")
Oct  7 21:56:09 Gardenshed dbus[1353]: [system] Rejected send message, 3 matched rules; type="method_call", sender=":1.26" (uid=501 pid=2629 comm="/usr/bin/perl /usr/bin/net_applet ") interface="org.mageia.monitoring.ifw" member="GetReports" error name="(unset)" requested_reply="0" destination="org.mageia.monitoring" (uid=0 pid=1354 comm="/usr/sbin/mandi -d ")
Oct  7 21:56:10 Gardenshed mgaapplet[2661]: running: ionice -p 2661 -n7
Oct  7 21:56:10 Gardenshed pulseaudio[2759]: [pulseaudio] main.c: User-configured server at localhost:30140, refusing to start/autospawn.
Oct  7 21:56:16 Gardenshed pulseaudio[2773]: [pulseaudio] main.c: User-configured server at localhost:30140, refusing to start/autospawn.


It would not be accurate to say "I don't know where to start" as I started trying to figure this out last May, but I cannot get any useful hints from the log messages and I am hoping someone will recognise why a service I installed on my computer should be refusing to let me use it.

Richard

jaywalker wrote:

Code: Select all

Oct  7 21:56:09 Gardenshed dbus[1353]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.26" (uid=501 pid=2629 comm="/usr/bin/perl /usr/bin/net_applet ") interface="org.freedesktop.DBus.Introspectable" member="Introspect" error name="(unset)" requested_reply="0" destination="org.mageia.monitoring" (uid=0 pid=1354 comm="/usr/sbin/mandi -d ")
Oct  7 21:56:09 Gardenshed dbus[1353]: [system] Rejected send message, 3 matched rules; type="method_call", sender=":1.26" (uid=501 pid=2629 comm="/usr/bin/perl /usr/bin/net_applet ") interface="org.mageia.monitoring.ifw" member="GetMode" error name="(unset)" requested_reply="0" destination="org.mageia.monitoring" (uid=0 pid=1354 comm="/usr/sbin/mandi -d ")
Oct  7 21:56:09 Gardenshed dbus[1353]: [system] Rejected send message, 3 matched rules; type="method_call", sender=":1.26" (uid=501 pid=2629 comm="/usr/bin/perl /usr/bin/net_applet ") interface="org.mageia.monitoring.ifw" member="GetReports" error name="(unset)" requested_reply="0" destination="org.mageia.monitoring" (uid=0 pid=1354 comm="/usr/sbin/mandi -d ")

Not sure if that's related or a red herring. You may want to kill mandi (interactive firewall thingie) on client and server and retest

Code: Select all

service mandi stop

Although I should mention that our x2go packages are not really maintained since quite some time.
So the question would be, was anyone else able to get sound in an x2go session, at least for Mageia.

Some related links on that topic:
http://lists.freedesktop.org/archives/p ... 08289.html
http://mail.kde.org/pipermail/freenx-kn ... 09806.html

But most obvious

http://wiki.x2go.org/doku.php/doc:faq:start wrote:Why is there no sound using Linux?

Probably because the server does not listen to client connections. Check whether the file /etc/pulse/default.pa on the client contains the line:

Code: Select all

load-module module-native-protocol-tcp auth-cookie=".pulse-cookie"


If not, add it. Alternatively you can load the module at runtime:

Code: Select all

pactl load-module module-native-protocol-tcp 'auth-cookie=".pulse-cookie"'

doktor5000 wrote:Not sure if that's related or a red herring. You may want to kill mandi (interactive firewall thingie) on client and server and retest

Damn, and I thought the three days I took to kill shorewall was enough! I didn't even know I had turned mandi on. Still, I think you are quite right, it is a bit of a red herring as everything should be tunnelling through the established and proven ssh connection.

There appears to be a more fundamental problem with the way I am using x2go and pulseaudio on the server. Everything I have read about the experience of others suggests that it either works straight out of the box, or, for a few of us, it just doesn't. Even our own guru Colin's article (part two at least) does an excellent job of explaining how a working system performs but that is for people who can join with him in the pleasures of a working system and not for those of us outside, in the cold street, with our noses pressed against the window wishing we could join the party.

doktor5000 wrote:So the question would be, was anyone else able to get sound in an x2go session, at least for Mageia.

That would be great to know. I am pretty sure there is nothing too funky about the server. It was a clean MGA4 install with none of my usual fiddling to improve performance. I have just rigged it as a DVD/TV/PVR player and kept it up to date. Because it is installed in my mother's living room I find it more convenient to control it from another room, or another town - hence the ssh setup for maintenance and the x2go arrangement for editing and transcoding video.

One thing I did get from Colin's article was to check the X11 root window properties with

Code: Select all

xprop -root | grep PULSE

When I do this at the ssh console I get

Code: Select all

[richard@Gardenshed ~]$ xprop -root | grep PULSE
PULSE_COOKIE(STRING) = "4736ddcae7adef3a8661bf7673c6fe0a29b710ae18d22a58a2d3c5eccbc1723c2d98087de58a03018ee007e902fef236b4702fcf0cef7253a1beba19ef6b509f372ebe3467a37e952fc4f028fd6f139dbd894152b11aaabc05af95d2f474838f078c54db65944824525e1e484ae4c31dda13bd4ed9e8b0078021b9f3dbc7e2a0108673710014d864be8963caa4a538a0047e5f40ccdcb7d0a60a94746b0cef7902c3f8cf1735d524eb610f735156a1e84f207fc6d6c26968412b0f53019ba0646bff05d35f89ce1eb06962b6cff5b17b73aa6377725bae16dfb3366223cd927d439fc19311152e9ff0c3db9decaeb2c65e7c6e5870b5d5eba9b4409de5fa7a44"
PULSE_SERVER(STRING) = "{4eda2d50e7ed4725bd13b43e72dd5d0c}unix:/run/user/501/pulse/native tcp:localhost:4713 tcp6:localhost:4713 tcp:localhost:59861 tcp6:localhost:35456"
PULSE_SESSION_ID(STRING) = "1"
PULSE_ID(STRING) = "501@4eda2d50e7ed4725bd13b43e72dd5d0c/3817"


If I start a shell in my x2go session I get nothing; a zero response, not a dicky bird. I don't know if that is supposed to tell me what failed but it does tell me that pulseaudio cannot be working. There are one or two other things which do not work in the x2go session. Mostly they are utilities in the Tools menu which should prompt for a root password, but don't. The Mageia Control Centre is one of those. Starting it from a user console doesn't help either, whether I use a terminal in the x2go session or a ssh console I get this:

Code: Select all

[richard@Gardenshed ~]$ mcc
Error executing command as another user: Not authorized

This incident has been reported.


So, I am thinking I have a permissions problem, vaguely reminiscent of the issues we encountered with polkit and consolekit and LXDE during MGA3 Cauldron development last year. Trouble is I don't remember how that one was fixed or what was causing it. Might it be some strange authorisation problem do you think?

R

jaywalker wrote:So, I am thinking I have a permissions problem, vaguely reminiscent of the issues we encountered with polkit and consolekit and LXDE during MGA3 Cauldron development last year. Trouble is I don't remember how that one was fixed or what was causing it. Might it be some strange authorisation problem do you think?

Well for the drakxtools definitely. Check one of the earlier polkit threads: viewtopic.php?f=8&t=6893

But that's something totally different to the sound issue. Apart from x2go, are you able to forward sound via pulseaudio to a remote box at all?
Then you could test via an ssh session.

doktor5000 wrote:Apart from x2go, are you able to forward sound via pulseaudio to a remote box at all?Then you could test via an ssh session.

I think I managed it once, though I have tried since and still haven't re-discovered the magic. I used the server machine as an RTP stream source and was able to hear it on the LAN connected client. Even now it still shows on my local Pulse Volume Control (what a strange name for this program!) as an available source but it remains resolutely mute.

I am not sure what procedure to follow to test via ssh. Dos it involve some specialist client-side diagnostic tool on the MGA3 box or does it just "work" if I forward a media player from the server (MGA4)?

R

jaywalker wrote:or does it just "work" if I forward a media player from the server (MGA4)?

It should, if you enable your server (on your client) to allow incoming network connections, see previously posted link about that¹. Maybe that's even included in default Mageia pulse config, I didn't check that.

You can check if the module is loaded via

Code: Select all

pactl list modules short | grep tcp

1: http://wiki.x2go.org/doku.php/doc:faq:s ... sing_linux

Then you should be able to route the sound from the remote box to your local machine.

Maybe you should read
http://www.freedesktop.org/wiki/Softwar ... r/Network/
http://psung.blogspot.de/2011/09/networ ... -made.html

And quoting from Colin's article:
http://colin.guthr.ie/2009/08/sound-on- ... ulseaudio/

Remote X11 application
One of the handiest things with X11 is the ability to connect to another machine on your network and run GUI applications and have them display on your local display. With PulseAudio, the sound is also heard on the local machine. Out of the box (for security reasons), remote connections are not enabled. To enable them, run paprefs and enable the option Enable network access to local sound devices. This is the only option needed for this example. It loads an additional module into the server that listens on TCP port 4713 for incoming connections. Obviously, it goes without saying that any firewall on the machine must allow connections to this port!

• User starts a normal X11 session and the start-pulseaudio-x11 script ensures the X11 properties are set as in the previous example.
• User then connects to another machine on his network via SSH and starts an audio player (e.g. RhythmBox, Amarok, etc.)
• Even tho' the app is running remotely the visual display will be local.
• When the app starts playing audio, the PulseAudio client portion will find the X11 properties that have been forwarded through the SSH connection.
• The PulseAudio client will then connect over TCP to the PulseAudio server running on the user's local machine.
• The User revels in the local display and audio the application provides.

So as you can see, the use of the X11 properties has allowed us to piggy back on top of the X11 forwarding. It's not a totally clean connection as under SSH the X11 data will actually be tunnelled over a secure link handled by SSH itself, whereas all we are doing is telling the PulseAudio client where to connect directly, outside of any SSH tunnels. This means that while the display can work over a NATed system, the sound will not. This is fairly easily addressed, but we'd have to teach SSH about PulseAudio for this to work. The reason it works for X11 is because SSH is aware of, and has specific support for, X11. We're just piggy backing on this. That said, the current arrangement is "good enough" for most use cases.

Code: Select all

[richard@localhost ~]$ ssh richard@blackbox
Last login: Sat Oct 11 22:09:29 2014 from babybuffalo.home
[richard@Gardenshed ~]$ cat /etc/pulse/default.pa | grep module-native-protocol-tcp
#load-module module-native-protocol-tcp
[richard@Gardenshed ~]$ pactl load-module module-native-protocol-tcp auth-cookie=".pulse-cookie"
33
[richard@Gardenshed ~]$ pavucontrol

** (pavucontrol:2406): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-TTPtwsRElU: Connection refused
[richard@Gardenshed ~]$ vlc
VLC media player 2.1.5 Rincewind (revision 2.1.4-49-gdab6cb5)
[0xd0d118] main libvlc: Running vlc with the default interface. Use 'cvlc' to use vlc without interface.


Well, I can hear vlc trying to play "Sweet Home Chicago" but I almost wish I couldn't. It is stuttering _almost_ in time with the music in a most disheartening way. I can stream that track to my local player AND enjoy it Doing it now, in fact. I notice that the network traffic stream is much lighter - almost half of the reote vlc over ssh. That must be because I am streaming a flac file and the remote player was sending me full-cream audio - no compression.

I have to admit, I really have no feel for this pulse thing. It seems to have a mind of its own, or at least a language of its own and a rationale of its own. I managed to click on the right combination of options, I reckon, but there were probably quite a few of the changes which actually did not contribute to getting a partial result.

For my next trick I am going to reboot the server to a console and see how far I can get doing a similar thing from an X2Go session....

R

And now I am half way there, I think. I have the x2go session showing Me-TV output and a separate connection between pulses on client on server. The total network load is about the same as it was when I was trying to play Eric Clapton from a ssh forwarded vlc instance and the sound is immeasurably better.

Before I try again with a normal boot on the server (autologin to my LXDE desktop) I am going to see if I can persuuade x2go to start a session with sound enabled. This is something I have NEVER achieved before.

R

Code: Select all

Oct 11 23:42:03 Gardenshed sshd[4298]: Accepted publickey for richard from XX.XX.XX.XX port 48523 ssh2
Oct 11 23:42:11 Gardenshed /usr/bin/x2goterminate-session: ERROR: failed to terminate session with ID richard-105-1413067249_stDLXDE_dp24
Oct 11 23:42:18 Gardenshed /usr/bin/x2gostartagent: successfully started X2Go agent session with ID richard-106-1413067336_stDLXDE_dp24
Oct 11 23:42:18 Gardenshed sshd[4694]: Accepted publickey for richard from 192.168.1.78 port 48527 ssh2
Oct 11 23:42:19 Gardenshed /usr/bin/x2goruncommand: launching session with Xsession-x2go mechanism, using STARTUP="startlxde"
Oct 11 23:42:21 Gardenshed pulseaudio[4883]: [pulseaudio] client-conf-x11.c: xcb_connection_has_error() returned true
Oct 11 23:42:21 Gardenshed pulseaudio[4883]: [pulseaudio] main.c: User-configured server at localhost:30170, refusing to start/autospawn.
Oct 11 23:42:21 Gardenshed net_applet[4875]: ### Program is starting ###
Oct 11 23:42:21 Gardenshed pulseaudio[4903]: [pulseaudio] client-conf-x11.c: xcb_connection_has_error() returned true
Oct 11 23:42:21 Gardenshed pulseaudio[4903]: [pulseaudio] main.c: User-configured server at localhost:30170, refusing to start/autospawn.
Oct 11 23:42:21 Gardenshed pulseaudio[4917]: [pulseaudio] client-conf-x11.c: xcb_connection_has_error() returned true
Oct 11 23:42:21 Gardenshed pulseaudio[4917]: [pulseaudio] main.c: User-configured server at localhost:30170, refusing to start/autospawn.
Oct 11 23:42:21 Gardenshed mgaapplet[4909]: ### Program is starting ###


Yep, that's what I thought. X2Go still cannot start a remote session with sound, but at least a new session with no sound is still sending sound to my client over its own LAN connection.

Next try will be to see if I can achive the current result when the server is booted normally...

R

No I am back at square one. The x2go session is completey mute. Starting vlc to play the test file produces the same old

Code: Select all

Audio output failed:
The audio device "default" could not be used:
Connection refused.

Now that we have ruled out a deficiency in the pulseaudio installations on client and server, or rather, we have established that any deficiencies found are the same for everybody, and bearing in mind that some others, with the apparent exception of Mageia users, can make use of X2Go sound support, it seems to follow that what is preventing it to work for me is some Mageia-specific configuration of one or both of polkit and systemd. I am, perhaps, influenced by the observed failure in x2go sessions of attempts to run tools which require root authority from their desktop, taskbar or menu icons. This suggests to me that something is preventing the normally working links from recognising that they should respond correctly to a properly authenticated valid user on the system.

When I am logged on to the desktop of the server there is no way I know of to get an x2go session with working sound. It looks like pulseaudio is configured as a single seat service which is unavailable to the same user if not using the pre-existing desktop session. But that would be crazy so it cannot be the right explanation, can it?

R

Nope, so far you haven't ruled out anything.

See previous hints:

Apart from x2go, are you able to forward sound via pulseaudio to a remote box at all?
Then you could test via an ssh session.

So did you check that on the remote box there's a working pulseaudio server? That there's a cookie?
Where did you use paprefs, a mixer or something to send the sound to your local box?
Did you ensure that your local box can receive something via network, e.g. also with paprefs ?

Please read the documentation I've linked to above, go through it and then you can try again.

OK then, from the top; the first reference was to another Mageia forum thread discussing remote VNC connections and KDE and polkit. From that I have

Code: Select all

[richard@Gardenshed ~]$ ps -ef | grep polkit
polkitd   1520     1  0 Oct11 ?        00:00:00 /usr/lib/polkit-1/polkitd --no-debug
richard   2241     1  0 Oct11 ?        00:00:00 /usr/libexec/polkit-mate-authentication-agent-1
richard   9229  9173  0 14:15 pts/0    00:00:00 grep --color polkit


So I have the necessary polkit agent in place, and indeed it works for me when I am working locally on the server.

doktor5000 wrote:Apart from x2go, are you able to forward sound via pulseaudio to a remote box at all?Then you could test via an ssh session.

That one is a little trickier as the answer is "yes and no"; "yes" if I am in the same room as the server and set it to play sound from some source or other and then return to the client to listen to it, and "no" if I try to set the server to play sound in a session started by x2go on the client while I still have my local desktop on the server, active but idle (the normal state of affairs after a normal boot with autologin to the desktop), but "yes" if the server oots to a console so that the only desktop session is the one I start remotely with x2go.

Like I said, it's complicated. The answer to your subsequent question on whether the right modules are loaded might help to clarify this.

Code: Select all

[richard@Gardenshed ~]$ pactl list modules short | grep tcp
11   module-native-protocol-tcp   auth-anonymous=1   
12   module-esound-protocol-tcp   auth-anonymous=1   


That was from a ssh console from the client. The server is currently running two X sessions for me; one is the usual local session and the other is the x2go remote session. The local session is displaying the output from Me-TV and I am now sitting in front of the client, listening to it. If I try the same command in a terminal started in the x2go session I get:

Code: Select all

[richard@Gardenshed ~]$ pactl list modules short | grep tcp
Connection failure: Connection refused

That seems worthy of further linguistic analysis, which should work if the writer of the code is a native english user. The first part is quite neutral and appears to be a generalised announcement. The use of the word "failure" implies nothing more than it states; something didn't work and we will try to say what that is (the colon implies more to come). The second part, after the colon tells us much more. It says that the attempt to connect was actively refused by the intended recipient; the running pulse server. So, in one simple check we have already got a lot of information and enough to start wondering by what criterion the pulse server decided it should refuse what should be a perfectly valid request.

jaywalker wrote:One thing I did get from Colin's article was to check the X11 root window properties with

Code: Select all

xprop -root | grep PULSE

When I do this at the ssh console I get

Code: Select all

[richard@Gardenshed ~]$ xprop -root | grep PULSEPULSE_COOKIE(STRING) = "4736ddcae7adef3a8661bf7673c6fe0a29b710ae18d22a58a2d3c5eccbc1723c2d98087de58a03018ee007e902fef236b4702fcf0cef7253a1beba19ef6b509f372ebe3467a37e952fc4f028fd6f139dbd894152b11aaabc05af95d2f474838f078c54db65944824525e1e484ae4c31dda13bd4ed9e8b0078021b9f3dbc7e2a0108673710014d864be8963caa4a538a0047e5f40ccdcb7d0a60a94746b0cef7902c3f8cf1735d524eb610f735156a1e84f207fc6d6c26968412b0f53019ba0646bff05d35f89ce1eb06962b6cff5b17b73aa6377725bae16dfb3366223cd927d439fc19311152e9ff0c3db9decaeb2c65e7c6e5870b5d5eba9b4409de5fa7a44"PULSE_SERVER(STRING) = "{4eda2d50e7ed4725bd13b43e72dd5d0c}unix:/run/user/501/pulse/native tcp:localhost:4713 tcp6:localhost:4713 tcp:localhost:59861 tcp6:localhost:35456"PULSE_SESSION_ID(STRING) = "1"PULSE_ID(STRING) = "501@4eda2d50e7ed4725bd13b43e72dd5d0c/3817"

If I start a shell in my x2go session I get nothing; a zero response, not a dicky bird.

That is what first told me that the x2go session, configured to start without sound support, was having problems starting the pulseaudio server. The pulse cookie and everything else related to pulse in the X properties is absent when checking from the x2go session but present when checking with the simultaneously connected ssh terminal. If I had read more closely I would also have seen that the pusle server had been started with the correct network module (PULSE_SERVER), but that none of this information is available to me, the same user, in my remote x2go session.

doktor5000 wrote:Where did you use paprefs, a mixer or something to send the sound to your local box?

That one is a little harder to answer as it is still not clear to me what I did to make it work as I have tried everyting I could think of and in every possible way; remotely by ssh using X forwarding to manipulate paprefs and pa volume control, as before but locally on the server, using mc in a ssh shell to modify /etc/pulse/default.pa. Another thing I have done is follow the advice at one of your references

Code: Select all

Alternatively you can load the module at runtime:
pactl load-module module-native-protocol-tcp 'auth-cookie=".pulse-cookie"'

I then moved on to trying RTP from the server as that seemed to produce a "device" which I could see in the pulse volume control and use to broadcast the cound. It worked well but I wanted the sound to be fowrwarded in the "standard" x2go manner, over the X via ssh connection. So I turned that off and tried again with the paprefs option "Make discoverable PulseAudio network sound devices locally" and ticking all the Network Server options on the next tab. That is how things have been since my first attempt to listen to Eric Clapton reported yesterday.

As to the pulse volume control settings, that is still largely a matter of point, poke, check and try again until I get a combination that works on the server, and a similar operation on the client.

doktor5000 wrote:Did you ensure that your local box can receive something via network, e.g. also with paprefs ?

I reckon I must have, though I don't remember the exact procedure. It was compliacted by having to re-install all the MGA3 pulse-related rpms a few days ago (Friday?) and go through many failed attempts as there had not been anything coming from the server to check. Once I got both ends working I conducted the tests reported yesterday to establish under what conditions I could get a reliable sound link. Those are the conditions which I summarised above and again here:

I can achieve a working x2go session on the server ONLY IF I configure the client to connect with no sound support.
I can manage/control the server's pulseaudio from the x2go session ONLY IF the server is started in runlevel 3 and the x2go session is the ONLY session for my user.
I can hear the audio on my client ONLY IF I use a separate data stream coming directly from the pulseaudio server as the x2go route is impossible to achieve until I can resolve the problem which prompted me to seek help to get x2go sound support working.

doktor5000 wrote:Please read the documentation I've linked to above, go through it and then you can try again.

I will do as you suggest.

R

Meanwhile ... No, I am still studying for my PulseAudio degree. Long way to go though, I am not out of Primary School yet:~)

I just wanted to record that I have had an opportunity to try out the whole x2go/pulse thing on a different server running on very similar hardware to the MGA4 server, but this one is running MGA3 - same as the client, and I got a LOT further in the half hour or so I had available. I will be going back to that tomorrow to see if I can get any useful knowledge which I can transfer to the original problem's solution.

R