ungoogled chromium updated

[Xunzi_23Member]

Hi andfree,
if my memory serves me correctly you are not using full antiX version.

My assumption you are missing some libs or tools, unzipping in the described works
for me and has done so for years, had no user complaints or comments until now.

Problems like you are experiencing are why full Version is the recommended way to go.

Locally all users get the same setup, antiX Full customized ICEWM, problems are rare.

[andfreeMember]

I was mistaken. I expected to see the squashfs-root folder in the same folder as the appimage, but I found it in its parent folder (my $HOME folder). I will continue to experiment with @masinick’s method.

antiX utilities for processing PDF files (posted by ChPol)

[Brian MasinickModerator]

andfree wrote:

I was mistaken. I expected to see the squashfs-root folder in the same folder as the appimage, but I found it in its parent folder (my $HOME folder). I will continue to experiment with @masinick’s method.

That is unexpected behavior to me too. At least you found the squashfs-root directory. The content organization within this directory has also recently changed as @Xunzi_23 and I have both noted. Perhaps these differences explain what happened, is that possible?

--
Brian Masinick
Alternate "Search B":
This search page

[Brian MasinickModerator]

Xunzi_23 wrote:

Hi andfree,
if my memory serves me correctly you are not using full antiX version.

My assumption you are missing some libs or tools, unzipping in the described works
for me and has done so for years, had no user complaints or comments until now.

Problems like you are experiencing are why full Version is the recommended way to go.

Locally all users get the same setup, antiX Full customized ICEWM, problems are rare.

I missed or forgot about that point; I agree with @Xunzi_23. Switch to Full if you are not using it. There are a lot of little things that are absent from the other versions that are features of Full. With the issues you have faced, make sure you are running Full. That’s the easiest way to determine if something else is causing these seemingly strange quirks.

--
Brian Masinick
Alternate "Search B":
This search page

[Brian MasinickModerator]

The appimage-extract argument has two dashes preceding it. This forum repeatedly alters those dashes so make sure you account for this and manually alter your command. If you copy literally what I wrote that’s the issue, so try again. This has introduced syntax errors many times so please carefully note and retype the preceding dashes. The dash within, just to make certain, is one dash, but personally I would manually type it too. I believe that it is typesetting in the forum software that is responsible for the quirk. Knowing that, always hand type command arguments and you will experience fewer of these problems.

--
Brian Masinick
Alternate "Search B":
This search page

[andfreeMember]

Indeed, unzipping appimage.zip worked for me via roxfiler on antiX-25, which is a full version (however, zzzfm still gives the same message of failure). I missed that my frugal 23.2 installation was the base version. I’m trying to download 23.2 full version for a testing, but it takes hours.

Brian Masinick wrote:

The appimage-extract argument has two dashes preceding it. This forum repeatedly alters those dashes (…)

I know, you can try to use the code tags in such a case. Look:

--appimage-extract

• This reply was modified 11 months, 2 weeks ago by andfree.

antiX utilities for processing PDF files (posted by ChPol)

[Brian MasinickModerator]

andfree wrote:

Indeed, unzipping appimage.zip worked for me via roxfiler on antiX-25, which is a full version (however, zzzfm still gives the same message of failure). I missed that my frugal 23.2 installation was the base version. I’m trying to download 23.2 full version for a testing, but it takes hours.

Brian Masinick wrote:

The appimage-extract argument has two dashes preceding it. This forum repeatedly alters those dashes (…)

I know, you can try to use the code tags in such a case. Look:

--appimage-extract

The fact that antiX 25 Full works is evidence that something is missing in the Base Edition. If you want to struggle with this for a long time until you stumble onto what’s missing, that’s up to you, but I think you’re with us on this. I used to work mostly with Core or Base, and for years, I had THREE instances of antiX – Core, Base, and Full. I might still have one of those left on an older system, but I doubt it. Here’s why: for me there are two factors that keep bringing me back to Full:

1) For the past seven (plus) years, I’ve lived in a retirement community. Out of that time, for a short while we had Ethernet connections available, and there are a few “jacks” still hanging around here and there, but somewhere between the 4G LTE and 5G time frame in our area, Ethernet jacks – in libraries and other public spots – and also here – went inactive. Everybody went to wireless networking.

2) Most of my systems require fairly recent system kernels in order to work properly with wireless.

These two factors heavily contributed to my full-time move to “Full”, but there is a third reason that further cemented my choice:
I DID build both a Core and a Base implementation on one of my older systems that could still support wireless with the available kernels, but since antiX 23+ the improvements in Full justify using them.

While I still acknowledge that there are those of us who like to build the systems ourselves (I’ve been one of them for a large percentage of my life), I don’t feel the urge to do that any more, and there are many tangible improvements in Full that I don’t want to repeatedly implement myself, so I’ll only go back to one of the other three forms if I’m helping to test something; otherwise I’ll confine the majority of my testing to what we have, and that’s what I recommend for over 90% of our population. Unless individuals can build any and all parts of their systems without the assistance of anyone, I strongly recommend against using the other versions.

