[digikam] [Bug 319383] New: Crash while applying lensfun distortion correction

[Gilles Caulier-4]

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

--- Comment #19 from Gilles Caulier <[hidden email]> ---
Git commit 2ad23dae290c64c293d9c3d3ae2c8734c99f902b by Gilles Caulier.
Committed on 02/09/2014 at 15:06.
Pushed by cgilles into branch 'master'.

Make digiKam ready to use next Lensfun API where CII correction have been
removed.
Related: bug 331523, bug 333540
FIXED-IN: 4.3.0

M  +1    -2    imageplugins/enhance/lensautofixtool.cpp
M  +1    -1    imageplugins/enhance/lensautofixtool.h
M  +3    -12   libs/dimg/filters/lens/lensfunfilter.cpp
M  +3    -5    libs/dimg/filters/lens/lensfunfilter.h
M  +3    -6    libs/dimg/filters/lens/lensfuniface.cpp
M  +0    -1    libs/dimg/filters/lens/lensfuniface.h
M  +1    -26   libs/dimg/filters/lens/lensfunsettings.cpp
M  +1    -2    libs/dimg/filters/lens/lensfunsettings.h
M  +8    -13   utilities/queuemanager/basetools/enhance/lensautofix.cpp
M  +1    -1    utilities/queuemanager/basetools/enhance/lensautofix.h

http://commits.kde.org/digikam/2ad23dae290c64c293d9c3d3ae2c8734c99f902b

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

--- Comment #20 from Gilles Caulier <[hidden email]> ---
Mathias,

With current implementation from git/master (next digiKam 4.3.0), CCI
correction have been removed from digiKam because Lensfun team have dropped
this feature for next 0.2.9 release.

Can you test if crash still reproducible with current implementation ?

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

[Karl-Wilhelm Frommeyer]

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

--- Comment #21 from Karl-Wilhelm Frommeyer <[hidden email]> ---
Dear Gilles
I tested the function with digikam 4.2 on kubuntu 14.04. When using the lens
correction function digikam crashes but not with the first image. Only with the
second or third. But unfortunately than it crashes.
Instead of digikam I use darktable that works fine in the same os.
Thank you for all your effort you took to give us users an improvement!!!!!!!!!
Kind regards Karl-Wilhelm

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

--- Comment #22 from Gilles Caulier <[hidden email]> ---
Can you share a set of images where you can reproduce the crash to check on my
computer.

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

[Gilles Caulier-4]

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

--- Comment #23 from Gilles Caulier <[hidden email]> ---
digiKam 4.5.0 have been released.

Crash still reproducible with this release ?

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

[Karl-Wilhelm Frommeyer]

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

--- Comment #24 from Karl-Wilhelm Frommeyer <[hidden email]> ---
Dear Gilles
shortly I updated kubuntu to 14.10. So now I can use digikam 4.2. But that
version has still the same bug.
At the moment I do not know how to upgrade safe digikam to 4.5.
Despite the bug with the lens correction digikam 4.2 is very stable and I love
this program-package. It's great.
Thank you so much for all the effort and I'm happy because of the outstanding
result.
Kind regards Karl-Wilhelm

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

Gilles Caulier <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Version|4.1.0                       |4.2.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

[Georg Schilling]

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

Georg Schilling <[hidden email]> changed:

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

--- Comment #25 from Georg Schilling <[hidden email]> ---
Application: digikam (3.5.0)
KDE Platform Version: 4.13.3
Qt Version: 4.8.6
Operating System: Linux 3.13.0-44-generic x86_64
Distribution: Ubuntu 14.04.1 LTS

-- Information about the crash:
- What I was doing when the application crashed:

It seems that there is a correlation betwenn crash and lens-type. Using
lenscorrection on pictures of my old Sony-Cam are functioning properly. Usind
the Canon EOS 650D whith "default" 18-55 lens will resukt in the crash.

The crash can be reproduced every time.

-- Backtrace:
Application: digiKam (digikam), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
[Current thread is 1 (Thread 0x7fc5f4bb3ac0 (LWP 16126))]

