Pluginregistry.cfg missing in new Linux Mint build from src?

[ericb7799]

Just built new install on Linux Mint 18 and everytime I try to launch Audacity I'm getting immediate debug crash log window and Audacity not launching. Per the log:
00:06:28: Audacity 2.1.2
00:06:28: Error: Impossible to get permissions for file '/home/ericmint/.audacity-data/pluginregistry.cfg' (error 2: No such file or directory)


checked the .audacity-data folder and that file is not there. Had previously tried making sure all permissions were read/write and the temp directory issue was corrected. But what is the deal with this? Can I just create a dummy file and hope it gets replaced when Audacity sees it?


also getting some other errors related to other apps when I launch audacity as sudo:

Code: Select all

 sudo audacity

(Audacity:8772): Gtk-WARNING **: gtk_disable_setlocale() must be called before gtk_init()
Error opening file /usr/lib/lv2/carla.lv2/manifest.ttl (No such file or directory)
lilv_world_load_file(): error: Error loading file `file:///usr/lib/lv2/carla.lv2/manifest.ttl'
lilv_world_load_bundle(): error: Error reading file:///usr/lib/lv2/carla.lv2/manifest.ttl
no more csLADSPA plugins
VST_PATH not set, defaulting to /root/vst:/usr/local/lib/vst:/usr/lib/vst
ericmint-System-Product-Name testdisk-7.0  # cd /home/ericmint/.audacity-data/
ericmint-System-Product-Name .audacity-data # ls
audacity.cfg  Plug-Ins  pluginsettings.cfg
ericmint-System-Product-Name .audacity-data # 

[steve]

Check that the directory /home/ericmint/.audacity-data/ exists and has read & write permission for the user account.
Are you logged in as ericmint ?

On first ever run, pluginregistry.cfg is created by Audacity. On subsequent launches, if the file exists, Audacity will attempt to use it. If the file does not exist Audacity will attempt to create a new one.

Sounds like a permission problem, but could be due to a misnamed directory or you're logged in with the wrong credentials.

[ericb7799]

It isnt launching even the first time. Immediately throws up the debug window and does not open. I checked the permissions first and it looks ok to me. It should be .audacity-data and not audacity-data right? Doesn't the . imply that it's hidden?

[ericb7799]

here is the debug info that pops up. I also tried purging my install and installing from Mint repo and got exact same message. Does not open the first time. First time its launched I get the cannot find place for temp directory message. Then I've been directing it to a temp folder, creating it and then Audacity closes. On relaunch all I get is the debug error.

[steve]

If there's anything in .audacity-data that you need to keep, make a backup copy, then delete the entire .audacity-data folder. So long as you are logged in as the user "ericmint" and the permissions are not screwed up for "/home/ericmint", then Audacity should recreate a new .audacity-data folder. This will essentially reset Audacity to "factory default" condition.

[Gale Andrews]

sudo audacity

Isn't sudo the cause of the problem? use sudo to install, not to make, and not to launch.

Gale

[steve]

Well spotted Gale.

[ericb7799]

ok will clean out everything that's there and lay off sudo to launch. i admit , being somewhat new to Linux, I brought some of my bad Windows habits of launching everything as admin with me. i've never quite understood when to sudo and when not to, when to gksu and when to gksudo. Seems that my limited experience is that the rules seem pretty inconsistent and vary quite widely among apps. Will give it a go at rebuild and launch later tonight. thanks.

[steve]

"su" is "super user".
"sudo" is "super user do ..."
"Super User" can trash your machine - use with care.

By default, "users" are not allowed to make changes to the system. Users can "use" the system, but not make changes to the operating system. This makes using a Linux computer relatively safe. However, there are times when it is necessary to make changes to the system, for example, to install new software, or update the system. As a normal user you cannot do that, so you have to call on the service of "Super User". Super User has the same access as "root", and "root" is source of all things - "root" is god.

Note that some applications do not need to be installed into the system, but may be run entirely with standard use access. In such cases, elevated privileges are not required, so "Super User" should not be invoked. Only use the power of root when you must make changes to the system.

"gksu" is the same as "su" but with a graphic interface.
"gksudo" is the same as "sudo" but with a graphic interface.
The "gk" part comes from "GTK", which forms the basis of very many graphical elements in Linux.

[Gale Andrews]

If you must run a graphical application with sudo, you should use gksudo instead which should stop ownership problems occurring: https://help.ubuntu.com/community/RootS ... hical_sudo.


Gale