[digikam] [Bug 326959] New: Digikam crash while scanning pictures for thumnails maintenance

[eldk]

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

            Bug ID: 326959
           Summary: Digikam crash while scanning pictures for thumnails
                    maintenance
    Classification: Unclassified
           Product: digikam
           Version: 4.0.0-beta1
          Platform: Compiled Sources
                OS: Linux
            Status: UNCONFIRMED
          Keywords: drkonqi
          Severity: crash
          Priority: NOR
         Component: general
          Assignee: [hidden email]
          Reporter: [hidden email]

Application: digikam (4.0.0-beta1)
KDE Platform Version: 4.11.2 (Compiled from sources)
Qt Version: 4.8.2
Operating System: Linux 3.2.0-55-generic i686
Distribution: Ubuntu 12.04.3 LTS

-- Information about the crash:
- What I was doing when the application crashed:
look at pictures while thumbnail maintenance (all collection)

-- Backtrace:
Application: digiKam (digikam), signal: Aborted
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0xb5141780 (LWP 29444))]

Thread 6 (Thread 0xb2d8ab40 (LWP 29445)):
#0  0x008e7416 in __kernel_vsyscall ()
#1  0x00f7e96b in pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:169
#2  0x077546ec in __pthread_cond_wait (cond=0x9f3c078, mutex=0x9f3c060) at
forward.c:139
#3  0x02c26420 in wait (time=4294967295, this=0x9f3c060) at
thread/qwaitcondition_unix.cpp:86
#4  QWaitCondition::wait (this=0x9f3bfd4, mutex=0x9f3bfd0, time=4294967295) at
thread/qwaitcondition_unix.cpp:158
#5  0x0820b3e6 in Digikam::ScanController::run (this=0x9f34290) at
/home/eric/digikamgit2/dkgitdigikamsoftwarecompilation/core/digikam/database/scancontroller.cpp:725
#6  0x02c25eb0 in QThreadPrivate::start (arg=0x9f34290) at
thread/qthread_unix.cpp:307
#7  0x00f7ad4c in start_thread (arg=0xb2d8ab40) at pthread_create.c:308
#8  0x07746dde in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 5 (Thread 0xb23ffb40 (LWP 29446)):
#0  0x008e7416 in __kernel_vsyscall ()
#1  0x07738690 in __GI___poll (fds=0xb1a02178, nfds=1, timeout=-1) at
../sysdeps/unix/sysv/linux/poll.c:87
#2  0x03b3ca3b in g_poll () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0x03b2f06e in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#4  0x03b2f1c1 in g_main_context_iteration () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#5  0x02d6dde7 in QEventDispatcherGlib::processEvents (this=0xb1a00468,
flags=...) at kernel/qeventdispatcher_glib.cpp:426
#6  0x02d396ad in QEventLoop::processEvents (this=0xb23ff200, flags=...) at
kernel/qeventloop.cpp:149
#7  0x02d39949 in QEventLoop::exec (this=0xb23ff200, flags=...) at
kernel/qeventloop.cpp:204
#8  0x02c22a1c in QThread::exec (this=0x9f4fab0) at thread/qthread.cpp:501
#9  0x02d16cfd in QInotifyFileSystemWatcherEngine::run (this=0x9f4fab0) at
io/qfilesystemwatcher_inotify.cpp:248
#10 0x02c25eb0 in QThreadPrivate::start (arg=0x9f4fab0) at
thread/qthread_unix.cpp:307
#11 0x00f7ad4c in start_thread (arg=0xb23ffb40) at pthread_create.c:308
#12 0x07746dde in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 4 (Thread 0xb19ffb40 (LWP 29450)):
#0  0x008e7416 in __kernel_vsyscall ()
#1  0x00f7e96b in pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:169
#2  0x077546ec in __pthread_cond_wait (cond=0xa0c8e08, mutex=0xa0c8df0) at
forward.c:139
#3  0x02c26420 in wait (time=4294967295, this=0xa0c8df0) at
thread/qwaitcondition_unix.cpp:86
#4  QWaitCondition::wait (this=0xa0ca498, mutex=0xa0ca494, time=4294967295) at
thread/qwaitcondition_unix.cpp:158
#5  0x012e3da8 in Digikam::ParkingThread::run (this=0xa0ca488) at
/home/eric/digikamgit2/dkgitdigikamsoftwarecompilation/core/libs/threads/threadmanager.cpp:119
#6  0x02c25eb0 in QThreadPrivate::start (arg=0xa0ca488) at
thread/qthread_unix.cpp:307
#7  0x00f7ad4c in start_thread (arg=0xb19ffb40) at pthread_create.c:308
#8  0x07746dde in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 3 (Thread 0xa4711b40 (LWP 29540)):
#0  0x008e7416 in __kernel_vsyscall ()
#1  0x00f7e96b in pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:169
#2  0x077546ec in __pthread_cond_wait (cond=0xeb2cc80, mutex=0xeb2cc68) at
forward.c:139
#3  0x02c26420 in wait (time=4294967295, this=0xeb2cc68) at
thread/qwaitcondition_unix.cpp:86
#4  QWaitCondition::wait (this=0xe936e04, mutex=0xe936e08, time=4294967295) at
thread/qwaitcondition_unix.cpp:158
#5  0x00d7e4c5 in KDcrawIface::RActionThreadBase::run (this=0xa6cb6e0) at
/home/eric/digikamgit2/dkgitdigikamsoftwarecompilation/extra/libkdcraw/libkdcraw/ractionthreadbase.cpp:138
#6  0x02c25eb0 in QThreadPrivate::start (arg=0xa6cb6e0) at
thread/qthread_unix.cpp:307
#7  0x00f7ad4c in start_thread (arg=0xa4711b40) at pthread_create.c:308
#8  0x07746dde in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 2 (Thread 0xa6f16b40 (LWP 29541)):
[KCrash Handler]
#7  0x008e7416 in __kernel_vsyscall ()
#8  0x076861df in __GI_raise (sig=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:64
#9  0x07689825 in __GI_abort () at abort.c:91
#10 0x0767f085 in __assert_fail_base (fmt=0xb3d9c764
"%s%s%s\302\240:%u\302\240:\302\240%s%s l'assertion
\302\253\302\240%s\302\240\302\273 a \303\251chou\303\251.\n%n",
assertion=0x98fafdd "!xcb_xlib_unknown_req_in_deq", file=0x98fafca
"../../src/xcb_io.c", line=179, function=0x98fb0a0 "dequeue_pending_request")
at assert.c:94
#11 0x0767f137 in __GI___assert_fail (assertion=0x98fafdd
"!xcb_xlib_unknown_req_in_deq", file=0x98fafca "../../src/xcb_io.c", line=179,
function=0x98fb0a0 "dequeue_pending_request") at assert.c:103
#12 0x098824c6 in ?? () from /usr/lib/i386-linux-gnu/libX11.so.6
#13 0x0988378f in _XReply () from /usr/lib/i386-linux-gnu/libX11.so.6
#14 0x098793c4 in XQueryTree () from /usr/lib/i386-linux-gnu/libX11.so.6
#15 0x01783203 in QWidgetPrivate::updateFrameStrut (this=0x9fd7480) at
kernel/qwidget_x11.cpp:2942
#16 0x0172a86e in QWidgetPrivate::frameStrut (this=0x9fd7480) at
kernel/qwidget.cpp:12038
#17 0x0172b2e0 in QWidget::frameGeometry (this=0x9f93af8) at
kernel/qwidget.cpp:3534
#18 0x0177bfb8 in QDesktopWidget::screenNumber (this=0x9eb8040,
widget=0x9f93af8) at kernel/qdesktopwidget_x11.cpp:393
#19 0x011a12fd in Digikam::IccSettings::Private::profileFromWindowSystem
(this=0x9f9b548, widget=0x9f93af8) at
/home/eric/digikamgit2/dkgitdigikamsoftwarecompilation/core/libs/dimg/filters/icc/iccsettings.cpp:204
#20 0x011a0efd in Digikam::IccSettings::monitorProfile (this=0xa021628,
widget=0x9f93af8) at
/home/eric/digikamgit2/dkgitdigikamsoftwarecompilation/core/libs/dimg/filters/icc/iccsettings.cpp:134
#21 0x01195f7a in Digikam::IccManager::displayProfile
(displayingWidget=0x9f93af8) at
/home/eric/digikamgit2/dkgitdigikamsoftwarecompilation/core/libs/dimg/filters/icc/iccmanager.cpp:385
#22 0x012c81cb in
Digikam::ThumbnailLoadThread::Private::createLoadingDescription
(this=0x130ed570, filePath=..., size=254, setLastDescription=true) at
/home/eric/digikamgit2/dkgitdigikamsoftwarecompilation/core/libs/threadimageio/thumbnailloadthread.cpp:335
#23 0x012c8944 in Digikam::ThumbnailLoadThread::find (this=0x130ed280,
filePath=..., size=256, retPixmap=0x0, emitSignal=true, detailRect=...) at
/home/eric/digikamgit2/dkgitdigikamsoftwarecompilation/core/libs/threadimageio/thumbnailloadthread.cpp:454
#24 0x012c8ca7 in Digikam::ThumbnailLoadThread::find (this=0x130ed280,
filePath=..., size=256) at
/home/eric/digikamgit2/dkgitdigikamsoftwarecompilation/core/libs/threadimageio/thumbnailloadthread.cpp:517
#25 0x012c8c53 in Digikam::ThumbnailLoadThread::find (this=0x130ed280,
filePath=...) at
/home/eric/digikamgit2/dkgitdigikamsoftwarecompilation/core/libs/threadimageio/thumbnailloadthread.cpp:512
#26 0x0814a814 in Digikam::ThumbsTask::run (this=0x130ed320) at
/home/eric/digikamgit2/dkgitdigikamsoftwarecompilation/core/utilities/maintenance/thumbstask.cpp:85
#27 0x00b47f33 in ThreadWeaver::JobRunHelper::runTheJob (this=0xa6f161ec,
th=0x181f8698, job=0x130ed320) at ../../../threadweaver/Weaver/Job.cpp:106
#28 0x00b480d3 in ThreadWeaver::Job::execute (this=0x130ed320, th=0x181f8698)
at ../../../threadweaver/Weaver/Job.cpp:135
#29 0x00b495f5 in ThreadWeaver::JobCollectionJobRunner::execute
(this=0x130edb58, t=0x181f8698) at
../../../threadweaver/Weaver/JobCollection.cpp:82
#30 0x00b475d6 in ThreadWeaver::Thread::run (this=0x181f8698) at
../../../threadweaver/Weaver/Thread.cpp:108
#31 0x02c25eb0 in QThreadPrivate::start (arg=0x181f8698) at
thread/qthread_unix.cpp:307
#32 0x00f7ad4c in start_thread (arg=0xa6f16b40) at pthread_create.c:308
#33 0x07746dde in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 1 (Thread 0xb5141780 (LWP 29444)):
#0  0x09883618 in _XReply () from /usr/lib/i386-linux-gnu/libX11.so.6
#1  0x09868aa8 in XGetWindowProperty () from
/usr/lib/i386-linux-gnu/libX11.so.6
#2  0x01759d25 in QETWidget::translatePropertyEvent (this=0x9f93af8,
event=0xbfcb733c) at kernel/qapplication_x11.cpp:5150
#3  0x01768be0 in QApplication::x11ProcessEvent (this=0xbfcb7768,
event=0xbfcb733c) at kernel/qapplication_x11.cpp:4002
#4  0x01795e1c in x11EventSourceDispatch (s=0x9d60e90, callback=0,
user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#5  0x03b2ed46 in g_main_context_dispatch () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#6  0x03b2f0e5 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#7  0x03b2f1c1 in g_main_context_iteration () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#8  0x02d6dd87 in QEventDispatcherGlib::processEvents (this=0x9d05bb0,
flags=...) at kernel/qeventdispatcher_glib.cpp:424
#9  0x01795a1a in QGuiEventDispatcherGlib::processEvents (this=0x9d05bb0,
flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#10 0x02d396ad in QEventLoop::processEvents (this=0xbfcb7634, flags=...) at
kernel/qeventloop.cpp:149
#11 0x02d39949 in QEventLoop::exec (this=0xbfcb7634, flags=...) at
kernel/qeventloop.cpp:204
#12 0x02d3f34a in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1187
#13 0x016da9c4 in QApplication::exec () at kernel/qapplication.cpp:3817
#14 0x0830e0e3 in main (argc=1, argv=0xbfcb79c4) at
/home/eric/digikamgit2/dkgitdigikamsoftwarecompilation/core/digikam/main/main.cpp:235

