These files are owned by both kdeutils and kdebase. They should only be owned by kdebase. /usr/share/apps/kfind/icons/locolor/22x22/actions/archive.png (only ['kdebase'] should own it, but ['kdeutils'] also does) /usr/share/apps/kfind/icons/locolor/22x22/actions/delete.png (only ['kdebase'] should own it, but ['kdeutils'] also does) /usr/share/apps/kfind/icons/locolor/22x22/actions/idea.png (only ['kdebase'] should own it, but ['kdeutils'] also does) /usr/share/apps/kfind/icons/locolor/22x22/actions/info.png (only ['kdebase'] should own it, but ['kdeutils'] also does) /usr/share/apps/kfind/icons/locolor/22x22/actions/openfile.png (only ['kdebase'] should own it, but ['kdeutils'] also does) /usr/share/apps/kfind/icons/locolor/22x22/actions/save.png (only ['kdebase'] should own it, but ['kdeutils'] also does) /usr/share/apps/kfind/icons/locolor/22x22/actions/search.png (only ['kdebase'] should own it, but ['kdeutils'] also does)
This defect is considered SHOULD-FIX for Fairfax.
No, this is quite intentional. KFindPart (part of Konqueror in kdebase) and KFind (part of kdeutils) both need those icons, and they can work nicely without each other. There's no reason for kdeutils to depend on kdebase (maybe some fvwm/twm/gnome/whatever user wants to use kfind?), so it should include those files.
But kdeutils _does_ require kdebase. So either this is a bug, or the bug should read kdeutils should not require kdebase. I don't care which is the proper bug, but this doesn't seem like the proper resolution.
Can't reproduce for hampton beta4. closing