Hey @ dancaer69 that's exactly what's happening to me, with the difference that your workaround only helps me mount partitions or devices. I still can't get any prompt for privileges elevation, with or without any DM. The only desktop showing me a prompt without any hack is KDE, but only with lightdm or without any DM. If I am right polkit is now fully dependent from (e)logind and getting it to work with an authentication agent is not an easy job.

Hello

Unfortunately, it seems to me that we are up at the front of the wall and that an action will have to be taken fairly quickly. The point is that consolekit2 even in the last release is already not a solid alternative to elogind and the horizon seems to be more and more distant for a chance to get the same compatibility with all the softwares as elogind has.

I would really like to have eric's opinion on this subject to understand where the problem comes from, if it is possible to solve it and if not what is to be considered for the future.

Honestly, after taking the advice of a former moderator of this forum, I got rid of all that policy-related stuff, since (as he told me) it only matters if you wanna automate stuff.

What's the worst impact on me? I have to run 'sudo gparted' rather than try to boot it any other way.

What's the benefit? Less resources used, more direct CLI usage.

I feel that my system was streamlined, not hampered, in the long run.

If I am right polkit is now fully dependent from (e)logind and getting it to work with an authentication agent is not an easy job

what do you mean? Obarun Polkit package do not support elogind at compile time.

I think we have two different issue.
First, dbus is compiled without the support of auto-launch a dbus session. That's me that any software which can try to launch a dbus-session will fail. As being said, the dbus-session should be handled by user with the dbus-session@ service. But, apparently some sotware cannot works on proper way and find the dbus session "number".
Second, like jean-michel said more and more software depends on elogind. The consolekit one is not bad or miss features, that's just dev prefer to use libsystemd (and so elogind) instead of making their software portable and compatible. Systemd is not a system manager, not only a service manager.
Complete DE will cause more and more problem due of this fact where WM will keep working correctly. On JWM i don't have any permissions issue.
So what to do?

eric wrote what do you mean? Obarun Polkit package do not support elogind at compile time.

Hi Eric, I mean that developers upstream are apparently tweaking the source code to work well with systemd, it's not by chance that even Void, that uses elogind and not the full systemd package, does not have a working automated privileges elevation prompt anymore.

Eric wrote Complete DE will cause more and more problem due of this fact where WM will keep working correctly. On JWM i don't have any permissions issue.
So what to do?

Thanks for clarifying the situation, I think that the best solution would simply be getting used to use CLI to edit system file, for example with pkexec that works fine :)

it's not by chance that even Void, that uses elogind and not the full systemd package, does not have a working automated privileges elevation prompt anymore

Pretty weird, , I have no issue with privileges elevation on Gentoo with elogind.

Me too, I had been using Redcore with no issue, maybe it depends on the DE, in plasma the authentication works perfectly, even without any DM, I tried Xfce and MATE on Void but it didn't work.