Repository navigation
dbus service timeout handling for D-Bus activation #2
Description
I did some tests for D-Bus service activation again for firewalld (https://bugzilla.redhat.com/show_bug.cgi?id=876683) and it seems that having consumers (senders) of a D-Bus interface is not an issue any more. Registered signal receivers are working if the service is started again. Maybe there have been other issues or special cases that you are aware of that are not working in case of using D-Bus activation.
I recognized though that switching from one D-Bus implementation to another one was not working. I tested dbus-python to gdbus (with gobject introspection). In this case not even name owner changed seems to be working.
This might need further investigation.
Activity
nphilipp commentedon Sep 22, 2015
We were talking about this earlier, just for reference: Are you talking about switching the DBus implementation on the client or on the backend side (I assume client)?
Anyway, I have no idea what could cause this, the implementation shouldn't really matter at all for
NameOwnerChangedsignals to get through. I'm kind of at a loss here, but thankfully this shouldn't really affect productive use because these kind of changes should only come in when an OS is upgraded to a subsequent release, involving a reboot or at least a restart of the service.