Difference between revisions of "Partial Support for Mac Sierra in 2.1.3"

From Audacity Wiki
Jump to: navigation, search
(Reporting: grammar)
(Added more text for users about bug 1567. Added bug where Audacity is "damaged" if run a second time by other than user who installed it.)
Line 2: Line 2:
  
 
{{Ednote|Actually anyone with edit rights is welcome to edit.  The WIP notice is more about indicating this is rough and ready placeholder text}}
 
{{Ednote|Actually anyone with edit rights is welcome to edit.  The WIP notice is more about indicating this is rough and ready placeholder text}}
{{Alert|Audacity 2.1.3 only has partial support for Mac Sierra.  This is due to problems with Audacity on that operating system}}
+
{{Alert|Audacity 2.1.3 only has partial support for macOS Sierra.  This is due to problems with Audacity on that operating system.}}
  
 +
==Symptom 1 ==
  
==Symptoms==
+
On macOS Sierra 10.12.1 and later (but not 10.12.0) on some users' machines, Audacity can lose access to:
 +
* all effects that are not shipped with Audacity
 +
* MP3 export using LAME
 +
* the FFmpeg import/export library. Note that FFmpeg is not needed on Mac for MPEG-4 audio like M4A, only for a few other formats like AC3 and WMA. 
 +
Plug-in effects disappear from menus, or might show an intialisation error. Affected plug-ins will always return to "New" in Plug-in Manager, even if they are re-enabled.
  
On macOS Sierra, on some users' machines, Audacity:
+
We have added code into Audacity to reduce this problem.  We have not solved the problem completely, and you may see the problem on your machine, especially if using COMMAND + W to close a project window without saving changes.  
* Can lose access to Effects, MP3 decoding and encoding and to FFmpeg.
 
  
The items disappear from menus.  We have added code into Audacity to reduce the problem.  We have not solved the problem completely, and you may see the problem on your machine.
+
===Workarounds===
  
==Workarounds==
+
We believe the problem is caused by changes in Gatekeeper for macOS Sierra.  If the problem occurs, opening /Applications/Utilities/Terminal.app and entering the  following command will fix the issue:
 +
{{code|sudo xattr -r -d com.apple.quarantine /Applications/Audacity/}}
 +
If Audacity is elsewhere than in /Applications, change the location in the command accordingly. After typing the above command, hit ENTER on your keyboard. Type your admin password (you won't see it on the screen) then hit ENTER again. You may also need to reboot the Mac.
  
We believe the problem is caused by changes in Gatekeeper for macOS Sierra.  If the problem occurs, the following command will fix the issue.
+
Unfortunately this command is needed each time the problem happens again.  
  
  xattr something something
+
== Symptom 2==
  
Unfortunately this command is needed each time the problem reoccurs.
+
On all versions of macOS Sierra, on some users' machines:
 +
* On first launch of Audacity, Gatekeeper may take a minute or more to verify Audacity, displaying a progress dialogue. Please let verification complete.
 +
* If a given user installs Audacity but another user runs it, then on second run by that other user, a warning will say that Audacity is damaged and can't be opened.
 +
** When the user that installed Audacity runs it, Gatekeeper may verify Audacity each time this user runs Audacity, not just first time, and this verification may take a minute or more.
  
==Details==
+
===Workarounds===
 +
 
 +
 
 +
 
 +
== For Developers ==
  
 
This section is mainly for programmers.
 
This section is mainly for programmers.

Revision as of 18:43, 25 January 2017

Example.png

This page is a User "Work in Progress"

Please let the claimant work with it at least two weeks after this sticker was put up (or until this sticker has been removed, if earlier).

Suggestions may be made to the claimant by clicking on the page's "discussion" tab.

Actually anyone with edit rights is welcome to edit. The WIP notice is more about indicating this is rough and ready placeholder text
Warning icon Audacity 2.1.3 only has partial support for macOS Sierra. This is due to problems with Audacity on that operating system.

Symptom 1

On macOS Sierra 10.12.1 and later (but not 10.12.0) on some users' machines, Audacity can lose access to:

  • all effects that are not shipped with Audacity
  • MP3 export using LAME
  • the FFmpeg import/export library. Note that FFmpeg is not needed on Mac for MPEG-4 audio like M4A, only for a few other formats like AC3 and WMA.

Plug-in effects disappear from menus, or might show an intialisation error. Affected plug-ins will always return to "New" in Plug-in Manager, even if they are re-enabled.

We have added code into Audacity to reduce this problem. We have not solved the problem completely, and you may see the problem on your machine, especially if using COMMAND + W to close a project window without saving changes.

Workarounds

We believe the problem is caused by changes in Gatekeeper for macOS Sierra. If the problem occurs, opening /Applications/Utilities/Terminal.app and entering the following command will fix the issue:

sudo xattr -r -d com.apple.quarantine /Applications/Audacity/

If Audacity is elsewhere than in /Applications, change the location in the command accordingly. After typing the above command, hit ENTER on your keyboard. Type your admin password (you won't see it on the screen) then hit ENTER again. You may also need to reboot the Mac.

Unfortunately this command is needed each time the problem happens again.

Symptom 2

On all versions of macOS Sierra, on some users' machines:

  • On first launch of Audacity, Gatekeeper may take a minute or more to verify Audacity, displaying a progress dialogue. Please let verification complete.
  • If a given user installs Audacity but another user runs it, then on second run by that other user, a warning will say that Audacity is damaged and can't be opened.
    • When the user that installed Audacity runs it, Gatekeeper may verify Audacity each time this user runs Audacity, not just first time, and this verification may take a minute or more.

Workarounds

For Developers

This section is mainly for programmers.

  • Originally Nyquist effects were affected too. We have largely overcome that problem by placing the Nyquist effects with the Audacity app, so that they are part of the signed bundle.
  • Audacity now implements a fork and crash strategy at start up, where a separate fork is initiated and deliberately crashed. For some reason that we do not understand this seems to stop the problem happening at initialization of Audacity.

Reporting

If you experience the problem and would like to help us with understanding the cause, please contact us at.... One of the obstacles to us progressing with solving the problem is that it only happens on some users' machines.