[use file-roller instead] engrampa FAILS to "Extract ..." via Caja, nor Terminal

[scjet45]

Update:
##################################################################
All the below was fixed by installing/upgrading "file-roller" as per xenopeek:
viewtopic.php?p=2533983#p2533983
#################################################################

Using Mate 22:
In Caja, right-click on a *.tar.gz file and it fails with:

Also, in Terminal:

Code: Select all

engrampa --extract-here makemkv-bin-1.17.8.tar.gz

fails with same error/output as above.
And,

Code: Select all

tar -xvzf * .tar.gz

also fails,via a Terminal, in both Mate and Cinnamon. ?

However, if I right-click on the *.tar.gz file, via Caja, and select the top "Open with Archive Manager" it will extract fine.?

Note: If using Cinnamon 22, via Nemo, it will successfully "Extract Here" that *.tar.gz files ?, albeit, Nemo uses a different archiver/file-roller than Caja.

UPDATE:
after I manually "gzip -d *.tar.gz; tar -xvf *.tar", and then re-compressed them with a "tar -zcvf makemkv-bin-1.17.8.tar.gz makemkv-bin-1.17.8", Caja could "Extraxt Here" successfully.
So, it looks like depending on the way some folders/files are archived and compressed, "Engrampa" in Mate doesn't like it, however, I'm a bit surprised that a "tar -xvzf *.tar.gz" also could not handle it.?

Could this be a small bug in Engrampa and/or Tar. ?
Anyway, for now, I'll mark this as solved and chalk it up to a weird tar.gz method, (they probably used Windows), as used by the Author of those makemkv archives.

[1000]

Using Mate 22:

Probably Linux Mint 22. You can check output

Code: Select all

inxi -Fxxxrzc0

Check with this file https://cdn.kernel.org/pub/linux/kernel ... 0.1.tar.gz

[scjet45]

Using Mate 22:

Probably Linux Mint 22. You can check output

Code: Select all

inxi -Fxxxrzc0

Check with this file https://cdn.kernel.org/pub/linux/kernel ... 0.1.tar.gz

and how the heck am I supposed to decipher https://cdn.kernel.org/pub/linux/kernel ... 0.1.tar.gz, care to narrow it down a bit.?

[1000]

Clicking on the link will automatically download the tar.gz file
Check if you get the same error while unpacking with engrampa.

[scjet45]

Clicking on the link will automatically download the tar.gz file
Check if you get the same error while unpacking with engrampa.

ah k, and yes, engrampa extracts the *.tar.gz, file, from your link, successfully, but it fails on "makemkv-oss-1.17.8.tar.gz" as mentioned in my OP.
( Download from here: https://forum.makemkv.com/forum/viewtopic.php?f=3&t=224 )
However, if in a terminal, I run:

Code: Select all

file-roller --extract-here makemkv-oss-1.17.8.tar.gz

It works fine.

So the problem is with engrampa, and since engrampa is a fork of file-roller, afaik?, then maybe the Mate devs need to fix their engrampa.
Or, they could just change the name from "engrampa" to "engrumpy".

[MiZoG]

This has not been solved yet upstream.
Same error message on latest version 1.28.2.
There's an open issue on engrampa github that looks related if the not same.

[karlchen]

There's an open issue on engrampa github that looks related if the not same.

Something wrong with my glasses?
That Github issue is from 2018, 6 years ago.
Shall we assume that the same issue has not been analyzed and resolved after 6 years?

Looks a bit as if this may be the case.
At the end of the issue #206 there is a link to another issue: https://github.com/mate-desktop/engrampa/pull/491
The comments suggests that .tar.gz files are indeed not identified correctly.

Oh well.

[1000]

Maybe someone knows how to check if two different files are tar.gz
And maybe he will share his knowledge
I only found information on the internet that
- the file is double compressed : gzip and tar .

1. gzip starts with two bytes: 0x1F and 0x8B. https://en.wikipedia.org/wiki/Gzip

Code: Select all

$ od -A n -v -t x1 -N10 makemkv-oss-1.17.8.tar.gz 
 1f 8b 08 00 00 00 00 00 00 03

Both files start the same ( 1f 8b ) , so it is gzip file.


2. I can try unpack from gzip to tar

Code: Select all

gzip -dk makemkv-oss-1.17.8.tar.gz

3. I have a problem with the definition of the tar file. https://en.wikipedia.org/wiki/Tar_(computing)

There are multiple tar file formats

Magic number ... u s t a r \040 \040 \0 (for old GNU tar format)

I didn't find this definition in both files.

Code: Select all

$ file linux-2.0.1\(3\).tar
linux-2.0.1(3).tar: POSIX tar archive (GNU)

$ file makemkv-oss-1.17.8.tar
makemkv-oss-1.17.8.tar: gzip compressed data, from Unix, original size modulo 2^32 34099200

As you can see, the system recognizes these two files differently.

Something else

Code: Select all

$ mimetype --file-compat linux-2.0.1\(3\).tar
linux-2.0.1(3).tar: Tar archive

$ mimetype --file-compat makemkv-oss-1.17.8.tar
makemkv-oss-1.17.8.tar: Tar archive

4. In the engrampa report someone wrote that it is not an engrampa bug.
This may be true.
Because anyone can make their own graphical frontend for terminal commands.
But I don't know if this is the case with engrampa.
Secondly, both programs do not have to use their own algorithms to recognize files.
But only the file command is enough.

About Maintainers:

Code: Select all

$ apt-cache show file | grep 'Source\|Maintainer\|Bugs\|Homepage'
Maintainer: Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
Original-Maintainer: Christoph Biedl <debian.axhn@manchmal.in-ulm.de>
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Homepage: https://www.darwinsys.com/file/
Maintainer: Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
Original-Maintainer: Christoph Biedl <debian.axhn@manchmal.in-ulm.de>
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Homepage: https://www.darwinsys.com/file/

If I am wrong, please correct me.
If anyone has more information, please write.

[1000]

There is one more thing I can't understand in my Ubuntu 22.04.4 LTS (Jammy Jellyfish)

I was looking for which package the command belongs to

$ LC_ALL=C dpkg -S $(type -P tar)
dpkg-query: no path found matching pattern /usr/bin/tar

Default tar package contents

$ dpkg-query -L tar | grep bin
/bin
/bin/tar
/usr/sbin
/usr/sbin/rmt-tar
/usr/sbin/tarcat

So these two locations are different.

It looks like a copy of the same file

Code: Select all

$ file /usr/bin/tar 
/usr/bin/tar: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=817b2c5944e048940016de52c410947e4f46ccf6, for GNU/Linux 3.2.0, stripped

$ ls -l /usr/bin/tar
-rwxr-xr-x 1 root root 517952 Dec  5  2023 /usr/bin/tar
$ ls -l /bin/tar
-rwxr-xr-x 1 root root 517952 Dec  5  2023 /bin/tar

$ sha256sum /bin/tar
148313667aa9111de45fe3c70a1c7c963ae5f015071a106c4cdabea749d2db9f  /bin/tar
$ sha256sum /usr/bin/tar
148313667aa9111de45fe3c70a1c7c963ae5f015071a106c4cdabea749d2db9f  /usr/bin/tar

Has this been fixed / corrected in the newer version of Ubuntu?
Can you check it on your system?

About Maintainers:

Code: Select all

$ apt-cache show tar | grep 'Source\|Maintainer\|Bugs\|Homepage'
Maintainer: Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
Original-Maintainer: Janos Lenart <ocsi@debian.org>
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Homepage: https://www.gnu.org/software/tar/
Maintainer: Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
Original-Maintainer: Janos Lenart <ocsi@debian.org>
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Homepage: https://www.gnu.org/software/tar/

[scjet45]

There is one more thing I can't understand in my Ubuntu 22.04.4 LTS (Jammy Jellyfish)

I was looking for which package the command belongs to

$ LC_ALL=C dpkg -S $(type -P tar)
dpkg-query: no path found matching pattern /usr/bin/tar

Default tar package contents

$ dpkg-query -L tar | grep bin
/bin
/bin/tar
/usr/sbin
/usr/sbin/rmt-tar
/usr/sbin/tarcat

So these two locations are different.

It looks like a copy of the same file

Code: Select all

$ file /usr/bin/tar 
/usr/bin/tar: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=817b2c5944e048940016de52c410947e4f46ccf6, for GNU/Linux 3.2.0, stripped

$ ls -l /usr/bin/tar
-rwxr-xr-x 1 root root 517952 Dec  5  2023 /usr/bin/tar
$ ls -l /bin/tar
-rwxr-xr-x 1 root root 517952 Dec  5  2023 /bin/tar

$ sha256sum /bin/tar
148313667aa9111de45fe3c70a1c7c963ae5f015071a106c4cdabea749d2db9f  /bin/tar
$ sha256sum /usr/bin/tar
148313667aa9111de45fe3c70a1c7c963ae5f015071a106c4cdabea749d2db9f  /usr/bin/tar

Has this been fixed / corrected in the newer version of Ubuntu?
Can you check it on your system?

About Maintainers:

Code: Select all

$ apt-cache show tar | grep 'Source\|Maintainer\|Bugs\|Homepage'
Maintainer: Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
Original-Maintainer: Janos Lenart <ocsi@debian.org>
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Homepage: https://www.gnu.org/software/tar/
Maintainer: Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
Original-Maintainer: Janos Lenart <ocsi@debian.org>
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Homepage: https://www.gnu.org/software/tar/

I don't have Ubuntu 22.04.4 LTS (Jammy Jellyfish) right now, (although Mint 21.* is based upon same Ubuntu), but thanks for your very detailed info here.
It is definitely worth checking out, and yes, i've read about double-gziped, ..., but why does "file-roller" and even some other (gui) extractors work fine, in Linux, and yet engrampa doesn't?, ... but yes, more research needs to be done.

So, engrampa/tar is somewhat unresolved for now, as it should be.

In the meantime, there is this honest answer from Xeno.
viewtopic.php?p=2533983#p2533983

Note:
Just as a secondary test, I installed Arch Linux with (full) Mate 1.28.2 desktop environment on a spare box, and even with Engrampa version 1.28.2 via Caja it still "failed" as per my top post, whereas "file-roller" via Caja worked fine on anything.
I was hoping with Mate 1.28.2 the folks@mate-desktop would've fixed engrampa by now, but ...?
I dunno.