Bug 154892 - kfind slow startup caused by extensive icon loading
Summary: kfind slow startup caused by extensive icon loading
Status: RESOLVED WORKSFORME
Alias: None
Product: kfind
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Eric Coquelle
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-12-31 12:17 UTC by FiNeX
Modified: 2008-11-29 18:54 UTC (History)
7 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description FiNeX 2007-12-31 12:17:10 UTC 
Version:           Revision 755041 (using KDE Devel)
Installed from:    Compiled sources

When started, kfind try to load ALL mimetype icons. On the shell output there are more than 300 lines as: 

kfind(28463)/kdeui (KIconLoader) KIconLoader::loadIcon: No such icon "audio-x-aifc"
kfind(28463)/kdeui (KIconLoader) KIconLoader::loadIcon: No such icon "audio-x-aiffc"
kfind(28463)/kdeui (KIconLoader) KIconLoader::loadIcon: No such icon "audio-AMR"
kfind(28463)/kdeui (KIconLoader) KIconLoader::loadIcon: No such icon "audio-AMR-WB"

Why kfind need to load all this icons ?
Comment 1 Lubos Lunak 2008-06-30 13:47:48 UTC 
This was most probably avoided in KDE3 by the delayed icon loading in KIconLoader.
Comment 2 Damien Gombault 2008-07-25 22:31:23 UTC 
This seems to be fixed in KDE 4.1 RC1.
Comment 3 Dario Andres 2008-08-01 15:13:39 UTC 
Using KDE: 4.1.00 (KDE 4.1.0) in ArchLinux i686:

I can reproduce this bug.

In the first start, Kfind startup will be delayed because of this icon loading (~215 lines). In the next starts, kfind will open without delay (and without displaying the icon loading errors).
Comment 4 Will Stephenson 2008-09-22 10:31:58 UTC 
Downstream at https://bugzilla.novell.com/show_bug.cgi?id=428229
Comment 5 Kristjan Ugrin 2008-10-02 13:54:37 UTC 
I can confirm this too - very annoying bug.
Comment 6 Peter Penz 2008-11-29 16:26:53 UTC 
It seems the issue has been fixed already (I cannot reproduce it on trunk).
Comment 7 FiNeX 2008-11-29 18:54:49 UTC 
Yes, it seems fixe. Thanks Peter.