I am working with Enlightenment running on the RC of Mageia 6 and for some reason the authentication agent is not running. E does not read the xdg/autostart, but I have copied the authentication agent into E's startup application folder. This is the standard procedure recommended for E and the one that works on my Manjaro installations. However, the authentication agent either does not load or does no remain running for some reason. As a result, attempting to start a program needing authentication from the menu simply fails with no action performed.

Starting the application from the terminal results in the following:

$ mcc
==== AUTHENTICATING FOR org.mageia.drakconf.pkexec.run ===
Authentication is required to run Mageia Control Center GUI
Authenticating as: aguador
Password:
polkit-agent-helper-1: error response to PolicyKit daemon:
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
==== AUTHENTICATION FAILED ===
Error executing command as another user: Not authorized

If I load the authentication agent in the terminal, I can start applications needing authentication from the application menu or "Everything". Of course, on interrupting the program in the terminal, authentication fails.

The E package on Mageia comes with the Mate (fork of old Gnome) authentication agent. However, I have also tried with lxpolkit with the same results.

I have also searched this forum and the Internet without successfully finding a solution. I am obviously missing something . . . enabling a systemd service or . . . ?

what is mcc?
the authentication agent, or an app you are trying to start with the authentication agent?
what is the command for succesfully starting the authentication agent? is it the same as the one you are using in the autostart? are you sure the command is actually getting executed? have you made tests, like "Echo 'executed!' > testfile"?

"mcc" is one of the ways of calling the Mageia Control Center, a graphical configuration tool that I used to illustrate the error message.

In the terminal, "lxpolkit" is all that is needed to start the authentication agent. In E's applications at startup it is listed as "/etc/xdg/autostart/lxpolkit.desktop" a format that works in both my Manjaro installations. After reading your reply I tried "lxpolkit.desktop" and "lxpolkit", as well as moving lxpolkit to be the first application loaded. None of this produced any change.

In the initial post I should have noted:

$ ps aux | grep polkit
polkitd 2988 0.0 0.3 379032 13724 ? Ssl nov15 0:00 /usr/lib/polkit-1/polkitd --no-debug

In other words, the polkit daemon is running, but not the authentication agent. The same command in my Manjaro systems shows both polkitd and lxpolkit running.

I have also poked around in the DM for possible configuration issues. (My Manjaro systems use Entrance and Mageia uses lxdm.) However, I see nothing related to authentication in the config files used by the respective DMs.

I have to apologize. I have been beating my head against a wall on this one for a while only to realize today that perhaps NONE of the startup applications were running . . . which turns out to be the case. None of the "~/.e/e/applications/startup/.order" are being loaded.

I have never experienced this in E before, so despite now having the right question, I still have no answer.

Special thanks to ondoho for replying to the original post.

Apologies to all for a) not identifying the problem correctly at the outset and b) apparently not being able to edit the title of the original post or its tags.

As it turn out, this was a bug in E20.7 that appeared with LXDM (and I believe LightDM). I ran E20.7 in another distro for months with Entrance DM with not problems.