Possible duplicates by query: bug 315521, bug 311955.

Reported using DrKonqi

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

[eldk]

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

--- Comment #1 from [hidden email] ---
from console log :

digikam(29444)/KEXIV2 KExiv2Iface::KExiv2::Private::printExiv2MessageHandler:
Exiv2 ( 2 ) :  Directory Minolta, entry 0x0088: Data area exceeds data buffer,
ignoring it.
digikam(29444)/digikam (core) Digikam::DImg::load:
"/media/DiskphotosTests/maison annoeullin/PICT0538.JPG"  : JPEG file identified
digikam(29444)/KEXIV2 KExiv2Iface::KExiv2::getImageOrientation: Orientation =>
Exif.Image.Orientation =>  1
[xcb] Unknown request in queue while dequeuing
[xcb] Most likely this is a multi-threaded client and XInitThreads has not been
called
[xcb] Aborting, sorry about that.
digikam: ../../src/xcb_io.c :179 : dequeue_pending_request:  l'assertion «
!xcb_xlib_unknown_req_in_deq » a échoué.
KCrash: Application 'digikam' crashing...

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

[eldk]

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

--- Comment #2 from [hidden email] ---
maintenance tool options :
digikam(30351)/digikam (core) Digikam::MaintenanceMngr::setSettings:
wholeAlbums         : true
wholeTags           : true
Albums              : 387
Tags                : 495
useMutiCoreCPU      : false
newItems            : false
thumbnails          : true
scanThumbs          : false
fingerPrints        : false
scanFingerPrints    : false
duplicates          : false
similarity          : 90
faceManagement      : false
faceScannedHandling : 0
qualitySort         : false
quality             :
EnableSorter      : false
DetectBlur        : true
DetectNoise       : true
DetectCompression : true
LowQRejected      : true
MediumQPending    : true
HighQAccepted     : true
Speed             : 1
Rejected Threshold: 10
Pending Threshold : 40
Accepted Threshold: 60
Blur Weight       : 100
Noise Weight      : 100
Compression Weight: 100

