What to do about warning "directory permissions differ on..." ?

Hello!
I have gotten this warning when upgrading today:
warning: directory permissions differ on var/run/gdm/
filesystem: 1775 package: 711
warning: directory permissions differ on var/log/gdm/
filesystem: 1770 package: 755
This means that the permissions on my computer didn't match with the ones from the package being upgraded/installed, right?
Which permissions should I leave for that folder (var/log/gdm/) and why? And why is the warning on there twice with different values? i'm confused
Last edited by trusktr (2010-04-06 18:07:37)

trusktr wrote:
Hello!
I have gotten this warning when upgrading today:
warning: directory permissions differ on var/run/gdm/
filesystem: 1775 package: 711
warning: directory permissions differ on var/log/gdm/
filesystem: 1770 package: 755
This means that the permissions on my computer didn't match with the ones from the package being upgraded/installed, right?
Which permissions should I leave for that folder (var/log/gdm/) and why? And why is the warning on there twice with different values? i'm confused
If you or another package had good reason to change it, leave it at its current value. If not, change it to the package value listed above (and see if anything breaks).
You're seeing different permissions for two different folders: read the warnings more closely.

Similar Messages

[SOLVED] warning: directory permissions differ on var/log/wicd/

Hi,
I've seen several posts about this but I couldn't really figure out what's the appropriate action. Well, anyway I get the following error message when doing a pacman -Syu
warning: directory permissions differ on var/log/wicd/
filesystem: 1363 package: 755
Is it a bug? Should I change the filepermission of the directory, and if so to what?
Last edited by OMGitsUGOD (2009-09-18 10:38:32)

This is sort of related,
http://bbs.archlinux.org/viewtopic.php?pid=432588
or at least thats the post at the end has the same file permisions as I have in /var/log/wicd.
$ ls -la /var/log/ | grep wicd
d-wxrw--wt 2 root root 4096 2009-08-27 07:58 wicd
I'm pretty bad at this stuff, but isn't this rather 1361 than 1363, or am I totally wrong? And why not allow theowner to read the file?
Last edited by OMGitsUGOD (2009-09-17 08:43:32)

Warning: directory permissions differ

