[digikam] [Bug 387946] find new items stalls at 90%

[bugzilla_noreply]

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

caulier.gil...@gmail.com changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED
   Version Fixed In||7.5.0

--- Comment #12 from caulier.gil...@gmail.com ---
o feedback. not reproducible with 7.5.0. Closed

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 387946] find new items stalls at 90%

[bugzilla_noreply]

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

--- Comment #11 from caulier.gil...@gmail.com ---
Jasper,

Stable digiKam 7.4.0 is published. Please check if problem is reproducible.

https://www.digikam.org/download/

Thanks in advance

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 387946] find new items stalls at 90%

[bugzilla_noreply]

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

--- Comment #10 from caulier.gil...@gmail.com ---
digiKam 7.2.0 official release is published with more than 360 files closed
from bugzilla:

https://www.digikam.org/news/2021-03-22-7.2.0_release_announcement/

Can you reproduce the dysfunction with this version ?

Thanks in advance for your feedback

Gilles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 387946] find new items stalls at 90%

[bugzilla_noreply]

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

--- Comment #9 from caulier.gil...@gmail.com ---
Jasper,

do you seen my previous comment ?

Gilles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 387946] find new items stalls at 90%

[bugzilla_noreply]

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

--- Comment #8 from caulier.gil...@gmail.com ---
Good news,

After 2 weeks of works, the pre-release 6.1.0 bundles are now reconstructed
from scratch with:

- All OpenCV options for CUDA, OPenMP, and OPenCL disabled to prevent crashes
in face management.
- A large upgrade of Qt5 from 5.9.7 to 5.11.3.
- An upgrade to KF5 5.55.
- An upgrade to Ffmpeg 3.3.9
- The fontconfig/freetype integration in the bundle to reduce system
dependencies

Files can be downloaded here :

https://files.kde.org/digikam/

Please test and report.

Gilles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 387946] find new items stalls at 90%

[bugzilla_noreply]

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

--- Comment #7 from caulier.gil...@gmail.com ---
Can you reproduce the dysfunction using the last digiKam 6.0.0-beta3 just
released ?

https://www.digikam.org/news/2018-12-30-6.0.0-beta3_release_announcement/

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 387946] find new items stalls at 90%

[bugzilla_noreply]

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

--- Comment #6 from caulier.gil...@gmail.com ---
Can you reproduce the dysfunction using digiKam 6.0.0 pre-release bundle
available here :

https://files.kde.org/digikam/

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 387946] find new items stalls at 90%

[Jasper]

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

--- Comment #5 from Jasper  ---
Great that there are debugging symbols in the appimage. I was basing this
assumption off GDB outputting

Reading symbols from digikam-5.8.0-20171212T132305-x86-64.appimage...(no
debugging symbols found)...done.

But I had started the appimage from gdb i.e wrongly.

Running the appimage 'find new files' halts at 21%. Note that this is without
the problematic directory such that digikam 5.6 installed from ubuntu was able
to complete the 'find new images' without a problem.
I can still not see any reference to the image that may be causing the
lockup/halt if this is indeed the fault.


