2

For some reason, opening a folder in the Finder from the command line with

open path/to/folder

does not work anymore for subdirectories of my Documents folder:

% cd
% mkdir Documents/TestDir
% open Documents/TestDir 

opens a new Finder window, but that does not show the “TestDir” folder but the “Computer” folder.

The system log shows these error messages about “untranslocated nodes”:

% log stream --predicate 'process == "Finder" and messageType == error' 
Filtering the log data using "process == "Finder" AND logType == 16"
Timestamp                       Thread     Type        Activity             PID    TTL  
2022-04-10 14:07:42.994683+0200 0xb6f5     Error       0x0                  444    0    Finder: (LaunchServices) [com.apple.launchservices:default] capability properties: could not find untranslocated node for <FSNode 0x6000035b9aa0> { isDir = ?, path = <private> }, proceeding on the assumption it is not translocated: Error Domain=NSPOSIXErrorDomain Code=2 "No such file or directory"
2022-04-10 14:07:42.994777+0200 0xb6f5     Error       0x0                  444    0    Finder: (LaunchServices) [com.apple.launchservices:default] capability properties: could not find untranslocated node for <FSNode 0x6000035b9aa0> { isDir = ?, path = <private> }, proceeding on the assumption it is not translocated: Error Domain=NSPOSIXErrorDomain Code=2 "No such file or directory"
2022-04-10 14:07:43.003949+0200 0xb6f5     Error       0x0                  444    0    Finder: (LaunchServices) [com.apple.launchservices:default] capability properties: could not find untranslocated node for <FSNode 0x60000358d0c0> { isDir = ?, path = <private> }, proceeding on the assumption it is not translocated: Error Domain=NSPOSIXErrorDomain Code=2 "No such file or directory"
2022-04-10 14:07:43.004319+0200 0xb6f5     Error       0x0                  444    0    Finder: (LaunchServices) [com.apple.launchservices:default] capability properties: could not find untranslocated node for <FSNode 0x60000358d0c0> { isDir = ?, path = <private> }, proceeding on the assumption it is not translocated: Error Domain=NSPOSIXErrorDomain Code=2 "No such file or directory"

Running First Aid on Macintosh HD (in Recovery mode) did not report any errors.

The problem occurs only with (nested) subdirectories of “Documents”. Opening “Documents” itself or any other folder works correctly.

Sometimes it works if I specify the "-R" flag explicitly, e.g.

% open -R Documents/TestDir 

but not always.

My configuration: macOS 12.3.1 on a MacBook Air (Retina, 13-inch, 2020).

Any ideas how to fix (or further investigate) this problem are welcome.

6
  • It looks like the same (unsolved) problem reported here: Finder cannot navigate to folders inside ~/Documents – I had not noticed that when posting this question.
    – Martin R
    Apr 13, 2022 at 13:04
  • I can confirm what you said in other thread. Problem happens when Documents is NOT in the sidebar. macOS 12.3.1. That might be a bug.
    – Gilby
    Apr 15, 2022 at 4:25
  • @Gilby: Thanks for the confirmation.
    – Martin R
    Apr 15, 2022 at 7:55
  • Weird. I don't get the same problem for Downloads or Desktop which, like Documents, are a bit special. Surprised this has not been highlighted before as it applies to both open and Finder's Go to Folder. I will do a Feedback to Apple.
    – Gilby
    Apr 15, 2022 at 10:08
  • @Gilby: Yes, only Documents is affected, nothing else, as far as I can see.
    – Martin R
    Apr 15, 2022 at 11:34

1 Answer 1

2

It looks like a bug in macOS 12.3.1, but apparently it happens only if the “Documents” folder is not shown in the Finder sidebar.

So there is a workaround: Make sure that the “Documents” folder is selected in the “Sidebar” tab of the Finder preferences:

enter image description here

1
  • Other answers (perhaps providing more insight on the problem) are welcome, of course.
    – Martin R
    Apr 15, 2022 at 7:55

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .