[digikam] [Bug 317943] New: Auto rotate/flip using EXIF Information destroys pictures

[Nicofo]

https://bugs.kde.org/show_bug.cgi?id=317943

Nicofo <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Auto rotate/flip using EXIF |(Auto) rotate/flip using
                   |Information destroys        |EXIF Information destroys
                   |pictures                    |pictures

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Nicofo]

https://bugs.kde.org/show_bug.cgi?id=317943

--- Comment #21 from Nicofo <[hidden email]> ---
I have made additional tests:

1) I have downgraded libjpeg-turbo(-utils) to the version 1.2.1-3.fc18.i686
(instead of 1.2.90-1.fc18.i686) => bug was already present with that version

2) actually, the bug is not only present with the 'autorotate' function: the
bug also happened with the normal rotate function. As already said, I think the
chance is bigger for the bug to happen if you do multiple operations on the
pictures: in my case, I have selected several pictures in digikam and clicked a
lot of time (> 10 in a row) on the rotate left button => all my pictures where
destroyed !!

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Quincy]

https://bugs.kde.org/show_bug.cgi?id=317943

[hidden email] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]

--- Comment #22 from [hidden email] ---
Not really news, but just to push the really critical bug (backup of raw images
is essential, otherwise data loss occurs) to a "confirmed" status:

Using a similar configuration as Reinhard Biegel I'm also on Gentoo x86_64 with
digikam-3.1.0, images on ext4 FS, but libjpeg-turbo-1.2.1 and experiencing
similar problems. I'm rotating groups of selected pictures via shortcut and
images get destroyed in various ways as described above (size 0, reduced or
even increased). Rotating larger amounts of images at the same time seems to
make the problem worse, as until now I could not reproduce the error while
rotating single files.

Interestingly not the pictures being reported as "JPEG transform failed" but
others are destroyed. For example I rotated 6 pictures at the same time (58,
60, 61, 62, 63, 64), 60 and 61 were reported as failed, but 58, 60, 61 and 62
have been rotated, 63 and 64 have been destroyed. 63 has zero size, 64 is now
about 75% larger than before (concatenated data of 63?). Additionally there is
a temporary file of 61 with digikams PID as suffix leftover.

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Peter Albrecht-2]

https://bugs.kde.org/show_bug.cgi?id=317943

Peter Albrecht <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]

--- Comment #23 from Peter Albrecht <[hidden email]> ---
And here is another gentoo linux user confirming this problem:
  - arch: x86_64
  - digiKam 3.1.0
  - libjpeg-turbo  1.2.1
  - KDE 4.10.2
  - pictures on an ext4 filesystem on SSD

I did not encounter this problem with
  - digiKam 2.9.0
  - libjpeg-turbo 1.2.1 (same as above)
  - KDE 4.9.5

Components Information:
---------------------------------- 8< ----------------------------------
digiKam version 3.1.0
Exiv2 can write to Jp2: Yes
Exiv2 can write to Jpeg: Yes
Exiv2 can write to Pgf: Yes
Exiv2 can write to Png: Yes
Exiv2 can write to Tiff: Yes
Exiv2 supports XMP metadata: Yes
LibCImg: 130
LibClapack: external shared library
LibExiv2: 0.23
LibJPEG: 80
LibJasper: 1.900.1
LibKDE: 4.10.2
LibKExiv2: 2.3.0
LibKGeoMap: 2.0.0
LibKdcraw: 2.2.0
LibLCMS: 119
LibPGF: 6.12.27 - external shared library
LibPNG: 1.5.15
LibQt: 4.8.4
LibRaw: 0.15.0-Beta1
LibTIFF: LIBTIFF, Version 4.0.2 Copyright (c) 1988-1996 Sam Leffler Copyright
(c) 1991-1996 Silicon Graphics, Inc.
Marble Widget: 0.15.1 (stable version)
Parallelized PGF codec: No
Parallelized demosaicing: No
RawSpeed codec support: No
Database backend: QSQLITE
Kipi-Plugins: 3.0.0
LibKface: 2.0.0
LibKipi: 2.0.0
LibOpenCV: 2.4.3
Libface: 0.2
---------------------------------- >8 ----------------------------------

