I've tried several times to update my Discord. It's a simple .deb download, and I open up the file to run in gDebi, click Install, and the whole box goes away and nothing happens.

which version of bodhi are you running?

i need this info as well. i am on Bodhi 5.0 and i just cant run DEB files like the OP. to even use synaptic requires sudo synaptic to run but opera and team viewer are not in this, only via deb files from their sites.

start gdebi from the terminal, reproduce the problem, and show us what output you get.

sudo apt install --reinstall esudo

that will fix it. happened for me a couple days ago too. this is a reoccurring issue with bodhi, often needed after updates.

1 members found this post helpful.

I'm running 5.0.0. hope the fix works, I'm not at home tonight.

1 members found this post helpful.

Chances are you need to run a policykit like lxpolkit. It needs to be enabled in the start up apps.

2 members found this post helpful.

When I installed Bodhi 5.0.0, I was told that esudo conflicted with policykit, was told to update policykit2 and disable esudo. Now I'm being told to reinstall esudo... has the conflict with policykit been resolved? Anyhow, going now to run the supposed fix.

zaivala@zaivala-ThinkPad-T430:~$ sudo apt install --reinstall esudo
[sudo] password for zaivala:
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
Need to get 7,868 B of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://packages.bodhilinux.com/bodhi bionic/b5main amd64 esudo all 1.39bodhi8 [7,868 B]
Fetched 7,868 B in 0s (25.9 kB/s)
(Reading database ... 189093 files and directories currently installed.)
Preparing to unpack .../esudo_1.39bodhi8_all.deb ...
Unpacking esudo (1.39bodhi8) over (1.39bodhi8) ...
File /usr/bin/pkexec-old exists, moving it back now that esudo is removed
Processing triggers for mime-support (3.60ubuntu1) ...
Processing triggers for desktop-file-utils (0.23-1ubuntu3.18.04.2) ...
Setting up esudo (1.39bodhi8) ...
File /usr/bin/pkexec exists, replacing it with esudo
zaivala@zaivala-ThinkPad-T430:~$

The suggested fix works. I won't mark this as "Solved" until I hear back about the policiykit thing.

I dunno about the policykit stuff. I just know that reinstalling esudo fixes this when it happens for me. Maybe the policykit thing is a permanent fix, if so I'm also interested in how to do it. Where'd you get the advice to disable esudo?

1 members found this post helpful.

No the esudo conflict with policykit has not been resolved. In some cases and for some apps reinstalling esudo after policykit has broken its substitution for pkexec works. But it does not work across the board for all applications using pkexec.

The advice came from me. And disabling esudo is not what was suggested, I merely suggested marking it so that it is never updated unless you force an update.

1 members found this post helpful.

Ok thanks! Read those. Decided to try the "sudo apt-mark hold esudo" command to see if that alone prevents this from happening again for me.

1 members found this post helpful.

i think this is related to another thread on policykit- i followed Robert's advice and have not had any issues since.

(wish i knew 1/2 of what he knows!!!).

Thanks Ylee

1 members found this post helpful.

Makes me wonder if this isn't related to Ubuntu removing gksudo from it's repo and distro and instead trying to use pkexec and the admin:// path instead. Isn't esudo another form of gksudo?

I use a file manager action with pcmanfm, to open folders as admin. I had to create a policy in /usr/share/polkit-1/actions, and a script for pcmanfm-pkexec in /usr/bin The Ubuntu way of using admin://some/folder is a pain. all ya get done doing is entering your password.