qualityScanMode     : 0
metadataSync        : false
syncDirection       : 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

[eldk]

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

--- Comment #3 from [hidden email] ---
Installed components :
digiKam version 4.0.0-beta1
Codec PGF parallélisé: Non
Composant graphique Marble: 0.16.2 (stable version)
Demosaic GPL2 pack support: Inconnu
Demosaic GPL3 pack support: Inconnu
Dématriçage parallélisé: Inconnu
Exiv2 peut écrire dans un fichier JP2: Oui
Exiv2 peut écrire dans un fichier JPEG: Oui
Exiv2 peut écrire dans un fichier PGF: Oui
Exiv2 peut écrire dans un fichier PNG: Oui
Exiv2 peut écrire dans un fichier TIFF: Oui
Exiv2 prend en charge les métadonnées XMP: Oui
LibCImg: 130
LibEigen: 3.0.5
LibExiv2: 0.22
LibJPEG: 80
LibJasper: 1.900.1
LibKDE: 4.11.2
LibKExiv2: 2.3.1
LibKGeoMap: 2.0.0
LibKdcraw: 2.4.0
LibLCMS: 2040
LibLensFun: 0.2.7-0
LibPGF: 6.12.27 - bibliothèque interne
LibPNG: 1.2.46
LibQt: 4.8.2
LibRaw: 0.15.4
LibTIFF: LIBTIFF, Version 3.9.5 Copyright (c) 1988-1996 Sam Leffler Copyright
(c) 1991-1996 Silicon Graphics, Inc.
Prise en charge du codec RawSpeed: Inconnu
LibGphoto2: 2.4.14
LibKface: 3.0.0
LibKipi: 2.1.0
LibOpenCV: 2.4.5
Modules externes KIPI: 3.5.0
Moteur de base de données: QMYSQL
Serveur interne de base de données: Non

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

[eldk]

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

--- Comment #4 from [hidden email] ---
Hello,

I launch the same process now to see if I can reproduce it.

Eric

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

Gilles Caulier <[hidden email]> changed:

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

--- Comment #5 from Gilles Caulier <[hidden email]> ---
I recently fixed a huge memory leak in thumbnail process from maintenance tool.
Look this entry for details :

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

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

[eldk]

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

--- Comment #6 from [hidden email] ---
Hello,

I have read that post.

I use : Date de compilation : Oct 31 2013 (cible : debugfull)
Rév. : ea2847ec161df82f8d64e70afdbc5d12feb7708e

I update my git repositories on git digikamsoftwarecompilation yesterday.

So your modification have been apply (ensure by a diff on files that have been
modified).

I use a local start, with a script from terminal. Since this last update, I
can't quit digikam too, no crash, but I have to do ctrl+c after clicking on
quit in menu. It's hang on a "infinite time" without closing digikam.

terminal output :
digikam(30861)/digikam (core) Digikam::ImageScanner::commit: Scanning took 61
ms
digikam(30861)/digikam (core) Digikam::ImageScanner::~ImageScanner: Finishing
took 538 ms
digikam(30861)/digikam (core)
Digikam::CollectionScanner::completeHistoryScanning: items to tag (22180)
digikam(30861)/digikam (core) Digikam::ImageScanner::tagImageHistoryGraph:
Graph with 2 vertices:
"{ Id: 22180 UUID: 3b6a2a... } -> { Id: 61131 UUID: ac2c01... }"
digikam(30861)/digikam (core) Digikam::ImageScanner::tagImageHistoryGraph:
Image 22180 type QFlags(0x1|0x8)
digikam(30861)/digikam (core) Digikam::ImageScanner::tagImageHistoryGraph:
Image 61131 type QFlags(0x8)

