Version: 0.10.0-beta6 (using 4.1.80 (KDE 4.1.80 (KDE 4.2 Beta1)), Gentoo) Compiler: x86_64-pc-linux-gnu-gcc OS: Linux (x86_64) release 2.6.26-tuxonice when selecting images in the Import dialoge (using usb camera) it seems that during the selection process too much metadata is retrieved from the files or other slow operations lead to ~2seconds delay per picture and make the mouse hang when the selection rectange should be smooth this happens especially when selecting from the right side first (starting with the newer images )
SVN commit 892924 by cgilles: call right slot with File/new action BUG: 175898 M +3 -3 cameraiconview.h M +2 -3 cameraui.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=892924
Oups sorry, wrong commit (:=))). re-open Gilles Caulier
Works instantly for me in 0.10b7svn
seems to be related to bug #175894, i get those same error messages during selecting
sorry, forgot to paste the specific lines: --- error reading file:///media/disk-1/dcim/106_pana//p1060828.jpg loading writer for key "http://freedesktop.org/standards/xesam/1.0/core#cameraModel" loading writer for key "http://freedesktop.org/standards/xesam/1.0/core#focalLength" loading writer for key "http://freedesktop.org/standards/xesam/1.0/core#mimeType" loading writer for key "http://freedesktop.org/standards/xesam/1.0/core#cameraManufacturer" loading writer for key "http://freedesktop.org/standards/xesam/1.0/core#orientation" loading writer for key "http://www.w3.org/1999/02/22-rdf-syntax-ns#type" loading writer for key "http://freedesktop.org/standards/xesam/1.0/core#flashUsed" loading writer for key "http://freedesktop.org/standards/xesam/1.0/core#35mmEquivalent" loading writer for key "http://freedesktop.org/standards/xesam/1.0/core#contentCreated" loading writer for key "http://freedesktop.org/standards/xesam/1.0/core#whiteBalance" loading writer for key "http://freedesktop.org/standards/xesam/1.0/core#height" loading writer for key "http://freedesktop.org/standards/xesam/1.0/core#url" loading writer for key "http://freedesktop.org/standards/xesam/1.0/core#width" loading writer for key "http://freedesktop.org/standards/xesam/1.0/core#size" loading writer for key "http://strigi.sf.net/ontologies/0.9#depth" loading writer for key "http://freedesktop.org/standards/xesam/1.0/core#meteringMode" loading writer for key "http://freedesktop.org/standards/xesam/1.0/core#sourceModified" loading writer for key "http://strigi.sf.net/ontologies/0.9#parentUrl" loading writer for key "http://freedesktop.org/standards/xesam/1.0/core#exposureBias" loading writer for key "http://freedesktop.org/standards/xesam/1.0/core#exposureTime" loading writer for key "http://freedesktop.org/standards/xesam/1.0/core#name" loading writer for key "http://freedesktop.org/standards/xesam/1.0/core#fileExtension" error reading file:///media/disk-1/dcim/106_pana//p1060828.jpg loading writer for key "http://freedesktop.org/standards/xesam/1.0/core#cameraModel" loading writer for key "http://freedesktop.org/standards/xesam/1.0/core#focalLength" loading writer for key "http://freedesktop.org/standards/xesam/1.0/core#mimeType" loading writer for key "http://freedesktop.org/standards/xesam/1.0/core#cameraManufacturer" loading writer for key "http://freedesktop.org/standards/xesam/1.0/core#orientation" loading writer for key "http://www.w3.org/1999/02/22-rdf-syntax-ns#type" loading writer for key "http://freedesktop.org/standards/xesam/1.0/core#flashUsed" loading writer for key "http://freedesktop.org/standards/xesam/1.0/core#35mmEquivalent" loading writer for key "http://freedesktop.org/standards/xesam/1.0/core#contentCreated" loading writer for key "http://freedesktop.org/standards/xesam/1.0/core#whiteBalance" loading writer for key "http://freedesktop.org/standards/xesam/1.0/core#height" loading writer for key "http://freedesktop.org/standards/xesam/1.0/core#url" loading writer for key "http://freedesktop.org/standards/xesam/1.0/core#width" loading writer for key "http://freedesktop.org/standards/xesam/1.0/core#size" loading writer for key "http://strigi.sf.net/ontologies/0.9#depth" loading writer for key "http://freedesktop.org/standards/xesam/1.0/core#meteringMode" loading writer for key "http://freedesktop.org/standards/xesam/1.0/core#sourceModified" loading writer for key "http://strigi.sf.net/ontologies/0.9#parentUrl" loading writer for key "http://freedesktop.org/standards/xesam/1.0/core#exposureBias" loading writer for key "http://freedesktop.org/standards/xesam/1.0/core#exposureTime" loading writer for key "http://freedesktop.org/standards/xesam/1.0/core#name" loading writer for key "http://freedesktop.org/standards/xesam/1.0/core#fileExtension" ... and so on
@Simon: looks like Nepomuk problem - it tries to to instantly index new files. IMO if possible digiKam should disable Nepomuks interference - there is no need to index files if they are on camera or removable medias if not asked.
Simon, Sound like a broken KDE installation or something like that. this message come from DBUS, not digiKam Gilles Caulier
Mik, We don't use yet Nepomuk in digiKam... Sound like a part of KDE4 used in digiKam play with Nepomuk directly... Perhaps Solid... Marcel ? Gilles Caulier
*** Bug 175894 has been marked as a duplicate of this bug. ***
Maybe the messages are generated because we use KMetaFileInfo? (cameraitempropertiestab) XESAM is definitely related with nepomuk/strigi and not directly used by digikam.
I recently noticed those messages on my computer: but it doesn't slow down operations.
i think that the slowdown comes from "error reading file:///media/disk-1/dcim/106_pana//p1060828.jpg" Mikolaj: you have this errormessage too ? if not, thisshould be the culprit, i would also say that my kde install (trunk) and quite sane and dbus is working fine so far. --- start guesswork --- i think there must be two different access methods for * downloading files to the harddrive and (works) * getting data when thumbnails on usb are doubleclicked (as this fails with the same error message - error reading file) and when selecting the second approach is used --- end guesswork ---
No both for normal downloading and opening the image the same method is used. You can easily test from the command line if the relevant file is accessible or not. I dont know where the error string "error reading" comes from, it is not used anywhere in digikam.
"error reading" ... libkexiv2 or Exiv2 ? Gilles
it disappeared! i just tried it again after a finished kde-svn recompile and now i don't even get those messages ("loading writer for key ...") and selection just works smooth! yeah! also the "error reading" went away - i don't have the whole kde tree laying around here, but a grep should find the "error reading" message, might be libkexiv2 (which was also updated during the rebuild) but, it is now replaced by: QFSFileEngine::open: No file name specified digikam(1966)/digikam (core) Digikam::UMSCamera::downloadItem: Failed to open dest file for writing: "" when doubleclicking on a thumbnail, but i'll open a new bug for this and a other issue i found
bummer. its back! i had the "Properties" tab collapsed, but when this tab is open, the old behaviour is there again/still
I can confirm the Digikam::UMSCamera::downloadItem: Failed to open dest file for writing: "" error message, number one. Number two, if you have your speed problem only with the properties tab open, then it is indeed something in there. It can be either downloading exif info from the camera, opening DMetadata or KMetaFileInfo on the file.
Now I cannot force KDE to spit out xesam messages :/
With this commit: SVN commit 898140 by cgilles: backport commit #897995 from KDE3 branch M +1 -2 cameracontroller.cpp M +1 -2 gpcamera.cpp M +60 -84 umscamera.cpp M +4 -4 umscamera.h WebSVN link: http://websvn.kde.org/?view=rev&revision=898140 KFileMetaInfo is removed from USB Mass Storage driver. Now it's faster. Marcel: KFileMetaInfo do _not_ provide any informations about image or video. It's a huge regression because we cannot get minimal informations from images if not Exif info is available. Andreas: I CC you here because it become urgent to have a method in Exiv2 to get metadata outside Exif/iptc/XMP from file format. For ex, to be able to get image size from image header (JPEG, PNG, and JPEG2000 have these informations). Before, with KDE3, KFileMetaInfo class been used to extract it. Simon, Please update digiKam code using svn and try again. Thanks in advance Gilles Caulier
SVN commit 898152 by cgilles: digiKam from trunk: CameraGUi: fix empty tmp folder used to download item when user trying to open image from camera BUG: 175898 M +23 -23 cameracontroller.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=898152
works like a charm, thanks!
Re comment #19: Gilles, Some info is already available from the Exiv2::Image interface, in particular pixelHeight() and pixelWidth(): http://www.exiv2.org/doc/classExiv2_1_1Image.html#4d616c94b3d8129a3abcbec2c200feda A more general implementation is on the roadmap for 0.19, please add additional requirements there: http://dev.robotbattle.com/bugs/view.php?id=505 Andreas
Andreas, Thanks for the tip. I will fill Exiv2 report #505 Gilles