[digikam] [Bug 340389] New: Digikam crashes while editing pictures for color balancing on OSX

[Detlef Duerr]

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

            Bug ID: 340389
           Summary: Digikam crashes while editing pictures for color
                    balancing on OSX
           Product: digikam
           Version: 4.0.0
          Platform: MacPorts Packages
                OS: OS X
            Status: UNCONFIRMED
          Severity: grave
          Priority: NOR
         Component: Color Management
          Assignee: [hidden email]
          Reporter: [hidden email]

Created attachment 89335
  --> https://bugs.kde.org/attachment.cgi?id=89335&action=edit
Picture where digikam perspectiv-correction crashes

Every time I will change the color-balancing of a picture digikam crashes.
There is no crash-information though gdb is installed.

Digikam also crashes but not allways, only with special pictures (s.
attachment).

I am working long with digikam under Linux and it works very well. But now, i
am working with Mac it often crashes. Shall I use digikam no more?

Sincerly Detlef Dürr

--
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=340389

Gilles Caulier <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |BACKTRACE

--- Comment #1 from Gilles Caulier <[hidden email]> ---
We need a GDB backtrace to hack. Run digiKam into GDB as explained here :

https://www.digikam.org/contrib

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

[Detlef Duerr]

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

--- Comment #2 from Detlef Duerr <[hidden email]> ---
It's impossible to get a backtrace because after generating "qt4-mac
+debug" and "digikam @4.0.0_0 + debug" the digikam crashes directly by
calling the program. By reactivating "digikam @4.0.0_0" the program
starts with "qt-mac + debug".

If the system will not better working, i think I must change my program
for image-handling only using "gimp"

Sincerely
Detlef Dürr

Am 27.10.14 11:25, schrieb Gilles Caulier:

> https://bugs.kde.org/show_bug.cgi?id=340389
>
> Gilles Caulier <[hidden email]> changed:
>
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                  CC|                            |[hidden email]
>              Status|UNCONFIRMED                 |RESOLVED
>          Resolution|---                         |BACKTRACE
>
> --- Comment #1 from Gilles Caulier <[hidden email]> ---
> We need a GDB backtrace to hack. Run digiKam into GDB as explained here :
>
> https://www.digikam.org/contrib
>
> 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

[Gilles Caulier-4]

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

--- Comment #3 from Gilles Caulier <[hidden email]> ---
digiKam 4.10.0 PKG installer for MAC OSX Yosemite is available for download :

http://download.kde.org/stable/digikam/digikam-4.10.0.pkg.mirrorlist

Please try with this version and give us a feedback...

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

[Detlef Duerr]

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

--- Comment #4 from Detlef Duerr <[hidden email]> ---
With the new Version, I have got as a complete Package you announced me, I have
three times no problem with correcting the perspective but always the program
crashes by correcting the color. Here is the crash information:

 Application: digiKam (digikam), signal: Bus error: 10
(lldb) process attach --pid 73678
Process 73678 stopped
* thread #1: tid = 0xdf765, 0x00007fff9382c4de
libsystem_kernel.dylib`mach_msg_trap + 10, queue = 'com.apple.main-thread',
stop reason = signal SIGSTOP
    frame #0: 0x00007fff9382c4de libsystem_kernel.dylib`mach_msg_trap + 10
libsystem_kernel.dylib`mach_msg_trap:
->  0x7fff9382c4de <+10>: retq
    0x7fff9382c4df <+11>: nop

libsystem_kernel.dylib`mach_msg_overwrite_trap:
    0x7fff9382c4e0 <+0>:  movq   %rcx, %r10
    0x7fff9382c4e3 <+3>:  movl   $0x1000020, %eax

