Version: (using KDE 3.5.9) Installed from: Mandriva RPMs OS: Linux i have compile digikam 0.9.4 beta 3 when digikam is start and when i do nothing in it. the process gam_server use more than 40% CPU. when i close digikam gam_server stop using CPU.
digikam do not use gam stuff directly. it's KDE Library... Gilles Caulier
Ok but this bug arrive just when digikam run. note : I have the same sort off bug white NTFS-3G driver when my photos was on an NTFS partition. NTFS-3G use More than 40% CPU when digikam RUN. i have the NTFS bug with Digikam mandriva RPM 0.9.2, 0.9.3, and compiled version 9.4 beta3 i have the gam_server bug only with the 0.9.4 beta3 compiled vertion.
Sylvain, Try to use another file system to test. here i use reiserfs without any problem. Gilles
I need to put my photos on an NTFS or FAT32 partition to développe Raw of my D300 under Nikon capture NX at the beginin i use an NTFS partion with Digikam 0.9.2 to solve the problème i format my partition in FAT32 and it work whell until i compile digikam 0.9.4 beta3 i have no problème on this partion with other applications. so it is certainly à digikam bug on request system files.
i try with the SVN 0.9.4 beta4 version and i have always the same prolème :-(
i try with the SVN 0.9.4 beta5 and i have always the same problème what digikam doing in background to use gam_server when i do nothing in digikam ?
Sylvain, digiKam scan albums to find new/deleted items and records scanning results to database. digiKam code do not use gam_server... So i don't know why you have a loop at this time. Are you tried another FS than M$ stuff to host your photos ? just to check... Gilles Caulier
i try with an EXT3 partition and i dont see CPU overload but my partition is too small to test with all my photos. if i can i only use EXt3 but for use nikon NX i need an NTFS or FAT32 partition. and with this two FS digikam start cpu overload. perhaps digikam do a loop to scan new images in folder ?
Sylvain, There is no reason to have a loop with M$ FS and not with Linux native one. The FS is driven in background, by the kernel. Are you Syslog deamon running on your system ? If yes, please check log file as /var/log/messages when you start digiKam with a M$ FS. (tail -f /var/log/messages running as root in a separate console is enough) Gilles Caulier
i test with ntfs and fat32 and no messages in /var/log/message when i run digikam
Please, look into http://bugs.kde.org/show_bug.cgi?id=162535 ...and check if way used by Thomas can solve your problem... Gilles Caulier
I haven't got fam deamon on my mandriva 2008 spring. but i download & install "inotify-tools" and "dnotify" i download the last svn vertion. i comment the tree line in albummanger.cpp containing "d->dirWatch->addDir" i compile digikam and now digikam start as speed as road Runner (bip-bip). every thing work. the Marcel Wiesweg solution explaine for Thomas Eschenbacher http://bugs.kde.org/show_bug.cgi?id=162535 solve my two bug i have with digikam CPU usage over 40% : http://bugs.kde.org/show_bug.cgi?id=161093 and digikam don't start : https://bugs.kde.org/show_bug.cgi?id=156146
Sylvain, Can you test using Mandriva 2008.1 or 2009.0 with digiKam 0.9.4 final release ? Also, it will be fine to see if this problem exist with KDE4 and digiKam 0.10.0... Gilles Caulier
I have made tests with digikam 0.10.0 beta & RC the probleme is resolved