MX-21 beta 1 feedback thread

[grg]

The package installer failed (three times) when trying to use it by double clicking on a .deb install package downloaded from the web. There was nothing wrong with the package since it did successfully install from the command line with "sudo apt install code_1.58.2-1626302803_amd64.deb". The binary I was installing was the latest visual studio code.
The package installer gui would load and did indicate that all dependencies were met. When 'install' was clicked, the process would just silently fail. Since I do not know where to look for possible error logs, I cannot provide one for you.

[SwampRabbit]

@Gaer Boy you've changed the icons LibreOffice is using somehow, you can tell from comparing your pic to the one d.o. just shared.
It looks like you have Breeze Dark set. I checked and OOTB it's fine.

Can you go to Tools> Options > LibreOffice - View > Icon style to "Automatic (Colibre)

[SwampRabbit]

The package installer failed (three times) when trying to use it by double clicking on a .deb install package downloaded from the web. There was nothing wrong with the package since it did successfully install from the command line with "sudo apt install code_1.58.2-1626302803_amd64.deb". The binary I was installing was the latest visual studio code.
The package installer gui would load and did indicate that all dependencies were met. When 'install' was clicked, the process would just silently fail. Since I do not know where to look for possible error logs, I cannot provide one for you.

Please provide a link to where you got this .deb.

There does seem to be an issue with the pkexec and gdebi-gtk when doubleclicking on a .deb file, but running it manually in a terminal works.

I've been installing .debs for weeks on all our internal Alphas and Betas without issue by Right Clicking and selecting "Install Deb Files" ... so that can be used in the meantime if someone needs it.

Have you tried using MX Package Installer (MXPI) > Popular Applications > Development?
I just tried it, it installs the exact version without issue.

Edit: don't need a link to the .deb, just install VSCode using MXPI, installing .debs via right click menu, something is up with GDebi though

[dolphin_oracle]

The package installer failed (three times) when trying to use it by double clicking on a .deb install package downloaded from the web. There was nothing wrong with the package since it did successfully install from the command line with "sudo apt install code_1.58.2-1626302803_amd64.deb". The binary I was installing was the latest visual studio code.
The package installer gui would load and did indicate that all dependencies were met. When 'install' was clicked, the process would just silently fail. Since I do not know where to look for possible error logs, I cannot provide one for you.

thank you. I presume you mean "gdebi" when you say package installer.

[SwampRabbit]

@dolphin_oracle please see my edit above, yep its a gdebi issue but only seems an issue when double clicking a .deb file

[dolphin_oracle]

@dolphin_oracle please see my edit above, yep its a gdebi issue but only seems an issue when double clicking a .deb file

ok thanks.

I hate gdebi...

[timkb4cq]

We adopted it, but the migration is beyond my non-existant python skills.
source is here. this would be a good one to get in if someone can take it over. https://github.com/MX-Linux/disk-manager

Not only would it need to be ported to python3 but to Gtk3/GIO (or Qt5) from Gtk2 since bullseye doesn't have python3-gtk.
The pure python parts look pretty easy to fix (without digging too far into it - there could always be a hidden monster) - the GUI parts not so easy.

[davemx]

WARNING:

I was installing the beta to test it. With the new way of organising partitions, I thought I'd see what happened if I set a partition other than that which I was installing on, to something like /mnt/otherdistro and the type to "preserve". The next screen advised me that, indeed, the partition would be mounted at /mnt/otherdistro and the partition would not be formatted. So, I went back, added a partition which has all my data on at /mnt/Data to be preserved. Which the next screen assured me was going to happen. Guess what? All my data has been wiped! (and the partition wasn't even mounted!) My fault for not backing it up, but to save anyone else from testing that feature I'm posting this here. I will double post at the forum on this occasion because it's important.

[dolphin_oracle]

WARNING:

I was installing the beta to test it. With the new way of organising partitions, I thought I'd see what happened if I set a partition other than that which I was installing on, to something like /mnt/otherdistro and the type to "preserve". The next screen advised me that, indeed, the partition would be mounted at /mnt/otherdistro and the partition would not be formatted. So, I went back, added a partition which has all my data on at /mnt/Data to be preserved. Which the next screen assured me was going to happen. Guess what? All my data has been wiped! (and the partition wasn't even mounted!) My fault for not backing it up, but to save anyone else from testing that feature I'm posting this here. I will double post at the forum on this occasion because it's important.

we need your /var/log/minstall.log please. it will have been copied to the installed system.

[davemx]

we need your /var/log/minstall.log please. it will have been copied to the installed system.

Can't help with that. I initially thought that the problem was elsewhere so I installed another Linux over it in a vain attempt to get access to my other partitions. I didn't realise that they were empty!