Hi,
I'm trying to watch http://www.youtube.com/watch?v=HWqP-ejD6qA on a Debian Squeeze server ("pure" stable) with x2go's stable packages. Client is Windows 7, 32-bit. While it seems to work at first, the browser will lock up after a while and/or sound will simply cease to work. The issue is the same with the current as well as the older clients, and playing with the settings didn't help, either: With some settings, it basically works, but has the issues described above, with others, the session won't start at all or no sound is available.
@Mike: I remember you once mentioned that there was a newer version of pulseaudio available that would have to be manually merged with the Windows x2goclient. Is that still the case, or has the newer release been integrated into the Windows x2goclient?
-Stefan
On Thu, Mar 8, 2012 at 1:41 PM, newsgroups.mail2@stefanbaur.de <newsgroups.mail2@stefanbaur.de> wrote:
Hi,
I'm trying to watch http://www.youtube.com/watch?v=HWqP-ejD6qA on a Debian Squeeze server ("pure" stable) with x2go's stable packages. Client is Windows 7, 32-bit. While it seems to work at first, the browser will lock up after a while and/or sound will simply cease to work. The issue is the same with the current as well as the older clients, and playing with the settings didn't help, either: With some settings, it basically works, but has the issues described above, with others, the session won't start at all or no sound is available.
Have you tried disabling "Use SSH port forwarding to tunnel sound system connections through firewalls"?
I find that is the only way to get sound (and videos with sound) to work reliably with the Windows x2goclient. Except with client 3.01-13 (and earlier), where that is not necessary.
Am 08.03.2012 23:11, schrieb John Williams:
On Thu, Mar 8, 2012 at 1:41 PM, newsgroups.mail2@stefanbaur.de <newsgroups.mail2@stefanbaur.de> wrote:
Hi,
I'm trying to watch http://www.youtube.com/watch?v=HWqP-ejD6qA on a Debian Squeeze server ("pure" stable) with x2go's stable packages. Client is Windows 7, 32-bit. While it seems to work at first, the browser will lock up after a while and/or sound will simply cease to work. The issue is the same with the current as well as the older clients, and playing with the settings didn't help, either: With some settings, it basically works, but has the issues described above, with others, the session won't start at all or no sound is available. Have you tried disabling "Use SSH port forwarding to tunnel sound system connections through firewalls"?
I have (you had suggested it before), with the result that I don't have sound at all. Of course, the most likely reason for that is that my server indeed is behind a firewall, and I'm ssh'ing into it through that firewall (via port-forwarding)...
-Stefan
On Thu, Mar 8, 2012 at 2:15 PM, newsgroups.mail2@stefanbaur.de <newsgroups.mail2@stefanbaur.de> wrote:
I have (you had suggested it before), with the result that I don't have sound at all. Of course, the most likely reason for that is that my server indeed is behind a firewall, and I'm ssh'ing into it through that firewall (via port-forwarding)...
Ha! Sorry if you already told me that, and I forgot. Yes, I suppose the workaround of disabling sound tunneling is useless if the client and server are separated by a firewall.
I don't understand why tunneling the sound results in intermittent failures, but it does seem like that should be the focus of any debugging efforts to understand this problem with the Windows client.
-
John Williams -
newsgroups.mail2＠stefanbaur.de