Executable module set to
"/opt/digikam/Applications/KDE4/digikam.app/Contents/MacOS/digikam".
Architecture set to: x86_64-apple-macosx.
(lldb) set set term-width 200
(lldb) thread info
thread #1: tid = 0xdf765, 0x00007fff9382c4de
libsystem_kernel.dylib`mach_msg_trap + 10, queue = 'com.apple.main-thread',
stop reason = signal SIGSTOP

(lldb) bt all
* thread #1: tid = 0xdf765, 0x00007fff9382c4de
libsystem_kernel.dylib`mach_msg_trap + 10, queue = 'com.apple.main-thread',
stop reason = signal SIGSTOP
  * frame #0: 0x00007fff9382c4de libsystem_kernel.dylib`mach_msg_trap + 10
    frame #1: 0x00007fff9382b64f libsystem_kernel.dylib`mach_msg + 55
    frame #2: 0x00007fff92893eb4 CoreFoundation`__CFRunLoopServiceMachPort +
212
    frame #3: 0x00007fff9289337b CoreFoundation`__CFRunLoopRun + 1371
    frame #4: 0x00007fff92892bd8 CoreFoundation`CFRunLoopRunSpecific + 296
    frame #5: 0x00007fff8e9da56f HIToolbox`RunCurrentEventLoopInMode + 235
    frame #6: 0x00007fff8e9da2ea HIToolbox`ReceiveNextEventCommon + 431
    frame #7: 0x00007fff8e9da12b
HIToolbox`_BlockUntilNextEventMatchingListInModeWithFilter + 71
    frame #8: 0x00007fff995019bb AppKit`_DPSNextEvent + 978
    frame #9: 0x00007fff99500f68 AppKit`-[NSApplication
nextEventMatchingMask:untilDate:inMode:dequeue:] + 346
    frame #10: 0x00007fff994f6bf3 AppKit`-[NSApplication run] + 594
    frame #11: 0x000000010904421b
QtGui`QEventDispatcherMac::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)
+ 2027
    frame #12: 0x000000010a0d061f
QtCore`QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 495
    frame #13: 0x000000010a0d3857 QtCore`QCoreApplication::exec() + 199
    frame #14: 0x000000010503eb87 digikam`main + 9559
    frame #15: 0x00007fff955125c9 libdyld.dylib`start + 1

  thread #2: tid = 0xdf7bf, 0x00007fff93832232 libsystem_kernel.dylib`kevent64
+ 10, queue = 'com.apple.libdispatch-manager'
    frame #0: 0x00007fff93832232 libsystem_kernel.dylib`kevent64 + 10
    frame #1: 0x00007fff9054fd91 libdispatch.dylib`_dispatch_mgr_invoke + 247
    frame #2: 0x00007fff9054fa6a libdispatch.dylib`_dispatch_mgr_thread + 52

  thread #3: tid = 0xdf851, 0x00007fff938313fa libsystem_kernel.dylib`__select
+ 10, name = 'com.apple.CFSocket.private'
    frame #0: 0x00007fff938313fa libsystem_kernel.dylib`__select + 10
    frame #1: 0x00007fff928dfb7a CoreFoundation`__CFSocketManager + 730
    frame #2: 0x00007fff9198c268 libsystem_pthread.dylib`_pthread_body + 131
    frame #3: 0x00007fff9198c1e5 libsystem_pthread.dylib`_pthread_start + 176
    frame #4: 0x00007fff9198a41d libsystem_pthread.dylib`thread_start + 13

  thread #4: tid = 0xdf852, 0x00007fff93831136
libsystem_kernel.dylib`__psynch_cvwait + 10, name = 'Digikam::ScanController'
    frame #0: 0x00007fff93831136 libsystem_kernel.dylib`__psynch_cvwait + 10
    frame #1: 0x00007fff9198ce0c libsystem_pthread.dylib`_pthread_cond_wait +
693
    frame #2: 0x0000000109fc445b QtCore`QWaitConditionPrivate::wait(unsigned
long) + 203
    frame #3: 0x0000000109fc42bf QtCore`QWaitCondition::wait(QMutex*, unsigned
