<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - HDMI output source not remembered" href="https://bugs.freedesktop.org/show_bug.cgi?id=100064#c10">Comment # 10</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - HDMI output source not remembered" href="https://bugs.freedesktop.org/show_bug.cgi?id=100064">bug 100064</a> from <a class="email" href="mailto:tanuk@iki.fi" title="Tanu Kaskinen <tanuk@iki.fi>"> Tanu Kaskinen</a> <pre>That's weird indeed. The second instance removes the pid file: W: [pulseaudio] pid.c: Stale PID file, overwriting. If the pid file was created by the first instance, the second instance should have at this point noticed that a daemon was already running. Now the second instance determined that there's no other daemon running. This can happen if kill(pid, 0) fails. When passing 0 as the signal, no signal will be sent by kill(), but permission checks are done, so maybe pulseaudio doesn't have the permission to send any signals. Immediately after starting, the second instance receives SIGTERM. What's sending that signal? It looks like a controlled start-stop sequence, so I would guess that systemd is doing this. I don't have any idea why, though. Does the systemd journal have any strange stuff in it about starting pulseaudio? I don't know if this is related to the routing problem. It seems possible that the second instance messes something up, but I haven't yet studied the logs in detail.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>