Thread 6 (Thread 0x7fc5d0248700 (LWP 16128)):
#0  0x00007fc5ee5c9cbd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007fc5d4df3248 in ?? () from /lib/x86_64-linux-gnu/libusb-1.0.so.0
#2  0x00007fc5e9859182 in start_thread (arg=0x7fc5d0248700) at
pthread_create.c:312
#3  0x00007fc5ee5d700d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 5 (Thread 0x7fc5c97af700 (LWP 16129)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007fc5ef3b8816 in wait (time=18446744073709551615, this=0x261f060) at
thread/qwaitcondition_unix.cpp:86
#2  QWaitCondition::wait (this=this@entry=0x261ef70,
mutex=mutex@entry=0x261ef68, time=time@entry=18446744073709551615) at
thread/qwaitcondition_unix.cpp:158
#3  0x00000000005d5ede in Digikam::ScanController::run (this=0x261ece0) at
/build/buildd/digikam-3.5.0/core/digikam/database/scancontroller.cpp:725
#4  0x00007fc5ef3b832f in QThreadPrivate::start (arg=0x261ece0) at
thread/qthread_unix.cpp:349
#5  0x00007fc5e9859182 in start_thread (arg=0x7fc5c97af700) at
pthread_create.c:312
#6  0x00007fc5ee5d700d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 4 (Thread 0x7fc5c8fae700 (LWP 16130)):
#0  0x00007fc5e70c261a in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x00007fc5e70c29a9 in g_mutex_unlock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007fc5e7080f91 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007fc5e70810ec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007fc5ef4e77be in QEventDispatcherGlib::processEvents
(this=0x7fc5bc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436
#5  0x00007fc5ef4b90af in QEventLoop::processEvents
(this=this@entry=0x7fc5c8fadae0, flags=...) at kernel/qeventloop.cpp:149
#6  0x00007fc5ef4b93a5 in QEventLoop::exec (this=this@entry=0x7fc5c8fadae0,
flags=...) at kernel/qeventloop.cpp:204
#7  0x00007fc5ef3b5c5f in QThread::exec (this=this@entry=0x252ef80) at
thread/qthread.cpp:537
#8  0x00007fc5ef49a823 in QInotifyFileSystemWatcherEngine::run (this=0x252ef80)
at io/qfilesystemwatcher_inotify.cpp:265
#9  0x00007fc5ef3b832f in QThreadPrivate::start (arg=0x252ef80) at
thread/qthread_unix.cpp:349
#10 0x00007fc5e9859182 in start_thread (arg=0x7fc5c8fae700) at
pthread_create.c:312
#11 0x00007fc5ee5d700d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 3 (Thread 0x7fc5b6b2e700 (LWP 16226)):
#0  idleTimerSourceCheck (source=<optimized out>) at
kernel/qeventdispatcher_glib.cpp:230
#1  0x00007fc5e7080a61 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007fc5e7080f7b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007fc5e70810ec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007fc5ef4e77be in QEventDispatcherGlib::processEvents
(this=0x7fc5b00008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436
#5  0x00007fc5ef4b90af in QEventLoop::processEvents
(this=this@entry=0x7fc5b6b2dae0, flags=...) at kernel/qeventloop.cpp:149
#6  0x00007fc5ef4b93a5 in QEventLoop::exec (this=this@entry=0x7fc5b6b2dae0,
flags=...) at kernel/qeventloop.cpp:204
#7  0x00007fc5ef3b5c5f in QThread::exec (this=this@entry=0x2e7d5d0) at
thread/qthread.cpp:537
#8  0x00007fc5ef49a823 in QInotifyFileSystemWatcherEngine::run (this=0x2e7d5d0)
at io/qfilesystemwatcher_inotify.cpp:265
#9  0x00007fc5ef3b832f in QThreadPrivate::start (arg=0x2e7d5d0) at
thread/qthread_unix.cpp:349
#10 0x00007fc5e9859182 in start_thread (arg=0x7fc5b6b2e700) at
pthread_create.c:312
#11 0x00007fc5ee5d700d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 2 (Thread 0x7fc5a951c700 (LWP 16627)):
[KCrash Handler]
#6  setColor (sixteenBit=false, data=0x7fc61e34ef0c <error: Cannot access
memory at address 0x7fc61e34ef0c>, this=<synthetic pointer>) at
/build/buildd/digikam-3.5.0/core/libs/dimg/dcolorpixelaccess.h:42
#7  Digikam::DImg::getSubPixelColorFast (this=this@entry=0x6d61e38,
x=<optimized out>, y=<optimized out>) at
/build/buildd/digikam-3.5.0/core/libs/dimg/dimg.cpp:1391
#8  0x00007fc5f21a3a9b in Digikam::LensFunFilter::filterImage (this=0x6d61df0)
at
/build/buildd/digikam-3.5.0/core/libs/dimg/filters/lens/lensfunfilter.cpp:196
#9  0x00007fc5f2086b6c in Digikam::DImgThreadedFilter::startFilterDirectly
(this=0x6d61df0) at
/build/buildd/digikam-3.5.0/core/libs/dimg/filters/dimgthreadedfilter.cpp:194
#10 0x00007fc5f22335de in Digikam::DynamicThread::DynamicThreadPriv::run
(this=0x6d17c40) at
/build/buildd/digikam-3.5.0/core/libs/threads/dynamicthread.cpp:186
#11 0x00007fc5ef3abfee in QThreadPoolThread::run (this=0x416c3c0) at
concurrent/qthreadpool.cpp:108
#12 0x00007fc5ef3b832f in QThreadPrivate::start (arg=0x416c3c0) at
thread/qthread_unix.cpp:349
#13 0x00007fc5e9859182 in start_thread (arg=0x7fc5a951c700) at
pthread_create.c:312
#14 0x00007fc5ee5d700d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 1 (Thread 0x7fc5f4bb3ac0 (LWP 16126)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007fc5ef3b8816 in wait (time=18446744073709551615, this=0x29e3660) at
thread/qwaitcondition_unix.cpp:86
#2  QWaitCondition::wait (this=this@entry=0x2c83400,
mutex=mutex@entry=0x2c833d8, time=time@entry=18446744073709551615) at
thread/qwaitcondition_unix.cpp:158
#3  0x00007fc5ef3ab242 in QThreadPoolPrivate::waitForDone (this=0x2c83350,
msecs=msecs@entry=-1) at concurrent/qthreadpool.cpp:295
#4  0x00007fc5ef3ac6b5 in QThreadPool::~QThreadPool (this=0x29e8500,
__in_chrg=<optimized out>) at concurrent/qthreadpool.cpp:438
#5  0x00007fc5ef3ac6e9 in QThreadPool::~QThreadPool (this=0x29e8500,
__in_chrg=<optimized out>) at concurrent/qthreadpool.cpp:440
#6  0x00007fc5ef4d1168 in QObjectPrivate::deleteChildren
(this=this@entry=0x28b3a50) at kernel/qobject.cpp:1907
#7  0x00007fc5ef4d36ff in QObject::~QObject (this=0x29e24d0,
__in_chrg=<optimized out>) at kernel/qobject.cpp:926
#8  0x00007fc5f2230737 in ~ThreadManagerCreator (this=0x29e24d0,
__in_chrg=<optimized out>) at
/build/buildd/digikam-3.5.0/core/libs/threads/threadmanager.cpp:236
#9  destroy () at
/build/buildd/digikam-3.5.0/core/libs/threads/threadmanager.cpp:241
#10 0x00007fc5ee518259 in __run_exit_handlers (status=1, listp=0x7fc5ee89b6c8
<__exit_funcs>, run_list_atexit=run_list_atexit@entry=true) at exit.c:82
#11 0x00007fc5ee5182a5 in __GI_exit (status=<optimized out>) at exit.c:104
#12 0x00007fc5eff13878 in qt_xio_errhandler () at
kernel/qapplication_x11.cpp:783
#13 0x00007fc5f0bb68d0 in KApplication::xioErrhandler (this=0x7fff49daef40,
dpy=0x2465aa0) at ../../kdeui/kernel/kapplication.cpp:419
#14 0x00007fc5ecace5ee in _XIOError () from
/usr/lib/x86_64-linux-gnu/libX11.so.6
#15 0x00007fc5ecacbfed in _XEventsQueued () from
/usr/lib/x86_64-linux-gnu/libX11.so.6
#16 0x00007fc5ecabe0db in XEventsQueued () from
/usr/lib/x86_64-linux-gnu/libX11.so.6
#17 0x00007fc5eff4e687 in x11EventSourcePrepare (s=0x2464670,
timeout=<optimized out>) at kernel/qguieventdispatcher_glib.cpp:77
#18 0x00007fc5e708068d in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x00007fc5e7080f03 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x00007fc5e70810ec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x00007fc5ef4e77a1 in QEventDispatcherGlib::processEvents (this=0x238caa0,
flags=...) at kernel/qeventdispatcher_glib.cpp:434
#22 0x00007fc5eff4ebb6 in QGuiEventDispatcherGlib::processEvents
(this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#23 0x00007fc5ef4b90af in QEventLoop::processEvents
(this=this@entry=0x7fff49daea20, flags=...) at kernel/qeventloop.cpp:149
#24 0x00007fc5ef4b93a5 in QEventLoop::exec (this=this@entry=0x7fff49daea20,
flags=...) at kernel/qeventloop.cpp:204
#25 0x00007fc5ef4beb79 in QCoreApplication::exec () at
kernel/qcoreapplication.cpp:1225
#26 0x00007fc5efeab37c in QApplication::exec () at kernel/qapplication.cpp:3828
#27 0x0000000000492023 in main (argc=<optimized out>, argv=<optimized out>) at
/build/buildd/digikam-3.5.0/core/digikam/main/main.cpp:235

Possible duplicates by query: bug 333523.

An https://bugs.kde.org/ berichten

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

[Georg Schilling]

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

--- Comment #26 from Georg Schilling <[hidden email]> ---
Application: digikam (3.5.0)
KDE Platform Version: 4.13.3
Qt Version: 4.8.6
Operating System: Linux 3.13.0-44-generic x86_64
Distribution: Ubuntu 14.04.1 LTS

-- Information about the crash:
The flash seems not to be the difference betwenn the picture. At least, I have
no clue!

The crash can be reproduced every time.

-- Backtrace:
Application: digiKam (digikam), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
[Current thread is 1 (Thread 0x7ffa96926ac0 (LWP 18656))]

Thread 6 (Thread 0x7ffa71fbb700 (LWP 18658)):
#0  0x00007ffa9033ccbd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007ffa76b66248 in ?? () from /lib/x86_64-linux-gnu/libusb-1.0.so.0
#2  0x00007ffa8b5cc182 in start_thread (arg=0x7ffa71fbb700) at
pthread_create.c:312
#3  0x00007ffa9034a00d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 5 (Thread 0x7ffa6b522700 (LWP 18659)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007ffa9112b816 in wait (time=18446744073709551615, this=0x2581a90) at
thread/qwaitcondition_unix.cpp:86
#2  QWaitCondition::wait (this=this@entry=0x25819a0,
mutex=mutex@entry=0x2581998, time=time@entry=18446744073709551615) at
thread/qwaitcondition_unix.cpp:158
#3  0x00000000005d5ede in Digikam::ScanController::run (this=0x2581710) at
/build/buildd/digikam-3.5.0/core/digikam/database/scancontroller.cpp:725
#4  0x00007ffa9112b32f in QThreadPrivate::start (arg=0x2581710) at
thread/qthread_unix.cpp:349
#5  0x00007ffa8b5cc182 in start_thread (arg=0x7ffa6b522700) at
pthread_create.c:312
#6  0x00007ffa9034a00d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 4 (Thread 0x7ffa6ad21700 (LWP 18660)):
#0  0x00007ffa88df3860 in g_main_context_query () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x00007ffa88df3f52 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007ffa88df40ec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007ffa9125a7be in QEventDispatcherGlib::processEvents
(this=0x7ffa5c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436
#4  0x00007ffa9122c0af in QEventLoop::processEvents
(this=this@entry=0x7ffa6ad20ae0, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007ffa9122c3a5 in QEventLoop::exec (this=this@entry=0x7ffa6ad20ae0,
flags=...) at kernel/qeventloop.cpp:204
#6  0x00007ffa91128c5f in QThread::exec (this=this@entry=0x26936f0) at
thread/qthread.cpp:537
#7  0x00007ffa9120d823 in QInotifyFileSystemWatcherEngine::run (this=0x26936f0)
at io/qfilesystemwatcher_inotify.cpp:265
#8  0x00007ffa9112b32f in QThreadPrivate::start (arg=0x26936f0) at
thread/qthread_unix.cpp:349
#9  0x00007ffa8b5cc182 in start_thread (arg=0x7ffa6ad21700) at
pthread_create.c:312
#10 0x00007ffa9034a00d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 3 (Thread 0x7ffa58853700 (LWP 18770)):
#0  0x00007ffa9033ccbd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007ffa88df3fe4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007ffa88df40ec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007ffa9125a7be in QEventDispatcherGlib::processEvents
(this=0x7ffa540008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436
#4  0x00007ffa9122c0af in QEventLoop::processEvents
(this=this@entry=0x7ffa58852ae0, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007ffa9122c3a5 in QEventLoop::exec (this=this@entry=0x7ffa58852ae0,
flags=...) at kernel/qeventloop.cpp:204
#6  0x00007ffa91128c5f in QThread::exec (this=this@entry=0x2ed0ed0) at
thread/qthread.cpp:537
#7  0x00007ffa9120d823 in QInotifyFileSystemWatcherEngine::run (this=0x2ed0ed0)
at io/qfilesystemwatcher_inotify.cpp:265
#8  0x00007ffa9112b32f in QThreadPrivate::start (arg=0x2ed0ed0) at
thread/qthread_unix.cpp:349
#9  0x00007ffa8b5cc182 in start_thread (arg=0x7ffa58853700) at
pthread_create.c:312
#10 0x00007ffa9034a00d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 2 (Thread 0x7ffa46cdb700 (LWP 19011)):
[KCrash Handler]
#6  setColor (sixteenBit=false, data=0x7ffaa72eff0c <error: Cannot access
memory at address 0x7ffaa72eff0c>, this=<synthetic pointer>) at
/build/buildd/digikam-3.5.0/core/libs/dimg/dcolorpixelaccess.h:42
#7  Digikam::DImg::getSubPixelColorFast (this=this@entry=0x7005468,
x=<optimized out>, y=<optimized out>) at
/build/buildd/digikam-3.5.0/core/libs/dimg/dimg.cpp:1391
#8  0x00007ffa93f16a9b in Digikam::LensFunFilter::filterImage (this=0x7005420)
at
/build/buildd/digikam-3.5.0/core/libs/dimg/filters/lens/lensfunfilter.cpp:196
#9  0x00007ffa93df9b6c in Digikam::DImgThreadedFilter::startFilterDirectly
(this=0x7005420) at
/build/buildd/digikam-3.5.0/core/libs/dimg/filters/dimgthreadedfilter.cpp:194
#10 0x00007ffa93fa65de in Digikam::DynamicThread::DynamicThreadPriv::run
(this=0x6bfec30) at
/build/buildd/digikam-3.5.0/core/libs/threads/dynamicthread.cpp:186
#11 0x00007ffa9111efee in QThreadPoolThread::run (this=0x41c1ac0) at
concurrent/qthreadpool.cpp:108
#12 0x00007ffa9112b32f in QThreadPrivate::start (arg=0x41c1ac0) at
thread/qthread_unix.cpp:349
#13 0x00007ffa8b5cc182 in start_thread (arg=0x7ffa46cdb700) at
pthread_create.c:312
#14 0x00007ffa9034a00d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 1 (Thread 0x7ffa96926ac0 (LWP 18656)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007ffa9112b816 in wait (time=18446744073709551615, this=0x2931a60) at
thread/qwaitcondition_unix.cpp:86
#2  QWaitCondition::wait (this=this@entry=0x2cd7940,
mutex=mutex@entry=0x2cd7918, time=time@entry=18446744073709551615) at
thread/qwaitcondition_unix.cpp:158
#3  0x00007ffa9111e242 in QThreadPoolPrivate::waitForDone (this=0x2cd7890,
msecs=msecs@entry=-1) at concurrent/qthreadpool.cpp:295
#4  0x00007ffa9111f6b5 in QThreadPool::~QThreadPool (this=0x2906050,
__in_chrg=<optimized out>) at concurrent/qthreadpool.cpp:438
#5  0x00007ffa9111f6e9 in QThreadPool::~QThreadPool (this=0x2906050,
__in_chrg=<optimized out>) at concurrent/qthreadpool.cpp:440
#6  0x00007ffa91244168 in QObjectPrivate::deleteChildren
(this=this@entry=0x2a36cd0) at kernel/qobject.cpp:1907
#7  0x00007ffa912466ff in QObject::~QObject (this=0x2cd84f0,
__in_chrg=<optimized out>) at kernel/qobject.cpp:926
#8  0x00007ffa93fa3737 in ~ThreadManagerCreator (this=0x2cd84f0,
__in_chrg=<optimized out>) at
/build/buildd/digikam-3.5.0/core/libs/threads/threadmanager.cpp:236
#9  destroy () at
/build/buildd/digikam-3.5.0/core/libs/threads/threadmanager.cpp:241
#10 0x00007ffa9028b259 in __run_exit_handlers (status=1, listp=0x7ffa9060e6c8
<__exit_funcs>, run_list_atexit=run_list_atexit@entry=true) at exit.c:82
#11 0x00007ffa9028b2a5 in __GI_exit (status=<optimized out>) at exit.c:104
#12 0x00007ffa91c86878 in qt_xio_errhandler () at
kernel/qapplication_x11.cpp:783
#13 0x00007ffa929298d0 in KApplication::xioErrhandler (this=0x7fffeec44750,
dpy=0x24b9aa0) at ../../kdeui/kernel/kapplication.cpp:419
#14 0x00007ffa8e8415ee in _XIOError () from
/usr/lib/x86_64-linux-gnu/libX11.so.6
#15 0x00007ffa8e83efed in _XEventsQueued () from
/usr/lib/x86_64-linux-gnu/libX11.so.6
#16 0x00007ffa8e8310db in XEventsQueued () from
/usr/lib/x86_64-linux-gnu/libX11.so.6
#17 0x00007ffa91cc162c in x11EventSourceCheck (s=0x24b8670) at
kernel/qguieventdispatcher_glib.cpp:85
#18 0x00007ffa88df3a61 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x00007ffa88df3f7b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x00007ffa88df40ec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x00007ffa9125a7a1 in QEventDispatcherGlib::processEvents (this=0x23e0aa0,
flags=...) at kernel/qeventdispatcher_glib.cpp:434
#22 0x00007ffa91cc1bb6 in QGuiEventDispatcherGlib::processEvents
(this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#23 0x00007ffa9122c0af in QEventLoop::processEvents
(this=this@entry=0x7fffeec44230, flags=...) at kernel/qeventloop.cpp:149
#24 0x00007ffa9122c3a5 in QEventLoop::exec (this=this@entry=0x7fffeec44230,
flags=...) at kernel/qeventloop.cpp:204
#25 0x00007ffa91231b79 in QCoreApplication::exec () at
kernel/qcoreapplication.cpp:1225
#26 0x00007ffa91c1e37c in QApplication::exec () at kernel/qapplication.cpp:3828
#27 0x0000000000492023 in main (argc=<optimized out>, argv=<optimized out>) at
/build/buildd/digikam-3.5.0/core/digikam/main/main.cpp:235

