BL4.5-32bit - cannot install deb
 

I'm trying to install a DEB package by double clicking it.
Privileges in the file's properties are like this:
Show content: everybody
Change content: Owner only
Execute: Owner only

eSudo comes up with the command:

gdebi-gtk /Path/to/the/DEB

Below that, I enter my password and hit OK, but nothing happens.

What's wrong, please?

Are you sure the command is gdebi-gtk? Most distros call it gdebi.

As a workaround, you can install it from the command line with apt. for example
sudo apt install ./filename.deb

At least if that doesnt work, you might see the error. Maybe it's a 64-bit deb?

Sorry, I have to postpone this topic.

I'm back asap.

@ enigma9o7

You're right, it was a 64bit DEB.
But I tried another one, but it didn't work either.

@ hazel
I'm not sure about that, so far.

Did you try install the other one with apt from command line? If it didnt work, what was the output?

edit: what are you trying to install? sometimes i, and i imagine, others read msgs and try it themselves

This happens if esudo is broken. Either reinstall esudo or use policy kit.

we have mentioned policykit to this guy before for other issues. seems he did not fix it andhe keeps running into all of these various issues.

I remember having this issue before, but I forgot how to fix it, especially by using the policy kit.

In fact, I did fix it back then, but now it's happening again,
which leads me to the question, why is eSudo broken again?

Perhaps somethings are best left unexplained ...

But anyways policy kit updates will always overwrite it as it is currently packaged. For what it matters I didn't package it and I recommend replacing with policy kit anyways. If you wish to use esudo and not pkexec then either stop policy kit stuff from updating or always reinstall esudo afterwards. I wish to avoid this problem in BL 6.0 but as it is already a done deal in BL 5.x I am uncertain how best to 'fix' it.

Again, I cannot install a DEB.

What on earth is this? Again and again, it is failing, which meanwhile is annoying as hell.
Sorry, but it is annoying, because each time, I have this issue, I fix it, and some weeks or months later, when I want to install an updated version of a DEB, I'm running into this again and again.

As far as I understood, I am supposed to install policykit-1-gnome on BL5-64bit, but now I'm on BL4.5-32bit (since I have two computers with different versions of Bodhi).
On BL4.5, I should reinstall esudo, right?... Well, I did that, but with no effect.

Btw. ... you think, some things are best unexplained? Sorry, I prefer to understand what's going on... (oh, and let me add, no offence intended, but actually, I prefer to be addressed not as "this guy", but by my name, respectively nick name in this case)

So, could you (or whoever is able or willing to) please tell me how to fix this for

a) BL4.5
b) BL5

and for both architectures, please, in case this makes any difference.

Still waiting for help...
Reinstalling eSudo or installing the policykit package didn't help for BL4.5-32bit.

You not only have to install policykit, but also add it to startup programs. At least for BL5, and I have confirmed it works on 32-bit BL5 too. But, I also don't know if that applies to BL4.5.

But as a workaround, you can install debs with sudo apt install ./filename.deb. Or even sudo gdebi-gtk ./filename.deb prolly works too. And other apps like synaptic gparted grub-customizer etc you can sudo them from command line. I agree its annoying, but you can still function around it (as we all had to do until fairly recently).

a) In fact, I did add policykit (its agent) to the startup programs.
I just didn't mention this step, because I consider it part of the installation of the policykit.

The policykit solution does indeed work for BL5-64bit.
Not sure, if this is true for BL5-32bit as well,
because I don't have the 32bit version.

b) None of your suggestions to install a DEB is working on BL4.5-32bit.
The only chance to succeed is when I do:

First of all there is going to be no difference between what works for 64 bit vs what works for 32 bit almost 100% of the time.

Second of all BL4.5 is unsupported and not maintained. Unless someone volunteers to take on BL 4.x maintenance or we receive a donation so larger Štefan and I can quit our jobs and work full time on Bodhi this is unlikely to change. If at all possible update to BL 5.0. If you can't update to BL 5.0 then the support you receive here is going to be variable. I personally can't waste my time looking at issues which are almost certainly self inflicted.

Third, it is unclear what issue you are even having. Are you saying doubling clicking on a deb file in pcmanfm fails to launch the esudo dialog which then launches gdebi? or that gdebi fails to launch after you type your password into esudo? Or do you mean something else.

I took the time to create a BL 4.5 VM, updated/upgraded the VM and gdebi is still working and is launched by esudo regardless of the policy kit thing (with or without it). That is because Jeffs package, gdebi-bodhi-launcher, is installed on BL 4.5 by default and it changes the gdebi desktop file.

As far as you saying, "Sorry, I prefer to understand what's going on.." that is understandable. Please take the time to learn linux. Whatever issue yo are having here, whatever you did to break your system would be a trivial thing to fix if you knew your way around linux and debian package management.

So explain in as much detail as you can what is going on what problem you are having. What version of esudo, gdebi and so on do you installed. Any error messages or errors in xsession-errors and so on.