Audacity Bug Summary
••• Introduction •••
••• Keywords •••
    Audacity 3.0.3 development began 19th April 2021

Audacity Bugzilla



Bug 1585 - Mac: Audacity does not launch on a few El Capitan systems
Mac: Audacity does not launch on a few El Capitan systems
Status: CLOSED NOT-A-BUG
Product: Audacity
Classification: Unclassified
Component: Application Core
2.1.3
Per OS macOS
: P3 MoonPhase
Assigned To: Default Assignee for New Bugs
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2017-01-31 14:02 UTC by Gale Andrews
Modified: 2019-05-08 15:55 UTC (History)
7 users (show)

See Also:
Steps To Reproduce:
1 Launch Audacity on an affected El Capitan system. An error message "The application “Audacity.app” can’t be opened." appears. 2 In 10.11.1 Beta these Console messages were reported: 10/13/15 12:48:08.004 PM com.apple.xpc.launchd[1]: (com.apple.xpc.launchd.oneshot.0x10000033.Audacity.sh[7734]) Could not find and/or execute program specified by service: 2: No such file or directory: /Applications/Audacity/Audacity.app/Contents/MacOS/Audacity.sh 10/13/15 12:48:08.003 PM Finder[553]: spawn_via_launchd() failed, errno=111 label=[0x0-0xa80a80].net.sourceforge.audacity path=/Applications/Audacity/Audacity.app/Contents/MacOS/Audacity.sh flags=1 : LaunchApplicationClient.cp #963 LaunchApplicationWithSpawnViaLaunchD() q=com.apple.root.default-qos 10/13/15 12:48:08.003 PM Finder[553]: spawn_via_launchd() failed, errno=111 label=[0x0-0xa80a80].net.sourceforge.audacity path=/Applications/Audacity/Audacity.app/Contents/MacOS/Audacity.sh flags=1 10/13/15 12:48:37.073 PM com.apple.xpc.launchd[1]: (com.apple.xpc.launchd.oneshot.0x10000034.Audacity.sh[7738]) Could not find and/or execute program specified by service: 2: No such file or directory: /Applications/Audacity/Audacity.app/Contents/MacOS/Audacity.sh 10/13/15 12:48:37.072 PM Finder[553]: spawn_via_launchd() failed, errno=111 label=[0x0-0xa83a83].net.sourceforge.audacity path=/Applications/Audacity/Audacity.app/Contents/MacOS/Audacity.sh flags=1 : LaunchApplicationClient.cp #963 LaunchApplicationWithSpawnViaLaunchD() q=com.apple.root.default-qos 10/13/15 12:48:37.072 PM Finder[553]: spawn_via_launchd() failed, errno=111 label=[0x0-0xa83a83].net.sourceforge.audacity path=/Applications/Audacity/Audacity.app/Contents/MacOS/Audacity.sh flags=1 One user with fresh 10.11.6 installations had this issue on multiple machines and also had accompanying Console log messages of the form: 9/25/16 9:44:51.829 PM lsd[296]: LaunchServices: Could not store lsd-identifiers file at /private/var/db/lsd/com.apple.lsdschemes.plist 3 Some other apps than Audacity are reported to have a similar problem. According to these reports the reason is that the "lsd" folder in /private/var/db/ is missing, or the Launch Services database is corrupted, or it is some El Capitan caching bug (some system file not being updated or deleted). Gale does not have a /private/var/db/lsd/ folder on his 10.10 or 10.12 systems, nor any "com.apple.lsdschemes.plist" files according to the find command run in a terminal on 10.12. Other users say the same.
Release Note:
GROUP: Launching Audacity * (Mac El Capitan) '''Audacity may not launch and a "Can't be opened" message will be displayed.''' Console log messages may refer to "Could not store lsd-identifiers file at /private/var/db/lsd/com.apple.lsdschemes.plist".
First Git SHA:
Group: ---
Workaround:
Right-click or CTRL-click over Audacity.app, choose "Show Package Contents", then in the "MacOS" folder, double-click the "Audacity" executable. This will launch a Terminal window and Audacity will also launch. Alternatively you can try resetting the LaunchServices database by running the following Terminal command then rebooting: {{codelist|sudo /System/Library/Frameworks/CoreServices.framework/Frameworks/LaunchServices.framework/Support/lsregister -kill -r -domain local -domain system -domain user ; killall Dock}}
Closed:
gale: Regression+


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gale Andrews 2017-01-31 14:02:39 UTC
Regression on 2.1.1 which launches without issue on the affected systems.
Comment 1 Peter Sampson 2017-11-21 12:54:36 UTC
Do we still see this with 2.2.0

I don't recall such complaints on the Forum
Comment 2 Peter Sampson 2019-05-08 15:55:01 UTC
We have had no complaints about this for many a long year so I'm gonna close this