<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [abrt] pulseaudio: pa_sink_input_set_requested_latency_within_thread(): pulseaudio killed by SIGSEGV"
href="https://bugs.freedesktop.org/show_bug.cgi?id=93443#c8">Comment # 8</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [abrt] pulseaudio: pa_sink_input_set_requested_latency_within_thread(): pulseaudio killed by SIGSEGV"
href="https://bugs.freedesktop.org/show_bug.cgi?id=93443">bug 93443</a>
from <span class="vcard"><a class="email" href="mailto:tanuk@iki.fi" title="Tanu Kaskinen <tanuk@iki.fi>"> <span class="fn">Tanu Kaskinen</span></a>
</span></b>
<pre>Ok, the problem is that once the old alsa sink is gone and the new alsa sink
isn't yet created, the echo-cancel sink isn't connected anywhere.
module-device-manager changes the routing of the pacat stream (which is
connected to the echo-cancel sink) during the profile change. I guess it tries
to move pacat from the echo-cancel sink to the null sink. That doesn't seem
very smart, but I thought that in principle we should support that. However, it
turned out that making it work is pretty much impossible with the current
architecture.
So, our architecture doesn't support rerouting streams on top of virtual sinks
that themselves are being moved. There doesn't seem to be any easy way to
change that. I'll try a different approach next: rerouting pacat in this case
is not useful, so there should be some way to prevent that from happening.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>