xxx@xxx:/opt/audacity$ ./audacity-linux-3.7.0-x64-20.04.AppImage
Could not parse file “/home/master/.local/share/applications/xxx.desktop”: Invalid key name: Path[$e]
Could not parse file “/home/master/.local/share/applications/xxx.desktop”: Invalid key name: Path[$e]
…
.
.
…and so on.
Anyone explain why these .desktop files are parsed at startup? Just curious…
The directory /home/user-name/.local/share/applications/ is part of the XDG Base Directory Specification (Linux and unix-like operating systems). It stores desktop entry files (.desktop files) for applications, which are shortcuts that tell the system how the application should appear in the desktop environment’s menu / application launcher.
If you have other question about your operating system, the best place to ask is the operating system’s help channel (This forum is for help using Audacity audio editing software).
Thank you for your fast reply. But still I’m curious why the data of other .desktop files are needed for Audacity, isn’t that Audacity should just put its .desktop file there and that’s all. Hope you don’t mind I’m currently learning about stuff like this… I do believe Audacity is honest project, pure curiosity here.
Data of other .desktop files are not needed for Audacity.
I don’t know why you are seeing those messages. That does not happen for me (Ubuntu 22.04). Are you using the official AppImage release version of 3.7?
No, I don’t see those lines when I launch the .AppImage.
I configure the AppImage to use the “Portable Home” option. Run the AppImage with the option -h and it will show you the available options. The “Portable Home” option creates a folder in the same directory as the AppImage, so that when you launch the AppImage normally, it puts its configuration files in the new folder. This allows you to run different versions of Audacity without them messing up your main version.
This is what I see when running Audacity 3.6 AppImage (My 3.7 version is built from source, and is not an AppImage, so that looks different).