# NOTE: we are only echoing with sudo, the other commands are run as user # really crazy: modify the command line, set sudocmd=sudo. # repeat several times: last terminal command line (hit KEY UP in Terminal.app), in info window verify place (Where:) is now '/foo/bar', close info window It's simply wrong and causes problems in many Finder operations: opening files, renaming, copying, moving, applying. # in info window: verify place (Where:) is now '/foo/bar' -> This is the issue. # repeat last terminal command line (hit KEY UP in Terminal.app) # open info window with the last terminal command line (KEY UP in Terminal.app) # share folder '/Volumes/Test/foo/bar/baz' with next steps. # repeat several times: last terminal command line (KEY UP in Terminal.app), in info window verify place (Where:), close info window # in info window: verify place (Where:) is '/Volumes/Test/foo/bar' -> This is how it should be, everything looks correct. Sudocmd= $sudocmd echo start test $sudocmd diskutil unmount Test sleep 3 $sudocmd echo some command with or without sudo diskutil mount Test osascript -e 'set macpath to POSIX file "/Volumes/Test/foo/bar/baz" as alias' -e 'tell application "Finder" to open information window of macpath' # Now begin testing step by step, comments (#) contain instructions. Hdiutil create -size 10m /tmp/Test.dmg -ov -volname "Test" -fs HFS+ TIP2: Manually closing the info window can be omitted, cause its done automatically on unmount. TIP: Copy/paste into a text editor that has line wrapping disabled. For effective reproducibility I tried to put the steps into command line. I enabled sharing it and the issue was present again.įinally I was able to reproduce the issue with a dmg and a newly created folder in that dmg: I disabled sharing of that folder and the issue was gone. I then remembered that this folder was a shared folder for local networking. I did a binary search by moving around folders and subfolders and so realized that a certain subfolder ‘/Volumes/FMB/data/marc/Movies/x/mov/cool_movie/’ was the only folder needed to reproduce the issue. As I mentioned before it seemed to be related to that folder ‘/data’.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |