I recently compiled 14.1.0, and just like my 14.0.13 before it, the TDE "identify" program does not work on much of anything for me. For example, running it on a fairly innocuous JPEG, I get Cannot decode /home/zsd/cyclone-copper.jpg: Unsupported file format or not RAW file whereas the identify that comes with my distro's (Slackware64 15.0, fwiw) imagemagick says cyclone-copper.jpg JPEG 3840x1776 3840x1776+0+0 8-bit sRGB 1.49897MiB 0.000u 0:00.000
I'm trying to track down whether this is (a) a TDE problem, (b) a Slackware64 problem, or (c) a me problem.
Would someone mind taking a minute to tell me if trinity's identify works correctly on your system (and what distro you are using)?
Thanks. Jim
On Tue May 9 2023 08:45:01 Jim via tde-users wrote:
I recently compiled 14.1.0, and just like my 14.0.13 before it, the TDE "identify" program does not work on much of anything for me. For example, running it on a fairly innocuous JPEG, I get Cannot decode /home/zsd/cyclone-copper.jpg: Unsupported file format or not RAW file whereas the identify that comes with my distro's (Slackware64 15.0, fwiw) imagemagick says cyclone-copper.jpg JPEG 3840x1776 3840x1776+0+0 8-bit sRGB 1.49897MiB 0.000u 0:00.000
I'm trying to track down whether this is (a) a TDE problem, (b) a Slackware64 problem, or (c) a me problem.
Would someone mind taking a minute to tell me if trinity's identify works correctly on your system (and what distro you are using)?
I'm using TDE 14.1.0 with Debian Bullseye 11.7. Debian provides several different alternative versions of "identify". The version I am using comes from Debian package "imagemagick-6.q16".
$ identify 20220209sunset.jpg 20220209sunset.jpg JPEG 1920x1080 1920x1080+0+0 8-bit sRGB 216354B 0.000u 0:00.000
The version of TDE I find here is not a TDE program:
$ which identify /usr/bin/identify $ ldd /usr/bin/identify | grep tde $
I can't find a TDE "identify" program. Can you tell me where you are finding it please?
--Mike
On Tue, May 9, 2023 at 11:51 (-0700), Mike Bird via tde-users wrote:
On Tue May 9 2023 08:45:01 Jim via tde-users wrote:
I recently compiled 14.1.0, and just like my 14.0.13 before it, the TDE "identify" program does not work on much of anything for me. For example, running it on a fairly innocuous JPEG, I get Cannot decode /home/zsd/cyclone-copper.jpg: Unsupported file format or not RAW file whereas the identify that comes with my distro's (Slackware64 15.0, fwiw) imagemagick says cyclone-copper.jpg JPEG 3840x1776 3840x1776+0+0 8-bit sRGB 1.49897MiB 0.000u 0:00.000
I'm trying to track down whether this is (a) a TDE problem, (b) a Slackware64 problem, or (c) a me problem.
Would someone mind taking a minute to tell me if trinity's identify works correctly on your system (and what distro you are using)?
I'm using TDE 14.1.0 with Debian Bullseye 11.7. Debian provides several different alternative versions of "identify". The version I am using comes from Debian package "imagemagick-6.q16".
$ identify 20220209sunset.jpg 20220209sunset.jpg JPEG 1920x1080 1920x1080+0+0 8-bit sRGB 216354B 0.000u 0:00.000
The version of TDE I find here is not a TDE program:
$ which identify /usr/bin/identify $ ldd /usr/bin/identify | grep tde $
I can't find a TDE "identify" program. Can you tell me where you are finding it please?
Mine is in /opt/trinity/bin/identify.
The build scripts for Slackware put the TDE stuff either in /opt/trinity or in /opt/tde, at the option of the person building it.
Your question makes me wonder whether the pre-built Debian packages install TDE under /usr or under /opt.
If you have the "locate" program running on your system you could also try locate bin/identify and see how many matching files it comes up with.
Cheers.
Jim
On Tue May 9 2023 12:28:13 Jim via tde-users wrote:
I can't find a TDE "identify" program. Can you tell me where you are finding it please?
Mine is in /opt/trinity/bin/identify.
The build scripts for Slackware put the TDE stuff either in /opt/trinity or in /opt/tde, at the option of the person building it.
Your question makes me wonder whether the pre-built Debian packages install TDE under /usr or under /opt.
For Debian and Ubuntu the pre-built packages install TDE in /opt/trinity.
If you have the "locate" program running on your system you could also try locate bin/identify and see how many matching files it comes up with.
I've searched several ways and have not yet found an "identify" in TDE.
When was your /opt/trinity/bin/identify created? Does this match your other TDE executables?
What is the output of running "ldd /opt/trinity/bin/identify"?
Can you tell the main source file from which your /opt/trinity/bin/identify was built?
Thanks,
--Mike
On Tue, May 9, 2023 at 13:29 (-0700), Mike Bird via tde-users wrote:
On Tue May 9 2023 12:28:13 Jim via tde-users wrote:
I can't find a TDE "identify" program. Can you tell me where you are finding it please?
Mine is in /opt/trinity/bin/identify.
The build scripts for Slackware put the TDE stuff either in /opt/trinity or in /opt/tde, at the option of the person building it.
Your question makes me wonder whether the pre-built Debian packages install TDE under /usr or under /opt.
For Debian and Ubuntu the pre-built packages install TDE in /opt/trinity.
Thanks.
If you have the "locate" program running on your system you could also try locate bin/identify and see how many matching files it comes up with.
I've searched several ways and have not yet found an "identify" in TDE.
I got it as part of tdelibkdcraw
When was your /opt/trinity/bin/identify created? Does this match your other TDE executables?
It was created about the same time (+/- a few seconds) as a bunch of other executables.
What is the output of running "ldd /opt/trinity/bin/identify"?
linux-vdso.so.1 (0x00007ffc73be9000) liblcms2.so.2 => /usr/lib64/liblcms2.so.2 (0x00007fca2fd2e000) libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00007fca2fa00000) libm.so.6 => /lib64/libm.so.6 (0x00007fca2f8b8000) libomp.so => /usr/lib64/libomp.so (0x00007fca2fc4e000) libgcc_s.so.1 => /usr/lib64/libgcc_s.so.1 (0x00007fca2fc33000) libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fca2fc12000) libc.so.6 => /lib64/libc.so.6 (0x00007fca2f6d9000) /lib64/ld-linux-x86-64.so.2 (0x00007fca2fdea000) librt.so.1 => /lib64/librt.so.1 (0x00007fca2f6cf000) libdl.so.2 => /lib64/libdl.so.2 (0x00007fca2f6ca000)
The list for my /usr/bin/identify is much longer (46 lines).
Can you tell the main source file from which your /opt/trinity/bin/identify was built?
Looking at the build log, I see some compiler warnings from libkdcraw-trinity-14.1.0/libkdcraw/libraw/samples/identify.c
Given the lack of other people seeing this, I am beginning to guess it is an issue with the Slackware build scripts, although I don't know why Slackware would include (alleged) TDE programs that aren't used in the Debian/Ubuntu packages.
So thanks for your responses, I think I should probably go and talk to the guy who creates the Slackware build scripts.
Jim
On Tue May 9 2023 14:50:11 Jim via tde-users wrote:
I got it as part of tdelibkdcraw
When was your /opt/trinity/bin/identify created? Does this match your other TDE executables?
It was created about the same time (+/- a few seconds) as a bunch of other executables.
What is the output of running "ldd /opt/trinity/bin/identify"?
linux-vdso.so.1 (0x00007ffc73be9000) liblcms2.so.2 => /usr/lib64/liblcms2.so.2 (0x00007fca2fd2e000) libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00007fca2fa00000) libm.so.6 => /lib64/libm.so.6 (0x00007fca2f8b8000) libomp.so => /usr/lib64/libomp.so (0x00007fca2fc4e000) libgcc_s.so.1 => /usr/lib64/libgcc_s.so.1 (0x00007fca2fc33000) libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fca2fc12000) libc.so.6 => /lib64/libc.so.6 (0x00007fca2f6d9000) /lib64/ld-linux-x86-64.so.2 (0x00007fca2fdea000) librt.so.1 => /lib64/librt.so.1 (0x00007fca2f6cf000) libdl.so.2 => /lib64/libdl.so.2 (0x00007fca2f6ca000)
OK, there's an identify.cpp here: https://mirror.git.trinitydesktop.org/gitea/TDE/libkdcraw/src/branch/master/...
It's in a samples directory and I would guess that it is not supposed to be installed in /opt/trinity/bin/. For Debian and Ubuntu it is not even packaged and shipped.
That's about as far as I can take it. Looks like you'll need to talk to whoever prepared your TDE for Slackware build. It's roughly 27 years since I last used Slackware so I'm not really up to speed.
--Mike
On Tue, May 9, 2023 at 15:21 (-0700), Mike Bird via tde-users wrote:
On Tue May 9 2023 14:50:11 Jim via tde-users wrote:
I got it as part of tdelibkdcraw
When was your /opt/trinity/bin/identify created? Does this match your other TDE executables?
It was created about the same time (+/- a few seconds) as a bunch of other executables.
What is the output of running "ldd /opt/trinity/bin/identify"?
linux-vdso.so.1 (0x00007ffc73be9000) liblcms2.so.2 => /usr/lib64/liblcms2.so.2 (0x00007fca2fd2e000) libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00007fca2fa00000) libm.so.6 => /lib64/libm.so.6 (0x00007fca2f8b8000) libomp.so => /usr/lib64/libomp.so (0x00007fca2fc4e000) libgcc_s.so.1 => /usr/lib64/libgcc_s.so.1 (0x00007fca2fc33000) libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fca2fc12000) libc.so.6 => /lib64/libc.so.6 (0x00007fca2f6d9000) /lib64/ld-linux-x86-64.so.2 (0x00007fca2fdea000) librt.so.1 => /lib64/librt.so.1 (0x00007fca2f6cf000) libdl.so.2 => /lib64/libdl.so.2 (0x00007fca2f6ca000)
OK, there's an identify.cpp here: https://mirror.git.trinitydesktop.org/gitea/TDE/libkdcraw/src/branch/master/...
It's in a samples directory and I would guess that it is not supposed to be installed in /opt/trinity/bin/. For Debian and Ubuntu it is not even packaged and shipped.
That's about as far as I can take it. Looks like you'll need to talk to whoever prepared your TDE for Slackware build. It's roughly 27 years since I last used Slackware so I'm not really up to speed.
Thanks Mike, I have already put a question in to the guy who maintains the Slackware build system.
Jim
On Tuesday 09 May 2023 10:45:01 am Jim via tde-users wrote:
Would someone mind taking a minute to tell me if trinity's identify works correctly on your system (and what distro you are using)?
michael@local [~/data/trash]# locate bin/identify /usr/bin/identify /usr/bin/identify-im6 /usr/bin/identify-im6.q16
michael@local [~/data/trash]# identify tde-tcc-01.jpg tde-tcc-01.jpg JPEG 1098x800 1098x800+0+0 8-bit sRGB 198371B 0.000u 0:00.000
michael@local [~/data/trash]# which identify /usr/bin/identify
michael@local [~/data/trash]# identify Version: ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org Copyright: © 1999-2019 ImageMagick Studio LLC License: https://imagemagick.org/script/license.php Features: Cipher DPC Modules OpenMP Delegates (built-in): bzlib djvu fftw fontconfig freetype heic jbig jng jp2 jpeg lcms lqr ltdl lzma openexr pangocairo png tiff webp wmf x xml zlib Usage: identify-im6.q16 [options ...] file [ [options ...] file ... ]
michael@local [~/data/trash]# rel PRETTY_NAME="Debian GNU/Linux 10 (buster)" Kernel: 4.19.0-24-amd64 x86_64 bits: 64 Desktop: Trinity R14.0.13 Distro: MX-19.4_x64 patito feo May 31 2020
I did a full install of TDE, e.g. 'aptitude install tde-trinity' which does not seem to install a "TDE identify," so I'm guessing it's something with what you're compiling?
HTH, Michael
On Tue, May 9, 2023 at 15:34 (-0500), Michael via tde-users wrote:
On Tuesday 09 May 2023 10:45:01 am Jim via tde-users wrote:
Would someone mind taking a minute to tell me if trinity's identify works correctly on your system (and what distro you are using)?
michael@local [~/data/trash]# locate bin/identify /usr/bin/identify /usr/bin/identify-im6 /usr/bin/identify-im6.q16
Presumably not from TDE.
michael@local [~/data/trash]# identify tde-tcc-01.jpg tde-tcc-01.jpg JPEG 1098x800 1098x800+0+0 8-bit sRGB 198371B 0.000u 0:00.000
michael@local [~/data/trash]# which identify /usr/bin/identify
michael@local [~/data/trash]# identify Version: ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org
That's a bit old, but my /usr/bin/identify outputs similar bumph.
I did a full install of TDE, e.g. 'aptitude install tde-trinity' which does not seem to install a "TDE identify," so I'm guessing it's something with what you're compiling?
I am guessing so as well.
Thanks for your information, I'll go bark up the Slackware tree.
Jim
On Tue, 9 May 2023 15:34:32 -0500 Michael via tde-users users@trinitydesktop.org wrote:
I did a full install of TDE, e.g. 'aptitude install tde-trinity' which does not seem to install a "TDE identify," so I'm guessing it's something with what you're compiling?
If it's part of libkdcraw, then it isn't part of TDE proper. It's a library dependency of digikam, an additional application which isn't part of the desktop.
(But yeah, sounds like maybe something fishy with the build—if the machine in question had its compiler updated recently, I'd check for changes in the default options being passed, or something else flaky and subtle like that.)
E. Liddell
On Tuesday 09 May 2023 17:45:01 Jim via tde-users wrote:
I recently compiled 14.1.0, and just like my 14.0.13 before it, the TDE "identify" program does not work on much of anything for me. For example, running it on a fairly innocuous JPEG, I get Cannot decode /home/zsd/cyclone-copper.jpg: Unsupported file format or not RAW file whereas the identify that comes with my distro's (Slackware64 15.0, fwiw) imagemagick says I'm trying to track down whether this is (a) a TDE problem, (b) a Slackware64 problem, or (c) a me problem. Would someone mind taking a minute to tell me if trinity's identify works correctly on your system (and what distro you are using)?
Slackware was my first distribution. I appreciated CentOS (clone free of Redhat). Now Debian since a long time. Excepted error, Slackware is the most purist GNU/Linux distribution. It's one of the few who is able to compile a new kernel without difficulties. But, the corollary is that Slackware sometimes doesn't accept completely applications not purely GNU/Linux, as fashion graphics, Gnome, TDE, KDE...
-
ajh-valmer -
E. Liddell -
Jim -
Michael -
Mike Bird