On 10/07/2012, at 14.36, David B wrote:

I just had an auto update to 1637 and bundles will not load. Hence highlighting gone.

Did it prompt for password during the update?

For diagnostics purposes can you run the following in Terminal:

find /Applications/TextMate.app -exec ls -ld {} ;|bzip2 > /tmp/info.bz2

Then send me /tmp/info.bz2 ?

We have had a few users experience this, but have no clue what happens and so far not gotten any diagnostics because users have just re-downloaded and then it worked.

Kind regards Allan

On 10 Jul 2012, at 20:07, David B wrote:

...

users have just re-downloaded and then it worked.

Yes odd one. The default bundles are all there within the .app -

I suspect the permissions are somehow screwed, hence why I would really like to see the output of the find/ls command sequence.

[…] I tried removing all them plus a re-download. Will try one more.

Well, I’d actually prefer if you not mess with the broken version as I need to track down the issue so it doesn’t happen again (probably half a dozen users reported this for the latest update, but none provided me with any data so I am still clueless as to what went wrong — my hunch was that updating with admin pw. could somehow cause the bundles (for some users) to be non-readable for the current user, perhaps related to different versions of tar on the different user systems (explaining why it’s not reproducible), but given that you didn’t update as admin, I guess that theory is out).

I'll revert to a copy on a backup at weekend.

If you download a fresh copy then that should also work: http://download.macromates.com/

...

If you download a fresh copy then that should also work: http://download.macromates.com/

Already tried that & it didn't. But will try once more.

I was mistaken. A fresh download is fine. :-)

On 10 Jul 2012, at 22:07, David Barnes wrote:

...

...

If you download a fresh copy then that should also work: http://download.macromates.com/

Already tried that & it didn't. But will try once more.

Allan. Emailed ls output to your github email.

Thanks! Indeed it was a permission problem. All files were owned by root and the info.plist files for each bundle was set to 600 (non-readable for group/other). The reason the files have bad permissions is because the ‘defaults’ command is used to stamp the files in the deployment process, I wasn’t aware this command didn’t preserve permission flags — the issue affects all that run TextMate as another user than the one who installed it, so glad I found the course.