com.apple.flashupdater problem

I don't have that file, so I'm guessing that it's installed temporarily in order to update Flash, if necessary, and then deleted. And yes, apparently it won't work on a case-sensitive filesystem.

Back up all data if you haven’t already done so. Before proceeding, you must be sure you can restore your system to the state it’s in now.

Launch the Terminal application in any of the following ways:

☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)

☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.

☞ If you’re running Mac OS X 10.7 or later, open LaunchPad. Click Utilities, then Terminal in the page that opens.

Drag or copy — do not type — the following line into the Terminal window, then press return:

sudo launchctl remove com.apple.flashupdater

You'll be prompted for your login password, which won't be displayed when you type it. You may get a one-time warning not to screw up. You don't need to post the warning. If you don’t have a login password, you’ll need to set one before you can run the command.

Now look in the following folders for an item named "com.apple.flashupdater.plist":

/System/Library/LaunchDaemons

/Library/LaunchDaemons

If found, delete it. You'll again be prompted for your password.

Make sure Flash is up to date.

Here's a complete list of files installed by the FlashUpdateTool package:

/System/Library/CoreServices/FlashUpdaterAgent.app

/System/Library/LaunchAgents/com.apple.flashupdater.agent.plist

/System/Library/LaunchDaemons/com.apple.flashupdater.plist

/usr/libexec/FlashUpdater

/usr/libexec/PerUserLaunchEnv

Normally those files would be deleted automatically. You'll have to delete them yourself.

Unless you're doing something very unusual, there's no reason for your boot volume to be formatted as case-sensitive.

As long as you're sure there won't be any name conflicts, you can back up, reformat as case-insensitive, and restore.

tomcwilson wrote:

did apple just not test on case senstive file systems ?

Apparently Apple just did not test this on case-sensitive file systems.

See this post: https://discussions.apple.com/thread/3952378?tstart=0

Funny :-) I had these messages in my log as well and just created a dummy /usr/libexec/flashupdater to shut up the syslog. But then I had a better idea, create a symlink to the real FlashUpdater:

cd /usr/libexec/

sudo ln -s FlashUpdater flashupdater

Well, the FlashUpdater ran one more time, and then removed itself:

May 18 12:12:52 disko com.apple.flashupdater[56340]: /usr/libexec/flashupdater: line 3: 6400: command not found

May 18 12:12:52 disko com.apple.launchd[1] (com.apple.flashupdater[56340]): Exited with exit code: 127

May 18 12:12:52 disko FlashUpdaterAgent[240]: Checking in failed: -308

And com.apple.flashupdater is gone too! Not sure what to make of all this, but the logs a quiet now 🙂

But /usr/libexec/flashupdater still exists on your system and is a bad link. If Apple releases this tool again, and uses "flashupdater" as the file name, you could have another mystery on your hands. I suggest removing that link.

Oh, yes, did that as well. Forgot to mention it, sorry.

And you are right 🙂.

This experience with a software misnaming (flashupdater != FlashUpdater) is the proof that case sensitive filesystem are usefull.

Bad software editors don't make quality check on their file naming policy. To detect them a good practice is to use "case sensitive filesystem". Of course you won't detect all poor quality softwares,

but the worst will simply choke very early,

many malware will also choke very early (apparently they don't run QC either 🙂).

I'm not trying to stray too far off topic here, but why do you think a case-sensitive filesystem is strange. --legitimate opinion solicitation 🙂

This is not an Apple issue. It's an Adobe issue. CS5 does not work on case-sensitive filesystems either. The refuse to fix it however. Case-sensitve I much prefer but I am forced to go without if I want anything from Adobe.

Hopefully HTML5 will kill Flash off anyway.