Digikam never close, and no more logs or shutdown message (quit in menu,
ctrl+q) .

I try to reproduce it : I'm not sure it's related to thumbnail maintenance :
maybe something with threads and closing opening windows.

Thank you,

Eric

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

[eldk]

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

--- Comment #7 from [hidden email] ---
And for memory, it's good. Digikam don't full fill memory anymore when
rebuilding thumbnails.

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

[eldk]

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

--- Comment #8 from [hidden email] ---
This is gdb backtrace for "Digikam doesn't properly close - never close" :

#########################
START then c
#########################
.... cut the lines
#########################
digikam(31394)/KGEOMAP KGeoMap::ItemMarkerTiler::slotSourceModelReset: ----
digikam(31394)/KGEOMAP KGeoMap::ItemMarkerTiler::slotSourceModelReset: ----
[Thread 0xa343fb40 (LWP 31460) exited]
########################
Press ctrl+q to quit digikam
###########################
Nothing append (digikam windows close but digikam not close)
###########################
Press ctrl+c
##########################
^C
Program received signal SIGINT, Interrupt.
0x00132416 in __kernel_vsyscall ()
(gdb) backtrace
#0  0x00132416 in __kernel_vsyscall ()
#1  0x035be690 in __GI___poll (fds=0xa0774a8, nfds=19, timeout=29999) at
../sysdeps/unix/sysv/linux/poll.c:87
#2  0x05066a3b in g_poll () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0x0505906e in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#4  0x050591c1 in g_main_context_iteration () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#5  0x03200d87 in QEventDispatcherGlib::processEvents (this=0x8626bb0,
flags=...) at kernel/qeventdispatcher_glib.cpp:424
#6  0x0249ba1a in QGuiEventDispatcherGlib::processEvents (this=0x8626bb0,
flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#7  0x031cc6ad in QEventLoop::processEvents (this=0x89bf470, flags=...) at
kernel/qeventloop.cpp:149
#8  0x031cc949 in QEventLoop::exec (this=0x89bf470, flags=...) at
kernel/qeventloop.cpp:204
#9  0x00ecc4dc in Digikam::ProgressManager::slotAbortAll (this=0x89ca0e8) at
/home/eric/digikamgit2/dkgitdigikamsoftwarecompilation/core/libs/progressmanager/progressmanager.cpp:594
#10 0x081b6c03 in Digikam::DigikamApp::~DigikamApp (this=0x88b86c8,
__in_chrg=<optimized out>, __vtt_parm=<optimized out>) at
/home/eric/digikamgit2/dkgitdigikamsoftwarecompilation/core/digikam/main/digikamapp.cpp:307
#11 0x081b6efd in Digikam::DigikamApp::~DigikamApp (this=0x88b86c8,
__in_chrg=<optimized out>, __vtt_parm=<optimized out>) at
/home/eric/digikamgit2/dkgitdigikamsoftwarecompilation/core/digikam/main/digikamapp.cpp:369
#12 0x031e2203 in qDeleteInEventHandler (o=0x88b86c8) at
kernel/qobject.cpp:4277
#25 0x031d229c in QCoreApplication::sendPostedEvents (receiver=0x0,
event_type=0) at kernel/qcoreapplication.cpp:1432
#26 0x03200994 in sendPostedEvents () at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236
#27 postEventSourceDispatch (s=0x8681f28) at
kernel/qeventdispatcher_glib.cpp:279
#28 0x05058d46 in g_main_context_dispatch () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#29 0x050590e5 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#30 0x050591c1 in g_main_context_iteration () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#31 0x03200d87 in QEventDispatcherGlib::processEvents (this=0x8626bb0,
flags=...) at kernel/qeventdispatcher_glib.cpp:424
#32 0x0249ba1a in QGuiEventDispatcherGlib::processEvents (this=0x8626bb0,
flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#33 0x031cc6ad in QEventLoop::processEvents (this=0xbfffebd4, flags=...) at
kernel/qeventloop.cpp:149
#34 0x031cc949 in QEventLoop::exec (this=0xbfffebd4, flags=...) at
kernel/qeventloop.cpp:204
#35 0x031d234a in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1187
#36 0x023e09c4 in QApplication::exec () at kernel/qapplication.cpp:3817
#37 0x0830e0e3 in main (argc=1, argv=0xbfffef64) at
/home/eric/digikamgit2/dkgitdigikamsoftwarecompilation/core/digikam/main/main.cpp:235
##################
try to start but digikam not properly closed
##################
(gdb) start
The program being debugged has been started already.
Start it from the beginning? (y or n) n
Program not restarted.
######################
Press c and digikam continuing to doing nothing (no digikam windows)
####################################################################
(gdb) c
Continuing.
################
second ctrl+c and same backtrace (no digikam window but digikam is still there)
#################################
^C
Program received signal SIGINT, Interrupt.
0x00132416 in __kernel_vsyscall ()
(gdb) backtrace
#0  0x00132416 in __kernel_vsyscall ()
#1  0x035be690 in __GI___poll (fds=0xa0774a8, nfds=13, timeout=9986) at
../sysdeps/unix/sysv/linux/poll.c:87
#2  0x05066a3b in g_poll () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0x0505906e in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#4  0x050591c1 in g_main_context_iteration () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#5  0x03200d87 in QEventDispatcherGlib::processEvents (this=0x8626bb0,
flags=...) at kernel/qeventdispatcher_glib.cpp:424
#6  0x0249ba1a in QGuiEventDispatcherGlib::processEvents (this=0x8626bb0,
flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#7  0x031cc6ad in QEventLoop::processEvents (this=0x89bf470, flags=...) at
kernel/qeventloop.cpp:149
#8  0x031cc949 in QEventLoop::exec (this=0x89bf470, flags=...) at
kernel/qeventloop.cpp:204
#9  0x00ecc4dc in Digikam::ProgressManager::slotAbortAll (this=0x89ca0e8) at
/home/eric/digikamgit2/dkgitdigikamsoftwarecompilation/core/libs/progressmanager/progressmanager.cpp:594
#10 0x081b6c03 in Digikam::DigikamApp::~DigikamApp (this=0x88b86c8,
__in_chrg=<optimized out>, __vtt_parm=<optimized out>) at
/home/eric/digikamgit2/dkgitdigikamsoftwarecompilation/core/digikam/main/digikamapp.cpp:307
#11 0x081b6efd in Digikam::DigikamApp::~DigikamApp (this=0x88b86c8,
__in_chrg=<optimized out>, __vtt_parm=<optimized out>) at
/home/eric/digikamgit2/dkgitdigikamsoftwarecompilation/core/digikam/main/digikamapp.cpp:369
#12 0x031e2203 in qDeleteInEventHandler (o=0x88b86c8) at
kernel/qobject.cpp:4277
#13 0x031e91a8 in QObject::event (this=0x88b86c8, e=0xc2906e0) at
kernel/qobject.cpp:1176
#14 0x0243ccb2 in QWidget::event (this=0x88b86c8, event=0xc2906e0) at
kernel/qwidget.cpp:8830
#15 0x0287885c in QMainWindow::event (this=0x88b86c8, event=0xc2906e0) at
widgets/qmainwindow.cpp:1478
#16 0x0212da94 in KMainWindow::event (this=0x88b86c8, ev=0xc2906e0) at
../../kdeui/widgets/kmainwindow.cpp:1084
#17 0x02177972 in KXmlGuiWindow::event (this=0x88b86c8, ev=0xc2906e0) at
../../kdeui/xmlgui/kxmlguiwindow.cpp:126
#18 0x023e2df4 in notify_helper (e=0xc2906e0, receiver=0x88b86c8,
this=0x86825d8) at kernel/qapplication.cpp:4556
#19 QApplicationPrivate::notify_helper (this=0x86825d8, receiver=0x88b86c8,
e=0xc2906e0) at kernel/qapplication.cpp:4528
#20 0x023e81f2 in QApplication::notify (this=0x86825d8, receiver=0x88b86c8,
e=0xc2906e0) at kernel/qapplication.cpp:4521
#21 0x02051ed1 in KApplication::notify (this=0xbfffed08, receiver=0x88b86c8,
event=0xc2906e0) at ../../kdeui/kernel/kapplication.cpp:311
#22 0x031cde0e in QCoreApplication::notifyInternal (this=0xbfffed08,
receiver=0x88b86c8, event=0xc2906e0) at kernel/qcoreapplication.cpp:915
#23 0x031d1f68 in sendEvent (event=<optimized out>, receiver=<optimized out>)
at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#24 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0,
data=0x8626050) at kernel/qcoreapplication.cpp:1539
#25 0x031d229c in QCoreApplication::sendPostedEvents (receiver=0x0,
event_type=0) at kernel/qcoreapplication.cpp:1432
#26 0x03200994 in sendPostedEvents () at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236
#27 postEventSourceDispatch (s=0x8681f28) at
kernel/qeventdispatcher_glib.cpp:279
#28 0x05058d46 in g_main_context_dispatch () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#29 0x050590e5 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#30 0x050591c1 in g_main_context_iteration () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#31 0x03200d87 in QEventDispatcherGlib::processEvents (this=0x8626bb0,
flags=...) at kernel/qeventdispatcher_glib.cpp:424
#32 0x0249ba1a in QGuiEventDispatcherGlib::processEvents (this=0x8626bb0,
flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#33 0x031cc6ad in QEventLoop::processEvents (this=0xbfffebd4, flags=...) at
kernel/qeventloop.cpp:149
#34 0x031cc949 in QEventLoop::exec (this=0xbfffebd4, flags=...) at
kernel/qeventloop.cpp:204
#35 0x031d234a in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1187
#36 0x023e09c4 in QApplication::exec () at kernel/qapplication.cpp:3817
#37 0x0830e0e3 in main (argc=1, argv=0xbfffef64) at
/home/eric/digikamgit2/dkgitdigikamsoftwarecompilation/core/digikam/main/main.cpp:235
######
end of backtrace
###############

