Wrong permissions????

hi all
when i try to drag photos from i photo to the desktop it wont do it cos it says i have the wrong permissions, they re my photos and its my f@@@n computer what more permission do i need
thanks all
apologies for outburst, i m having a very frustrating computer morning

karlos1544
Download BatchMod from
http://macchampion.com/arbysoft/
And apply it to the iPhoto Library Folder using the settings found here:
http://homepage.mac.com/toad.hall/.Pictures/Forum/BatChmod.png
(Credit to Old Toad for this one).
Regards
TD

Similar Messages

When I repair disk permissions using Disk Utility and it says it's completed the task, I click on it again and it repairs more. This has been going on for hours now. Could there be that many wrong permissions? Should it get to "all repaired" eventually?

When I repair disk permissions using Disk Utility and it says it's completed the task, I click on it again and it repairs more. This has been going on for hours now. Could there be that many wrong permissions? Should it get to "all repaired" eventually?

It's normal behavior. You don't have to worry about. Most of what's listed is just a report of what the utility finds., not necessarily that there is omething wrong.
If you want to find out more, read the link below, or see the More Like This links on this page.
http://support.apple.com/kb/TS1448?viewlocale=en_US

** (firefox:6083): WARNING **: Wrong permissions for /home/kevin/tmp/orbit-kevin

Firefox is starting to crash a bunch. I am running pclinuxos and after the last crash I typed "firefox" in konsole and got the following:
** (firefox:6083): WARNING **: Wrong permissions for /home/kevin/tmp/orbit-kevin
What is happening?
I checked the permission for that folder and it says kevin for user and group, and owner, group and others can view and modify content.
I have the following extensions:
downloadhelper 4.8.6
evernote
firefox sync 1.7
quickprint 0.1.2

Uups. Now, why didn't I think of that? Last update had 1GB of size installed. pacman -Scc fixed it, of course.

Time Capsule and Time Machine Wrong Permissions 10.6.6

Well, I have a 2TB TimeCapsule, and I used to backup my external Drobo HD with no problems, that means, my main drive is my Drobo and backup disk is internal TC 2TB HD.
From the last Airport or system update, it started to backup with wrong permissions, so it keeps backing up, but I cant access it back anymore.
So I tried the hard way, I reinstalled a clean Snow Leopard on my iMac and did the combo update to 10.6.6, then I erased the TimeCapsule internal HD and did all the Time Machine backup again (about 1.2TB). Great, almost 2 days, and now the same problem! Here is a picture of what is going on:
http://dl.dropbox.com/u/536514/imagens/shot2.jpg
I just can't access the backup data because its backing up with root owner, with no access to other users, so my main user can't access any data from Time Machine.
Course, if I manually change every time all the permissions, it will keep to backup with the wrong permissions and I will not have access to data again.
Here is another picture:
http://dl.dropbox.com/u/536514/imagens/shot1.jpg
So, how to solve and repair definitely the permissions issues with TC?!
Thanks in advance!

Ok guys, I managed to resolve this issue (hopefully you did too, but for those who might still be experiencing it), but it was a while ago so I don't remember exactly what the fix was... I think it went something like this:
*If you have many folders to do, it might take some time, and I'm not sure if there is a better way to do it, but here is my fix since nobody has proposed anything else...
1) Grab the blocked file in your TC and restore it to current Mac HD
2) Once it has transfered, locate it in Finder and check it's info (Command+I)
3) At the bottom of the pop-up window, you will have the list of "Sharing & Permissions" and there are good chances that in there, your current user (under the Name column) has "No access"
4) If need be, unlock the Preferences at the bottom right-hand corner (lock icon), to allow access to modify permissions. (This is were it gets fuzzy... I think you need to use the username and password that was used to create the folder back in the day...) Once it is unlocked, change the "Privilege" to "Read & Write" and you're all set to go! (I hope...)
Hope it works for you,
Matt