./digikam-5.8.0-20171217T160920-x86-64.appimage debug  --config
~/digikam.config
-- digiKam AppImage Bundle
-- Use 'help' as CLI argument to know all available options
Starting digiKam into GDB...
Use 'bt' command on debugger prompt to get a crash backtrace.
Use 'q' command to quit debugger session.
GNU gdb (Ubuntu 8.0.1-0ubuntu1) 8.0.1
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from digikam...done.
Starting program: /tmp/.mount_jCx752/usr/bin/digikam --config
/home/jasper/digikam.config
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe63ea700 (LWP 25731)]
[New Thread 0x7fffe598b700 (LWP 25732)]
[New Thread 0x7fffd700 (LWP 25734)]
[New Thread 0x7fffde44b700 (LWP 25735)]
[Thread 0x7fffde44b700 (LWP 25735) exited]
[New Thread 0x7fffde44b700 (LWP 25736)]
[Thread 0x7fffde44b700 (LWP 25736) exited]
[New Thread 0x7fffde44b700 (LWP 25737)]
[New Thread 0x7fffd2f3f700 (LWP 25738)]
[New Thread 0x7fffd273e700 (LWP 25739)]
[New Thread 0x7fffd1f3d700 (LWP 25740)]
[New Thread 0x7fffd173c700 (LWP 25741)]
[New Thread 0x7fffd0f3b700 (LWP 25742)]
[New Thread 0x7fffb7fff700 (LWP 25743)]
[New Thread 0x7fffb77fe700 (LWP 25744)]
[New Thread 0x7fffb6ffd700 (LWP 25745)]
[New Thread 0x7fffb67fc700 (LWP 25746)]
[New Thread 0x7fffb5ffb700 (LWP 25747)]
[New Thread 0x7fffb57fa700 (LWP 25748)]
[New Thread 0x7fffb4ff9700 (LWP 25749)]
[New Thread 0x7fff97fff700 (LWP 25750)]
[New Thread 0x7fff577fc700 (LWP 25753)]
[New Thread 0x7fff56ffb700 (LWP 25754)]
[New Thread 0x7fff567fa700 (LWP 25755)]
QtAV 1.12.0(Jul 20 2017, 17:39:32)
Multimedia framework base on Qt and FFmpeg.
Distributed under the terms of LGPLv2.1 or later.
Shanghai University->S3 Graphics->Deepin->PPTV, Shanghai, China Copyright (C)
2012-2016 Wang Bin (aka. Lucas Wang) wbse...@gmail.com
Donate: http://qtav.org/donate.html
Source: https://github.com/wang-bin/QtAV
Home page: http://qtav.org
capi::version: 0.6.0
[New Thread 0x7fffd0301700 (LWP 25756)]
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for 4294967295,
skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for 4294967295,
skipping unlock
[Thread 0x7fffd0301700 (LWP 25756) exited]
[New Thread 0x7fff55ff9700 (LWP 25757)]
[Thread 0x7fff55ff9700 (LWP 25757) exited]
[New Thread 0x7fff55ff9700 (LWP 25758)]
[Thread 0x7fff55ff9700 (LWP 25758) exited]
[New Thread 0x7fff55ff9700 (LWP 25759)]
[New Thread 0x7fffd0280700 (LWP 25760)]
[New Thread 0x7fff54fe0700 (LWP 25761)]
[New Thread 0x7fff3bffe700 (LWP 25762)]
[New Thread 0x7fff3b7fd700 (LWP 25763)]
[New Thread 0x7fff3affc700 (LWP 25764)]
[New Thread 0x7fff3a7fb700 (LWP 25765)]
[New Thread 0x7fff39ffa700 (LWP 25766)]
[New Thread 0x7fff397f9700 (LWP 25767)]
QFSFileEngine::open: No file name specified
[New Thread 0x7fff1bfff700 (LWP 25769)]
[New Thread 0x7fff1b7fe700 (LWP 25770)]
[New Thread 0x7fff1affd700 (LWP 25771)]
[New Thread 0x7fff1a7fc700 (LWP 25772)]
[New Thread 0x7fff19ffb700 (LWP 25773)]
[New Thread 0x7fff197fa700 (LWP 25774)]
[New Thread 0x7fff18ff9700 (LWP 25775)]
[New Thread 0x7fff0bfff700 (LWP 25776)]
[New Thread 0x7fff0b7fe700 (LWP 25777)]
[New Thread 0x7fff0affd700 (LWP 25778)]
[New Thread 0x7fff0a7fc700 (LWP 25779)]
[New Thread 0x7fff09ffb700 (LWP 25780)]
[New Thread 0x7fff097fa700 (LWP 25781)]
[New Thread 0x7fff08ff9700 (LWP 25782)]
[New Thread 0x7fff087f8700 (LWP 25783)]
[New Thread 0x7fff07ff7700 (LWP 25784)]
[New Thread 0x7fff077f6700 (LWP 25785)]
[New Thread 0x7fff06ff5700 (LWP 2578

[digikam] [Bug 387946] find new items stalls at 90%

[bugzilla_noreply]

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

--- Comment #4 from caulier.gil...@gmail.com ---
"and neither the Ubuntu package or the appimage have debugging symbols."

==> The AppImage bundle that we provide HAS debug symbols. I'm sure. I build
myself the bundles, so i know exactly how the files are compiled. This is not
the case for Ubuntu stuff where we have no vision about the packaging. This is
why AppImage is so far better than native package. It include last code and we
control all the settings.

Use the current 5.8.0 pre release bundle just compiled yesterday evening. The
files are here :

https://files.kde.org/digikam/

And run it from a console with "debug" argument as explained here :

https://www.digikam.org/contribute/

Voilà...

Gilles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 387946] find new items stalls at 90%

[Jasper]

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

--- Comment #3 from Jasper  ---
Please note the bug was persistent on a Digikam database that had been stable
for a very long time, and only had this years images added to it.

I tried moving all the directories on the NFS server side away, adding them one
at a time, starting digikam, letting it scan to completion, quitting digikam,
moving one more directory (one directory per year) etc.

In this way I found that the digikam scanning was failing on some very old
images, very large 20x30x300dpi TIFF's which would have been scanned a long
time ago. 

I have not found the exact file yet.
I am not sure whether this makes the current bug _solved_/_resolved_/whatever.
It would have been very useful to have some more verbose logging to know which
file it is failing on. 
Amazingly there is a lot of bitrot, with more corrupt images than I would
expect, yet digikam handled these fine.

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 387946] find new items stalls at 90%

