<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - org.bluez.MediaEndpoint1.Release should do nothing, not raise a DBUS error"
href="https://bugs.freedesktop.org/show_bug.cgi?id=104646#c5">Comment # 5</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - org.bluez.MediaEndpoint1.Release should do nothing, not raise a DBUS error"
href="https://bugs.freedesktop.org/show_bug.cgi?id=104646">bug 104646</a>
from <span class="vcard"><a class="email" href="mailto:faminebadger@googlemail.com" title="faminebadger@googlemail.com">faminebadger@googlemail.com</a>
</span></b>
<pre>Yes, that seems to work.
However, I think it's not the best design to check dbus_message_get_no_reply in
endpoint_release. That means there will be dozens of other places that
construct dbus responses that remain unprotected.
I think it preferable to find a place higher up that call tree that is common
to all dbus message handlers (or at least all bluez ones) that can check the
flag and destroy any unsolicited message that has been constructed and returned
by the individual handlers.
That would fix this, but also every other possible instance.</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>