Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 199197 - kbluetooth or k3b installs files in /usr/share/mimelnk, but makes /usr/share/mimelnk readable only to root
Summary: kbluetooth or k3b installs files in /usr/share/mimelnk, but makes /usr/share/...
Status: RESOLVED DUPLICATE of bug 141619
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] KDE (show other bugs)
Hardware: All Linux
: High minor (vote)
Assignee: Gentoo KDE team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-11-15 00:42 UTC by C Sincock
Modified: 2007-12-05 11:00 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description C Sincock 2007-11-15 00:42:02 UTC
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.
Comment 1 C Sincock 2007-11-15 00:47:17 UTC
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.

Comment 2 Jakub Moc (RETIRED) gentoo-dev 2007-12-05 11:00:56 UTC
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 ***