Wrong Permissions 10.9.3

Every time after repairing I've got this :
wrong permissions "Applications/Safari.app/Contents/Resources/Safari.help/Contents/Resources/inde x.html", should be lrwxr-xr-x, now -rwxr-xr-x
"private/etc/aliases" should be lrwxr-xr-x, now -rwxr-xr-x
Mac Pro 2010, 10.9.3 all updates, find my mac disabled

That's been an issue with Mavericks for some time now. It's been reported in the beta test program for several updates so Apple knows about it. It's nothing to worry about so just ignore it.

New account gets created with wrong permissions (777 instead of 755)

Hey Apple and Forum people, looks like there's a pretty bothersome error in the way that user permissions get set when you set a user's home folder to a drive partition.
By default, a user's home folder is supposed to get 755, with all of its subdirectories (excluding Public and Sites) as 700. But if you set up a new user and point his/her home folder to a partition or a separate drive, the folder is set to 777 - meaning that anyone can read, write, and execute any file they'd like to from that drive.
Given the sensible defaults of 755 during normal user creation, I can't believe this was intentional. And if it was intentional, then it's wrong and ought to be changed.

Set the permissions on the other volume's root directory the same as the boot volume.
owner:root
group:admin
chmod 1775
Make a /Users directory on the other volume and
set permissions same as on the boot volume,
owner:root
group:admin
chmod 755
create your new user directory in the /Users directory on the other volume.

ITunes on Win 7 64 bit says file on locked disk or wrong permissions

I am using Windows 7 pro 64 bit.
I have been using iTunes forever without a problem,
Recently, probably after a version update, iTunes opens a small window and says iTunes is on a locked disk or the permissions are wrong.
I have read several so-called solutions on many forums and I have found nothing that either works or makes any sense.
I am running the latest version of iTunes. 10.4.0.80
I can play files that are allready in my libray and I can sysnc podcasts to my iphone 4 but I can no longer add any music files to iTunes.
I would really appreciate any help.

It may have something to do with AMDS not started.
Refer to this article:
iOS: Device not recognized in iTunes for Windows
http://support.apple.com/kb/TS1538

Newly imported photos in shared iPhoto library have wrong permissions

I have recently encountered some problems with a shared iPhoto '09 library. When I initially shared it by placing it in users/shared iPhoto prompted to fix the permissions and everything was hunky dory. However, it seems that any newly imported photos do not have their permissions set properly so that the other user of the library on my computer can't do useful things like edit or email the newly imported photos.
Looking inside the library reveals that the permissions on newly imported photos are set to read write for me as the owner and no access for 'everyone'. If I hold down cmd-opt and repair permissions it is all fine - until I import some new photos and then the permissions are wrong for those.
I noted this effect on a pristine iPhoto library that I created to test this as well as my venerable iPhoto library.
Is there something I can do to change this behaviour so newly imported photos get the correct permissions set and the shared user of this library (my wife) is able to edit and email photos I import (and, presumably, vice versa)?

I have made changes to permissions to my old library a number of times. Originally this was to enable sharing in earlier versions of iPhoto and it worked fine. For example I've added a group that consists of myself and my wife and given it read and write permissions and applied that to all enclosed items. I've also had iPhoto repair the permissions as per the startup options.
Notwithstanding this, I created a new library in my pictures folder; moved it to the shared folder; switched accounts and allowed iPhoto to repair permissions; switched back and then imported new photos. While most files and folders inside the package are OK (including any modified files and the enclosing originals/year/event folder) the actual original photo files themselves have the permissions problem. This seems to prevent emailing or editing by the other account.

Wrong permissions when it is built.