? perhaps something to do with the progressmanager modification ?

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

Gilles Caulier <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|general                     |Progress Manager

--- Comment #9 from Gilles Caulier <[hidden email]> ---
yes, the crash is due to my last changes in progress manager, from this entry :

https://bugs.kde.org/show_bug.cgi?id=302810#c5

Before this fix, digiKAm crash because main application is closed when progress
tasks still running.

My patch must wait than all progress tasks are stopped before to close main
application.

Here it doesn't crash when thumbnails are processed in progress manager and
when i close digiKam by window manager close button.

Which condition you use exactly to reproduce the crash as :

- how many progress task are running ?
- Which progress tasks are running ?
- which digiKam windows are open when you close application (as light table,
albumui, import tool, BQM) ?
- You press CTRL+Q to quit application ?
- It crash when you close application through window manager close button ?

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]

I tried to reproduce crash here with :

- digiKam running under GDB.
- thumb processing running in background (with multicore support)
- only AlbumGui open.

When i press CTRL+Q, digiKam stop all threads and close as expected.
There is no crash.

Gilles Caulier

2013/11/1 Gilles Caulier <[hidden email]>:

> https://bugs.kde.org/show_bug.cgi?id=326959
>
> Gilles Caulier <[hidden email]> changed:
>
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>           Component|general                     |Progress Manager
>
> --- Comment #9 from Gilles Caulier <[hidden email]> ---
> yes, the crash is due to my last changes in progress manager, from this entry :
>
> https://bugs.kde.org/show_bug.cgi?id=302810#c5
>
> Before this fix, digiKAm crash because main application is closed when progress
> tasks still running.
>
> My patch must wait than all progress tasks are stopped before to close main
> application.
>
> Here it doesn't crash when thumbnails are processed in progress manager and
> when i close digiKam by window manager close button.
>
> Which condition you use exactly to reproduce the crash as :
>
> - how many progress task are running ?
> - Which progress tasks are running ?
> - which digiKam windows are open when you close application (as light table,
> albumui, import tool, BQM) ?
> - You press CTRL+Q to quit application ?
> - It crash when you close application through window manager close button ?
>
> 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

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[eldk]

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

