[X2Go-User] pyhoca-cli sound issues

[Tim Kruse]

Am 14.10.2013 13:51, schrieb Tim Kruse:
> [...]
>
> If I try to connect from client (within a fresh KDE session) to server
> with the following command, I don't have any sound in this x2gosession:
>
> pyhoca-cli --server $SERVER --new --command startkde --username $USR
> --sound pulse --geometry 1440x900 --link adsl --pack 16m-png-9
> --kbd-layout de --kbd-type '105/de'
>
> Now I connect to the server (or another x2goserver, that doesn't matter)
> with x2goclient and there is sound. When I then connect again with above
> pyhoca-cli command, I have sound in this session.
>
> When I restart the local KDE Desktop on the client, I don't have any
> sound with pyhoca, until I connect with x2goclient ...
>
> I think, there is some process/program, that pyhoca-cli is not able to
> start, until x2goclient will start it, but I can't find it ...

An update about this ...

I digged into this problem a bit deeper and found one inportant 
difference. The pulseaudio deamon get's started with KDE, so this is ok:

ps -ef | grep pulse
tkruse    3887     1  0 07:02 ?        00:00:00 /usr/bin/pulseaudio 
--start --log-target=syslog

But at this time no TCP port for pulseaudio is opened, so that no 
network sound connection is possible (I use the standard port 4713). If 
I start pyhoca-cli, it does not open the port (or is not able to, 
dunno). X2Goclient DOES open the port, so that the connection can be 
made. If I close the x2goclient session, the port remains open, so now a 
pyhoca-cli session has sound, too.

I started pyhoca-cli with --debug --libdebug and got the messages

pyhoca-cli[10399] (x2gorevtunnel-pylib) DEBUG: notifying thread of 
incoming channel: <X2GoRevFwTunnel(Thread-5, started daemon 24821416)>
pyhoca-cli[10399] (x2gorevtunnel-pylib) DEBUG: detected incoming data 
channel on X2Go server port: [127.0.0.1]:30089
pyhoca-cli[10399] (x2gorevtunnel-pylib) DEBUG: data channel 
<paramiko.Channel 14 (open) window=2097152 -> <paramiko.Transport at 
0x1813710L (cipher aes128-ctr, 128 bits) (active; 2 open channel(s))>> 
for server port [127.0.0.1]:30089 is up
pyhoca-cli[10399] (x2gorevtunnel-pylib) DEBUG: waiting for incoming data 
channel on X2Go server port: [127.0.0.1]:30089

which is clear, as there is no open port 4713.

So, if pyhoca or python-x2go is not able to handle this, is there a 
chance to let pulseaudio open this port otherwise? I think of some kind 
of script, which will be executed before pyhoca ...

So long,
Tim