I maintain Vulturesclaw. http://aur.archlinux.org/packages.php?ID=14157
I was about to update but I've noticed on my old PKGBUILD though everything seems to be building fine, there is just one problem with the permissions on the $USERS/~ file. It resorts to being owned by root.
Can anyone see what I can do to change it, I have to admit I really struggled with this pkg first time around.
pkgname=vulturesclaw
pkgver=2.1.1
pkgrel=1
pkgdesc="An isometric graphics interface to Slashem."
arch=('i686' 'x86_64')
url="http://www.darkarts.co.za/projects/vultures/"
license=('custom')
depends=('sdl_mixer' 'sdl_ttf' 'sdl_image' 'libpng' 'flex' 'bison')
source=(http://usrsrc.org/svn/vultures/releases/$pkgver/vultures-$pkgver-full.tar.bz2)
md5sums=('3f0393e112407ae0e99b8da6784ec7d9')
build() {
mkdir -p $startdir/pkg/usr/bin
mkdir -p $startdir/pkg/usr/share/applications
mkdir -p $startdir/pkg/usr/share/icons/hicolor/48x48/apps
mkdir -p $startdir/pkg/usr/share/licenses
cd $startdir/src/vultures-$pkgver/slashem/sys/unix
sh setup.sh
cd $startdir/src/vultures-$pkgver/slashem/include
sed -e '/define HACKDIR/ s|/boot/apps/NetHack|/usr/share/vulturesclaw|' \
-e '/^# define COMPRESS\s/ s|/usr/bin/compress|/bin/gzip|' \
-e '/^# define COMPRESS_EXTENSION/ s|".Z"|".gz"|' \
-e 's|^/\* $#define DLB$ \*/|\1|' -i config.h
sed -e 's|^/\* $#define LINUX$ \*/|\1|' \
-e 's|^/\* $#define TIMED_DELAY$ \*/|\1|' -i unixconf.h
cd $startdir/src/vultures-$pkgver/slashem
sed -e '/^GAMEUID\s*=/ s|games|root|' \
-e '/^GAMEGRP\s*=/ s|bin|root|' \
-e '/^SHELLDIR\s*=/ s|/local||' \
-e '/^GAMEDIR\s*=/ s|/local/slashemdir|/share/vulturesclaw|' -i Makefile
make || return 1
make PREFIX=$startdir/pkg/usr install
cd $startdir/pkg/usr/bin
sed -e 's|^HACKDIR=.*|HACKDIR=/usr/share/vulturesclaw|' -i vulturesclaw
install -Dm644 $startdir/src/vultures-$pkgver/slashem/dat/license $startdir/pkg/usr/share/licenses/$pkgname/license
install -Dm644 $startdir/src/vultures-$pkgver/dist/linux/vulturesclaw.desktop $startdir/pkg/usr/share/applications/vulturesclaw.desktop
install -Dm644 $startdir/pkg/usr/share/$pkgname/vulturesclaw.png $startdir/pkg/usr/share/icons/hicolor/48x48/apps/vulturesclaw.png

It does, but the folder seems to be only created after first time ran, so unsure how I would implement it.
I tried to use the plain vulturesclaw but that refused to compile, seemed to be looking for headers in the wrong place.
Having just updated it, the final PKGBUILD
pkgname=vulturesclaw
pkgver=2.1.2
pkgrel=1
pkgdesc="An isometric graphics interface to Slashem."
arch=('i686' 'x86_64')
url="http://clivecrous.lighthouseapp.com/projects/11282-vulture-s"
license=('custom')
depends=('sdl_mixer' 'sdl_ttf' 'sdl_image' 'libpng' 'flex' 'bison')
source=(http://downloads.usrsrc.org/vultures/$pkgver/vultures-$pkgver-full.tar.bz2)
md5sums=('d31598c0e347648896c085fc961385d7')
build() {
mkdir -p $startdir/pkg/usr/bin
mkdir -p $startdir/pkg/usr/share/applications
mkdir -p $startdir/pkg/usr/share/icons/hicolor/48x48/apps
mkdir -p $startdir/pkg/usr/share/licenses
cd $startdir/src/vultures-$pkgver/slashem/sys/unix
sh setup.sh
cd $startdir/src/vultures-$pkgver/slashem/include
sed -e '/define HACKDIR/ s|/boot/apps/NetHack|/usr/share/vulturesclaw|' \
-e '/^# define COMPRESS\s/ s|/usr/bin/compress|/bin/gzip|' \
-e '/^# define COMPRESS_EXTENSION/ s|".Z"|".gz"|' \
-e 's|^/\* $#define DLB$ \*/|\1|' -i config.h
sed -e 's|^/\* $#define LINUX$ \*/|\1|' \
-e 's|^/\* $#define TIMED_DELAY$ \*/|\1|' -i unixconf.h
cd $startdir/src/vultures-$pkgver/slashem
sed -e '/^GAMEUID\s*=/ s|games|root|' \
-e '/^GAMEGRP\s*=/ s|bin|users|' \
-e '/^SHELLDIR\s*=/ s|/local||' \
-e '/^GAMEDIR\s*=/ s|/local/slashemdir|/share/vulturesclaw|' -i Makefile
make || return 1
make PREFIX=$startdir/pkg/usr install
cd $startdir/pkg/usr/bin
sed -e 's|^HACKDIR=.*|HACKDIR=/usr/share/vulturesclaw|' -i vulturesclaw
install -Dm644 $startdir/src/vultures-$pkgver/slashem/dat/license $startdir/pkg/usr/share/licenses/$pkgname/license
install -Dm644 $startdir/src/vultures-$pkgver/dist/linux/vulturesclaw.desktop $startdir/pkg/usr/share/applications/vulturesclaw.desktop
install -Dm644 $startdir/pkg/usr/share/$pkgname/vulturesclaw.png $startdir/pkg/usr/share/icons/hicolor/48x48/apps/vulturesclaw.png
As you can see I'm doing some sed in the makefile, I suspect changing the GAMEUID would work, but some how that doesn't sound like the solution or would I even know what to.

The last ship, season 2, ep 5 is not working - wrong permissions have been set to the episode

I can watch every other episode apart from this one, I know some access rights/permissions are set wrong atm for this episode because I get a different message on the right hand side of the screen it says "You will need to be a Sky TV customer with the relevant pack to watch this programme." Also something else is wrong with the title, the webpage shows it as "The Last Ship The Last Ship Series 2 Ep 5 Last Ship, The 5" . Sky1 - 1st Broadcast = Aug 2nd 2015 - Available for 29 days - Availability = Free

Seriously. I called up yesterday and nothing!!Common+man+-+common+sense wrote:
This has clearly been known about for a week now, so when are you going to get it sorted Sky?

/dev/video0 and wrong permissions

Hi.
I have a usb webcam (/dev/video0, uvcvideo module)
After latest updates, /dev/video0 permissions are wrong (group root, access None instead of group Video, access RW)
Reloading uvcvideo module fixes the permissions.
This happens randomly, some times the permissions are right, other wrong, and i need to reload the module or do:
chgrp video /dev/video0
chmod 660 /dev/video0
I am in the 'video' group.
Never had this problem before.
Is this a udev problem? Kernel module problem?
Thanks.
Last edited by tritonas00 (2013-10-05 16:43:12)

I've read some forum posts that suggest that being in the video group (or audio etc.) can actually cause problems for you now. Try removing yourself from the group, log out then back in again, and see if the problem goes away.
Last edited by skottish (2013-10-05 17:44:51)

[SOLVED] Wrong permissions on fail2ban.sock

I have a problem with fail2ban. For some reason fail2ban creates its socket in /var/run/fail2ban with chmod 1700 and fails2start because it can't read from it.
If I chmod 1777 the socket everything works fine, but that's not very reliable. Any idea what could be wrong here?
EDIT: Nevermind, I just needed to run fail2ban-client as root.
Last edited by fsa (2010-03-26 01:38:32)

Post the output of 'pacman -Q systemd'.
Edit:
Ledti wrote:Err, systemd 207 hasn't even been announced/released yet as far as I know. And according to this, testing is still on version 206.
+1 ;P
Last edited by karol (2013-07-26 21:11:27)

Disc Utility always set wrong permissions of the startup disc

The permissions of the startup disc should be "drwxrwxr-t 39 root admin", right?
But everytime I repair my permissions with disc utility I get the (german) message:
Benutzer unterscheidet sich für ., Soll-Wert: 501, Ist-Wert: 0
Die Gruppe unterscheidet sich für ., Soll-Wert: 501, Ist-Wert: 80.
Die Zugriffsrechte unterscheiden sich für ., Soll-Wert: drwxr-xr-x , Ist-Wert: drwxrwxr-t .
And the permissions of the startup disc are set to:
drwxr-xr-x 39 Nomis101 Nomis101
(I've read that out with "$ ls -ld /")
Than I "repair" the permissions with "$ chmod 1775 /". And next time I use disc utility I have the same again.
I've repaired the permissions in single user mode, I've booted from the install DVD and reseted my ACLs, I've removed my ACLs. But nothing seems to help.
Sometimes I also have the issue that I cannot move any file on my desktop anymore or that I have suddenly no write permissions in the folder /Volumes/Macintosh HD
I suspect MacPorts 1.7 or Mercurial as the malefactor, because the issues accumulate after I've done something with MacPorts (or Mercurial). But I'am not sure with that.

{quote:title=V.K. wrote in another thread...:}If I'm not mistaken you told me once a while ago how to modify permissions database which seems to be required there.{quote}
Hmm, that's actually a bit of a tough one - Sorry, but I think it's beyond me.
My understanding of the permissions database consists of only what I have been able to piece together from tinkering, and while I have been able to edit individual entries and have "repair permissions" behave as expected with the edits, "/" is a bit different.
Basically, every time something is installed that results in an update to the permissions database, entries are added, i.e. the entry for a file isn't edited but rather a whole new entry is added. That applies to a given file in the update, as well as every folder on the path to that file. Since installations are pretty much all rooted in "/", that means a new entry for "/" is created every time any installer updates the receipt database, and other things may add entries as well -- I have 88 entries for "/" in there on my system. This does't display all of the entries, but a slightly more user-friendly way is to view most of them is to use:<pre>
pkgutil --file-info /</pre>
I haven't dug that deeply, but I don't know what determines which entry will be used during the actual permissions verification / repair operation (it's been a while but I seem to recall that it wasn't as simple a matter as "most recent", for example), so figuring out which one to edit might be a challenge.
And there are cases like "/" where there are entries in the database, but as you pointed out, that seem to be ignored when repairing of verifying permissions, and I have no idea what flags the system to ignore those.
Interestingly, of the 88 entries on my system, 83 call for "1775" permissions, but 5 of them (mostly "Safari" updates but also the "BaseSystem" package) actually say the permissions should be "1755"...
I think for the OP, the bigger issue is trying to figure out (and stopping) whatever it is that keeps wrecking security by changing the ownership to the user...

Wrong permissions after 10.5.3 update

When I do permissions repair after the 10.5.3 update I get a number of persisting errors (I include the log below). Anybody else seen that? Is there a way to fix those?
Thomas
The Disk Utility Log:
Repairing permissions for “Macintosh HD”
Reading permissions database.
Reading the permissions database can take several minutes.
Permissions differ on "usr/lib/libruby.1.dylib", should be lrwxr-xr-x , they are -rwxr-xr-x .
Permissions differ on "usr/bin/update_prebinding", should be lrwxr-xr-x , they are -rwxr-xr-x .
Permissions differ on "usr/lib/libproc.dylib", should be lrwxr-xr-x , they are -rwxr-xr-x .
Permissions differ on "usr/libexec/cups/filter/rastertodymo", should be lrwxr-xr-x , they are -rwxr-xr-x .
Permissions differ on "System/Library/Printers/Libraries/convert", should be lrwxr-xr-x , they are -rwxr-xr-x .
Permissions differ on "System/Library/CoreServices/dotmacsyncclient", should be lrwxr-xr-x , they are -rwxr-xr-x .
Permissions differ on "usr/bin/testrb", should be lrwxr-xr-x , they are -rwxr-xr-x .
Permissions differ on "usr/bin/ruby", should be lrwxr-xr-x , they are -rwxr-xr-x .
Permissions differ on "usr/bin/ri", should be lrwxr-xr-x , they are -rwxr-xr-x .
Permissions differ on "usr/bin/rdoc", should be lrwxr-xr-x , they are -rwxr-xr-x .
Permissions differ on "usr/bin/irb", should be lrwxr-xr-x , they are -rwxr-xr-x .
Permissions differ on "usr/bin/erb", should be lrwxr-xr-x , they are -rwxr-xr-x .
Permissions differ on "usr/bin/pydoc", should be lrwxr-xr-x , they are -rwxr-xr-x .
Permissions differ on "usr/bin/newaliases", should be lrwxr-xr-x , they are -rwxr-xr-x .
Permissions differ on "usr/bin/mailq", should be lrwxr-xr-x , they are -rwxr-xr-x .
Permissions differ on "usr/bin/ldapadd", should be lrwxr-xr-x , they are -rwxr-xr-x .
Permissions differ on "System/Library/Frameworks/Automator.framework/Frameworks/MediaBrowser.framewor k/Versions/A/MediaBrowser", should be lrwxr-xr-x , they are -rwxr-xr-x .
Permissions differ on "Library/Printers/EPSON/LaserPrinter/GD2/filter/pdftoescpage", should be lrwxr-xr-x , they are -rwxr-xr-x .
Permissions differ on "usr/X11/lib/libGLU.1.3.dylib", should be lrwxr-xr-x , they are -rwxr-xr-x .
Permissions differ on "usr/X11/lib/libGL.1.2.dylib", should be lrwxr-xr-x , they are -rwxr-xr-x .
Permissions repair complete

You are absolutely correct. I got it backwards.
I checked on my machine
[16:15 root@mpro] ls -al /usr/bin/ruby
lrwxr-xr-x 1 root wheel 76 Feb 27 22:23 /usr/bin/ruby -> ../../System/Library/Frameworks/Ruby.framework/Versions/Current/usr/bin/ruby
This is the actual binary:
-rwxr-xr-x 1 root wheel 38304 Dec 6 2007 ruby
As you can see, 'ruby' appears to be from a pristine installation. (just looking at the date).
Maybe the original poster has installed some additional development packages from Apples Dev Site.
Message was edited by: pmau
Fixed attribution to point to the original poster. Sorry.

My preremove script fails because of wrong permissions

So I have postinstall and preremove scripts (one starts a service after installing it, the other stops the service before removing the files)
My postinstall script works fine and I am adding the preremove. Even though I make sure the preinstall script is 755, it ends up in /var/sadm/pkg/mypackage/install/preremove with permissions 644 after installation. pkgrm then fails to execute it saying "bad interpreter: Permission denied"
Can anyone think of a reason why this might be happening or how I can go about fixing it?
In my prototype I have this:
i preremove=./scripts/preremove.sh
i postinstall=./scripts/postinstall.sh
Message was edited by:
sunbie

The install and remove scripts are all run with a direct call from /bin/sh, so the permissions should not be an issue here. In looking at my desktop system, almost all preremove scripts are not directly executable (mode 444).
Try running pkgrm with the -v option, which will show what it's trying to do when executing the preremove script.
-- Alan

Wrong permissions????

Similar Messages

Maybe you are looking for