Bug 266248

Summary:	Duplicate search never finishes
Product:	[Applications] digikam	Reporter:	Matthieu Pupat <kde>
Component:	Searches-Similarity	Assignee:	Digikam Developers <digikam-bugs-null>
Status:	RESOLVED FIXED
Severity:	normal	CC:	caulier.gilles
Priority:	NOR
Version:	1.7.0
Target Milestone:	---
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:		Version Fixed In:	2.5.0
Sentry Crash Report:

Description Matthieu Pupat 2011-02-14 01:05:27 UTC

Version:           1.7.0 (using KDE 4.5.5) 
OS:                Linux

Sometimes, duplicate serach will be stuck at 100%. No duplicates shows up (although there are some).

I was able to reproduce this when launching digikam from a terminal. Here is the output:

QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is still in use, all queries will cease to work.
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
QMetaObject::invokeMethod: No such method KUniqueApplication::loadCommandLineOptionsForNewInstance()
kbuildsycoca4 running...
Time elapsed: 303 ms
Model: Time elapsed: 436 ms
Time elapsed: 4 ms
Model: Time elapsed: 23 ms
TextureColorizer: Time elapsed: 40 ms
Time elapsed: 5 ms
Model: Time elapsed: 20 ms
Time elapsed: 4 ms
Model: Time elapsed: 18 ms
Time elapsed: 3 ms
Model: Time elapsed: 18 ms
digikam(4495)/digikam (core) Digikam::StateSavingObjectPriv::getGroupFromObjectName: Object name for  Digikam::ImagePropertiesSideBarDB(0x7483490)  is empty. Returning the default config group 
digikam(4495)/digikam (core) Digikam::StateSavingObjectPriv::getGroupFromObjectName: Object name for  Digikam::ImagePropertiesSideBarDB(0x776a050)  is empty. Returning the default config group 
QDBusObjectPath: invalid path ""
QMetaObject::invokeMethod: No such method KUniqueApplication::loadCommandLineOptionsForNewInstance()
QSqlDatabasePrivate::removeDatabase: connection 'digikamDatabase-37276816' is still in use, all queries will cease to work.
klauncher(4515)/kio (KLauncher): SlavePool: No communication with slave. 

QSocketNotifier: Invalid socket 12 and type 'Read', disabling...
klauncher(4515)/kio (KLauncher): SlavePool: No communication with slave. 

klauncher(4515)/kio (KLauncher): SlavePool: No communication with slave. 

klauncher(4515)/kio (KLauncher): SlavePool: No communication with slave. 

QSqlDatabasePrivate::removeDatabase: connection 'digikamDatabase-37276816' is still in use, all queries will cease to work.
QSocketNotifier: Invalid socket 12 and type 'Read', disabling...
klauncher(4515)/kio (KLauncher): SlavePool: No communication with slave. 

klauncher(4515)/kio (KLauncher): SlavePool: No communication with slave. 

klauncher(4515)/kio (KLauncher): SlavePool: No communication with slave. 

klauncher(4515)/kio (KLauncher): SlavePool: No communication with slave. 

klauncher(4515)/kio (KLauncher): SlavePool: No communication with slave. 

klauncher(4515)/kio (KLauncher): SlavePool: No communication with slave. 

klauncher(4515)/kio (KLauncher): SlavePool: No communication with slave. 

klauncher(4515)/kio (KLauncher): SlavePool: No communication with slave. 

klauncher(4515)/kio (KLauncher): SlavePool: No communication with slave. 

klauncher(4515)/kio (KLauncher): SlavePool: No communication with slave. 

*** glibc detected *** kdeinit4: kio_digikamsearch [kdeinit] digikamsearch local:/tmp/ksocket-matthieu/klauncherMT4515.slave-socket local:/tmp/ksocket-matthieu/digikamfE4495.slave-socket: corrupted double-linked list: 0x00000000026e5590 ***


Reproducible: Sometimes

Steps to Reproduce:
SEarch for duplicate pictures

Actual Results:  
Stuck at 100% with no results displayed (cancel button is still active)

Expected Results:  
Search completes and displays results

Comment 1 caulier.gilles 2011-02-14 07:29:11 UTC

Dupplicate search are delegate to separate process (KIOSlave, which crash in you case)

Check your system... There is a binary compatibility issue...

Gilles Caulier

Comment 2 Matthieu Pupat 2011-02-14 14:27:15 UTC

Sorry I have no clue where to search. Do you have any hint on what to do?

OTOH, I moved to MySQL and cannot reproduce the issue anymore.

Comment 3 Andi Clemens 2011-04-30 11:07:06 UTC

So this bug can be closed?

Comment 4 Matthieu Pupat 2011-05-02 15:52:55 UTC

Not sure. I cannot reproduce it anymore now that I am using MySQL but it might still be there if you don't.