Request MX19 - Ungoogled Chromium

[dolphin_oracle]

here, try this PM file, (extract and drop it in /usr/share/mx-packageinstaller-pkglist) and then install from the MXPI->Popular Apps->Browsers area and let me know if it works.

I'm pretty sure it will fail if chromium or chromium-common is already installed.

[JayM]

It worked to add Ungoogled Chromium to MXPI, but after I installed it it looks just like regular Chromium AFAICT. It's about page says "Version 81.0.4044.138 (Developer Build) built on Debian buster/10, running on Debian buster/10 (64-bit)" and I assume that "Developer Build" refers to the ungoogled version? Maybe the OP can try it and see if this is the version he was asking for? I also assume that this is why installation will fail if you already have Chrome or Chromium installed, because this one's identical to Chromum except under the hood somewhere so MXPI will say that it's already installed (I have Vivaldi but not Chrome or Chromium. I don't like them.)

[dolphin_oracle]

It worked to add Ungoogled Chromium to MXPI, but after I installed it it looks just like regular Chromium AFAICT. It's about page says "Version 81.0.4044.138 (Developer Build) built on Debian buster/10, running on Debian buster/10 (64-bit)" and I assume that "Developer Build" refers to the ungoogled version? Maybe the OP can try it and see if this is the version he was asking for? I also assume that this is why installation will fail if you already have Chrome or Chromium installed, because this one's identical to Chromum except under the hood somewhere so MXPI will say that it's already installed (I have Vivaldi but not Chrome or Chromium. I don't like them.)

Yeah, I'm on the fence on including it because of that. I don't like unclean install actions in Popular Apps. apt reports conflicting files between 2 packages and craps out.

[JayM]

Maybe just let those who want this browser manually add it as per your instructions and knowing that they'll need to uninstall any existing versions of Chrome and Chromium first.

[andyprough]

You could probably offer up the Iridium browser instead, which is what ungoogled is a fork of. Both projects have the same goals, and Iridium's repos looked more typical to me last time I looked. Hopefully it wouldn't conflict with chromium or chrome. I'll check on it tonight if I have time.

EDIT - never mind, the Iridium browser deb is not being kept up to date, over a year old now.

[Stevo]

Getting back on topic, can I request for the OP that whoever maintains MXPI add the OBS/3rd-party/whatever repo for Ungoogled Chromium to Popular Apps/Browsers so it adds that repo to their apt sources then installs the browser, just like the entries for Brave and Chrome do? Thanks.

I support that request. Using MX-19 I tried adding the repo in the terminal. It seemed to work, but the repo didn't show up in Synaptic. The ungoogled-chromium packages had arm64 in the name despite I had added the correct Buster repo. Maybe the packages (even amd64) are built from arm source?

Then I tried to download and install ungoogled-chromium amd64 deb directly. That also fails in Gdebi. Unnamed dependency is not satisfied.

Like chromium, ungoogled-chromium isn't just one deb, it's several. That's why it's easier to install from the repo.

What happens when you follow the instructions given?

Code: Select all

sudo apt-get install ungoogled-chromium

The arm64 thing seems to be a Synaptic issue with OBS repos, but the command line works anyway. I've been using the OBS to build and host Pale Moon for years now, and have had reports of the same thing. Just use the command line. Probably the same thing with my rebuild of MX's Chromium for Debian users that don't want to add MX's repo: https://build.opensuse.org/package/show ... m/chromium

[dreamer]

Getting back on topic, can I request for the OP that whoever maintains MXPI add the OBS/3rd-party/whatever repo for Ungoogled Chromium to Popular Apps/Browsers so it adds that repo to their apt sources then installs the browser, just like the entries for Brave and Chrome do? Thanks.

I support that request. Using MX-19 I tried adding the repo in the terminal. It seemed to work, but the repo didn't show up in Synaptic. The ungoogled-chromium packages had arm64 in the name despite I had added the correct Buster repo. Maybe the packages (even amd64) are built from arm source?

Then I tried to download and install ungoogled-chromium amd64 deb directly. That also fails in Gdebi. Unnamed dependency is not satisfied.

Like chromium, ungoogled-chromium isn't just one deb, it's several. That's why it's easier to install from the repo.

What happens when you follow the instructions given?

Code: Select all

sudo apt-get install ungoogled-chromium

The arm64 thing seems to be a Synaptic issue with OBS repos, but the command line works anyway. I've been using the OBS to build and host Pale Moon for years now, and have had reports of the same thing. Just use the command line. Probably the same thing with my rebuild of MX's Chromium for Debian users that don't want to add MX's repo: https://build.opensuse.org/package/show ... m/chromium

Thanks, that's good to know. I don't have the repo anymore, but could add it back of course. However:

Maybe just let those who want this browser manually add it as per your instructions and knowing that they'll need to uninstall any existing versions of Chrome and Chromium first.

If this is true, this browser is a no-go on Linux and shouldn't be added to MXPI IMHO. I don't feel confident about the project anymore. The last thing I need is a browser causing dependency hell. Thanks for your efforts. This just seems dumb, since google chrome is one deb.

[Stevo]

That's funny, I think it removed the chromium packages when I test installed it before trying to rebuild it. Do you remember which one it conflicted with?

Yes, it's going to use Chromium's settings, so should look exactly the same.

[dreamer]

That's funny, I think it removed the chromium packages when I test installed it before trying to rebuild it. Do you remember which one it conflicted with?

Yes, it's going to use Chromium's settings, so should look exactly the same.

It seems OP has disappeared. I wouldn't put any effort into this.

EDIT: A couple thoughts. There is a "Portable" version that avoids package conflicts. However, profile conflicts will still be problematic. If you want Chromium extensions in Ungoogled Chromium you must use a special extension to access Chrome store. This might conflict with extensions in proper Chromium.

[dolphin_oracle]

the conflict was with chromium-common