Bug 454739 - Find New Items is stuck at 0%
Summary: Find New Items is stuck at 0%
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Maintenance-Engine (show other bugs)
Version: 7.7.0
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-06-02 10:59 UTC by Steve Franks
Modified: 2022-11-27 16:51 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 8.0.0
Sentry Crash Report:


Attachments
Debugview log (4.09 KB, application/zip)
2022-06-02 10:59 UTC, Steve Franks
Details
attachment-32615-0.html (913 bytes, text/html)
2022-06-02 20:15 UTC, Steve Franks
Details
attachment-873-0.html (1.35 KB, text/html)
2022-06-02 20:21 UTC, Steve Franks
Details
attachment-31131-0.html (399 bytes, text/html)
2022-06-04 14:57 UTC, Steve Franks
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Steve Franks 2022-06-02 10:59:50 UTC
Created attachment 149399 [details]
Debugview log

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
Digikam Find new items isn't finding new images. The progress bar remains at zero and debugview shows no activity.
Other functions appear to be working.

STEPS TO REPRODUCE
1.  Start digikam
2.  Select Tools Maintenance
3.  Chose a folder with sub-folders and Find New Items
4. Click OK

OBSERVED RESULT
The Maintenance dialog appears when switching tasks, but is not selectable. The progress bar doesn't move.

EXPECTED RESULT
Progress bar moves rapidly to 100% and new items appear in the items with no tags collection.

SOFTWARE/OS VERSIONS
Windows:  11
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Digikam appeared to work without problems yesterday. No updates have been made to the laptop's software since.
Comment 1 Maik Qualmann 2022-06-02 11:24:06 UTC
The log doesn't show any problems at first, unfortunately it's not complete at the moment. Nothing is recorded after a certain number of debug outputs. The cause is currently unknown. So we can't see possible error messages at the moment. I don't see anything suspicious other than McAfee.

Maik
Comment 2 Maik Qualmann 2022-06-02 11:28:44 UTC
Do I understand correctly that the maintenance dialog does not close when you press OK?

Maik
Comment 3 Maik Qualmann 2022-06-02 11:35:52 UTC
We have a similar problem here, but it is also not to be reproduced: Bug 453971

Maik
Comment 4 Maik Qualmann 2022-06-02 11:53:05 UTC
The reason for the interruption of the debug output is the Generic_PicFlowView_Plugin.dll.
Please delete the file and create a new debug output.

C:\Program Files\digiKam\plugins\digikam\generic\Generic_PicFlowView_Plugin.dll

Maik
Comment 5 Steve Franks 2022-06-02 20:15:31 UTC
Created attachment 149419 [details]
attachment-32615-0.html

It appears to close, but when I alt+tab it appears briefly.
Steve

On Thu, 2 Jun 2022 at 12:28, Maik Qualmann <bugzilla_noreply@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=454739
>
> --- Comment #2 from Maik Qualmann <metzpinguin@gmail.com> ---
> Do I understand correctly that the maintenance dialog does not close when
> you
> press OK?
>
> Maik
>
> --
> You are receiving this mail because:
> You reported the bug.
Comment 6 Steve Franks 2022-06-02 20:21:26 UTC
Created attachment 149420 [details]
attachment-873-0.html

I allowed digikam to run for about 10 minutes, but nothing new was added to
the debugview output.
I circumvented the problem by restoring the database files from Tuesday.
When I have time I will restore the database from today and delete
Generic_PicFlowView_Plugin.dll.
I will let you know what happens.
Regards
Steve

On Thu, 2 Jun 2022 at 12:53, Maik Qualmann <bugzilla_noreply@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=454739
>
> --- Comment #4 from Maik Qualmann <metzpinguin@gmail.com> ---
> The reason for the interruption of the debug output is the
> Generic_PicFlowView_Plugin.dll.
> Please delete the file and create a new debug output.
>
> C:\Program
> Files\digiKam\plugins\digikam\generic\Generic_PicFlowView_Plugin.dll
>
> Maik
>
> --
> You are receiving this mail because:
> You reported the bug.
Comment 7 Maik Qualmann 2022-06-02 20:49:32 UTC
Git commit a4f8e09ce3b0080c16a0bdcca0ff29923ff46682 by Maik Qualmann.
Committed on 02/06/2022 at 20:47.
Pushed by mqualmann into branch 'qt5-maintenance'.