[Jasper]

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

--- Comment #2 from Jasper  ---
Nothing on the console seems that useful, and neither the Ubuntu package or the
appimage have debugging symbols.

THe best I can get you is running in GDB up to the point I kill it (after
freezing at 90%).
Please note that there is _nothing_ emitted in the console at the point at
which digikam scan reaches 90%. So the last output are some time before then.
THe scan is very fast up to this point 8)

Starting program: /usr/bin/digikam 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffbd9f6700 (LWP 20935)]
[New Thread 0x7fffb36a2700 (LWP 20936)]
[New Thread 0x7fffb2ea1700 (LWP 20937)]
[New Thread 0x7fffb26a0700 (LWP 20938)]
[New Thread 0x7fffb0fdf700 (LWP 20939)]
[New Thread 0x7fffa1fa2700 (LWP 20941)]
[New Thread 0x7fffa17a1700 (LWP 20942)]
[Thread 0x7fffa17a1700 (LWP 20942) exited]
[New Thread 0x7fffa17a1700 (LWP 20956)]
[New Thread 0x7fff965cb700 (LWP 20957)]
[New Thread 0x7fff95b82700 (LWP 20958)]
[New Thread 0x7fff94ce3700 (LWP 20959)]
[New Thread 0x7fff4fffd700 (LWP 20960)]
[New Thread 0x7fff4f7fc700 (LWP 20961)]
[New Thread 0x7fff4effb700 (LWP 20962)]
QFSFileEngine::open: No file name specified
[New Thread 0x7fff4d887700 (LWP 20965)]
QFSFileEngine::open: No file name specified
[New Thread 0x7fff4cb84700 (LWP 20968)]
[New Thread 0x7fff2700 (LWP 20969)]
[New Thread 0x7fff2f7fe700 (LWP 20970)]
[New Thread 0x7fff4cb84700 (LWP 20971)]
[Thread 0x7fff4cb84700 (LWP 20968) exited]
[Thread 0x7fff2f7fe700 (LWP 20970) exited]
[New Thread 0x7fff2f7fe700 (LWP 20972)]
QFSFileEngine::open: No file name specified
QFSFileEngine::open: No file name specified
[Thread 0x7fff2700 (LWP 20969) exited]
[Thread 0x7fff2f7fe700 (LWP 20972) exited]
[Thread 0x7fff4d887700 (LWP 20965) exited]
[Thread 0x7fff4cb84700 (LWP 20971) exited]
^C
Thread 1 "digikam" received signal SIGINT, Interrupt.
0x73472901 in __GI___poll (fds=0x55df1dc0, nfds=11, timeout=5636)
at ../sysdeps/unix/sysv/linux/poll.c:29
29  ../sysdeps/unix/sysv/linux/poll.c: No such file or directory.
(gdb) bt
#0  0x73472901 in __GI___poll (fds=0x55df1dc0, nfds=11,
timeout=5636) at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7fffe97db169 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fffe97db27c in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7439d47f in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x74342e3a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x774a8056 in
Digikam::ScanController::completeCollectionScanCore(bool, bool) () at
/usr/lib/digikam/libdigikamgui.so.5.6.0
#6  0x7766f6e8 in Digikam::NewItemsFinder::slotStart() () at
/usr/lib/digikam/libdigikamgui.so.5.6.0
#7  0x74374452 in QObject::event(QEvent*) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x750bf46c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#9  0x750c6d34 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#10 0x74344de8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x7434755d in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x7439de53 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x7fffe97dafb7 in g_main_context_dispatch () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#14 0x7fffe97db1f0 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#15 0x7fffe97db27c in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#16 0x7439d47f in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x74342e3a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x7434bda4 in QCoreApplication::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#19 0x9fd0 in  ()
#20 0x7338b1c1 in __libc_start_main (main=
0x9360, argc=1, argv=0x7fffde68, init=,
fini=, rtld_fini=, stack_end=0x7fffde58)
at ../csu/libc-start.c:308
#21 0xb06a in _start ()

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 387946] find new items stalls at 90%

[bugzilla_noreply]

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

caulier.gil...@gmail.com changed:

   What|Removed |Added

 CC||caulier.gil...@gmail.com

--- Comment #1 from caulier.gil...@gmail.com ---
What do you seen as debug traces when you run digiKam from a console

-- 
You are receiving this mail because:
You are watching all bug changes.