When looking at bluetooth:/ in konqueror: as a normal user: - only plain document icons were used for the items in the view - there was no applications associated for the items in the view - (eg no application for bluetooth/phone-device-class mimetype). as root: - each item in the view has a custom icon. - mimetypes seemed to be set up correctly and custom apps opened by default for the different bluetooth services. it turned out that the /usr/share/mimelnk dir on my system had permissions: drwx------ chmod go+rX /usr/share/mimelnk fixed it. The permissions on the subdirectories were already OK. possible causes: The only stuff I have in there however is /usr/share/mimelnk/application/x-k3b.desktop and /usr/share/mimelnk/bluetooth/*.desktop so I think either kdebluetooth or k3b ebuilds or the kde eclasses would be the culprit. I installed kbluetoothd a while ago (long before k3b which was just last week), so the directory was probably initially created with bad permissions by the kdebluetooth ebuild. my package versions: net-wireless/kdebluetooth-1.0_beta1-r2 (0) app-cdr/k3b-0.12.17 (0) Reproducible: Always Steps to Reproduce: see the description above.
in case it also helps, my kde version is 3.5.7 and my portage version is portage-2.1.3.16 (but probably was older when I installed kdebluetooth) and my /usr/portage/eclass/kde* files are: $> ls -altr /usr/portage/eclass/kde* -rw-r--r-- 1 portage portage 462 2004-06-25 10:43 /usr/portage/eclass/kde-base.eclass -rw-r--r-- 1 portage portage 29 2005-10-06 02:47 /usr/portage/eclass/kde-i18n.eclass -rw-r--r-- 1 portage portage 2323 2006-01-01 12:05 /usr/portage/eclass/kde-dist.eclass -rw-r--r-- 1 portage portage 5390 2006-10-15 06:08 /usr/portage/eclass/kde-source.eclass -rw-r--r-- 1 portage portage 14344 2007-03-19 08:35 /usr/portage/eclass/kde-meta.eclass -rw-r--r-- 1 root root 30195 2007-09-28 06:07 /usr/portage/eclass/kde-functions.eclass -rw-r--r-- 1 root root 15003 2007-10-19 22:35 /usr/portage/eclass/kde.eclass again, some of them are newer than when I installed kdebluetooth which would have been about july this year.
No point in pondering which ages-old ebuild messed this up, for sure not anything that's in the tree ATM. Portage should behave consistently. *** This bug has been marked as a duplicate of bug 141619 ***