long) + 111
    frame #4: 0x0000000104ec8cb1 digikam`Digikam::ScanController::run() + 641
    frame #5: 0x0000000109fc2db2 QtCore`QThreadPrivate::start(void*) + 418
    frame #6: 0x00007fff9198c268 libsystem_pthread.dylib`_pthread_body + 131
    frame #7: 0x00007fff9198c1e5 libsystem_pthread.dylib`_pthread_start + 176
    frame #8: 0x00007fff9198a41d libsystem_pthread.dylib`thread_start + 13

  thread #5: tid = 0xdf854, 0x00007fff9382c4de
libsystem_kernel.dylib`mach_msg_trap + 10
    frame #0: 0x00007fff9382c4de libsystem_kernel.dylib`mach_msg_trap + 10
    frame #1: 0x00007fff9382b64f libsystem_kernel.dylib`mach_msg + 55
    frame #2: 0x00007fff92893eb4 CoreFoundation`__CFRunLoopServiceMachPort +
212
    frame #3: 0x00007fff9289337b CoreFoundation`__CFRunLoopRun + 1371
    frame #4: 0x00007fff92892bd8 CoreFoundation`CFRunLoopRunSpecific + 296
    frame #5: 0x00007fff995c966b AppKit`_NSEventThread + 137
    frame #6: 0x00007fff9198c268 libsystem_pthread.dylib`_pthread_body + 131
    frame #7: 0x00007fff9198c1e5 libsystem_pthread.dylib`_pthread_start + 176
    frame #8: 0x00007fff9198a41d libsystem_pthread.dylib`thread_start + 13

  thread #6: tid = 0xdf8d0, 0x00007fff93831136
libsystem_kernel.dylib`__psynch_cvwait + 10, name = 'QThread'
    frame #0: 0x00007fff93831136 libsystem_kernel.dylib`__psynch_cvwait + 10
    frame #1: 0x00007fff9198ce0c libsystem_pthread.dylib`_pthread_cond_wait +
693
    frame #2: 0x0000000109fc445b QtCore`QWaitConditionPrivate::wait(unsigned
long) + 203
    frame #3: 0x0000000109fc42bf QtCore`QWaitCondition::wait(QMutex*, unsigned
long) + 111
    frame #4: 0x000000010636a160
libdigikamcore.4.10.0.dylib`Digikam::ParkingThread::run() + 176
    frame #5: 0x0000000109fc2db2 QtCore`QThreadPrivate::start(void*) + 418
    frame #6: 0x00007fff9198c268 libsystem_pthread.dylib`_pthread_body + 131
    frame #7: 0x00007fff9198c1e5 libsystem_pthread.dylib`_pthread_start + 176
    frame #8: 0x00007fff9198a41d libsystem_pthread.dylib`thread_start + 13

  thread #7: tid = 0xdf960, 0x00007fff93831902 libsystem_kernel.dylib`__wait4 +
10, name = 'Thread (pooled)'
    frame #0: 0x00007fff93831902 libsystem_kernel.dylib`__wait4 + 10

  thread #8: tid = 0xdf9eb, 0x00007fff9383221a libsystem_kernel.dylib`kevent +
10, name = 'QKqueueFileSystemWatcherEngine'
    frame #0: 0x00007fff9383221a libsystem_kernel.dylib`kevent + 10
    frame #1: 0x000000010a0b577a QtCore`QKqueueFileSystemWatcherEngine::run() +
106
    frame #2: 0x0000000109fc2db2 QtCore`QThreadPrivate::start(void*) + 418
    frame #3: 0x00007fff9198c268 libsystem_pthread.dylib`_pthread_body + 131
    frame #4: 0x00007fff9198c1e5 libsystem_pthread.dylib`_pthread_start + 176
    frame #5: 0x00007fff9198a41d libsystem_pthread.dylib`thread_start + 13

  thread #9: tid = 0xe0e7b, 0x00007fff9383194a
libsystem_kernel.dylib`__workq_kernreturn + 10
    frame #0: 0x00007fff9383194a libsystem_kernel.dylib`__workq_kernreturn + 10
    frame #1: 0x00007fff9198c6c3 libsystem_pthread.dylib`_pthread_wqthread +
869
    frame #2: 0x00007fff9198a40d libsystem_pthread.dylib`start_wqthread + 13
(lldb) detach
Process 73678 detached
(lldb) (lldb) quit

With best regards,
Detlef Dürr

Detlef Dürr
Ringstr. 87
78465 Konstanz
Tel.:  [phone]
Mobil: [phone]
EMail: [hidden email]
Fingerprint: 971D BE20 D168 F253 8C77  DB09 5CCD 6F47 8312 E7DF

> Am 28.05.2015 um 15:11 schrieb Gilles Caulier <[hidden email]>:
>
> https://bugs.kde.org/show_bug.cgi?id=340389
>
> --- Comment #3 from Gilles Caulier <[hidden email]> ---
> digiKam 4.10.0 PKG installer for MAC OSX Yosemite is available for download :
>
> http://download.kde.org/stable/digikam/digikam-4.10.0.pkg.mirrorlist
>
> Please try with this version and give us a feedback...
>
> Thanks in advance.
>
> Gilles Caulier
>
> --
> You are receiving this mail because:
> You reported the 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

[Gilles Caulier-4]

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

Gilles Caulier <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|grave                       |task
             Status|RESOLVED                    |REOPENED
         Resolution|BACKTRACE                   |---
     Ever confirmed|0                           |1
            Version|4.0.0                       |4.10.0

--- Comment #5 from Gilles Caulier <[hidden email]> ---
Ok, i need to know your color management settings and your ICC profiles files.
For these one, please attach .icc files to this report

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

[Gilles Caulier-4]

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

Gilles Caulier <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|---                         |WAITINGFORINFO

--- Comment #6 from Gilles Caulier <[hidden email]> ---
When you said "but always the program crashes by correcting the color", what do
you mean by "correcting the color" ?

Did you use color management settings ?

Did you use a specific tool from editor to change color
tonality/brightness/contrast/etc... ?

What do you do exactly in digiKam to crash application ?

Note your backtrace do not give any information about digiKam source 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

[Detlef Duerr]

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

--- Comment #7 from Detlef Duerr <[hidden email]> ---
»Color correction« means the menupoint in German »Farbabgleich«. I worked in
the following steps:

1. Starting digikam
2. click on 1 picture in the actual album
3. click menupoint  »Bildbearbeitung«
4. Choose the menu point »Farbabgelich«
5. if the program not crashes exactly now, test of lowering blue => crash
6. program crash report…

Sometimes the system also crashes by choosing the menupoint »Anpassung der
Perspektive«.

With best regards,
Detlef Dürr
Ringstr. 87
78465 Konstanz
Tel.:  [phone]
Mobil: [phone]
EMail: [hidden email]
Fingerprint: 971D BE20 D168 F253 8C77  DB09 5CCD 6F47 8312 E7DF

> Am 29.05.2015 um 09:56 schrieb Gilles Caulier <[hidden email]>:
>
> https://bugs.kde.org/show_bug.cgi?id=340389
>
> Gilles Caulier <[hidden email]> changed:
>
>           What    |Removed                     |Added
> ----------------------------------------------------------------------------
>             Status|REOPENED                    |RESOLVED
>         Resolution|---                         |WAITINGFORINFO
>
> --- Comment #6 from Gilles Caulier <[hidden email]> ---
> When you said "but always the program crashes by correcting the color", what do
> you mean by "correcting the color" ?
>
> Did you use color management settings ?
>
> Did you use a specific tool from editor to change color
> tonality/brightness/contrast/etc... ?
>
> What do you do exactly in digiKam to crash application ?
>
> Note your backtrace do not give any information about digiKam source code...
>
> Gilles Caulier
>
> --
> You are receiving this mail because:
> You reported the 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

[Gilles Caulier-4]

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

Gilles Caulier <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|WAITINGFORINFO              |---
             Status|RESOLVED                    |REOPENED
            Summary|Digikam crashes while       |digiKam crashes while
                   |editing pictures for color  |editing pictures for color
                   |balancing on OSX            |balancing on OSX

--- Comment #8 from Gilles Caulier <[hidden email]> ---
Ok, it's color balance tool.

Go to digiKam/setup dialog, into MICS section and choose QtCurves widget
styles.

Try again to check if it's improve stability.

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

[Detlef Duerr]

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

--- Comment #9 from Detlef Duerr <[hidden email]> ---
Setting QtCurves doesn’t change the stability. By choosing »color balance« und
choosing for »blue« -1 stops the program because of crash

with best regards
Detlef Dürr
Ringstr. 87
78465 Konstanz
Tel.:  [phone]
Mobil: [phone]
EMail: [hidden email]
Fingerprint: 971D BE20 D168 F253 8C77  DB09 5CCD 6F47 8312 E7DF

> Am 29.05.2015 um 15:35 schrieb Gilles Caulier <[hidden email]>:
>
> https://bugs.kde.org/show_bug.cgi?id=340389
>
> Gilles Caulier <[hidden email]> changed:
>
>           What    |Removed                     |Added
> ----------------------------------------------------------------------------
>         Resolution|WAITINGFORINFO              |---
>             Status|RESOLVED                    |REOPENED
>            Summary|Digikam crashes while       |digiKam crashes while
>                   |editing pictures for color  |editing pictures for color
>                   |balancing on OSX            |balancing on OSX
>
> --- Comment #8 from Gilles Caulier <[hidden email]> ---
> Ok, it's color balance tool.
>
> Go to digiKam/setup dialog, into MICS section and choose QtCurves widget
> styles.
>
> Try again to check if it's improve stability.
>
> Gilles Caulier
>
> --
> You are receiving this mail because:
> You reported the 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

[Gilles Caulier-4]

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

--- Comment #10 from Gilles Caulier <[hidden email]> ---
I think that problem is similar than bug #320382, excepted that you crash in
this condition.

Can you try to reproduce the problem from this file ?

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

[Detlef Duerr]

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