Possible duplicates by query: bug 333523.

An https://bugs.kde.org/ berichten

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

Gilles Caulier <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
   Version Fixed In|                            |4.9.0
      Latest Commit|                            |http://commits.kde.org/digi
                   |                            |kam/a0ea63613faf5062e6891eb
                   |                            |12d53b334b1babc4a
         Resolution|---                         |FIXED

--- Comment #27 from Gilles Caulier <[hidden email]> ---
Git commit a0ea63613faf5062e6891eb12d53b334b1babc4a by Gilles Caulier.
Committed on 15/03/2015 at 23:21.
Pushed by cgilles into branch 'master'.

Apply patch # 91573 from Maik Qualmann to wrap image pixel positions to image
sizes when Lens Corrections are applied by LensFun.
Related: bug 333540, bug 345168
FIXED-IN: 4.9.0

M  +4    -1    NEWS
M  +22   -13   libs/dimg/dimg.cpp

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

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

--- Comment #28 from Gilles Caulier <[hidden email]> ---
Git commit 53fd2de987febf552103de3ecc910a4d9c94c0d2 by Gilles Caulier.
Committed on 15/03/2015 at 22:47.
Pushed by cgilles into branch 'frameworks'.

backport commit #a0ea63613faf5062e6891eb12d53b334b1babc4a from git/master to
frameworks branch
Related: bug 333540, bug 345168

M  +16   -7    libs/dimg/dimg.cpp

http://commits.kde.org/digikam/53fd2de987febf552103de3ecc910a4d9c94c0d2

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

[hidden email] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|Lens Distortion             |Tool-LensDistortion
            Product|digikamimageplugins         |digikam

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