<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Changing device profile to HDMI is reset to default after short delay"
href="https://bugs.freedesktop.org/show_bug.cgi?id=93946#c5">Comment # 5</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Changing device profile to HDMI is reset to default after short delay"
href="https://bugs.freedesktop.org/show_bug.cgi?id=93946">bug 93946</a>
from <span class="vcard"><a class="email" href="mailto:patrakov@gmail.com" title="Alexander E. Patrakov <patrakov@gmail.com>"> <span class="fn">Alexander E. Patrakov</span></a>
</span></b>
<pre>So (without the log) I have a theory.
When the monitor is DPMSed, its HDMI audio port becomes unavailable. PulseAudio
notices that and, due to module-switch-on-port-available, switches. To verify
the theory, please disable the module in /etc/pulse/default.pa, enable DPMS,
and retest.
It would be especially interesting (but I understand that it's a bit more than
one can expect from a user) if you compiled PulseAudio from git, with this
commit reverted, just to prove or disprove that it is indeed the curlpit:
author David Henningsson <<a href="mailto:david.henningsson@canonical.com">david.henningsson@canonical.com</a>> 2015-11-17
14:10:35 (GMT)
committer Tanu Kaskinen <<a href="mailto:tanuk@iki.fi">tanuk@iki.fi</a>> 2015-11-22 02:59:30 (GMT)
commit e87100d41ef6d14f8dc7f803582191d9f8d8f183 (patch)
tree 51caaca6a650c58a702fedb0a0228f7cf7775c23
parent 063a1d350fad1cb6fac28dbffe26a7e805626cb2 (diff)
module-switch-on-port-available: Route to preferred profile
This makes the routing slightly more aggressive:
* It will try to route to another profile, if such a profile
is preferred by the port.
* It will allow changing profiles on transitions both to
PA_AVAILABLE_YES and PA_AVAILABLE_NO
To accommodate there is also some refactoring.
Signed-off-by: David Henningsson <<a href="mailto:david.henningsson@canonical.com">david.henningsson@canonical.com</a>>
There is also a patch on the mailing list that attempts to fix up the module
for a different bug, but I suspect that it will not help:
<a href="https://patchwork.freedesktop.org/patch/72053/">https://patchwork.freedesktop.org/patch/72053/</a></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>