--- Comment #11 from Detlef Duerr <[hidden email]> ---
Thats my reproduction of the file #320382 with one of my pictures. The picture
itself will not be corrupted (see the right picture in the appendix (I have the
picture scaled to a small version and copied into the screenshot of digikam
after selecting "Aspect Ratio Crop«, so I can  send it to you) of my answer.
The left small picture shows an undiscernible rightangle an there is no
information for the cropping.

With best regards
Detlef Dürr
Ringstr. 87
78465 Konstanz
Tel.:  [phone]
Mobil: [phone]
EMail: [hidden email]
Fingerprint: 971D BE20 D168 F253 8C77  DB09 5CCD 6F47 8312 E7DF

> Am 29.05.2015 um 21:42 schrieb Gilles Caulier <[hidden email]>:
>
> #320382

--
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

[Detlef Duerr]

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

--- Comment #12 from Detlef Duerr <[hidden email]> ---
Thats my reproduction of the file #320382 with one of my pictures. The picture
itself will not be corrupted (see the right picture in the appendix (I have the
picture scaled to a small version and copied into the screenshot of digikam
after selecting "Aspect Ratio Crop«, so I can  send it to you) of my answer.
The left small picture shows an undiscernible rightangle an there is no
information for the cropping.

With best regards
Detlef Dürr
Ringstr. 87
78465 Konstanz
Tel.:  [phone]
Mobil: [phone]
EMail: [hidden email]
Fingerprint: 971D BE20 D168 F253 8C77  DB09 5CCD 6F47 8312 E7DF

> Am 29.05.2015 um 21:42 schrieb Gilles Caulier <[hidden email]>:
>
> #320382

--
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

[Maik Qualmann]

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

Maik Qualmann <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
      Latest Commit|                            |http://commits.kde.org/digi
                   |                            |kam/a8b7a0713609fc752bbd718
                   |                            |30f72ae01bd8dbb67
   Version Fixed In|                            |4.12.0
             Status|REOPENED                    |RESOLVED

--- Comment #13 from Maik Qualmann <[hidden email]> ---
Git commit a8b7a0713609fc752bbd71830f72ae01bd8dbb67 by Maik Qualmann.
Committed on 22/06/2015 at 17:23.
Pushed by mqualmann into branch 'master'.

corrects the values for width and height of the preview image from the image
data interface
Related: bug 269682, bug 317689, bug 320382
FIXED-IN: 4.12.0

M  +5    -1    NEWS
M  +2    -1    utilities/imageeditor/plugin/imageiface.cpp

http://commits.kde.org/digikam/a8b7a0713609fc752bbd71830f72ae01bd8dbb67

--
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=340389

--- Comment #14 from Gilles Caulier <[hidden email]> ---
Git commit 9f4b909f94f7e4623ad8b434637b2c3d6c09934d by Gilles Caulier.
Committed on 22/06/2015 at 19:12.
Pushed by cgilles into branch 'frameworks'.

backport commit #a8b7a0713609fc752bbd71830f72ae01bd8dbb67 from git/master to
frameworks branch
Related: bug 269682, bug 317689, bug 320382

M  +4    -1    utilities/imageeditor/plugin/imageiface.cpp

http://commits.kde.org/digikam/9f4b909f94f7e4623ad8b434637b2c3d6c09934d

--
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

[Detlef]

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

Detlef <[hidden email]> changed:

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

--- Comment #15 from Detlef <[hidden email]> ---
Today I have installed digikam 4.13.0 and it runs but not in all possibilities.
If i click in picture editing the menue-option "color-management", then then
color-management opens, but by clicking on 1 color to change, by example the
color "blue" gving a "-1" in direction "yellow" digikam crashes.

The procedure is reproducible. See the crash-backtracking.
Application: digiKam (digikam), signal: Bus error: 10
(lldb) process attach --pid 39039
Process 39039 stopped
* thread #1: tid = 0x5e1d9, 0x00007fff8ffdc4de
libsystem_kernel.dylib`mach_msg_trap + 10, queue = 'com.apple.main-thread',
stop reason = signal SIGSTOP
    frame #0: 0x00007fff8ffdc4de libsystem_kernel.dylib`mach_msg_trap + 10
libsystem_kernel.dylib`mach_msg_trap:
->  0x7fff8ffdc4de <+10>: retq  
    0x7fff8ffdc4df <+11>: nop    

libsystem_kernel.dylib`mach_msg_overwrite_trap:
    0x7fff8ffdc4e0 <+0>:  movq   %rcx, %r10
    0x7fff8ffdc4e3 <+3>:  movl   $0x1000020, %eax

Executable module set to
"/opt/digikam/Applications/KDE4/digikam.app/Contents/MacOS/digikam".
Architecture set to: x86_64-apple-macosx.
(lldb) set set term-width 200
(lldb) thread info
thread #1: tid = 0x5e1d9, 0x00007fff8ffdc4de
libsystem_kernel.dylib`mach_msg_trap + 10, queue = 'com.apple.main-thread',
stop reason = signal SIGSTOP

(lldb) bt all
* thread #1: tid = 0x5e1d9, 0x00007fff8ffdc4de
libsystem_kernel.dylib`mach_msg_trap + 10, queue = 'com.apple.main-thread',
stop reason = signal SIGSTOP
  * frame #0: 0x00007fff8ffdc4de libsystem_kernel.dylib`mach_msg_trap + 10
    frame #1: 0x00007fff8ffdb64f libsystem_kernel.dylib`mach_msg + 55
    frame #2: 0x00007fff83670eb4 CoreFoundation`__CFRunLoopServiceMachPort +
212
    frame #3: 0x00007fff8367037b CoreFoundation`__CFRunLoopRun + 1371
    frame #4: 0x00007fff8366fbd8 CoreFoundation`CFRunLoopRunSpecific + 296
    frame #5: 0x00007fff90e8f56f HIToolbox`RunCurrentEventLoopInMode + 235
    frame #6: 0x00007fff90e8f2ea HIToolbox`ReceiveNextEventCommon + 431
    frame #7: 0x00007fff90e8f12b
HIToolbox`_BlockUntilNextEventMatchingListInModeWithFilter + 71
    frame #8: 0x00007fff888858ab AppKit`_DPSNextEvent + 978
    frame #9: 0x00007fff88884e58 AppKit`-[NSApplication
nextEventMatchingMask:untilDate:inMode:dequeue:] + 346
    frame #10: 0x00007fff8887aaf3 AppKit`-[NSApplication run] + 594
    frame #11: 0x000000010b78af1e
QtGui`QEventDispatcherMac::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)
+ 1966
    frame #12: 0x000000010b559de2
QtCore`QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 498
    frame #13: 0x000000010b55cfa7 QtCore`QCoreApplication::exec() + 199
    frame #14: 0x0000000106c1cfd7 digikam`main + 9127
    frame #15: 0x00007fff86b615c9 libdyld.dylib`start + 1

  thread #2: tid = 0x5e1f8, 0x00007fff8ffe2232 libsystem_kernel.dylib`kevent64
+ 10, queue = 'com.apple.libdispatch-manager'
    frame #0: 0x00007fff8ffe2232 libsystem_kernel.dylib`kevent64 + 10
    frame #1: 0x00007fff90b8dd91 libdispatch.dylib`_dispatch_mgr_invoke + 247
    frame #2: 0x00007fff90b8da6a libdispatch.dylib`_dispatch_mgr_thread + 52

  thread #3: tid = 0x5e218, 0x00007fff8ffe13fa libsystem_kernel.dylib`__select
+ 10, name = 'com.apple.CFSocket.private'
    frame #0: 0x00007fff8ffe13fa libsystem_kernel.dylib`__select + 10
    frame #1: 0x00007fff836bcb7a CoreFoundation`__CFSocketManager + 730
    frame #2: 0x00007fff9135d05a libsystem_pthread.dylib`_pthread_body + 131
    frame #3: 0x00007fff9135cfd7 libsystem_pthread.dylib`_pthread_start + 176
    frame #4: 0x00007fff9135a3ed libsystem_pthread.dylib`thread_start + 13

  thread #4: tid = 0x5e219, 0x00007fff8ffe1136
libsystem_kernel.dylib`__psynch_cvwait + 10, name = 'Digikam::ScanController'
    frame #0: 0x00007fff8ffe1136 libsystem_kernel.dylib`__psynch_cvwait + 10
    frame #1: 0x00007fff9135d560 libsystem_pthread.dylib`_pthread_cond_wait +
693
    frame #2: 0x000000010b44731b QtCore`QWaitConditionPrivate::wait(unsigned
long) + 203
    frame #3: 0x000000010b44717f QtCore`QWaitCondition::wait(QMutex*, unsigned
long) + 111
    frame #4: 0x0000000106aa5a41 digikam`Digikam::ScanController::run() + 641
    frame #5: 0x000000010b445c62 QtCore`QThreadPrivate::start(void*) + 386
    frame #6: 0x00007fff9135d05a libsystem_pthread.dylib`_pthread_body + 131
    frame #7: 0x00007fff9135cfd7 libsystem_pthread.dylib`_pthread_start + 176
    frame #8: 0x00007fff9135a3ed libsystem_pthread.dylib`thread_start + 13

  thread #5: tid = 0x5e224, 0x00007fff8ffdc4de
libsystem_kernel.dylib`mach_msg_trap + 10
    frame #0: 0x00007fff8ffdc4de libsystem_kernel.dylib`mach_msg_trap + 10
    frame #1: 0x00007fff8ffdb64f libsystem_kernel.dylib`mach_msg + 55
    frame #2: 0x00007fff83670eb4 CoreFoundation`__CFRunLoopServiceMachPort +
212
    frame #3: 0x00007fff8367037b CoreFoundation`__CFRunLoopRun + 1371
    frame #4: 0x00007fff8366fbd8 CoreFoundation`CFRunLoopRunSpecific + 296
    frame #5: 0x00007fff8894d56b AppKit`_NSEventThread + 137
    frame #6: 0x00007fff9135d05a libsystem_pthread.dylib`_pthread_body + 131
    frame #7: 0x00007fff9135cfd7 libsystem_pthread.dylib`_pthread_start + 176
    frame #8: 0x00007fff9135a3ed libsystem_pthread.dylib`thread_start + 13

  thread #6: tid = 0x5e23f, 0x00007fff8ffe1136
libsystem_kernel.dylib`__psynch_cvwait + 10, name = 'QThread'
    frame #0: 0x00007fff8ffe1136 libsystem_kernel.dylib`__psynch_cvwait + 10
    frame #1: 0x00007fff9135d560 libsystem_pthread.dylib`_pthread_cond_wait +
693
    frame #2: 0x000000010b44731b QtCore`QWaitConditionPrivate::wait(unsigned
long) + 203
    frame #3: 0x000000010b44717f QtCore`QWaitCondition::wait(QMutex*, unsigned
