Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mixx is broken on OSX with Case-Sensitive filesystems #7210

Closed
mixxxbot opened this issue Aug 22, 2022 · 3 comments
Closed

Mixx is broken on OSX with Case-Sensitive filesystems #7210

mixxxbot opened this issue Aug 22, 2022 · 3 comments

Comments

@mixxxbot
Copy link
Collaborator

Reported by: eugenesan
Date: 2013-12-06T08:26:50Z
Status: Fix Released
Importance: Undecided
Launchpad Issue: lp1258435


After .app dragged/copied to Case-Sensitive filesystem, it won't start while reporting broken application.
Application icon appears with grey "No-Entry" sign.

From command line it looks like this:
$ open -a /Applications/Mixxx.app
The application /Applications/Mixxx.app cannot be opened because its executable is missing.

The reason for that is in-consistency in naming of main executable.
Mixxx.app/Contents/Info.plist mention <key>CFBundleExecutable</key><string>Mixxx</string> while actual executable called "mixx". Replacng CFBundleExecutable value "Mixxx" with "mixxx" in .plist fixes the problem.

If invoked from installation .dmg, it work perfectly.

Similar report noted here:
http://www.mixxx.org/forums/viewtopic.php?f=3&t=904

@mixxxbot
Copy link
Collaborator Author

Commented by: rryan
Date: 2013-12-06T16:52:33Z


Thanks for the report! I'll take a look.

@mixxxbot
Copy link
Collaborator Author

Commented by: rryan
Date: 2013-12-06T18:23:25Z


Oh man, I had no idea HFS+ wasn't case sensitive unless you explicitly format it that way.

This has likely been an oversight for years. Fixed in master.
d4139eb

Thanks!t

@mixxxbot
Copy link
Collaborator Author

Issue closed with status Fix Released.

@mixxxbot mixxxbot transferred this issue from another repository Aug 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant