plasma-desktop freezes for 5 minutes after login reading subdirectory tree with my pictures for digikam

[Jan daciuk]

plasma-desktop freezes for 5 long minutes after login. Earlier, it used to be that digikam froze for 5 minutes after it had been launched. Unsetting the option "Scan for new items at startup (makes startup slower)" did not help. That bug was present in Kubuntu 11.10 on. Now that behavior of digikam is gone, i.e. it starts without delay (it used to show "reading database" for 5 minutes). Exactly the same time is now spent by plasma-desktop after login on reading the subdirectory tree where I keep my photos managed by digikam. This can be seen by repeatedly running lsof from the text console. I supect why plasma-desktop behaves that way, but I'm afraid that if I write so, my information will be censored just like it happened on Ubuntu Forums. The situation with plasma-desktop and digikam exhibits some parallels with kmail, to give you the clue. The bug manifested itself for the first time at the end of 2011, but I first suspected my unintensional changes in some configuration files. It is not a problem in my configuration files.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: plasma-desktop 4:4.7.4-0ubuntu0.1
ProcVersionSignature: Ubuntu 3.0.0-17.30-generic 3.0.22
Uname: Linux 3.0.0-17-generic x86_64
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
Date: Mon Apr 9 21:39:52 2012
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: kde-workspace
UpgradeStatus: Upgraded to oneiric on 2011-10-24 (168 days ago)

[Harald Sitter (apachelogger)]

Hi there!

Thanks for reporting this bug! Your bug seems to be a problem with the KDE program itself, and not with our KDE packages. While we appreciate your issue, it would be better if it was tracked at https://bugs.kde.org, so that the KDE developers can deal with this speedily and have direct communication with you as the reporter for more effective debugging.

Thanks!