long) + 111
    frame #4: 0x0000000107f58980
libdigikamcore.4.13.0.dylib`Digikam::ParkingThread::run() + 176
    frame #5: 0x000000010b445c62 QtCore`QThreadPrivate::start(void*) + 386
    frame #6: 0x00007fff9135d05a libsystem_pthread.dylib`_pthread_body + 131
    frame #7: 0x00007fff9135cfd7 libsystem_pthread.dylib`_pthread_start + 176
    frame #8: 0x00007fff9135a3ed libsystem_pthread.dylib`thread_start + 13

  thread #7: tid = 0x5e252, 0x00007fff8ffe1902 libsystem_kernel.dylib`__wait4 +
10, name = 'Thread (pooled)'
    frame #0: 0x00007fff8ffe1902 libsystem_kernel.dylib`__wait4 + 10

  thread #8: tid = 0x5e263, 0x00007fff8ffe221a libsystem_kernel.dylib`kevent +
10, name = 'QKqueueFileSystemWatcherEngine'
    frame #0: 0x00007fff8ffe221a libsystem_kernel.dylib`kevent + 10
    frame #1: 0x000000010b53e64a QtCore`QKqueueFileSystemWatcherEngine::run() +
106
    frame #2: 0x000000010b445c62 QtCore`QThreadPrivate::start(void*) + 386
    frame #3: 0x00007fff9135d05a libsystem_pthread.dylib`_pthread_body + 131
    frame #4: 0x00007fff9135cfd7 libsystem_pthread.dylib`_pthread_start + 176
    frame #5: 0x00007fff9135a3ed libsystem_pthread.dylib`thread_start + 13

  thread #9: tid = 0x5f961, 0x00007fff8ffe194a