Everyone can make their own choice, but if someone goes to help and discovers that a person is using [Net, Core, Base] I can promise you that almost all of the helpers will say either switch to Full or solve your own problem because the other three are intended for people to customize and build their own solutions.

I doubt that all of this is necessary to state to you in particular, but I put it out there because others may read this. I’m also not trying to be unkind, but I am asking others to be reasonable to the volunteers who help out. Even retirees like me have many other things going on during the day.

Back to the discussion at hand here:

To summarize, we have a common understanding about the appimage argument to extract, and we also believe that something’s missing from non-Full implementations – (it “might” be “fuse”, but is it worth trying to figure out?)

--
Brian Masinick
Alternate "Search B":
This search page

[andfreeMember]

Now, from another laptop (I’m not near to the other ones), without a 23.2 (base or full) installation, but with an antiX-25 frugal, reduced to base via @anticapitalx’s full-to-base script.
I opened rox-filer via terminal & tried to extract the appimage.zip file:

$ rox-filer
demo@antix1:~
$ /usr/local/bin/archive-extract.sh: 12: exec: file-roller: not found

I installed file-roller and now I can extract appimage.zip files.
I don’t know if file-roller is pre-installed in antiX-23.2-full, but @anticapitalista included it in the “base and full” and not in the “only full” package list. On the other hand, it’s included in the @anticapitalx’s list of packages for removing by the script. I don’t know why.

Many thanks for your help and really sorry for wasting your time.

• This reply was modified 11 months, 2 weeks ago by andfree.
• This reply was modified 11 months, 2 weeks ago by andfree.
• This reply was modified 11 months, 2 weeks ago by andfree.

antiX utilities for processing PDF files (posted by ChPol)

[Brian MasinickModerator]

Many thanks for your help and really sorry for wasting your time.

I don’t consider this a waste of time; I hope its been a learning experience. I’m not sure that file-roller is the cause or solution to the difficulties, but I’m glad you’re seeing this work in the full instance. I recommend doing most of the important work in Full rather than Base. At this point, even for me, I consider the other three images – Net, Core, and Base, to be predominantly for software building and configuring experts. Though I can still do such things, I’ve lost some of my edge and I keep my own advice, sticking to Full except for cases where I’m performing testing for a specific reason – such as assisting in the testing of our release candidates or when testers are requested; the rest of the time I take my own advice and use Full.

I hope you’re enjoying ungoogled chromium. It’s useful to know how to build and dismantle the images, but it’s not mandatory; most of the time I just use the appimage, make it executable and move it to a convenient, out of the way location that suits my private configuration; you’re welcome to do it that way or extract the appimage into it’s components. If that’s getting too painful, I believe there is a binary image that uses tar.gz format. If that’s not working, I’ll discuss it another time.

--
Brian Masinick
Alternate "Search B":
This search page

[Xunzi_23Member]

I’m trying to download 23.2 full version for a testing, but it takes hours.

Ouch, that is really slow, have you given torrent a try sometimes other people are seeding and
that can really speed up downloads.

https://antixlinux.com/torrent-files/

I am just testing, in my German location torrent down is very slow right now, I was seeding a lot more
than receiving.
Download from nearby server is slow too so something weird going on, probably too many people
watching streams or maybe DDOS on servers.

[Brian MasinickModerator]

One more thing: suppose you want to use ungoogled chromium but you don’t want to use the appimage?
There are THREE other options on the page cited in the past:
Here are the FOUR options:
1) Appimage binary format
2) tar.xz binary format
3) tar.xz source format
4) zip source format

Options 3 and 4 require compiling ungoogled chromium from source. Unless you have a powerful server or you can let it go for hours, compiling from source is a big challenge, so options 1 and 2 are preferable. But since the appimage format isn’t the most efficient use of space and execution, so here’s what I did to grab the tar.gz and install it effectively.