[hidden email] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|Progress Manager            |general

--- Comment #10 from [hidden email] ---
Hello,

I - For the  "Digikam doesn't properly close - never close" :  nothing is done,
simply start digikam wait all digikam starting task are to end then ctrl+q (or
other stuff to close) .

In this exemple :

digikam(30861)/digikam (core) Digikam::ImageScanner::commit: Scanning took 61
ms digikam(30861)/digikam (core) Digikam::ImageScanner::~ImageScanner:
Finishing took 538 ms digikam(30861)/digikam (core)
Digikam::CollectionScanner::completeHistoryScanning: items to tag (22180)
digikam(30861)/digikam (core) Digikam::ImageScanner::tagImageHistoryGraph:
Graph with 2 vertices: "{ Id: 22180 UUID: 3b6a2a... } -> { Id: 61131 UUID:
ac2c01... }" digikam(30861)/digikam (core)
Digikam::ImageScanner::tagImageHistoryGraph: Image 22180 type QFlags(0x1|0x8)
digikam(30861)/digikam (core) Digikam::ImageScanner::tagImageHistoryGraph:
Image 61131 type QFlags(0x8)

I only wait digikam finish starting and then ctrl+q.

- how many progress task are running ?
none

 - Which progress tasks are running ?
none
- which digiKam windows are open when you close application (as light table,
albumui, import tool, BQM) ?
only main windows
- You press CTRL+Q to quit application ?
yes, and try other like clic on quit in menu
- It crash when you close application through window manager close button ?
No, for this "Digikam doesn't properly close - never close", not crash.

II - I was thinking it should be in link with :
Digikam crash while scanning pictures for thumbnails maintenance which produce
this:

digikam(29444)/KEXIV2 KExiv2Iface::KExiv2::Private::printExiv2MessageHandler:
Exiv2 ( 2 ) : Directory Minolta, entry 0x0088: Data area exceeds data buffer,
ignoring it. digikam(29444)/digikam (core) Digikam::DImg::load:
"/media/DiskphotosTests/maison annoeullin/PICT0538.JPG" : JPEG file identified
digikam(29444)/KEXIV2 KExiv2Iface::KExiv2::getImageOrientation: Orientation =>
Exif.Image.Orientation => 1
 [xcb] Unknown request in queue while dequeuing
[xcb] Most likely this is a multi-threaded client and XInitThreads has not been
called
[xcb] Aborting, sorry about that. digikam: ../../src/xcb_io.c :179 :
dequeue_pending_request: l'assertion « !xcb_xlib_unknown_req_in_deq » a échoué.

- how many progress task are running ?
only one, scanning thumbnail with maintenance tool (no analyse)
 - Which progress tasks are running ?
only one : scanning thumbnail
- which digiKam windows are open when you close application (as light table,
albumui, import tool, BQM) ?
only main window
 - You press CTRL+Q to quit application ?
no, I play with reduce and resize with digikam main windows :
- It crash when you close application through window manager close button ?
no, when play with windows. When I'm trying to close digikam, it never end and
no crash.

I have two problems which are in relation I think.

Thank you,

Eric

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

--- Comment #11 from Gilles Caulier <[hidden email]> ---
None of both case are reproducible on my computer.

I suspect that problem is in another place that first expected...

Just to be sure :

- Do you compile digiKam with this cmake option :
"-DDIGIKAMSC_USE_PRIVATE_KDEGRAPHICS=on". This force digiKam to use libkipi,
libkdcraw, libkexiv2 from digiKam SC source code instead shared libs in your
system. HEre it's compiled like this. This includes all last code from
git/master
- Can you clean up whole digiKam compilation and make a new cmake config (use
bootstrap.linux script) and recompile all. You can remore "build" sub-dir to
clean-up. After that try again to reproduce the problem...

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

[eldk]

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

--- Comment #12 from [hidden email] ---
Gilles,

I'm trying now to reproduce the II.
1 - launch digikam
2 - launch in main window a maintenance thumbnail scan with no analyse
3 - wait it run for a while, then play with digikam window (reduce ... but not
close)

and try to give you a backtrace for :
[xcb] Unknown request in queue while dequeuing
[xcb] Most likely this is a multi-threaded client and XInitThreads has not been
called
[xcb] Aborting, sorry about that. digikam: ../../src/xcb_io.c :179 :
dequeue_pending_request: l'assertion « !xcb_xlib_unknown_req_in_deq » a échoué.

Thank you

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

[eldk]

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

--- Comment #13 from [hidden email] ---
- Do you compile digiKam with this cmake option
:"-DDIGIKAMSC_USE_PRIVATE_KDEGRAPHICS=on" ?
Yes and it does

HEre it's compiled like this. This includes all last code from git/master - Can
you clean up whole digiKam compilation and make a new cmake config (use
bootstrap.linux script) and recompile all. You can remore "build" sub-dir to
clean-up. After that try again to reproduce the problem...

I use to cmake config with bootstrap.local (to have a working digikam 3.5.0
stable and beta version for test).

As I'm trying to use eclipse, I've made my "own" cmake script :

#!/bin/sh

# Copyright (c) 2008-2012, Gilles Caulier, <caulier dot gilles at gmail dot
com>
# Copyright (c)      2012, Benjamin Girault <benjamin dot girault at gmail dot
com>
#
# Redistribution and use is allowed according to the terms of the BSD license.
# For details see the accompanying COPYING-CMAKE-SCRIPTS file.
#
# See README.LOCAL for more information

########################## CONFIG ######################

# Set to 1 if you want to clean that directory (this script will delete and
recreate it)
CLEANROOT=1

# Set the ccache path for faster compile cycles
CCACHE_PATH=/usr/lib/ccache/bin

# Replace path/to/your/root/directory with the directory where you want your
local digikam

DIGIKAM_INSTALL_PREFIX=$HOME/kdedev-install-digikamsoftwarecompilation #Hacked
for eclipse build (out-off-source build) - choose install directory
BUILD_PREFIX=$HOME/digikamgit2 ##ADD FOR ECLIPSE BUILD (out-off-source build) -
choose subfolder for source and build

