NSLog();

7 Comments »

7 Responses to "RealPlayer WTF"

1. | Reply richard
   Posted 01 Feb 2006 at 10:09am #
   

   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. | Reply Andy Lee
   Posted 01 Feb 2006 at 10:30am #
   

   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. | Reply Erik J. Barzeski
   Posted 01 Feb 2006 at 11:43am #
   

   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. | Reply Erik J. Barzeski
   Posted 01 Feb 2006 at 12:10pm #
   

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

5. | Reply Andy Lee
   Posted 01 Feb 2006 at 12:30pm #
   

   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. | Reply Anon
   Posted 01 Feb 2006 at 8:33pm #
   

   Bad prebinding?

7. | Reply encro
   Posted 04 Feb 2006 at 9:32am #
   

   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