----- "Dan Williams" <d...@redhat.com> wrote: > > /var/log/messages: > > Mar 25 19:51:58 localhost dbus-daemon: Rejected send message, 2 > > matched rules; type="method_return", sender=":1.12" (uid=0 pid=1424 > > comm="/usr/sbin/bluetoothd) interface="(unset)" member="(unset)" > error > > name="(unset)" requested_reply=0 destination=":1.10" (uid=0 > pid=1414 > > comm="NetworkManager)) > > At what point does that failure come? This could be caused by recent > (well, year-old) dbus policy changes for unrequested reply messages > which I'm not 100% sure how to get fixed... > > walters; what could be the cause of this sort of thing again?
The operative component here is "requested_reply=0", and the policy is to reject unrequested replies. Often this is harmless because if a message wasn't expecting a reply, denying a reply shouldn't matter. If however the binding/code was setting no_reply AND actually expecting to process the reply, that's a bug in the calling code. _______________________________________________ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
