Audacity does not generate pluginregistry.cfg

[klikkolee]

When starting audacity 2.12 on one of my ubuntu 16.04 machines, I'm greeted with a "debug report" dialog. examining the log in the generated folder shows that pluginregistry.cfg does not exist. following advice I found elsewhere on this forum, I deleted .audacity-data and reran audacity to regenerate it. the folder was regenerated and a few files and a folder were created inside, but pluginregistry.cfg was not created and the same dialogue appeared creating an identical report folder. I then tried creating an empty pluginregistry.cfg with touch and the created file was deleted when audacity was ran, resulting in the same dialogue and same report. I then tried reinstalling audacity through apt to no effect. I also tried reinstalling the audacity-data package. I then tried using the .deb files directly from the online repositories to no effect again. I made sure to uninstall audacity before each of these attempts

I have another machine with the same ubuntu and audacity versions which functions normally. I was going to transplant the pluginregistry.cfg file from that pc to this one, but found that the working installation does not have a pluginregistry.cfg in its .audacity-data.

[Gale Andrews]

"2.12" is a typo, It should be 2.1.2.

Pluginregistry.cfg does not get written until you launch Audacity successfully and open Plug-in Manager.

I see in log.txt

Code: Select all

17:50:11: Error: Impossible to get permissions for file '/home/trevor/.audacity-data/pluginregistry.cfg' (error 2: No such file or directory)

If you are launching Audacity from the terminal with the sudo command, or running the terminal as root, don't.

Also make sure your own user is a member of the "audio" group.

If the problem continues after that and audacity.cfg in the Debug Report still contains no audio devices, then the audio devices on your computer are probably the problem.

Code: Select all

aplay -l

and

Code: Select all

arecord -l

(that's -l as in "lovely") will show you your playback and recording devices.


Gale

[klikkolee]

I apologize for the very late response. I was expecting an email notification when someone replied.

To address you points in turn: I am running audacity as my own user, not as root (though out of curiosity I tried it as root when you mentioned it and, unsurprisingly, it didn't help), my user is a member of the audio group, and aplay -l and arecord -l list numerous devices that I have been able to use all of successfully with pulseaudio, jack, and straight alsa (not at the same time, of course). the outputs of the two are attached. I also attached the log generated by running as my user in case it is any different.

[Gale Andrews]

I was expecting an email notification when someone replied.

If you subscribe to the topic (see bottom left) then you should get an e-mail, but you may need to check your Spam or Trash folders.


Gale

[Gale Andrews]

None of your debug reports show any audio devices, so I suspect that is the cause of the problem. Perhaps you could disable all but card 2 and see if that helps. Not all audio devices are compatible with Audacity, which could be relevant if your hardware was really meant for Windows.

Have you tried installing Wine and seen if the Windows release of Audacity 2.1.2 runs?


Gale

[klikkolee]

I have two physical sound devices in my machine. One is built into the motherboard and the other is built into my graphics card (since it has hdmi output). I was able to disable the virtual sound devices (loopback and dummy) but I could not disable the hdmi device despite blacklisting the snd_hda_codec_hdmi module (it still loaded on boot). Audacity still crashed with the report in "audacity-report-new" I then reinstalled audacity and tried again, resulting in the report "audacity-report-new-after-reinstall" running the diff command on these folders showed that they only differed in timestamps and the "address" property in the audacity.xml file

I downloaded the windows version of audacity and ran it in wine. it was able to start and play white noise. I might be able to use this in an emergency, but I would greatly like if I could use the native Linux version since I would like to more easily be able to leverage jack (which I should note was off for the tests) and since some parts of the user interface (such as drop-downs in the settings menus) do not work properly.

You mentioned that some sound cards are incompatible with audacity. may I ask what besides a fully-functional (in my experience) alsa driver is required?

[steve]

Let's see how far it's getting when you try to launch:
Open a terminal window and navigate to the directory where the "audacity" executable is installed, then enter the command:

Code: Select all

./audacity &> "valid-path-and-file-name.txt"

Attach the file to your reply.

[klikkolee]

The output file is completely empty, though if I have the file open in an editor while running the command, I get the file-has-been-changed notification even though it remains blank after reloading. I assume that is just bash grabbing the file so it is ready to feed it output. I tried the command with and without quotes around the file name.

[Gale Andrews]

The output file is completely empty, though if I have the file open in an editor while running the command, I get the file-has-been-changed notification even though it remains blank after reloading. I assume that is just bash grabbing the file so it is ready to feed it output. I tried the command with and without quotes around the file name.

Is there any output on the screen if you echo the output to screen and file?

Code: Select all

./audacity 2>&1 | tee file.txt

Gale

[klikkolee]

the command produces no output in either the terminal nor in the file