Arctica greeter malfunctioning under arch linux?

hello, there seems to be an issue with arctica-greeter under arch linux, i dont know why this happens but when i try to use this greeter, its resulting in a black screen and it seems to be restarting itself over and over.
i used this aur to install it but i did some changes to make it build successfully.
https://aur.archlinux.org/packages/lightdm-arctica-greeter

i tried downgrading to 0.99.3.0 and 0.99.4.0 and its the same result except it doesnt keep restarting.
could this issue be an incompatibility with newer versions of the dependencies?
whats weird is that debian seems to have a lot of dependencies for arctica-greeter compared to this aur so im not sure if this aur package was set up properly.
these are all the log files from /var/log/lightdm
lightdm.zip

this error in particular persists even if i dont have ayatana indicators installed.
** (process:917): WARNING **: 01:48:28.433: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such method ?RegisterClient?

i figured out that the issue might be caused by the latest update to mate-settings-daemon.
i downgraded mate-settings-daemon from 1.28.0 (latest version at the time of this issue) to 1.27.0 and that was the step that allowed me to finally load up arctica-greeter.
i suspect mate-settings-daemon 1.27.1 to be the cause of the issue since mate-settings-daemon 1.28.0 was nothing more than a translation update.
please fix this incompatibility with the latest version if you do not mind.

@tempuSr12 Can you pinpoint a patch between 1.27.0 and 1.27.1 of m-s-d that caused the imcompatibility?

im not a programmer or coder at all so im not sure i can point out what exactly caused this issue in detail but i did find out which commit in mate-settings-daemon introduced this issue for arctica-greeter.
if you revert all the changes from this commit in the latest mate-settings-daemon source then arctica-greeter boots up.

mate-desktop/mate-settings-daemon@b99fca7

though i had to revert these two commits as well to ensure that it builds successfully as doing otherwise gave me linker errors.

mate-desktop/mate-settings-daemon@66b5dde

mate-desktop/mate-settings-daemon@863aaf7

@sunweaver

Debian Testing with mate-settings-daemon 1.26 and Manjaro with mate-settings-daemon 1.28 are the same up to this point:

** (mate-settings-daemon:935): WARNING **: 21:03:16.872: There was a problem when setting QT_SCALE_FACTOR=1: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such method “Setenv”

after this

Debian Testing with mate-settings-daemon 1.26:

[+5.52s] DEBUG: arctica-greeter.vala:183: xsettings is ready
[+5.52s] DEBUG: arctica-greeter.vala:832: Creating background surface
[+5.56s] DEBUG: menubar.vala:235: Directly fetched sensitive color: rgb(238,238,238)
[+5.56s] DEBUG: menubar.vala:272: Adding override style provider to child widget GtkAccelLabel
[+5.56s] DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created
[+5.56s] DEBUG: util.vala:49: Updating DBus activation environment, updating 'INDICATOR_GREETER_MODE' to '1'
[+5.56s] DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created
(LOG CONTINUES)

Manjaro with mate-settings-daemon 1.28

[+4.32s] DEBUG: settings-daemon.vala:343: Our fake org.gnome.SessionManager received RegisterClient request (app_id: mate-settings-daemon, client_startup_id: ), returning ObjectPath /org/ArcticaProject/artica_greeter/client/2
(LOG ENDS HERE)

I have narrowed it down to this:

arctica-greeter/src/arctica-greeter.vala

Lines 179 to 189 in a673035

    
           settings_daemon_proxy.plugin_activated.connect ( 
        
               (name) => 
        
               { 
        
                   if (name == "xsettings") { 
        
                       debug ("xsettings is ready"); 
        
                       xsettings_ready (); 
        
                   } else { 
        
                       debug ("settings-daemon plugin %s loaded", name); 
        
                   } 
        
               } 
        
           );

We never get any PluginActivated signals. Strangely enough, I can't see any changes in this regard on the MATE side.

Reported upstream:

mate-desktop/mate-settings-daemon#418

	settings_daemon_proxy.plugin_activated.connect (
	(name) =>
	{
	if (name == "xsettings") {
	debug ("xsettings is ready");
	xsettings_ready ();
	} else {
	debug ("settings-daemon plugin %s loaded", name);
	}
	}
	);