You are not logged in.
- Topics: Active | Unanswered
#1 2020-12-08 08:46:15
- fakirinho
- Member
- Registered: 2016-03-21
- Posts: 26
[SOLVED] Permission issue after installing package with makepkg
I've been running Arch for quite some time (initially Antergos, since 2 years pure Arch, since 3 months Arch + KDE) and I thought that I know how to use AUR repositories, but...
Since I've moved to KDE (fresh install of whole system) I tend to have problems with file permission after installing AUR stuff. My normal workflow is following:
git clone <repo> && cd <repo>
makepkg -sir
run the app
Now mentioned issue is that quite often (probably not always, but reguraly (but honsetly, I don't remember if always or not)) I can't run the app afterwards due to permissions mismatch - things are installed for root & without permissions for "others".
This is the actual issue I've run into today when installing vmware-workstation15 from AUR (skipped git cloning part).
[stawka@darn-dyffra vmware-workstation15](master)$ makepkg -sir
==> WARNING: A package has already been built, installing existing package...
==> Installing package vmware-workstation15 with pacman -U...
loading packages...
resolving dependencies...
looking for conflicting packages...
Packages (6) atkmm-2.28.0-2 cairomm-1.12.2-4 gcr-3.38-1 gtkmm3-3.24.2-2 pangomm-2.42.1-2 vmware-workstation15-15.5.7-1
Total Installed Size: 904.46 MiB
:: Proceed with installation? [Y/n] y
(6/6) checking keys in keyring [####################################################################################################] 100%
(5/6) checking package integrity [####################################################################################################] 100%
(5/6) loading package files [####################################################################################################] 100%
(6/6) checking for file conflicts [####################################################################################################] 100%
(6/6) checking available disk space [####################################################################################################] 100%
:: Processing package changes...
(1/6) installing cairomm [####################################################################################################] 100%
(2/6) installing pangomm [####################################################################################################] 100%
(3/6) installing atkmm [####################################################################################################] 100%
(4/6) installing gtkmm3 [####################################################################################################] 100%
(5/6) installing gcr [####################################################################################################] 100%
(6/6) installing vmware-workstation15 [####################################################################################################] 100%
warning: directory permissions differ on /usr/share/appdata/
filesystem: 755 package: 750
warning: directory permissions differ on /usr/share/applications/
filesystem: 755 package: 750
warning: directory permissions differ on /usr/share/icons/
filesystem: 755 package: 750
warning: directory permissions differ on /usr/share/icons/hicolor/
filesystem: 755 package: 750
warning: directory permissions differ on /usr/share/icons/hicolor/16x16/
filesystem: 755 package: 750
warning: directory permissions differ on /usr/share/icons/hicolor/16x16/apps/
filesystem: 755 package: 750
warning: directory permissions differ on /usr/share/icons/hicolor/16x16/mimetypes/
filesystem: 755 package: 750
warning: directory permissions differ on /usr/share/icons/hicolor/22x22/
filesystem: 755 package: 750
warning: directory permissions differ on /usr/share/icons/hicolor/22x22/apps/
filesystem: 755 package: 750
warning: directory permissions differ on /usr/share/icons/hicolor/22x22/mimetypes/
filesystem: 755 package: 750
warning: directory permissions differ on /usr/share/icons/hicolor/24x24/
filesystem: 755 package: 750
warning: directory permissions differ on /usr/share/icons/hicolor/24x24/apps/
filesystem: 755 package: 750
warning: directory permissions differ on /usr/share/icons/hicolor/24x24/mimetypes/
filesystem: 755 package: 750
warning: directory permissions differ on /usr/share/icons/hicolor/256x256/
filesystem: 755 package: 750
warning: directory permissions differ on /usr/share/icons/hicolor/256x256/apps/
filesystem: 755 package: 750
warning: directory permissions differ on /usr/share/icons/hicolor/32x32/
filesystem: 755 package: 750
warning: directory permissions differ on /usr/share/icons/hicolor/32x32/apps/
filesystem: 755 package: 750
warning: directory permissions differ on /usr/share/icons/hicolor/32x32/mimetypes/
filesystem: 755 package: 750
warning: directory permissions differ on /usr/share/icons/hicolor/48x48/
filesystem: 755 package: 750
warning: directory permissions differ on /usr/share/icons/hicolor/48x48/apps/
filesystem: 755 package: 750
warning: directory permissions differ on /usr/share/icons/hicolor/48x48/mimetypes/
filesystem: 755 package: 750
warning: directory permissions differ on /usr/share/icons/hicolor/scalable/
filesystem: 755 package: 750
warning: directory permissions differ on /usr/share/icons/hicolor/scalable/mimetypes/
filesystem: 755 package: 750
warning: directory permissions differ on /usr/share/man/
filesystem: 755 package: 750
warning: directory permissions differ on /usr/share/man/man1/
filesystem: 755 package: 750
warning: directory permissions differ on /usr/share/mime/
filesystem: 755 package: 750
warning: directory permissions differ on /usr/share/mime/packages/
filesystem: 755 package: 750
==> Before using VMware, you need to reboot or load vmw_vmci and vmmon kernel modules (in a terminal on root: modprobe -a vmw_vmci vmmon)
==> You may also need to enable some of these services:
- vmware-networks.service: to have network access inside VMs
- vmware-usbarbitrator.service: to connect USB devices inside VMs
- vmware-hostd.service: to share VMs on the network
Optional dependencies for vmware-workstation15
linux-headers: build modules against Arch kernel [installed]
:: Running post-transaction hooks...
(1/7) Reloading system manager configuration...
(2/7) Arming ConditionNeedsUpdate...
(3/7) Install DKMS modules
==> dkms install --no-depmod -m vmware-workstation15 -v 15.5.7_17171714 -k 5.9.12-arch1-1
==> depmod 5.9.12-arch1-1
(4/7) Compiling GSettings XML schema files...
(5/7) Updating icon theme caches...
(6/7) Updating the desktop file MIME type cache...
(7/7) Updating the MIME type database...[stawka@darn-dyffra vmware-workstation15](master)$ vmware
bash: /usr/bin/vmware: Permission denied[stawka@darn-dyffra vmware-workstation15](master)$ lla /usr/bin/vmware
-rwxr-x--x 1 root root 3282 Dec 8 09:14 /usr/bin/vmware...there are some issues with the directories permissions, but those should be ok, right? Or am I wrong about it?
Last edited by fakirinho (2020-12-10 12:57:15)
Offline
#2 2020-12-09 14:21:45
- mpan
- Member
- Registered: 2012-08-01
- Posts: 1,640
- Website
Re: [SOLVED] Permission issue after installing package with makepkg
Report that as a bug to the PKGBUILD maintainer on AUR. They are using permissions that differ from what official packages set. Hence the mismatches.
As for bash being unable to start “/usr/bin/vmware”: it’s a weirder thing. Can you see what this gives?
getfacl -p /usr/bin/vmwareLast edited by mpan (2020-12-09 14:22:16)
Offline
#3 2020-12-10 00:52:52
- loqs
- Member
- Registered: 2014-03-06
- Posts: 19,031
Re: [SOLVED] Permission issue after installing package with makepkg
file vmware
vmware: Bourne-Again shell script, ASCII text executableOffline
#4 2020-12-10 12:56:48
- fakirinho
- Member
- Registered: 2016-03-21
- Posts: 26
Re: [SOLVED] Permission issue after installing package with makepkg
@mpan, hard to answer, your question came too late. I've been trying to work around this problem and double checked if "yay" will not solve this... And it turned out using "yay" solved this problem. Still, there are warnings about permissions differing between filesystem and packages, but in the end everything works and even "vmware" script from /usr/bin has different permissions than when I've used makepkg (-rwxr-x-r-x vs -rwxr-x--x). Even KDE Launcher entries are created which was not the case with makepkg.
I find all this quite odd, but I don't have enough will to pursuit where this differences come from.
@loqs, yeah, sure, I've started to change permissions but it's a cascade - one thing leads to another.
Offline
#5 2020-12-11 17:45:07
- mpan
- Member
- Registered: 2012-08-01
- Posts: 1,640
- Website
Re: [SOLVED] Permission issue after installing package with makepkg
If there is a difference betwen makepkg and yay, it’s a bug in yay. Therefore not solved — at most circumvented by making one bug triggering another bug not appearing.
Last edited by mpan (2020-12-11 17:45:35)
Offline
#6 2020-12-11 19:46:58
- loqs
- Member
- Registered: 2014-03-06
- Posts: 19,031
Re: [SOLVED] Permission issue after installing package with makepkg
@fakirinho please consider leaving a message on the packages AUR page about the issue so it can be fixed for others.
The changes below might fix the directory permissions and executable permissions:
diff --git a/PKGBUILD b/PKGBUILD
index d56d2f9..645f872 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -208,7 +208,7 @@ package() {
# Make directories and copy files.
- mkdir -p \
+ install -dm 755 \
"$pkgdir/etc"/{cups,pam.d,modprobe.d,thnuclnt,vmware} \
"$pkgdir/usr"/{share,bin} \
"$pkgdir/usr/include/vmware-vix" \
@@ -341,7 +341,7 @@ fi
# Apply permissions where necessary.
- chmod +x \
+ chmod +rx \
"$pkgdir/usr/bin"/* \
"$pkgdir/usr/lib/vmware/bin"/* \
"$pkgdir/usr/lib/vmware/setup"/* \Offline