Digikam startup hangs

[Thomas Hummel-2]

Hello,

I'm running digikam-0.9.3 on kde-3.5.8 on FreeBSD 7.0-RC1.
If I launch digikam via

  truss digikam (which is like strace digikam on linux), it works

If I launch digikam the first time I start X, it works.
But if I quit digikam and launch it again, I get only the splash screen and
digikam stop doing anything after "Found dcraw version: 8.81".

ps says digikam is in Idle state and top says it is in the sbwait state.
gam_server (comming from the gamin-0.1.9 port) is also in the sbwait state.
If I kill gam_server, digikam resumes its normal operations.

So may there be some kind of dead lock issue with these two ?
What can I do, since gamin is a digikam dependency ?

Thanks.

--
Thomas Hummel
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Gilles Caulier-4]

2008/1/9, Thomas Hummel <[hidden email]>:

Hello,

I'm running digikam-0.9.3 on kde-3.5.8 on FreeBSD 7.0-RC1.
If I launch digikam via

  truss digikam (which is like strace digikam on linux), it works

If I launch digikam the first time I start X, it works.
But if I quit digikam and launch it again, I get only the splash screen and
digikam stop doing anything after "Found dcraw version: 8.81".

ps says digikam is in Idle state and top says it is in the sbwait state.
gam_server (comming from the gamin-0.1.9 port) is also in the sbwait state.
If I kill gam_server, digikam resumes its normal operations.

So may there be some kind of dead lock issue with these two ?
What can I do, since gamin is a digikam dependency ?

not directly, but digiKam use KDirWatch  to handle change of directories contents to update automatically database information about image files and albums from root collection directory.

If you look at KDirWatch class doc :

http://api.kde.org/3.5-api/kdelibs-apidocs/kio/kio/html/classKDirWatch.html

...you can read KDirWatch use :

"The implementation uses the FAM service when available; if FAM is not available, the DNOTIFY functionality is used on LINUX. As a last resort, a regular polling for change of modification times is done; the polling interval is a global config option: DirWatch/PollInterval and DirWatch/NFSPollInterval for NFS mounted directories."

If something is wrong with FAM FreeBSD port, this can be have side effect on KDirWatch, and of course on digiKam...

Best

Gilles Caulier

Thanks.

--
Thomas Hummel
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Thomas Hummel-2]

On Wed, Jan 09, 2008 at 10:40:48AM +0100, Gilles Caulier wrote:

> not directly, but digiKam use KDirWatch  to handle change of directories
> contents to update automatically database information about image files and
> albums from root collection directory.
>
> If you look at KDirWatch class doc :
>
> http://api.kde.org/3.5-api/kdelibs-apidocs/kio/kio/html/classKDirWatch.html
>
> ...you can read KDirWatch use :
>
> "The implementation uses the FAM service when available; if FAM is not
> available, the DNOTIFY functionality is used on LINUX. As a last resort, a
> regular polling for change of modification times is done; the polling
> interval is a global config option: DirWatch/PollInterval and
> DirWatch/NFSPollInterval for NFS mounted directories."

Actually, FAM is provided by gamin on my system. What's weird is (I can
reproduce it), I can launch and quit (immediatly) digikam twice. Then, the
third time, the hang problem occur...

--
Thomas Hummel
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Thomas Hummel-2]

On Wed, Jan 09, 2008 at 02:24:16PM +0100, Thomas Hummel wrote:

I forgot to mention my home directory is on a zfs file system. As a matter of
fact, lauching digikam after cd'ing into /tmp (which is ufs) seems to work each
time (although my picture collection is still on my zfs home), although I don't
see any socket in it... But launching it from my home dir occasionnaly cause
the problem.

Could it be an incompatibility of gamin/fam, digikam or some kde component with
zfs ?

--
Thomas Hummel
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Gilles Caulier-4]

2008/1/9, Thomas Hummel <[hidden email]>:

On Wed, Jan 09, 2008 at 02:24:16PM +0100, Thomas Hummel wrote:

I forgot to mention my home directory is on a zfs file system. As a matter of
fact, lauching digikam after cd'ing into /tmp (which is ufs) seems to work each
time (although my picture collection is still on my zfs home), although I don't
see any socket in it... But launching it from my home dir occasionnaly cause
the problem.

Could it be an incompatibility of gamin/fam, digikam or some kde component with
zfs ?

I don't know. but it's certainly more relevant of a low level component as gamin/fam than kde/digikam

Gilles

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users