Please explain what you mean by "relaunch Finder".
Anybody else: when you see that, how do you interpret it?
Um.... either this:Please explain what you mean by "relaunch Finder".
Anybody else: when you see that, how do you interpret it?
Hmm... while I'm usually of the "don't worry too much about it" school, if you completely wiped the drive (and didn't restore your previous users/settings from a backup), and you haven't installed any system add-ons at all, I'm actually kind of inclined to suspect some sort of graphics card issue. And I know for a fact that those can sometimes get by the Hardware Test--I've seen systems with such severe graphic corruption you could barely read the Hardware Test screen, yet it said there was no issue.I tried the Hardware Test and it showed everything to be ok so I guess it's not a problem with the laptop...
Um.... either this:
or this:
or this:
followed by launching Finder.
As a general rule, if Finder crashes or is "relaunched" via the Dock, it will re-start automatically. If you manually quit it, however, it will stay closed until its Dock icon is clicked. (I believe, though am not bothering to test, it will also open automatically if no other apps are open, so you don't get stuck on a "dead" desktop).And I've never noticed the Quit Finder menu command either! Does it then "relaunch" automatically?
And I've never noticed the Quit Finder menu command either!
Um, that would be because it's not there! ...neither is the Launch Finder contextual menu choice. Now I don't feel so clueless, just ancient. After all, I still use 10.5.8, oh my!
Hmm... while I'm usually of the "don't worry too much about it" school, if you completely wiped the drive (and didn't restore your previous users/settings from a backup), and you haven't installed any system add-ons at all, I'm actually kind of inclined to suspect some sort of graphics card issue. And I know for a fact that those can sometimes get by the Hardware Test--I've seen systems with such severe graphic corruption you could barely read the Hardware Test screen, yet it said there was no issue.
Question: Have you tried playing any 3D games or doing anything graphically intensive like that? Curious if there would be glitches if the graphics hardware was pushed harder.
Maybe it's fine to ignore it, but I'd personally call Apple while it's still under warranty--better than ignoring a minor problem that turns into a major one after your warranty has expired.
If, on the other hand, you bought AppleCare, then you've got three years to ignore it, so if you're ok with that no issue.
And, just to be clear, it COULD, in theory, be a software glitch--might just stop happening after 10.6.5 is released or something. I'm just paranoid about things that could be hardware and are still under warranty.
I know, shame shame shame on me for bringing this back to life, but I just wanted to share what caused the problem for other Mac users that experience this and as a warning to others:
Do not, ever, use a program that removes languages or architectures (PPC for example) from your system. Despite the fact that you may not need them, apparently removing them may cause Finder (and other applications) to glitch up constantly. It's not worth the extra savings in space.
Avoid:
Monolingual especially and any apps similar to it.
Fix if you're having this problem:
A reinstall will fix the problem. Not much else will.
I've used Monolingual for years with zero problems, and yes, I've deleted the PPC architectures. That's not what caused your Finder issues.
If Monolingual was the cause of the problems, they would cause the same problems for everyone else that uses it. It must be something specific that you deleted, not just the general use of Monolingual.It is definitely what caused my Finder problems. I had the same problem occur on that Macbook Pro, my current iMac, and my Mac Mini. I used monolingual on all three of them, and after reinstalling Snow Leopard on all three, and not using the application, the problem hasn't occurred since.
Not necessarily, just as a simple software update doesn't cause problems for 99.9% of the people who run it, but something occasionally does go wrong with it. I'd be skeptical if you showed me two stock Macs with the same exact OS build, one of which was hosed running Monolingual and another not, but there are a lot of other variables involved here that could have caused Monolingual to do something it shouldn't have.If Monolingual was the cause of the problems, they would cause the same problems for everyone else that uses it.