Opening digikam5 from the command-line to see output. When running maintenance on a large number of albums, digikam seems to "hang" either at: digikam.general: Using 1 CPU core to run threads or digikam.general: Creating a fingerprints task for generating fingerprints Last time this took 00:36:35 for 2635 albums. There is no feedback on the command-line and no visual feedback (progress bar) in the GUI, also there is no HDD activity nor CPU activity. I realize digikam is probably doing something, but there is no indication of it. Is there a cli switch to see more output? My suggestion would be to include whatever digikam does to initialize maintenance within the progress bar or as a separate task on the progress bar before the intended maintenance-to-be-performed's task. Too, digikam is sluggish and unresponsive during this initialization process.
Can you describe step by step what you are doing (e.g. what options you choose in the maintenance dialogue).
For this specific instance, only fingerprints was selected and scan for changed or non-cataloged items (faster). Which reminds me of a separate bug, if more than one operation (find new, thumbnails, fingerprints, sync meta, etc) with many albums, then there is a sigfault crash when going from one operation to the next. I am not certain of the number of albums, probably 200+ or so. If there is not a bug report about this already, I will figure out more specifics and create one when I have more time. With a quick search I could not find any bugs, do you know of any by chance?
I can't think of anything from the top of my head. If you can reproduce it while running gdb to get a backtrace, just open a new issue. If it turns out to be a dupe, that wouldn't be a problem.