After repeated testing of PulseAudio builds leading up to PulseAudio
3.0, I determined that this commit introduced this
bug/incompatibility:
7fad67c46188991c04a42b190349ebb3f4a1756f
2012-05-15 17:06:53 (GMT)
Am 13.03.2014 05:17, schrieb Michael DePaulo:
After repeated testing of PulseAudio builds leading up to PulseAudio
3.0, I determined that this commit introduced this
bug/incompatibility:
7fad67c46188991c04a42b190349ebb3f4a1756f
2012-05-15 17:06:53 (GMT)
Actually, I spoke too soon.
7fad67c46188991c04a42b190349ebb3f4a1756f appears to have introduced an
even worse regression. The regression that prevents me from starting
pulseaudio.exe altogether. Specifically, I cannot even start it from
the command line. This regression occurs even when the
Also, Alex,
pulseaudio.exe provides me with good debug output on the command-line
if I pass --log-level=debug to it. How could I go about making
x2goclient.exe record/display that output? I am OK with either writing
it to a file, or having it go to the usual x2goclient console/debug
output.
