Summary: | digiKam extremely unresponsive and slow (probably related to tags) | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Kristian <kde-bugs> |
Component: | Tags-Engine | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED WORKSFORME | ||
Severity: | grave | CC: | caulier.gilles |
Priority: | NOR | ||
Version: | 4.2.0 | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 4.0.0 | |
Attachments: |
valgrind output
digiKam console output with debug statements |
Description
Kristian
2013-11-26 21:16:10 UTC
All that i can see is that something is broken on your computer, about network file system share through Samba. Perhaps it's due to a system update... It's not digiKam, just a side effect. Check your system. Gilles Caulier Created attachment 83800 [details]
valgrind output
valgrind --tool=memcheck --leak-check=full --error-limit=no --log-file="digikam-valgrind.log" digikam
What makes you so sure that it's not a digiKam issue? The Samba error message? That's easy resolved by installing samba (although it's not needed). But this doesn't change anything regarding to digiKam's responsiveness. Do you have any idea where to start searching? I attached the valgrind output to start. There is nothing to see in valgrind trace about your problem. A detailled trace of digiKam started will be more instructive. Look in this page about how to enable debug spaces before to run digiKam... http://www.digikam.org/contrib Gilles Caulier Created attachment 83811 [details]
digiKam console output with debug statements
Note: The missing libkvkontakte is not the reason.
Switching the icon theme from Oxygen to another one (.nitrux for example) somehow solves the problem. I don't know if this a digiKam or KDE problem. However, digiKam is the program that is predominantly affected. digiKam is not directly relevant of icon theme set in your KDE desktop. The way to render application style (widget/icons/window decoration) is relevant of theme. Oxygen style is the most complex with a lots of settings, as OpenGL effect for ex. I recommend to check advanced settings for this theme in KDE control panel and check the results. Some effects depend of video card and quality of video driver, which include time latency ... Gilles Caulier It's related to the ICON THEME, there are no further setting related to OpenGL etc. This issue returned in the last couple of days. Unfortunately, I can't tell you what triggered it. Changing the icon theme did not fix it. However, after reading the bugs #315574 and #307219, I saw that several of my tags had an symbol with a question mark. Resetting all tags with this icon to the standard icon improved performance significantly and now digiKam is usable again. Note: Contrary to bug #315574 the performance issue did not only appear when a sidebar was open, but all the time. I suspect that one of the tags with question mark icon was in the list of last used tags (right-click menu). Therefore, those bugs might be duplicates. Component info: digiKam version 4.2.0 Exiv2 kann in JP2 speichern: Ja Exiv2 kann in JPEG speichern: Ja Exiv2 kann in PGF speichern: Ja Exiv2 kann in PNG speichern: Ja Exiv2 kann in TIFF speichern: Ja Exiv2 unterstützt XMP-Metadaten: Ja LibCImg: 130 LibEigen: 3.2.1 LibExiv2: 0.24 LibJPEG: 80 LibJasper: 1.900.1 LibKDE: 4.13.3 LibKExiv2: 2.3.1 LibKGeoMap: 2.0.0 LibKdcraw: 2.4.2 LibLCMS: 2060 LibLensFun: 0.2.8-0 LibPGF: 6.14.12 - Interne Bibliothek LibPNG: 1.6.12 LibQt: 4.8.6 LibRaw: 0.16.0 LibTIFF: LIBTIFF, Version 4.0.3 Copyright (c) 1988-1996 Sam Leffler Copyright (c) 1991-1996 Silicon Graphics, Inc. Marble-Funktion: 0.18.3 (stable release) Parallelisierte PGF-Codecs: Keine Parallelisiertes Entfernen von Mosaikmustern: Unbekannt Prozessorkerne: 4 Unterstützung für Demosaic GPL2: Unbekannt Unterstützung für Demosaic GPL3: Unbekannt Unterstützung von RawSpeed-Codec: Unbekannt Datenbanktreiber: QSQLITE KIPI-Module: 4.2.0 LibGphoto2: 2.5.4 LibKface: 3.4.0 LibKipi: 2.1.0 LibOpenCV: 2.4.9 |