Neither v 2.1.1 nor 2.1.2 launches for me.
I’m running OS 10.11.2 on a macbook air.
I’ve deleted audacity.cfg, but it doesn’t help.
Quit 2.1.1 before trying 2.1.2.
The cause is possibly a new plugin, newly connected audio device or an old “lock file”.
Please see http://manual.audacityteam.org/o/man/faq_installation_and_plug_ins.html#launch and https://forum.audacityteam.org/t/audacity-is-already-running-error-solved/40481/2 for help.
Gale
I deleted lock file per instructions. Didn’t fix (subsequent attempts to launch Audacity replaced the lock file, though, FYI).
No new audio devices, plug-ins or other audio software of any sort added in past several years. I have no anti-virus app.
The first few times I tried to launch Audacity, “LoginWindow” became the active application (and remained so until I switched to another app). Subsequent attempts to launch, this did not happen. However, Activity Monitor shows that “LoginWindow” is still active.
FYI, here’s what Console is reading:
12/24/15 11:04:45.213 AM Audacity[7607]: WARNING: The Gestalt selector gestaltSystemVersion is returning 10.9.2 instead of 10.11.2. This is not a bug in Gestalt – it is a documented limitation. Use NSProcessInfo’s operatingSystemVersion property to get correct system version number.
Call location:
12/24/15 11:04:45.213 AM Audacity[7607]: 0 CarbonCore 0x9d5d1913 ___Gestalt_SystemVersion_block_invoke + 135
12/24/15 11:04:45.213 AM Audacity[7607]: 1 libdispatch.dylib 0x935c0763 _dispatch_client_callout + 50
12/24/15 11:04:45.213 AM Audacity[7607]: 2 libdispatch.dylib 0x935c063f dispatch_once_f + 78
12/24/15 11:04:45.213 AM Audacity[7607]: 3 libdispatch.dylib 0x935c1ec9 dispatch_once + 31
12/24/15 11:04:45.213 AM Audacity[7607]: 4 CarbonCore 0x9d54d576 _Gestalt_SystemVersion + 1047
12/24/15 11:04:45.214 AM Audacity[7607]: 5 CarbonCore 0x9d54c6a5 Gestalt + 154
12/24/15 11:04:45.214 AM Audacity[7607]: 6 Audacity 0x00462ae2 _Z14UMAInitToolboxtb + 50
Thanks, the Gestalt warning is not relevant to this.
Are there any crash or hang diagnostic reports for Audacity in the console?
Are you trying to run Audacity over a network?
Are you sure you are executing Audacity from its folder in /Applications and not from the DMG?
Have you added a “Portable Settings” folder to the Audacity folder? Or is audacity.cfg in its default location of ~/Library/Application Support/audacity ? Can you delete audacity.cfg then try to launch Audacity and post the resulting audacity.cfg so we can see how much gets written to it.
Have you tried rebooting the computer? Perhaps there is some old file or junk creating a problem in var/folders/ (inside which is the Audacity temporary directory). Rebooting will clear out var/folders/.
Gale
Problem seems to be solved (see below), but I’ll answer all questions in case they’re helpful to you in sussing out the problem.
No, just that same set of reports for each attempted launch.
Are you trying to run Audacity over a network?
No, nothing unusual.
Are you sure you are executing Audacity from its folder in /Applications and not from the DMG?
Certainly not from DMG. I had, however, as part of my attempt to solve this, put the app at root level of Applications folder, since I’d experienced similar problems from apps living in sub-folders. So I just threw it back into the Audacity sub-folder, tried to launch, and, interestingly, got a persistent “LoginWindow” showing as the active app…something which had previously appeared only upon first launch. Subsequent relaunches are, once again, NOT showing “LoginWindow” as the persistent active app. Could that be a clue?
Have you added a “Portable Settings” folder to the Audacity folder?
No
Or is audacity.cfg in its default location of ~/Library/Application Support/audacity ?
Yes
Can you delete audacity.cfg then try to launch Audacity and post the resulting audacity.cfg so we can see how much gets written to it.
I deleted audacity.cfg, and…app launches! I’d deleted the same file before without success. So, obviously, some other action on my part (since the last deletion of this file) combined to fix the issue. Perhaps the movement of the app back to its folder? Perhaps deleting the lock file?
I’ll save the old audacity.cfg file in case you want me to put it back and test both hypotheses…
Were the other contents of the “Audacity” folder in root of /Applications or still in /Applications/Audacity? Separating audacity.app from the folders that go with it will mean that you will lose access to the Manual and to Nyquist plugins.
By all means test, but please do so with 2.1.2, not 2.1.1.
Thanks!
Gale
Not an issue for me, as I don’t use them.
By all means test, but please do so with 2.1.2, not 2.1.1.
I see only 2.1.1 on the official download page.
Presumably you have 2.1.2 RC1, given you said at the outset that 2.1.2 did not launch.
2.1.2 has not been released yet and there will be a second release candidate RC2 in due course, but 2.1.2 RC1 (and RC2 when available) may be obtained here: http://www.fosshub.com/Audacity.html/.
Gale
Can’t dispute your logic. But I meant 2.1.0 and 2.1.1! Sorry for the imprecision!
I’ll fiddle around with the old, bad file and see if I can cause a problem. BTW, do you want me to email it to you?
I meant 2.1.0 and 2.1.1! Sorry for the imprecision!
2.1.0 and 2.1.2 are really, really different. We can’t see you and the only things we know about you are what you type and the flavor of how you type it. Accuracy is good.
Koz
Hey, thanks for the chewing out. Here’s one back at you: if an upgrade leaves the app really, really different, you might want to step that version # up by more than a .xx graduation. We have no way of knowing how significant an upgrade is otherwise. I can’t see you and the only thing I know is the numbering you give the upgrade. Intelligent version numbering is good.
If it were v2.1.1 and v2.2, I’d have paid closer attention. In 30 years of beta testing, including for some huge-name developers, I’ve never yet seen a .xx graduation I needed to be super-careful to distinguish.
I guess you were too busy to respond to my offer, so I guess I’ll just flush the file.
Good talk!
We went from 2.0.6 to 2.1.0 to reflect the introduction of real-time preview.
2.1.1 had a bug that could cause it not to launch: https://forum.audacityteam.org/t/fix-for-audacity-2-1-1-not-launching/39157/1 You were likely not helping by moving Audacity.app from its folder. We do not recommend doing that.
If you want to test our current code then please use the latest nightly build from the top of http://www.audacity.homerow.net/index.php?dir=mac/&sort=date&order=desc. Whatever is the latest build there will become 2.1.2 RC2 when the time comes. There is no point testing old releases.
If some old audacity.cfg file creates a problem in the latest nightly build, then please attach the .cfg file.Please see here for how to attach files: https://forum.audacityteam.org/t/how-to-attach-files-to-forum-posts/24026/1
Gale