* On 12/18/19 10:33 AM, Alexanderstr Miete wrote:
> Interesting. Thanks for the update. I also notice that no sound via standard
> PulseAudio (which previously worked) is transmitted to the client anymore from
> any remote machine (default port 4713, SSH port forwarding). Is that related
> to
>
Interesting. Thanks for the update. I also notice that no sound via
standard PulseAudio (which previously worked) is transmitted to the client
anymore from any remote machine (default port 4713, SSH port forwarding).
Is that related to this bug here too?
Control: forwarded -1
https://bugs.launchpad.net/ubuntu/+source/libssh/+bug/1856795
Control: reassign -1 x2goclient 4.1.2.1
Control: close -1
* On 12/16/19 7:42 PM, Alexanderstr Miete wrote:
> Is this similar issue probably related?
> Can we narrow down the reason for this bug?
> I can
Is this similar issue probably related?
Can we narrow down the reason for this bug?
I can reproduce it on at least 2 different remote instances of Ubuntu,
however I have only one client machine to test from at present.
https://bugzilla.redhat.com/show_bug.cgi?id=1057871#c19
Am Sa., 14. Dez. 2019
Package:
Body:
Package:
Version:
Not sure, if this is a real bug. But it seems to have been an issue
before (See here:
https://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=227)
Surprisingly, without any known changes, we suddenly receive a new error
when establishing previously error free
