March 15, 2011

CodeBar Issues

This information is for those who cannot launch CodeBar from Preferences window.

I contacted Apple technical support and we investigated into this. It seems like the problem origins from ACL that may be “corrupted” either by the Operating System either by the Time Machine.

Apple hackers propose to fix ACL by executing the following commands in the (please do not forget to omit the leading “$ ”):

$ chmod -a# 0 /var/db/launchd.db/$UID
$ chmod -a# 0 /var/db/launchd.db/$UID/overrides.plist

And below are some additional commands for those who use the Time Machine:

$ xattr -d /var/db/launchd.db/$UID
$ xattr -d /var/db/launchd.db/$UID/overrides.plist
$ xattr -d /var/db/launchd.db/$UID
$ xattr -d /var/db/launchd.db/$UID/overrides.plist

Now you should be able to enable and disable CodeBar in Preferences. Sorry for inconvenience.

Please note: Mentioned problems with access rights seem to be fixed in the latest update of Mac OS X 10.6.7, so please ensure that your system software is up-to-date.

How to launch CodeBar manually

Another rare issue that you may experience is that CodeBar may not be auto-launched after update or after restart. The reason for this is that the system process “launchd” cannot find where the helper app is located. In order to fix this, you should launch the app in Finder:


Then the operating system will know where the helper app is located and everything will work properly. Let’s hope this will be fixed in the future software updates of Mac OS X.

How to stop CodeBar errors logs

If you note launchd error logs about inability to launch CodeBar, the following receipt may help. Remove this XML from the file ~/Library/LaunchAgents/<ID>:


After a reboot, the error messages should stop appearing in the log file.

No comments:

Post a Comment