Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

younker

macrumors member
Original poster
Dec 8, 2006
94
24
After upgrade to Beta 4, when I run xattr, I always got the error of bad file descriptor.

Just wonder to know whether this is just my case.
 

mikejrslac

macrumors newbie
Jun 14, 2018
16
8
I have the same problem with xattr in Monterey with “bad file descriptor” error. No problem in Big Sur.
 

gilby101

macrumors 68030
Mar 17, 2010
2,921
1,616
Tasmania
Can you guys, give an example xattr command which fails, the error message, and the output of ls -le@ for the file. And just be certain the output from the command: which xattr
 

08380728

Cancelled
Aug 20, 2007
422
165
xattr -cr
Bad file descriptor
ls -le@ /Applications/ForkLift.app
total 0
drwxr-xr-x@ 10 randomuser admin 320 6 Jul 22:28 Contents
com.apple.quarantine 82

(actually sudo failed as well, thought it worked previously)
 

gilby101

macrumors 68030
Mar 17, 2010
2,921
1,616
Tasmania
Yes, I can reproduce the error with
xattr -cr /Applications/ForkLift.app

But no errors with
xattr -c /Applications/ForkLift.app

It seems to be the recursive option which causes trouble.

Why the r? Do any files inside the app bundle have xattrs? Not that I could find.
 

visualseed

macrumors 6502a
Dec 16, 2020
921
1,911
Yes, I can reproduce the error with
xattr -cr /Applications/ForkLift.app

But no errors with
xattr -c /Applications/ForkLift.app

It seems to be the recursive option which causes trouble.

Why the r? Do any files inside the app bundle have xattrs? Not that I could find.

Yes, I dropped the -r argument and it worked fine
 
  • Like
Reactions: gilby101
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.