[digikam] [Bug 382818] New: Rotating a picture ends in crash

[bugzilla_noreply]

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

            Bug ID: 382818
           Summary: Rotating a picture ends in crash
           Product: digikam
           Version: 5.6.0
          Platform: Other
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: AlbumsView
          Assignee: [hidden email]
          Reporter: [hidden email]
  Target Milestone: ---

If I rotate an image (clicking the button) it works one, two times. The next
rotation of an image ends in a sudden crash, digikam closes without any bug
description or hint.

It is possible to rotate pictures in the ImageEditor-Tool.

I am using ubuntu 17.04 and unity and with the package source of
http://ppa.launchpad.net/philip5/extra/ubuntu

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

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

Simon <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]
         Resolution|---                         |WAITINGFORINFO
             Status|UNCONFIRMED                 |NEEDSINFO

--- Comment #1 from Simon <[hidden email]> ---
Can you please run digikam in gdb and post the backtrace after the crash as
describe here:
https://www.digikam.org/contribute/

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

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

--- Comment #2 from Markus Kempf <[hidden email]> ---
Created attachment 106913
  --> https://bugs.kde.org/attachment.cgi?id=106913&action=edit
gdb export after crash

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

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

--- Comment #3 from Simon <[hidden email]> ---
After the segfault instead of quitting directly, you need to first run "bt" to
get the backtrace - which is the most essential part of the entire report.

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

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

--- Comment #4 from Markus Kempf <[hidden email]> ---
Created attachment 106914
  --> https://bugs.kde.org/attachment.cgi?id=106914&action=edit
gdb export after crash and bt

This time after bt in gdb

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

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

Simon <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Ever confirmed|0                           |1
         Resolution|WAITINGFORINFO              |---
             Status|NEEDSINFO                   |CONFIRMED

--- Comment #5 from Simon <[hidden email]> ---
I don't see anything obviously problematic in the function the backtrace points
to and I can't reproduce the crash here. I am out of my depth here.

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

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

Christoph Feck <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|normal                      |crash

--- Comment #6 from Christoph Feck <[hidden email]> ---
Pasting relevant part from comment #4 for duplicate searches.

(gdb) bt
#0  0x00007ffff677b5c3 in ?? () from /usr/lib/digikam/libdigikamcore.so.5.6.0
#1  0x00007ffff6774458 in
Digikam::JPEGUtils::JpegRotator::performJpegTransform(Digikam::MetaEngineRotation::TransformationAction,
QString const&, QString const&) () from
/usr/lib/digikam/libdigikamcore.so.5.6.0
#2  0x00007ffff67779d7 in
Digikam::JPEGUtils::JpegRotator::exifTransform(Digikam::MetaEngineRotation
const&) () from /usr/lib/digikam/libdigikamcore.so.5.6.0
#3  0x00007ffff67793f7 in
Digikam::JPEGUtils::JpegRotator::exifTransform(Digikam::MetaEngineRotation::TransformationAction)
()
   from /usr/lib/digikam/libdigikamcore.so.5.6.0

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

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

--- Comment #7 from Markus Kempf <[hidden email]> ---
I don't understand the last comment "relevant part for duplicate searches".

I tried to rotate pictures coming from different sources. It seems that
jpg-pictures from the camera don't crash during the roting (imported via the
import tool), but pictures exported by rawtherapee or cropped by imagemagick
show the crashes (created in the folder structure of the digikam).

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

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

Maik Qualmann <[hidden email]> changed:

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

--- Comment #8 from Maik Qualmann <[hidden email]> ---
The comment #6 is only for finding similar crashes within the bug tracker. Can
you provide an image that triggers a crash?

Maik

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

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

--- Comment #9 from Markus Kempf <[hidden email]> ---
Created attachment 107016
  --> https://bugs.kde.org/attachment.cgi?id=107016&action=edit
rotating this picture results in a crash

Rotating this picture ends in a crash of digikam. The picture comes from
rawtherapee, is cropped by imagemagick and stored as 85% jpg via gimp. Normally
I use 100% jpg but I have to reduce the image size.
Interesting point - after the crash there is a new jpg created in the folder. I
will attach it, too.

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

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

--- Comment #10 from Markus Kempf <[hidden email]> ---
Created attachment 107018
  --> https://bugs.kde.org/attachment.cgi?id=107018&action=edit
created jpg during the crash

During rotating and crashing of pic 107016 the attached digikamtempfile is
created...

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

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

--- Comment #11 from Maik Qualmann <[hidden email]> ---
Which libJPEG version you use, see digiKam component info? Which of the
messages below do you see in the console? The LibJPEG error with the "Maximum
supported image dimension is 65500 pixels" is strange. But there is no crash
here.

digikam.general: Jpegutils error, aborting operation: Maximum supported image
dimension is 65500 pixels
digikam.general: JPEG lossless transform failed for
"/daten/Bilder/Zugang/bretagne95_m6_P6040736_crop.jpg"
digikam.general: Trying lossy transform for
"/daten/Bilder/Zugang/bretagne95_m6_P6040736_crop.jpg"
digikam.dimg: "/daten/Bilder/Zugang/bretagne95_m6_P6040736_crop.jpg"  : JPEG
file identified
digikam.general: JPEG Quality:  85  File:
"/daten/Bilder/Zugang/bretagne95_m6_P6040736_crop.jpg"

Maik

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

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

--- Comment #12 from Markus Kempf <[hidden email]> ---
The digikam component info shows

LibJPEG: 80

ubuntu 17.04 installs
libjpeg8
JPEG-Laufzeitbibliothek der »Independent JPEG Group« (Abhängigkeitspaket)

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

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

[hidden email] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]
          Component|Albums-MainView             |FilesIO-JPEG

--
You are receiving this mail because:
You are the assignee for the bug.