###################### END CONFIG ######################

QT_INSTALL_PREFIX=`qmake -query "QT_INSTALL_PREFIX"`
QT_BIN=$QT_INSTALL_PREFIX/bin
export PATH=$QT_BIN:$PATH
export MAKEFILES_TYPE='Eclipse CDT4 - Unix Makefiles' #Hacked for eclipse build
export ECLIPSE_VERSION='4.3' #Hacked for eclipse build - choose eclipse version
number
export DIGIKAM_SOURCE='dkgitdigikamsoftwarecompilation' #Hacked for eclipse
build - choose source folder to build
export BUILD_ECLIPSE='builddigikamsoftwarecompilation'

export PATH=$CCACHE_PATH:$DIGIKAM_INSTALL_PREFIX/bin:$PATH
export LD_LIBRARY_PATH=$DIGIKAM_INSTALL_PREFIX/lib:$LD_LIBRARY_PATH
export PKG_CONFIG_PATH=$DIGIKAM_INSTALL_PREFIX/lib/pkgconfig:/usr/lib/pkgconfig

#export VERBOSE=1
#export CC=gcc4.4
#export CXX=g++4.4

# Manage local install dir
if [ $CLEANROOT == 1 ]
then
    rm -Rf $DIGIKAM_INSTALL_PREFIX
fi
mkdir -p $DIGIKAM_INSTALL_PREFIX

# Manage build sub-dir
cd $BUILD_PREFIX
if [ ! -d "$BUILD_ECLIPSE" ]
then
    mkdir $BUILD_ECLIPSE
fi
cd $BUILD_ECLIPSE

cmake -G "$MAKEFILES_TYPE" . \
      -DCMAKE_BUILD_TYPE=debugfull \
      -DCMAKE_INSTALL_PREFIX=$DIGIKAM_INSTALL_PREFIX/ \
      -DCMAKE_CXX_FLAGS="-pedantic -Werror=return-type" \
      -DCMAKE_C_FLAGS="-pedantic -Werror=return-type" \
      -DKDE4_BUILD_TESTS=on \
      -DDIGIKAMSC_USE_PRIVATE_KDEGRAPHICS=on \
      -DDIGIKAMSC_COMPILE_DOC=on \
      -DDIGIKAMSC_CHECKOUT_PO=off \
      -DENABLE_PRESENTATIONMODE=off\
      -DENABLE_LCMS2=on \
      -DENABLE_NEPOMUKSUPPORT=ON \
      -DCMAKE_ECLIPSE_GENERATE_SOURCE_PROJECT=ON \
      -D_ECLIPSE_VERSION=$ECLIPSE_VERSION \
      -Wno-dev \
      ../$DIGIKAM_SOURCE

and launch digikam with that script :
#!/bin/bash
#./digikam_env.sh
/home/eric/digikamgit2/builddigikamsoftwarecompilation/core/digikam/digikam
export
DIGIKAMCORE=$HOME/digikamgit2/builddigikamsoftwarecompilation/core/digikam/digikam
export
DIGIKAMLIB=$HOME/digikamgit2/builddigikamsoftwarecompilation/core/digikam/lib
export DIGIKAMINSTALL=$HOME/kdedev-install-digikamsoftwarecompilation
export KDEDIR=$DIGIKAMCORE
export KDEDIRS="$DIGIKAMCORE:$DIGIKAMLIB:$DIGIKAMINSTALL"
export KDEHOME="$HOME/.kde-dev-SC"
export LD_LIBRARY_PATH="$DIGIKAMLIB:$DIGIKAMINSTALL/lib:$LD_LIBRARY_PATH"
export LDPATH="$DIGIKAMLIB:$LD_LIBRARY_PATH"
# update KDE's system configuration cache
kbuildsycoca4
# start app
$@

for gdb I only add :
gdb $@ to the end.

First I try to reproduce then rebuild and compile with bootstrap.linux

Thank you,

Eric

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

--- Comment #14 from Gilles Caulier <[hidden email]> ---
I can reproduce the problem here, to reduce and restore main window during a
progress task.

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

Gilles Caulier <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]
          Component|general                     |Progress Manager

--- Comment #15 from Gilles Caulier <[hidden email]> ---
Marcel,

I can reproduce this crash here when digikam main window is reduced and
restored quickly while a progress task (thumbnails generator for ex) is
processed.

The trace said :

[xcb] Unknown sequence number while processing queue
[xcb] Most likely this is a multi-threaded client and XInitThreads has not been
called
[xcb] Aborting, sorry about that.
digikam: xcb_io.c :274 : poll_for_event:  l'assertion «
!xcb_xlib_threads_sequence_lost » a échoué.
KCrash: Application 'digikam' crashing...
X Error: BadImplementation (server does not implement operation) 17
  Major opcode: 20 (X_GetProperty)
  Resource id:  0x0
digikam: Fatal IO error: client killed

After investigations, i identified that my patch below is the problem :

https://bugs.kde.org/show_bug.cgi?id=302810#c5

... especially, the QEventLoop that i plugin in ProgressManager class here :

https://projects.kde.org/projects/extragear/graphics/digikam/repository/revisions/master/entry/libs/progressmanager/progressmanager.cpp#L384

