Version: 0.10.0-beta3 (using 4.1.2 (KDE 4.1.1 (KDE 4.1 >= 20080828)) "release 52.1", KDE:KDE4:Factory:Desktop / openSUSE_11.0) Compiler: gcc OS: Linux (i686) release 2.6.25.16-0.1-default Starting Digikam and pushing "Quit" from the "Album" menu quits Digikam only visually, the processes initiated by Digikam remain hang. If I start Digikam from a terminal and push "Quit" there's no finishing to see. `ps auxw|grep digikam` gives me an output like this: --- rene 19408 5.0 2.4 201824 49900 ? Sl 11:53 0:06 /usr/bin/digikam -caption digiKam -icon digikam rene 19436 0.2 0.6 67080 13060 ? S 11:53 0:00 kdeinit4: kio_digikamd up rene 19437 0.2 0.6 66860 12940 ? S 11:53 0:00 kdeinit4: kio_digikama up --- not changing even after a few minutes.
'killall digikam' quits the first of the above processes '/usr/bin/digikam', only, the two KIO processes remain hanging. Seems to be a synchronizing problem and hang in the KIO process.
... update: after several minutes the kio_digikamd process finished now, too. Is the solution to wait for this? Are these processes important, what happens on a shutdown meanwhile killing the kio_digikamd processes before they finish in their "natural" way?
Yep, happens for me also.
I noticed that before, too. But now it seems to be solved. For me it happened most of the time when I switched very fast between albums so that the thumbnail generation went crazy. Also "find duplicates" was not stopped properly when closing digiKam while it was running. There was no cancel action, but I have added this now. Maybe newest SVN will solve the problems? Bureports that might be related to this: bug 167320 bug 172738 Andi
KIO slave processes are started and stopped by kdelibs. I think it is normal behavior that they are kept running for a certain time as part of a process pool and stopped later. It would be a bug if they were running and consuming CPU, but I dont think this is the case.