Bug 440197

KDE Frame work 5.79.0
Qt 5.15.2

Is the digiKam version a snap package? If so, try our AppImage.

Maik

It is a shame that there are no up-to-date native digiKam packages for Ubuntu and Debian. We do not support Snap packages that use a sandbox. You can try to install the Snap package in Classic mode.

*** This bug has been marked as a duplicate of bug 439581 ***

Update: I move some picture files from the Network server (NAS) to a local hard drive and the JPG files are properly shown...

You did not reply to Comment 2. There are currently no known problems with network drives. To help, we need at least a complete terminal log with activated debug variable as described here:

https://www.digikam.org/contribute/

Maik

Created attachment 140418 [details]
Output after using: export QT_LOGGING_RULES="digikam*=true

This is a very strange problem and I don't think the bug is in digiKam.
First of all, Exiv2 cannot load metadata !!!
Loading via the JPG extension fails !!!
digiKam now checks the magic bytes and correctly finds 0xFF 0xD8 - a JPG file.
The JPG Loader checks again for 0xFF 0xD8 and rewinds to the beginning of the file with rewind(). The Libjpeg now identifies the 2 following bytes 0xFF 0xE0 and of course refuses it as a JPG file.

So your filesystem doesn't seem to support file positioning like rewind() for example. We could perhaps do a workaround for our JPG loader, but Exiv2 does not work with your file system either - you must repair your file system.

Maik

Git commit 7041168a8707d071bbedc0f612dff86cb1d078cc by Maik Qualmann.
Committed on 31/07/2021 at 20:41.
Pushed by mqualmann into branch 'master'.

remove extra check on a JPG file to avoid rewind ()
Libjpeg checks the Magic Bytes 0xFF, 0xD8.
FIXED-IN: 7.4.0

M  +0    -21   core/dplugins/dimg/jpeg/dimgjpegloader_load.cpp

https://invent.kde.org/graphics/digikam/commit/7041168a8707d071bbedc0f612dff86cb1d078cc

This will fix the loading of JPG files, but your mounted filesystem is not suitable for digiKam.

Maik

Git commit 276f52e692dc9fc43927d7e4edc7dd2d625c8447 by Maik Qualmann.
Committed on 31/07/2021 at 20:59.
Pushed by mqualmann into branch 'master'.

remove rewind() in the Jpeg2000 loader

M  +0    -26   core/dplugins/dimg/jpeg2000/dimgjpeg2000loader_load.cpp

https://invent.kde.org/graphics/digikam/commit/276f52e692dc9fc43927d7e4edc7dd2d625c8447

First, thank you for your detailed response in a very short time ! I am impressed.
But... I dont understand your comment about fixing this issue.
If I use the same computer and access the JPG files on the NAS, I see these pics no problem. I tried the same from a MacBook. So the JPG files are fine.
By curiosity, I tried the same setup I use for digiKam but did use the trial version of AfterShot from Corel and I got the same result than I got with digiKam.
So I agree with you that the problem do not seem to be in digikam.
I notice that to access these remote file, I dont use the same path because digikam do not show me the remote drive that I mapped. This may be the problem. If digikam could show me the same remote drive that my Ubuntu or my Mac give me, the problem may not be there...
I am very confuse. I sure would like to use the NAS to store my pics bu tuse digiKam to manage them.
Again, I very appreciate your time on this issue.

You have connected your NAS via FTP protocol. In this case, only linear reading of the file is possible, but programs cannot seek or rewind within the file. This is what some programs need. See the old bug report:

https://gitlab.gnome.org/GNOME/gvfs/-/issues/78

Your NAS provides additional protocols so that you can establish a connection at the file level, such as SMB or NFS.

Maik