I use it to wait progressitems cancellation when digiKam is closed (see bug
#302810)

Why i cannot use QEventLoop here ?
Or i use it in the wrong way ?

I suspect that ProgressManager run in a separated thread, and X11 don't like
it... But it's not the case... right ?

Gilles

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

[eldk]

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

[hidden email] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|Progress Manager            |general

--- Comment #16 from [hidden email] ---
Hello,

Reproduce it too : digikam crash when a task is process and quickly reduce and
restore digikam main window.

gdb :

digikam(338)/KDCRAW KDcrawIface::RWeaverObserver::slotThreadBusy:
RWeaverObserver: thread  1  busy
digikam(338)/digikam (core) Digikam::DImg::load: "/media/DiskphotosTests/chasse
pape moere/0025.jpg"  : JPEG file identified
######
Reduce, restore ... quickly and digikam crash with following backtrace :
#######
[xcb] Unknown request in queue while dequeuing
[xcb] Most likely this is a multi-threaded client and XInitThreads has not been
called
[xcb] Aborting, sorry about that.
digikam: ../../src/xcb_io.c :179 : dequeue_pending_request:  l'assertion «
!xcb_xlib_unknown_req_in_deq » a échoué.

Program received signal SIGABRT, Aborted.
[Switching to Thread 0xa04dfb40 (LWP 413)]
0x00132416 in __kernel_vsyscall ()
(gdb) backtrace
#0  0x00132416 in __kernel_vsyscall ()
#1  0x0350c1df in __GI_raise (sig=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:64
#2  0x0350f825 in __GI_abort () at abort.c:91
#3  0x03505085 in __assert_fail_base (fmt=0xb50ab764 "%s%s%s :%u : %s%s
l'assertion « %s » a échoué.\n%n", assertion=0x3a41fdd
"!xcb_xlib_unknown_req_in_deq", file=0x3a41fca "../../src/xcb_io.c", line=179,
    function=0x3a420a0 "dequeue_pending_request") at assert.c:94
#4  0x03505137 in __GI___assert_fail (assertion=0x3a41fdd
"!xcb_xlib_unknown_req_in_deq", file=0x3a41fca "../../src/xcb_io.c", line=179,
function=0x3a420a0 "dequeue_pending_request") at assert.c:103
#5  0x039c94c6 in ?? () from /usr/lib/i386-linux-gnu/libX11.so.6
#6  0x039ca78f in _XReply () from /usr/lib/i386-linux-gnu/libX11.so.6
#7  0x039c03c4 in XQueryTree () from /usr/lib/i386-linux-gnu/libX11.so.6
#8  0x02489203 in QWidgetPrivate::updateFrameStrut (this=0x893bb80) at
kernel/qwidget_x11.cpp:2942
#9  0x0243086e in QWidgetPrivate::frameStrut (this=0x893bb80) at
kernel/qwidget.cpp:12038
#10 0x024312e0 in QWidget::frameGeometry (this=0x88d0a28) at
kernel/qwidget.cpp:3534
#11 0x02481fb8 in QDesktopWidget::screenNumber (this=0x87d8e20,
widget=0x88d0a28) at kernel/qdesktopwidget_x11.cpp:393
#12 0x00ddf2fd in Digikam::IccSettings::Private::profileFromWindowSystem
(this=0x88d4428, widget=0x88d0a28) at
/home/eric/digikamgit2/dkgitdigikamsoftwarecompilation/core/libs/dimg/filters/icc/iccsettings.cpp:204
#13 0x00ddeefd in Digikam::IccSettings::monitorProfile (this=0x88d5c20,
widget=0x88d0a28) at
/home/eric/digikamgit2/dkgitdigikamsoftwarecompilation/core/libs/dimg/filters/icc/iccsettings.cpp:134
#14 0x00dd3f7a in Digikam::IccManager::displayProfile
(displayingWidget=0x88d0a28) at
/home/eric/digikamgit2/dkgitdigikamsoftwarecompilation/core/libs/dimg/filters/icc/iccmanager.cpp:385
#15 0x00f061cb in
Digikam::ThumbnailLoadThread::Private::createLoadingDescription
(this=0xfba0738, filePath=..., size=254, setLastDescription=true)
    at
/home/eric/digikamgit2/dkgitdigikamsoftwarecompilation/core/libs/threadimageio/thumbnailloadthread.cpp:335
#16 0x00f06944 in Digikam::ThumbnailLoadThread::find (this=0xfba0560,
filePath=..., size=256, retPixmap=0x0, emitSignal=true, detailRect=...)
    at
/home/eric/digikamgit2/dkgitdigikamsoftwarecompilation/core/libs/threadimageio/thumbnailloadthread.cpp:454
#17 0x00f06ca7 in Digikam::ThumbnailLoadThread::find (this=0xfba0560,
filePath=..., size=256) at
/home/eric/digikamgit2/dkgitdigikamsoftwarecompilation/core/libs/threadimageio/thumbnailloadthread.cpp:517
#18 0x00f06c53 in Digikam::ThumbnailLoadThread::find (this=0xfba0560,
filePath=...) at
/home/eric/digikamgit2/dkgitdigikamsoftwarecompilation/core/libs/threadimageio/thumbnailloadthread.cpp:512
#19 0x0814a814 in Digikam::ThumbsTask::run (this=0xfba0488) at
/home/eric/digikamgit2/dkgitdigikamsoftwarecompilation/core/utilities/maintenance/thumbstask.cpp:85
#20 0x00a06f33 in ThreadWeaver::JobRunHelper::runTheJob (this=0xa04df1ec,
th=0xb22b5e60, job=0xfba0488) at ../../../threadweaver/Weaver/Job.cpp:106
#21 0x00a070d3 in ThreadWeaver::Job::execute (this=0xfba0488, th=0xb22b5e60) at
../../../threadweaver/Weaver/Job.cpp:135
#22 0x00a085f5 in ThreadWeaver::JobCollectionJobRunner::execute
(this=0xfba0d58, t=0xb22b5e60) at
../../../threadweaver/Weaver/JobCollection.cpp:82
#23 0x00a065d6 in ThreadWeaver::Thread::run (this=0xb22b5e60) at
../../../threadweaver/Weaver/Thread.cpp:108
#24 0x030b8eb0 in QThreadPrivate::start (arg=0xb22b5e60) at
thread/qthread_unix.cpp:307
#25 0x04c34d4c in start_thread (arg=0xa04dfb40) at pthread_create.c:308
#26 0x035ccdde in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Eric

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

[eldk]

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

--- Comment #17 from [hidden email] ---
Created attachment 83265
  --> https://bugs.kde.org/attachment.cgi?id=83265&action=edit
bootstrap-eclipse.local for building digikam in out-of-source to local dev dir
for eclipse kepler C++  4.3

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

[eldk]

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

--- Comment #18 from [hidden email] ---
Created attachment 83266
  --> https://bugs.kde.org/attachment.cgi?id=83266&action=edit
starting script for launching digikam in local dev folder for testing,
debugging ..

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