ignore Flow View plugin in DPlugin Loader
The plugin breaks digiKam's debug handling
by installing its own Qt debug handler.
The external author must change this.
Related: bug 453971

M  +1    -0    core/libs/dplugins/setup/dpluginloader_p.cpp

https://invent.kde.org/graphics/digikam/commit/a4f8e09ce3b0080c16a0bdcca0ff29923ff46682
Comment 8 Steve Franks 2022-06-04 14:57:16 UTC
Created attachment 149455 [details]
attachment-31131-0.html

>
> My laptop does not have C:\Program
> Files\digiKam\plugins\digikam\generic\Generic_PicFlowView_Plugin.dll
>
 The only file in that folder is qtuiotouchplugin.dll
Steve
Comment 9 Maik Qualmann 2022-06-04 18:18:37 UTC
C:\Program Files\digiKam\plugins\digikam\generic\Generic_PicFlowView_Plugin.dll

The path is correct, you looked under this path:

C:\Program Files\digiKam\plugins\generic\

You forgot the "digikam" behind plugins.

Maik
Comment 10 Maik Qualmann 2022-06-18 20:15:46 UTC
Git commit b323c6dba8133023863f7a6a4a305e6494c8aa9e by Maik Qualmann.
Committed on 18/06/2022 at 20:14.
Pushed by mqualmann into branch 'master'.

use a simple folder counter progress for the partial scan
Connects only to the required signals from the ScanController.
FIXED-IN: 8.0.0

M  +2    -1    NEWS
M  +29   -24   core/utilities/maintenance/newitemsfinder.cpp
M  +4    -0    core/utilities/maintenance/newitemsfinder.h

https://invent.kde.org/graphics/digikam/commit/b323c6dba8133023863f7a6a4a305e6494c8aa9e
Comment 11 caulier.gilles 2022-11-27 09:13:05 UTC
To Maik, comment #7 : where is located the own Qt debug handler in plugin source code.

I cannot find it in main git module and sub-module used by the project.

https://github.com/cathaysia/digikamflowplugin
https://github.com/cathaysia/QtFlowLayout

Gilles
Comment 12 Maik Qualmann 2022-11-27 11:59:12 UTC
When the plugin is loaded, this log handler takes over and debug messages from digiKam are no longer printed.

https://github.com/cathaysia/digikamflowplugin/blob/master/src/plugflow.cpp#L26

Maik
Comment 13 Maik Qualmann 2022-11-27 12:08:44 UTC
Here the log handler is installed:

https://github.com/cathaysia/digikamflowplugin/blob/master/src/plugflow.cpp#L79

What is this for at this point?

https://github.com/cathaysia/digikamflowplugin/blob/master/src/plugflow.cpp#L97

Maik
Comment 14 caulier.gilles 2022-11-27 16:48:27 UTC
Git commit ffd179f90f4c4b1294828021626554796bee010f by Gilles Caulier.
Committed on 27/11/2022 at 16:46.
Pushed by cgilles into branch 'qt5-maintenance'.

add patch for digiKam debug space support in FlowView Plugin
Related: bug 453971

M  +2    -2    project/bundles/3rdparty/ext_flowview/CMakeLists.txt
A  +155  -0    project/bundles/3rdparty/ext_flowview/fix-c++-qdebug.patch
D  +0    -12   project/bundles/3rdparty/ext_flowview/fix-c++-rules.patch

https://invent.kde.org/graphics/digikam/commit/ffd179f90f4c4b1294828021626554796bee010f
Comment 15 caulier.gilles 2022-11-27 16:51:35 UTC
Git commit 5b2543fa4d6d5d872cedf7b3b12b4142912c6fdb by Gilles Caulier.
Committed on 27/11/2022 at 16:50.
Pushed by cgilles into branch 'qt5-maintenance'.

re-enable FlowView plugin
Related: bug 453971

M  +0    -1    core/libs/dplugins/setup/dpluginloader_p.cpp

https://invent.kde.org/graphics/digikam/commit/5b2543fa4d6d5d872cedf7b3b12b4142912c6fdb