Subscribe to
NSLog(); Header Image

RealPlayer WTF

For some reason, "RealPlayer" (the latest version) won't launch from my /Applications folder when it's named "RealPlayer." I'm told: You cannot open the application "RealPlayer" because it may be damaged or incomplete.

Renaming it "Real Player" or "RealPlayer X" or "Bob" allows the application to launch and work as expected.

WTF? Permissions are fine (they're repaired nightly). This makes almost no sense!

7 Responses to "RealPlayer WTF"

  1. Um, of course it makes sense. It's RealPlayer, of course it would have problems with something as easy as launching using it's own name. 🙂

    Seriously though, I have no clue. That's quite strange.

  2. Weird. I could sort of understand if a file got corrupted, except why the heck would renaming it "fix" the problem?

    What does Console say?

  3. Console says nothing (or I'd have posted that info here too). Keep in mind too that this isn't a crash, but a failure to launch for some reason. Perhaps my launch services database is somehow screwed up?

  4. I cleared all of my caches from ~/Library and /Library and now it launches when called "RealPlayer." Repeatedly.

  5. Well, there might have been a hint in Console even if it wasn't a crash. Just asking a stab-in-the-dark question.

    As for why clearing caches would fix it... when in doubt, I usually form a conspiracy theory. Some hacker is playing an early April Fool's on you. 🙂

  6. Bad prebinding?

  7. The most effective way to reset yor launch services database is the following terminal command:

    /System/Library/Frameworks/ApplicationServices.framework/Frameworks/LaunchServices.framework/Support/lsregister -kill -r -domain local -domain system -domain user