Terminal opens when clicking desktop…: Apple Support Communities. This is an interesting problem. Apparently the solution is from Linc below.
Enter the following command in the Terminal window in the same way as before (no typing):
xattr -c ~/Desktop
Try the action again. If the same thing happens, relaunch the Finder by selecting Apple menu > Force Quit… > Finder and pressing return or clicking Relaunch.
Finder right click \. Baltwo has the solution. I have never seen this solution before. Great work.
FWIW, there’s a com.apple.LaunchServices.plist in my user’s Preferences folder.
Launch the Terminal app in /Applications/Utilities/, copy & paste in this one-liner, hit the return key, quit Terminal, and restart:
/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/Support/lsregister -kill -r -domain local -domain system -domain user
It was interesting when I updated my computer to the newest current version of Safari 5.1.1. It seemed to cause my mac to freeze. I didn’t see the Finder, and there was no sign that the computer was responding even after waiting for 15 minutes. I tried to bring up the Force Quit Application dialog box but was unable. I held down the power key for 10 seconds and the computer turned off. When I started the computer up, everything seemed fine.
I had no other applications running when I did the update. Strange for Safari to cause the system to crash. I wonder why?
Ok. Looks like I made a mistake above. Just to double-check I ran software update again. Guess what? It said that Safari was 5.1.2. So the first time I asked Software Update to install the update, it froze and didn’t complete. The second time I asked it to update, it applied the update and restarted the computer. This is the first time I remember having a problem with Software Update. Well really a problem with the Safari installer from that. I wonder why?
Force Quit Applications warning on iMac…: Apple Support Communities. Interesting that it lists 3 programs that must be memory leakers. I seem to do better avoiding Firefox and Safari. Can’t really avoid the Finder but that is nice to know that restarting it may fix issues. The solution is below:
I just upgraded the recent version of Safari 5.1.2 for Snow Leopard and it’s supposed to fix the memory leak that’s eating up my RAM. Hopefully that will fix the problem.
You can’t use AirDrop over ethernet, so if you try to connect to a wired machine, it won’t work. Kellow goes into more detail below.
I might have found the reason behind the aforementioned behavior:
The AirDrop feature is apparently a Lion/AirPort-feature, and not a Lion/network-feature, meaning, if the iMac is connected to the network through a cable (RJ45), the above described behavior is the result.
The third issue mentioned, is apparently just how AirDrop works. AirDrop needs to be “activated” by Finder, which opens a ad hoc network though the AirPort. This does limit the use cases a lot.
Now, if only Apple would consider implementing AirDrop in iOS, the use cases would make a lot more sense…