It is strange, but since I know of this bug and having turned on debug output,
no further image got destroyed. But a few days ago, I lost about five pictures
(out of 300) on the same system. I did not update any packages during these
days.
Today I selected 160 images of mixed rotation and started "Image -> Auto
Rotate/Flip using EXIF information".

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

https://bugs.kde.org/show_bug.cgi?id=317943

--- Comment #24 from Gilles Caulier <[hidden email]> ---
If i understand you, when in debug, no problem, without debug, dysfunctions.
Right ?

This can be a race condition in code.

Gilles Caulier

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Peter Albrecht-2]

https://bugs.kde.org/show_bug.cgi?id=317943

--- Comment #25 from Peter Albrecht <[hidden email]> ---
Today I found time to run another test:
I copied an album of 415 images unrotated images and started "Image -> Auto
Rotate/Flip using EXIF information". Once with debug-output enabled and once
with debug-output disabled:

 - debug-output enabled: 2 images died (half gray)
 - debug-output disabled: 1 image died (reduced to 12 Byte in size)

So the problem seems not to be affected by debug-output beeing enabled or not.

In both directories some "JpegRotator-rx2207.digikamtempfile.jpg" files keep
existing after the rotation operation is finished. It is strange that one of
these "JpegRotator..." files is 12,2 MB in size. But my largest JPEG is only
9,7 MB in size!?!?

So there seems to be some mixing up of rotation operations as Alexander writes
in comment #20 and  Quincy writes in comment #22.

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

https://bugs.kde.org/show_bug.cgi?id=317943

--- Comment #26 from Gilles Caulier <[hidden email]> ---
Peter,

I thinking not about debug trace in fact, printed on the console.

I suspect more debug symbols included during compilation time.

Here with full debug symbol, i never reproduce this dysfunction.

In release compilation, all debug symbols are dropped and code in more
optimized (in speed in general). This can have any side effects...

Gilles Caulier

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Peter Albrecht-2]

https://bugs.kde.org/show_bug.cgi?id=317943

--- Comment #27 from Peter Albrecht <[hidden email]> ---
(In reply to comment #26)
> I thinking not about debug trace in fact, printed on the console.
> I suspect more debug symbols included during compilation time.
> Here with full debug symbol, i never reproduce this dysfunction.
> In release compilation, all debug symbols are dropped and code in more
> optimized (in speed in general). This can have any side effects...

What I did was enabling debug output with "kdebugdialog". Rebuilding digikam
with debug symbols would be a lot more effort. ;)

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Peter Albrecht-2]

https://bugs.kde.org/show_bug.cgi?id=317943

--- Comment #28 from Peter Albrecht <[hidden email]> ---
(In reply to comment #21)
> 2) actually, the bug is not only present with the 'autorotate' function: the
> bug also happened with the normal rotate function. As already said, I think
> the chance is bigger for the bug to happen if you do multiple operations on
> the pictures: in my case, I have selected several pictures in digikam and
> clicked a lot of time (> 10 in a row) on the rotate left button => all my
> pictures where destroyed !!

I can reproduce this error on my machine:
 - take 6 images
 - select them all
 - hit 10 times CTRL + SHIFT + "Cursor Right"  (to perform loss-less rotation)
=> 2 images of 6 are destroyed

  - doing another 20 rotations
=> no further images are destroyed

  - doing another 10 rotations
=> one half gray images gets reduced to a 0 Byte file

----------------------------------------------
Doing one CTRL + SHIFT + "Cursor Right" on my album of 415 images, I end up
with 10 images destroyed. So there is a 2,4% chance to destroy an image using
rotation.

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Peter Albrecht-2]

https://bugs.kde.org/show_bug.cgi?id=317943