I am getting an error when downloading and installing packages with pacman.
This is what I get:
$ sudo pacman -S nitrogen
warning: nitrogen-1.2-1 is up to date -- reinstalling
resolving dependencies...
looking for inter-conflicts...
Targets: nitrogen-1.2-1
Total Download Size: 0.00 MB
Total Installed Size: 0.13 MB
Proceed with installation? [Y/n]
checking package integrity...
(1/1) checking for file conflicts [#####################] 100%
(1/1) upgrading nitrogen [#####################] 100%
warning: directory permissions differ on usr/man/man1/
filesystem: 755 package: 700
I don't know if that has a serious impact, but I am sure it shouldn't be like that...

Snowman wrote:Submit a bug report.
This is one way and i hope it helps you and the other devs. But what do you think about that the systems can repair this by itselfs? On my opensuse server i have a tool named chkstat which runs as a cronjob and set the file permissions as loaded from a file.
Source: http://ftp.gwdg.de/pub/opensuse/distrib … 11.src.rpm
manpage: http://www.trinler.de/de/linux/man.html?command=chkstat
The advantage from my side is that one or a group of devs define the file permissions standard for arch linux and everyone can choose to use it or to append own more or less secure/paranoid settings. Another sideeffect is that every dev can take a look inside this config file to see what permission the own PKGBUILD need so that in the best case we will not see such messages in the future. The source includes config files so there is no need to restyle this all from zero.

GDM update: directory permissions differ on /var/log/gdm/

Hello,
Running Arch 64Bits kernel 3.9.9-1 with systemd and i got the following warning during a gdm update today:
(1/6) upgrading libgdm [######################] 100%
(2/6) upgrading gdm [######################] 100%
warning: directory permissions differ on /var/log/gdm/
filesystem: 711 package: 1770
Why would gdm need some 1770 permissions for log files? Looks pretty suspicious to me, especially the sticky bit thing. What did i miss?
PS: BTW the update is successful (it's a warning afterall, not an error)
Thanks
EDIT:
Looks like the opposite situation than 3 years ago:
https://bbs.archlinux.org/viewtopic.php?id=94681
https://bugs.archlinux.org/task/19294
EDIT2: here's what i have in /var/log:
msytux666 var # ls -la
total 64
drwxr-xr-x 14 root root 4096 Jul 6 15:34 .
drwxr-xr-x 20 root root 4096 Jul 16 20:24 ..
-rwxrwxrwx 1 root root 4192 Jun 19 11:27 .com.zerog.registry.xml
drwxr-xr-x 7 root root 4096 Jul 7 00:07 abs
drwxr-xr-x 8 root root 4096 Jun 16 17:28 cache
drwxr-xr-x 3 root root 4096 Jun 17 19:07 db
drwxr-xr-x 2 root root 4096 May 31 20:40 empty
drwxrwxr-x 2 root games 4096 May 31 20:40 games
drwx--x--x 2 gdm gdm 4096 Jun 15 14:23 gdm
drwxr-xr-x 26 root root 4096 Jul 16 01:13 lib
drwxr-xr-x 2 root root 4096 May 31 20:40 local
lrwxrwxrwx 1 root root 11 May 31 20:40 lock -> ../run/lock
drwxr-xr-x 6 root root 4096 Jul 18 00:33 log
lrwxrwxrwx 1 root root 10 May 31 20:40 mail -> spool/mail
drwxr-xr-x 2 root root 4096 May 31 20:40 opt
lrwxrwxrwx 1 root root 6 May 31 20:40 run -> ../run
drwxr-xr-x 6 root root 4096 Jun 16 17:28 spool
drwxrwxrwt 8 root root 4096 Jul 18 00:33 tmp
gdm is owned by gdm, so why would it needs 1770 permissions?
EDIT3:
After further research i appear the way gdm is installed may matter.
Well i installed gdm through pacman and always update it with pacman as well. Never manually compiled/make_install'd it nor used abs for it.
Last edited by BGK (2013-07-19 21:37:13)

Okay I'm confused ...
Commit:https://projects.archlinux.org/svntogit … 92c38d536d
@@ -68,8 +68,7 @@ package_gdm() {
cd $pkgbase-$pkgver
make DESTDIR="$pkgdir" install
- chmod 1770 "$pkgdir/var/log/gdm"
- chmod 700 "$pkgdir/var/lib/gdm/.config/dconf"
+ chmod 711 "$pkgdir/var/log/gdm"
rm -r "$pkgdir/var/run" "$pkgdir/var/gdm"
### Split libgdm
so that takes away the 1770 permissions, and replaces them with 711.
@@ -5,6 +5,7 @@ post_install() {
getent passwd gdm > /dev/null 2>&1 || usr/sbin/useradd -c 'Gnome Display Manager' -u 120 -g gdm -d /var/lib/gdm -s /sbin/nologin gdm
passwd -l gdm > /dev/null
chown -R gdm:gdm /var/lib/gdm > /dev/null
+ chown root:gdm /var/log/gdm > /dev/null
glib-compile-schemas /usr/share/glib-2.0/schemas
gtk-update-icon-cache -q -t -f /usr/share/icons/hicolor
however:
chown root:gdm /var/log/gdm > /dev/null
.. is where I get confused. This command makes root and the group gdm the new owners of /var/log/gdm, or did I go wrong somewhere?

Directory permissions differ on var/

When upgrading packages with pacman, I've been getting a warning that "directory permissions differ on var/ filesystem 775 package 755
This most recently was during my upgrade of xorg-server
I'm not sure what causes this warning, or whether some action needs to be taken, and if so, which way to change things.....:(

http://bbs.archlinux.org/viewtopic.php?id=42314

[SOLVED] Need Help Understanding Warning on Directory Permissions

Hi guys-
In my last update I got these warnings:
warning: directory permissions differ on /usr/share/polkit-1/rules.d/
filesystem: 700 package: 755
warning: directory permissions differ on /var/lib/libvirt/qemu/
filesystem: 755 package: 770
I've seen quite a few threads floating around like these, but they just add to my confusion. I have not changed persmissions to these files. From what I've gathered so far from a few threads is that the package handler may have changed persmissions resulting in the warning messages. This is where my confusion sets in, and I don't know if it's from staring at the screen for too long, but if I cd into those directories and ls -l, there's the rules.d directory with 700:
/usr/share/polkit-1/:
total 8
drwxr-xr-x 2 root root 4096 Jun 14 10:39 actions
drwx------ 2 polkitd root 4096 Jun 16 18:31 rules.d
However, if I cd into rules.d, there's two files in there, both with 644 permissions:
total 8
-rw-r--r-- 1 root root 281 Jun 1 02:17 50-libvirt.rules
-rw-r--r-- 1 root root 488 May 12 17:11 gnome-control-center.rules
Where's the file with 755?
Same thing with the other wanring. There's qemu with 755. Libvirt is 755. The directory inside qemu is empty. Where's 770?
total 36
drwxr-xr-x 2 root root 4096 Mar 2 05:39 boot
drwxr-xr-x 2 root root 4096 Mar 2 05:39 dnsmasq
drwxr-xr-x 2 root root 4096 Mar 2 05:39 filesystems
drwxr-xr-x 2 root root 4096 Mar 2 05:39 images
drwxr-xr-x 3 root root 4096 Mar 2 05:39 lockd
drwxr-xr-x 2 root root 4096 Mar 2 05:39 lxc
drwxr-xr-x 2 root root 4096 Mar 2 05:39 network
drwxr-xr-x 2 root root 4096 May 10 19:05 qemu
drwxr-xr-x 2 root root 4096 Mar 2 05:39 uml
Can someone help me understand this please?
Last edited by w201 (2015-06-17 03:23:03)

The message does indeed mean that the package maintainer has changed the permissions on those directories. You can change your directories to match or leave them as-is. I always change mine when I get messages like this. To do that in this case, you'd run:
chmod 755 /usr/share/polkit-1/rules.d
chmod 770 /var/lib/libvirt/qemu
That will make your directories consistent with the new versions of the packages.

Solved: pacman - permissions differ on tmp/

Not sure if anyone else is seeing this because this may have been part of something I did a way back. I'm getting:
( 35/400) upgrading filesystem [######################] 100%
warning: directory permissions differ on tmp/
filesystem: 777 package: 1777
I know a bit about the filesystem package. If I remember correctly it contains files that are Arch specific like the boot scripts... Now if I'm reading this correctly the 777 permissions of "filesystem" is original directory and "package" is the package's permissions for the tmp directory. Here's my /tmp directory permissions after the update:
drwxrwxrwt 11 root root 4.0K Sep 13 11:41 tmp
Can anyone help me clarify this? Is the problem now fixed, or is there something I need to do?
Last edited by Gen2ly (2010-09-13 19:49:14)

I haven't seen pacman changing permission on directories yet, but according to the message, your /tmp didn't have the sticky bit set before the upgrade. Though things will work fine with just 777, not having the sticky bit on /tmp will mean that someone could delete and replace files owned by someone else, which is a security risk.

Libvirt permissions differ on upgrade

(12/16) upgrading libvirt [--------------------------------] 100%
warning: /etc/libvirt/qemu/networks/default.xml installed as /etc/libvirt/qemu/networks/default.xml.pacnew
warning: directory permissions differ on /var/lib/libvirt/qemu/
filesystem: 755 package: 770
>>> You may need to run 'rm -rf ~/.libvirt'
Does pacman just never update permissions automatically? Anyway I just manually changed it with the following command. Hope that was the right call.
$ sudo chmod 770 /var/lib/libvirt/qemu/

Directory permissions are never changed automatically. A directory could be part of two different packages, with each package specifying different permissions. To make the job easier pacman only warns about changed directory permissions. File permissions are another matter, they will be modified.
You did the right thing with changing the permissions if the 755 wasn't set by you manually.

Mercury Install, directory permissions

[s3kt0r@localhost ~]$ sudo pacman -S mercury
resolving dependencies...
looking for inter-conflicts...
Targets (1): mercury-1.9.5-1
Total Download Size: 7.99 MB
Total Installed Size: 10.97 MB
Proceed with installation? [Y/n] y
:: Retrieving packages from community...
mercury-1.9.5-1-i686 8.0M 311.8K/s 00:00:26 [################################################################################################################################] 100%
checking package integrity...
(1/1) checking for file conflicts [################################################################################################################################] 100%
(1/1) installing mercury [################################################################################################################################] 100%
warning: directory permissions differ on usr/bin/
filesystem: 755 package: 700
warning: directory permissions differ on usr/share/gnome/
filesystem: 755 package: 700
warning: directory permissions differ on usr/share/icons/
filesystem: 755 package: 700
warning: directory permissions differ on usr/share/pixmaps/
filesystem: 755 package: 700
Anyway to fix this? Thanks

well 700 on /usr/bin looks like a very bad idea and could indeed partially wreck the system if these permissions were used. (but well, this should all be easily fixable as root).
But permissions of existing directories are not changed.
They would only be used if mercury was the very first package installed on a completely empty system. And this would probably never happen in real-world usage.
So basically, when you have this warning, you do the following :
1) if filesystem permissions are the correct ones, you are fine. just report a bug for the offending package
2) if filesystem permissions are the wrong ones, you might want to fix it manually
3) if you don't know, you can either just ignore the issue, or look for information, or ask around

What to do about error msg: Warning: SUID file "System/Library/Core/Services/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDA gent"has been modified and will not be repaired" on MacBook Air.

What to do about error msg in Disk Utility on MacBook Air:
Warning: SUID file “System/Library/Core/Services/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDA gent"has been modified and will not be repaired.”

As long as the report ends up with 'Permissions repair complete' then, as far as permissions go, you are fine. You can ignore the various statements in the report:
Permissions you can ignore on 10.5 onwards:
http://support.apple.com/kb/TS1448
Using 'should be -rw-r--r-- , they are lrw-r--r--' as an example, you will see the that the permissions are not changed, but the | indicates a different location. This is because an update to Leopard onwards changed the location of a number of system components.
Poster rccharles has provided this description of what it all means:
drwxrwxrwx
d = directory
r = read
w = write
x = executeable program
drwxrwxrwx
| | |
| | all other users not in first two types
| |
| group
|
owner

Warning: SUID File (11 Files) and "Permissions Differ" - No Install Disc

Hello,
Have had my black macbook for about 3 1/2 years now (leopard) and having problems with it being really sluggish and freezing up. Additionally, the fan is coming on a lot and being really loud. I have checked activity monitor (all processes) and nothing is running over 12...Question is are the "warning suid files" and "permissions differ" the source of these problems? I can't find my original install disc (have one for my i mac but no good I hear.) Guessing I need to go to the genius bar to fix this issue...Thanks, PoorGradStudent

Hello and welcome to the discussions, Those warning are normal and nothing to worry about.
While your at the genius bar see if they will run a diagnostics test on your laptop. Note, if your problems only show up after it has been on for an hour, get there an hour early and warm it up.
No use in have them look at it if you can't replicate the problem.
Cheers,
Glynn

What is 'Permissions differ...'?

Of late I am facing some problems in my Mac's performance. I have had to resort to using Disk utility for gauging the status of the Mac's HD and on both occasions, I found that there was this problem which came up under 'verify disk permissions' : permissions differ...[see screenshot, if this could help in diagnosing what the problem is]:
Of late I have been going to different sites on the net such as news and You Tube and is this problem related to such internet related issues? I would like to be enlightened in this matter since I have not experienced this problem earlier.

Whilst there is little point in using 'verify permissions' (you might as well go straight to 'repair permissions'), you can in fact ignore these messages:
As long as the report ends up with 'Permissions repair complete' then, as far as permissions go, you are fine. You can ignore the various statements in the report:
Permissions you can ignore on 10.5 onwards:
http://support.apple.com/kb/TS1448
Using 'should be -rw-r--r-- , they are lrw-r--r--' as an example, you will see the that the permissions are not changed, but the | indicates a different location. This is because an update to Leopard onwards changed the location of a number of system components.
Poster rccharles has provided this description of what it all means:
drwxrwxrwx
d = directory
r = read
w = write
x = executeable program
drwxrwxrwx
| | |
| | all other users not in first two types
| |
| group
|
owner
a little more info
Before the user had read & write. A member of the group had read.
After, only the user had read & write.

To build the organization's Active Directory permissions are what we need

To build the organization's Active Directory permissions are what we need

what is your actual question? Can you be more specific?
Santhosh Sivarajan | Houston, TX | www.sivarajan.com
ITIL,MCITP,MCTS,MCSE (W2K3/W2K/NT4),MCSA(W2K3/W2K/MSG),Network+,CCNA
Windows Server 2012 Book - Migrating from 2008 to Windows Server 2012
Blogs: Blogs
Twitter: Twitter
LinkedIn: LinkedIn
Facebook: Facebook
Microsoft Virtual Academy:
Microsoft Virtual Academy
This posting is provided AS IS with no warranties, and confers no rights.

Java 7 u45 gives yellow warning about a missing Permissions attribute that is not missing

Hi!
I have a Swing application distributed with Java WebStart. Since update 45 I can't get rid of the yellow warning about a missing permissions attrribute. I have reduced the JNLP to only reference a single signed jar that has the following manifest:
Manifest-Version: 1.0
Implementation-Vendor: Gunnar Grim
Ant-Version: Apache Ant 1.9.1
Implementation-Title: DOI Studio
Implementation-Version: 5.2.5.1310201149
Specification-Vendor: Gunnar Grim
Application-Name: DOI Studio
Permissions: all-permissions
Specification-Title: DOI Studio
Created-By: 1.7.0_45-b18 (Oracle Corporation)
Specification-Version: 5.2.5
Codebase: *
Name: ....
SHA-256-Digest: ...
Clearly, both Permissions and Codebase are there. Still I get the warning. Anyone knows if this is bug in Java WebStart?
TIA,
Gunnar

Are you signing your app with a 3rd party codesigning certificate ? Self-signing wont work anymore.

Permissions differ on "Library/Internet Plug-Ins/JavaAppletPlugin.plugin"; should be... WHAT IS THE PROBLEM?

Permissions differ on “Library/Internet Plug-Ins/JavaAppletPlugin.plugin”; should be... WHAT IS THE PROBLEM?

My imac OSX 10.8.2 IS awfully slow for opening the different applications, internet etc. I am running the CP monitor and everything seems fine. My speedtest is over 20MB
The hard disk is not even half full.
I have ran a utility check and I receive the same message as zolala. I am trying to repair as I am writing this post and it goes on and on. Not sure it will finish...

What to do about warning "directory permissions differ on..." ?

Similar Messages

Maybe you are looking for