There might be a problem with Bodhi's implementation of esudo replacing pkexec.

Use case: I've installed an alternative set of update tools from a PPA, that's owned by a former member of the official Linux Mint developer team:
https://easylinuxtipsproject.blogspo...buntuplus.html

They install fine, as expected. However, soon installing updates with that alternative updater fails. I've asked the PPA developer to look into it, which he was kind enough to do.

According to him, the esudo replacement of pkexec in Bodhi, breaks on the first update to or reinstall of the policykit-1 package. Which, again according to him, can only be fixed in the distribution itself.

Could you perhaps take a look into that?

A reasonable workaround would probably be, to install a polkit authentication agent in Bodhi. Which packages do I need to apt-get for that?

Update: I'm testing this:

Followed by:

...which (so far) appears to work as intended.

You should read my post esudo changes.

eSudo's introduction in Bodhi was not something I personally did and I always removed it anyway, regardless of the fact removing it used to be a bit of a hassle. But anyway if Bodhi 5.0 is up to date and ya install and use polkit authentication agent as suggested in the above forum post ya should be good to go.

1 members found this post helpful.

Thanks! Will this fix be included in the next Bodhi release?

Yes of course. Moksha,if updated to latest version, already adds policykit-1-gnome to startup on first boot. You prob didn't notice that. After installing BL 5.0 your first boot is using the old version of moksha and then unless you delete your ~/.e folder every other reboot Moksha will be using your configuration from ~/.e and will not recreate the ~/.e folder or change apps in startup.

But our next release will no longer use esudo for pkexec and will use a polkit authentication agent for pkexec as it should. Maybe in time we will provide native e/efl code for the polkit authentication agent, I would like to. I am unsure how difficult that would be and I don't want to do it and add it to the repos unless I 'get it right.' It is however in my plans and on our list of stuff to do. Considering the possible difficulty of that, that task prob falls solely on me, unless we get more capable devs willing to help.

1 members found this post helpful.

Good to hear!

1 members found this post helpful.