The PluginActivated DBus signal is no longer sent

[tari01]

Expected behaviour

When I subscribe to org.mate.SettingsDaemon + /org/mate/SettingsDaemon + PluginActivated via DBus, I expect to receive a notification for each activated plugin.

Actual behaviour

As of version 1.27.1, the daemon no longer sends the PluginActivated signal

Steps to reproduce the behaviour

Launch the mate-settings-daemon and create a signal watcher for PluginActivated.
I have written a small Python test script to demonstrate this (works as expected on 1.27.0, does nothing on 1.28.0):

#!/usr/bin/env python3

from gi.repository import Gio
from gi.repository import GLib
import subprocess

pLoop = None

def onPluginActivated (pConnection, sSender, sPath, sInterface, sSignal, lParameters, pData):

    print (sInterface, sSignal, lParameters[0])

def onNameAppeared (pConnection, sName, sOwner):

    pConnection.signal_subscribe (None, "org.mate.SettingsDaemon", "PluginActivated", "/org/mate/SettingsDaemon", None, Gio.DBusSignalFlags.NONE, onPluginActivated, None)

if __name__ == '__main__':

    Gio.bus_watch_name (Gio.BusType.SESSION, "org.mate.SettingsDaemon", Gio.BusNameWatcherFlags.NONE, onNameAppeared, None)

    pSubprocess = subprocess.Popen (["/usr/lib/mate-settings-daemon/mate-settings-daemon", "--replace"])

    pLoop = GLib.MainLoop.new (None, True)
    pLoop.run ()

m-s-d-test.py.zip

MATE general version

1.28.0

Package version

1.28.0

Linux Distribution

Arch/Debian

[tari01]

The cause of the issue seem to be the changes introduced in b99fca7 by @yetist. Even after going through the whole commit, I am not able to figure out why the daemon stopped sending signals...

[lukefromdc]

I don't have enough understanding of how dbus works to do anything with this one, so a fix will have to wait for one of the other team members.