Bug #281: Won't launch if run from case-sensitive HFS volume

From a user email:

----------------------------------------

2005-07-28 21:01:46.564 Synergy Advance[8835] failed to load iTunes bundle 2005-07-28 21:01:46.574 Synergy Advance[8835] *** Assertion failure in +[WOHotKeyClass00080 leafNodeWithParent:actionString:plistKey:target:action:type:], /Users/wincent/trabajo/WOHotKey/svn- files/WOHotKeyNode.m:60 sh: line 1: /Applications/Synergy: No such file or directory sh: line 1: /Applications/Synergy: No such file or directory

It happens every time I launch the application off of my Powerbook's hard disc. I'm current on OS and security updates. I have reformatted the drive recently to a Journaled and Case Sensitive file system, while my previous installation was on just a Journaled filed system. Oddly enough, Synergy will run just fine off its virtual disc.

This is the first time it's happened since I've been using both versions of Synergy; the previous betas of Synergy Advance worked just fine off of the drive, so it might be the Case Sensitive system.

----------------------------------------

Yes, it definitely sounds like a Case Sensitive file system issue. I've double checked the source code to make sure that there are no hard-coded paths with incorrect case sensitivity and everything is correct. I've also run a test to make sure that Cocoa isn't returning an incorrectly capitalized path when I call [[NSBundle mainBundle] builtInPlugInsPath]; on my system it returns:

/Users/wincent/trabajo/build/Debug/Synergy Advance.app/Contents/PlugIns/Player/iTunes.bundle

Which is correct. In Xcode when I built Synergy Advance I have it set to copy the bundle to the "PlugIns" folder, which is something you choose from a pop-up menu and don't type so you wouldn't expect any capitalization errors there. And in any case, if you look inside the application bundle you can see that the plug-in is indeed being copied to the correct path and that there are no capitalization discrepancies.

If it's all right with you I'll prepare a special build that logs more detailed information about the error it gets when trying to load the bundle. I suspect that whatever the issue is that is caused by case sensitivity, it can probably only be detected on your system and not figured out from here.