--- Comment #29 from Peter Albrecht <[hidden email]> ---
(In reply to comment #27)
> (In reply to comment #26)
> > I thinking not about debug trace in fact, printed on the console.
> > I suspect more debug symbols included during compilation time.
> > Here with full debug symbol, i never reproduce this dysfunction.
> > In release compilation, all debug symbols are dropped and code in more
> > optimized (in speed in general). This can have any side effects...
>
> What I did was enabling debug output with "kdebugdialog". Rebuilding digikam
> with debug symbols would be a lot more effort. ;)

Ok, I tried to build digikam with debug symbols, to help, finding out why you
can't reproduce the error.
On my gentoo system, I ...
   - added "-ggdb" to the CFLAGS in "make.conf"
   - added 'FEATURE="nostrip"' in "make.conf"
   - enabled the useflag "debug" for package "media-gfx/digikam"
  (according to http://www.gentoo.org/proj/en/qa/backtraces.xml)
Than I rebuild digikam. Now "/usr/bin/digikam" is 82 MByte large, so I guess,
there are a lot of debug symbols included. ;)

Additionally, I enabled every "*digikam*" setting in kdebugdialog.

Now I rerun my test of comment #28: "Doing one CTRL + SHIFT + "Cursor Right" on
my album of 415 images". This time I ended up with:
   - a total of 30 images destroyed
   - 16 "JpegRotator-XXXXXXX.digikamtempfile.jpg" files left after rotation
batch finished
   - 7 file of 0 Byte
   - 2 of those 0 Byte files with digikams thread-id attached to the filename
   - 2 files are larger than the larges original file

Another interesting fact: The destroyed images are not spread equally. Among
the 30 destroyed images, I have two blocks of 6 images with subsequent image
numbers:
   - IMG_7864.jpg to IMG_7869.jpg
   - IMG_8074.jpg to IMG_8079.jpg

=> To sum up: I still can reproduce this error with debug symbols enabled.

Do you have any idea, what I could test / debug / log next to help, find this
bug?

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Volker]

https://bugs.kde.org/show_bug.cgi?id=317943

Volker <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |CONFIRMED
     Ever confirmed|0                           |1

--- Comment #30 from Volker <[hidden email]> ---
*** This bug has been confirmed by popular vote. ***

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Volker]

https://bugs.kde.org/show_bug.cgi?id=317943

Volker <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]

--- Comment #31 from Volker <[hidden email]> ---
(In reply to comment #30)
> *** This bug has been confirmed by popular vote. ***

I confirm this problem with a lot of DK versions, as I remember from 2.6 on ,
all on OpenSuseLinux.
Only possibility for me: Do not select more then 20 pictures at the same time,
otherwise lot of pictures are destroyed and must be reloaded from the camera

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

https://bugs.kde.org/show_bug.cgi?id=317943

Gilles Caulier <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|general                     |Albums GUI

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[nous]

https://bugs.kde.org/show_bug.cgi?id=317943

nous <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]

--- Comment #32 from nous <[hidden email]> ---
I'm confirming a similar problem with EXIF auto-rotation: DK won't rotate at
all pictures with pertinent EXIF rotation information and I have to rotate them
manually. Picasa shows them correctly. If I rotate manually with DK sometimes
the thumbnail in Picasa retains the original orientation and gets surrounded by
a larger black frame of with the requested orientation and some garbage (see
attachment).

Arch linux with DK 3.2.0, libjpeg-turbo 1.3.0 and libpeg7.

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[nous]

https://bugs.kde.org/show_bug.cgi?id=317943

--- Comment #33 from nous <[hidden email]> ---
Created attachment 81240
  --> https://bugs.kde.org/attachment.cgi?id=81240&action=edit
Black bordered thumbnail in Picasa

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Nicofo]

https://bugs.kde.org/show_bug.cgi?id=317943

--- Comment #34 from Nicofo <[hidden email]> ---
Still present with Digikam 3.2 and Fedora 19

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[nous]

https://bugs.kde.org/show_bug.cgi?id=317943

--- Comment #35 from nous <[hidden email]> ---
Still present in Digikam 3.3.0 on Archlinux.

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

https://bugs.kde.org/show_bug.cgi?id=317943

Gilles Caulier <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Version|3.1.0                       |3.3.0

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Nicofo]

https://bugs.kde.org/show_bug.cgi?id=317943

--- Comment #36 from Nicofo <[hidden email]> ---
I have not been able to reproduce this bug in digikam 3.3.0.
Maybe some other modification in this version has solved this issue ?

Rem: not sure the bug reported by 'nous' is the same in comment #32 because the
'destruction' of the picture is not similar to mine ? For him: the original
picture is still there, but with strange strips around ; for me: an entire part
of the picture was removed.

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

https://bugs.kde.org/show_bug.cgi?id=317943

--- Comment #37 from Gilles Caulier <[hidden email]> ---
digiKam 3.5.0 is out.

Can you give a fresh feedback about your report ? Problem still reproducible ?

Thanks in advance

Gilles Caulier

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel