Audacity 2.1.1 crashes on OSX 10.8.5

[cmac185]

Don't know if this is related to this specific issue or not, but two of us on different machines with Yosemite 10.10.4 can't get 2.1.1. to run at all. Found the following in the Console: "

7/19/15 8:55:28.748 PM Audacity[1384]: WARNING: The Gestalt selector gestaltSystemVersion is returning 10.9.4 instead of 10.10.4. Use NSProcessInfo's operatingSystemVersion property to get correct system version number.
Call location:
7/19/15 8:55:28.749 PM Audacity[1384]: 0 CarbonCore 0x90847291 ___Gestalt_SystemVersion_block_invoke + 135
7/19/15 8:55:28.749 PM Audacity[1384]: 1 libdispatch.dylib 0x9955f0b5 dispatch_once_f + 251
7/19/15 8:55:28.750 PM Audacity[1384]: 2 libdispatch.dylib 0x995600d8 dispatch_once + 31
7/19/15 8:55:28.750 PM Audacity[1384]: 3 CarbonCore 0x907c069d _Gestalt_SystemVersion + 1050
7/19/15 8:55:28.750 PM Audacity[1384]: 4 CarbonCore 0x907bf7c0 Gestalt + 150
7/19/15 8:55:28.750 PM Audacity[1384]: 5 Audacity 0x00462ae2 _Z14UMAInitToolboxtb + 50
7/19/15 8:55:28.750 PM Audacity[1384]: 6 Audacity 0x0046843c _ZN5wxApp10InitializeERiPPw + 44


Could this be related to the latest 10.10.4 update?

Ideas?

Cliff

[cmac185]

Don't have an answer why the console messages I posted in the last post were there, but I finally got 2.1.1 running by renaming the Audacity directory at Library/Application Support/Audacity. Then I stated 2.1.1 and shut it back down and then restarted it again just fine so set some preferences then closed it again. Then I renamed the new directory and restored the name on the original directory. Now 2.1.0 and 2.1.1 both run fine with the old directory. Guess the renaming forced a rewrite of some things that cleared up what the issues were. Pretty strange. BTW, this was with the Zip download.

Cliff

[cyrano]

1) I deleted the settings directory, which had been generated by v2.0.6.
2) Started up v2.1.1, and entered the locations for the Lame and ffmgep libraries manually.
3) Closed 2.2.1
4) Started the old 2.0.6, which complained about missing libraries, now.
5) Entered, again, the right places where Lame and ffmpeg reside. Closed 2.0.6
6) Started 2.1.1, which would now no longer find the libraries.

Something very similar happened when I was rummaging around with the latest RC and 2.1.0.

Audacity didn't crash, but prefs didn't stick until I deleted the map let Audacity recreate prefs and saved them in **both** versions. Previous prefs file dated back to 2.0.6.

Sorry, don't remember much more as I was chasing something else at the time.

Were these preferences for LAME and FFmpeg or other settings?

I toggle between different versions of Audacity a lot (as admin). The only problem I recall is if I go back from 2.0.6 or 2.1.x to Audacity 2.0.5, 2.0.5 won't start first time because of incompatible FFmpeg libraries (2.0.5 requires an older FFmpeg 0.6.2).

But that is a problem in 2.0.5 only.


Gale

Just usual prefs settings, nothing to do with lame or ffmpeg. These kept working all the time.

With a portable install these problems are gone...

[Gale Andrews]

Sometimes the Repair Permissions without restart has enabled users to read /usr/local/ again. Other times they had to go in as root to change permissions on that folder or just not use it for LAME or FFmpeg.

And yes sometimes Repair Permissions can "seemingly" fix issues with ~/Library/Application Support/audacity/ (with or without restart and without changing audacity.cfg).

I was recently able to get two instances of Audacity running on Mac from two audacity.cfg's pointing to the same temp folder - it should have been impossible, but Repair Permissions stopped the problem.

Another problem Repair Permissions fixed without reboot was Audacity apparently reading the audacity.cfg in ~/Library/Application Support/audacity/ when I had audacity.cfg in a Portable Settings folder alongside Audacity which should have been read instead.

But that sounds like an Audacity bug to me?

If so, it is a bug that Repair Permissions appeared to hide, unless it was totally fortuitous.

If Audacity cannot read the Portable Settings folder it will look in the default location for audacity.cfg.


Gale

[Gale Andrews]

i'm pretty certain I have only one .cfg on this Mac, depite having two Audacity versions.

Right. Both v2.0.x and v2.1.1 are using the same path and file names to store the settings. IIRC, these were already used by v1.x.

1.3.x.

1.2.x used ~/Library/Preferences/audacity Preferences.

Gale

[Gale Andrews]

Don't know if this is related to this specific issue or not, but two of us on different machines with Yosemite 10.10.4 can't get 2.1.1. to run at all. Found the following in the Console: "

7/19/15 8:55:28.748 PM Audacity[1384]: WARNING: The Gestalt selector gestaltSystemVersion is returning 10.9.4 instead of 10.10.4. Use NSProcessInfo's operatingSystemVersion property to get correct system version number.
Call location:
7/19/15 8:55:28.749 PM Audacity[1384]: 0 CarbonCore 0x90847291 ___Gestalt_SystemVersion_block_invoke + 135
7/19/15 8:55:28.749 PM Audacity[1384]: 1 libdispatch.dylib 0x9955f0b5 dispatch_once_f + 251
7/19/15 8:55:28.750 PM Audacity[1384]: 2 libdispatch.dylib 0x995600d8 dispatch_once + 31
7/19/15 8:55:28.750 PM Audacity[1384]: 3 CarbonCore 0x907c069d _Gestalt_SystemVersion + 1050
7/19/15 8:55:28.750 PM Audacity[1384]: 4 CarbonCore 0x907bf7c0 Gestalt + 150
7/19/15 8:55:28.750 PM Audacity[1384]: 5 Audacity 0x00462ae2 _Z14UMAInitToolboxtb + 50
7/19/15 8:55:28.750 PM Audacity[1384]: 6 Audacity 0x0046843c _ZN5wxApp10InitializeERiPPw + 44


Could this be related to the latest 10.10.4 update?

It's related to any 10.10 version, not an update to 10.10.4. http://forum.audacityteam.org/viewtopic ... 53#p280853.


Gale

[Gale Andrews]

I finally got 2.1.1 running by renaming the Audacity directory at Library/Application Support/Audacity. Then I stated 2.1.1 and shut it back down and then restarted it again just fine so set some preferences then closed it again. Then I renamed the new directory and restored the name on the original directory. Now 2.1.0 and 2.1.1 both run fine with the old directory. Guess the renaming forced a rewrite of some things that cleared up what the issues were.

One identified issue that sometime causes 2.1.1 not to start is having a line like

Code: Select all

TempDir=/tmp/audacity1.2-<your user name>

in audacity.cfg. 2.1.1 seems unable to write to that location sometimes.

There may be other problems.

Gale

[cyrano]

If Audacity cannot read the Portable Settings folder it will look in the default location for audacity.cfg.

I've deleted both portable install folders (after zipping them).

No new file is created anywhere. I've checked plugins folder, Application support/audacity, /tmp and so on. I've even checked the Melda plugin folder because that contained an "Audacity" folder. I didn't create that, and I'm not sure why it would be in the Melda plugins folder. Anyhow, deleted that too.

I've also cleared ALL caches, rebooted into su mode and ran a disk check. Nothing...

Updated locate db again. No audacity.cfg to be found.

Yet, Audacity 2.1.1 retains its preferences perfectly. And after a short test, 2.1.0 seems to remember prefs too.

Prefs do not copy over completely from 2.1.0 to 2.1.1!

Setting meter waveform dB range passes over.
Tracks/Default view mode (Waveform prefs for the wave window) doesn't.

[Gale Andrews]

Prefs do not copy over completely from 2.1.0 to 2.1.1!

Setting meter waveform dB range passes over.

You said before that "did not stick" (did not get the same setting in 2.1.1 as 2.1.0).

Tracks/Default view mode (Waveform prefs for the wave window) doesn't.

That and the meter/waveform range had extra choices added for 2.1.1. But they do get transferred over correctly from 2.1.0 on Windows as far as I can see.

I'll have to try Mac later.

If you change to another view mode in 2.1.1 then go back to 2.1.0, 2.1.0 will stay with its old choice not take 2.1.1's choice. 2.1.1 uses a different preferences key (so that you do - or should - get the 2.1.0 view mode in 2.1.1).


Gale

[cyrano]

OK Mystery solved.

I'm stupid. Definitely.

The audacity.cfg is where it should be. In:

/users/user/Application support/audacity/

I've since discovered that neither locate nor find (the cli versions), nor SpotLight could find it because of permissions.

Something screws things on this Mac. I have an encrypted data partition that shouldn't be indexed by SpotLight. It's excluded in System prefs/Spotlight. Yet it is indexed. And it seems SpotLight and locate/find use the same index?

Searching for "Audacity" with locate or find does find a map called "Audacity" in:

/users/user/Application support/MeldaProduction/

Both the folders "Audacity" and "MeldaProduction" have different permissions, but both are owned by the user. And the user has read/write access.

Audicity has drwxr-xr-x
MeldaProduction has 0777.

Audacity's permissions seem to be like most folders in there. Melda's are not. And something is changing files in there, even if no plugin using programs are open.

Mmm... Same for LightTable...

Anyhow, mystery solved. Need another beer