libsystem_kernel.dylib`__workq_kernreturn + 10
    frame #0: 0x00007fff8ffe194a libsystem_kernel.dylib`__workq_kernreturn + 10
    frame #1: 0x00007fff9135cb29 libsystem_pthread.dylib`_pthread_wqthread +
869
    frame #2: 0x00007fff9135a3dd libsystem_pthread.dylib`start_wqthread + 13
(lldb) detach
Process 39039 detached
(lldb) (lldb) quit

--
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=340389

Gilles Caulier <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Version|4.10.0                      |4.12.0
             Status|RESOLVED                    |REOPENED
           Severity|task                        |crash
         Resolution|FIXED                       |---

--
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

[bugzilla_noreply]

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

--- Comment #16 from [hidden email] ---
digiKam 5.0.0-beta7 Installer for MacOSX is now available for testing...

https://drive.google.com/open?id=0B7yq-xFihT0_ZjlIazRPb1lRTEE

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

[bugzilla_noreply]

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

--- Comment #17 from [hidden email] ---
Detlef,

Do you seen my previous comment ?

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

[bugzilla_noreply]

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

[hidden email] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
   Version Fixed In|4.12.0                      |5.0.0
             Status|REOPENED                    |RESOLVED

--- Comment #18 from [hidden email] ---
I tried to reproduce the dysfunction using digiKam 5.0.0 PKG installer with CM
enabled in image editor. No crash...

I close this file now. Re-open if necessary.

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