<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - systemd emits UnitNew in response to Properties.Get, potentially leading to loops."
href="https://bugs.freedesktop.org/show_bug.cgi?id=69575#c1">Comment # 1</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - systemd emits UnitNew in response to Properties.Get, potentially leading to loops."
href="https://bugs.freedesktop.org/show_bug.cgi?id=69575">bug 69575</a>
from <span class="vcard"><a class="email" href="mailto:marius.vollmer@redhat.com" title="Marius Vollmer <marius.vollmer@redhat.com>"> <span class="fn">Marius Vollmer</span></a>
</span></b>
<pre>Fwiw, I am still seeing this behavior with systemd 219. As a workaround, I am
now listening to the Reloading, JobNew, and JobRemoved signals instead of
UnitNew. This seems to catch all points where unit properties might change
without a PropertiesChanged signal.</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>