MX Linux Forum

rod178 wrote: Mon Jul 08, 2024 10:45 am

Code: Select all

           Active apt repos in: /etc/apt/sources.list.d/atom.list 
           1: deb [arch=amd64] https://packagecloud.io/AtomEditor/atom/any/ any main

As mentioned already
1st: remove the no-longer working atom repo Next:
on command line:
update package list ignore any warnings.
upgrade to latest mxpi ignore the warnings.
Now open MXPI
and install Google Chrome from MXPI->Pop.Apps->Browser
The warnings will we gone after installing.
+++EDIT+++
Do also upgrade to latest checkaptgpg and rerun This will fix a deprecation warnings create by usage of apt-key.
( Someone may adjust the chrome installer in MXPI )

@fehlix I see mixed MBR and GPT, is that going to be an issue, maybe?

Eadwine Rose wrote: Mon Jul 08, 2024 11:12 am @fehlix I see mixed MBR and GPT, is that going to be an issue, maybe?

Depends on the UEFI firmware, in theory it is allowed, but the best practice has shown,,
both GPT and MBR may go through different firmware driver, and by this
may create issue, in case firmware developer have not tested well enough
the combo of MBR + GPT with UEFI booting.
Recommendation: Stay with GPT in UEFI booting.

This will fix a deprecation warnings create by usage of apt-key

Thanks for the detailed response.
The execution of the commands did resolve the error messages in MX Package Installer and Chrome did seem to reinstall, although would still not run. I later Purged and Installed with the same result.

Something seems broken, so I will later do a MX23.3 clean install and rebuild from scratch, something that I am not looking forward to!

Also noted the comments on the 'preference' for GPT over MBR, which from memory is selected during a fresh install, under Advanced tab
My MB is over 14 years old, never updated the firmware, so UEFI compatibility may be an issue, although never seemed an issue previously, and have installed MX many times on several machines.

My issues started after I reinstalled my MX21.3 system from an MX Snapshot via a (UEFI) Live USB, which I have done previously with no issues.
All else is working fine except the Paths in LuckyBackUp ie 'mnt' was changed to 'media', easily resolved
Also note that the Live USB that I used for the Installation runs with no issues as UEFI booted Live USB ie Chrome runs fine.

The reinstall goes pretty easy if you preserve your home during it, and run our newer tool user-installed-packages first to create a list of your extra package installs, and then use that list to reinstall them. Some that have trouble with UIP can be reinstalled with MXPI, such as Google Chrome.

Working somewhat better after removing LUKS on the system SSD, although still some cleaning up to do. Will then have another attempt as installing MX23 over MX21, without LUKS, then install Chrome.
GRUB does not seem to like LUKS, at least for me, so was also causing some boot issues.
Next step is to transfer all my sensitive data to a separate LUKS encrypted drive, which is best practice anyway, although will take some significant reorganisation as I'm running out of spare drives.
I'll post the outcome next week,

rod178 wrote: Tue Jul 09, 2024 2:16 am GRUB does not seem to like LUKS, at least for me, so was also causing some boot issues.

GRUB has limited support for LUKS2 with several caveats that make it more than a little difficult to use. If you intend to use LUKS2, use a bootloader that fully supports it. If you want to use GRUB, stick with LUKS1.

Finally got all working again, ie Chrome. Installed an old Snapshot and added back the missing data. Thanks all for the advice.

Seems that LUKS corrupted something related to Chrome. No other programs were affected and I've used LUKS (suppose LUKS 1) previously with no issues.