Step one: Visit the site https://github.com/ungoogled-software/ungoogled-chromium-portablelinux to find the current version.
Step two: select the current release, for example the current release is https://github.com/ungoogled-software/ungoogled-chromium-portablelinux/releases/tag/141.0.7390.76-1
Step three: Select the linux.tar.xz release, for example, the current linux.tar.xz release is https://github.com/ungoogled-software/ungoogled-chromium-portablelinux/releases/download/141.0.7390.76-1/ungoogled-chromium-141.0.7390.76-1-x86_64_linux.tar.xz
Step four: Download the release chosen above.
Step five: Extract the file downloaded, for example tar xvf ungoogled-chromium-141.0.7390.76-1-x86_64_linux.tar.xz
Step six: Switch to the directory where the image was extracted, for example: cd ungoogled-chromium-141.0.7390.76-1-x86_64_linux/
Step seven (optional): cd to the previous directory and remove the tar.tz file, for example: rm ungoogled-chromium-141.0.7390.76-1-x86_64_linux.tar.xz
Step eight: Move the image directory containing the image to /usr/local/bin, for example, sudo mv ungoogled-chromium-141.0.7390.76-1-x86_64_linux /usr/local/bin
Step nine: List the contents of the directory in /usr/local/bin, for example, cd /usr/local/bin; ls ungoogled-chromium-141.0.7390.76-1-x86_64_linux/
This should contain a number of files and libraries, including chrome, chrome-wrapper, and the supporting files.
Step ten: If the previous step is confirmed, then execute the command ./chrome-wrapper from the /usr/local/bin directory; it should work; if not, make sure it is executable and located in /usr/local/bin.
Step eleven: If all the steps above succeed, you are ready to try it out. I created a symbolic link, ungoogled-chromium in the /usr/local/bin directory; you can do this, or just run chrome or chrome wrapper from the current version directory. Here’s what I did: sudo ln -sf /usr/local/bin/ungoogled-chromium-141.0.7390.76-1-x86_64_linux/chrome-wrapper /usr/local/bin/ungoogled-chromium
Step twelve: finally, I created an alias in my personal .bashrc to shorten all of this: alias uc='~/bin/null.bash /usr/local/bin/ungoogled-chromium $@'
~/bin/null.bash just backgrounds and silences the messages; you don’t want to do this unless and until you have a working tool.

Null.bash looks like this:

#!/bin/bash
# File: null.bash
# Purpose: Provide a mechanism to run detached processes
# conveniently without tying up the terminal or typing
# in very long commands.

# Author: Brian Masinick

  if [ -z "$1" ]  # Checks if parameter #1 is zero length
    then
        echo "No program parameter provided"
    return 1
    else # Detach the process with the argument list
        nohup "$@" > /dev/null 2>&1 &
  fi

You can customize this the way you want it. This way works nicely for me and I use it for many of my tools. If any of them fail to work, I run them manually because null.bash gets rid of ALL feedback, so make sure everything works first if you want to implement this approach; otherwise, use your own customized approach, whatever you prefer; in any case I hope this is helpful.

--
Brian Masinick
Alternate "Search B":
This search page

[Brian MasinickModerator]

A couple of additional comments if you decide to use the tar.gz version of the binaries and move them around:

This is something that will have to be done frequently; it might be worth creating your own notes on this OR building a script or two for automating these tasks; again, that’s up to each person to decide what’s worth the effort or if this is merely a one time experiment.

--
Brian Masinick
Alternate "Search B":
This search page

[Brian MasinickModerator]

Xunzi_23 wrote:

I’m trying to download 23.2 full version for a testing, but it takes hours.

Ouch, that is really slow, have you given torrent a try sometimes other people are seeding and
that can really speed up downloads.

https://antixlinux.com/torrent-files/

I am just testing, in my German location torrent down is very slow right now, I was seeding a lot more
than receiving.
Download from nearby server is slow too so something weird going on, probably too many people
watching streams or maybe DDOS on servers.

@Xunzi_23 are you and your community using the appimage as is, altering it in the squash-root and moving the image, downloading in tar.xz format, or using an entirely different approach? I’ve tried two or three different ways and they all work. I may decide to stick with the tar.xz format going forward unless they keep changing the contents; if this remains stable, I may create a personal script to make all of this happen a bit quicker, though it takes more time to write about it than actually do it; both the appimage and xz formats just take a few minutes to put them in place.

I am a fan of automation though; I may automate it, providing the creators don’t keep “moving the goal posts” as they recently did when they put an opt directory in the appimage!

--
Brian Masinick
Alternate "Search B":
This search page

[Xunzi_23Member]

Hi Brian,
appimage most popular as very easy to use. I usually stick with the portable tar.xz version
but try and keep up to date with the contents of the appimage.
OT. I always unpack libreWolf too.

Unless I am asked I let users get on as they like. There is plenty of info here on the forum.

I must prepare a fresh live students setup for my daughter, that will use the appimage as is.

Not all of her student friends are rich and can purchase new devicces with win 11 so I hope to gain a few users.

A completely automated download and setup of ungoogledchromium would be nice, as is it may be too geeky for some.

[Brian MasinickModerator]

A completely automated download and setup of ungoogled chromium would be nice, as is it may be too geeky for some.

I’d be willing to share what I put together, assuming I do so, but my fear is that it won’t be extensible and won’t work for long because we’ve seen too many changes and alterations, so if I get there we can collaborate. My initial thoughts are to use parameters to pass to one or two scripts; the parameters would contain the name or names of the download locations and the destination. If I can’t get something consistent I’d also try to use a few variables, hoping that changes can be dealt with by either changing parameters or variables, but who knows if this is going to be worth the effort.
I’ve not made a final decision on whether I do this or not; so far I’m observing a few more updates; keep an eye on my “scripts”, “What are you here with” and “ungoogled chromium” threads, just in case this ends up being viable and worthwhile.

--
Brian Masinick
Alternate "Search B":
This search page

[Author]

Posts