I came across this issue on my laptop the other day where OS X thought my Desktop was actually a package. If you’re unfamiliar with packages (or bundles), they are really just directories containing more files and directories, but by default they open with an application or they are themselves an application. In fact, if you right click on almost any Mac application, there is an option to “Show Package Contents.” That’s all great and wonderful, but the Desktop is not supposed to be a package. So how the heck do I fix this? Well, my normal *nix intuition was that it was a permission, but I couldn’t turn anything up. After a bit of digging, I found a ManPage with all the details on these extra file/directory attributes.
Here’s how I fixed it:
- Open Terminal (Located in your /Applications/Utilities directory)
- setFile -a b Desktop/ (by default a new terminal will be in your users directory)
Well, I’m happy because I have access to my Desktop again. I’ll stop nerding out now and let you back to your life!
So I’ve been on and off playing with some of the developer builds of Chromium on Mac. For folks who don’t know, Chromium is the name of the open source browser that Google builds Chrome from. There isn’t an official Chrome for Mac yet but the source for Chromium has been in a state such that you can build the browser for a few months now. Well I just found out that I’ve been wasting my time doing my own builds because there is a buildbot up now.
Trust me, the browser is still far from prime time. Things like plugins don’t work yet – so you won’t be watching any Single Ladies videos quite yet, but it is still fun to play around with and wonderful to see that even in it’s early stages it is QUITE snappy at rendering web pages!
To download a copy go to http://build.chromium.org/buildbot/snapshots/sub-rel-mac/ and then select the most recent build number and download the zip. Enjoy!