I was wondering why audacity is slow to launch
I found that its command line in the properties dialog is
env UBUNTU_MENUPROXY=0 audacity %F
I would expect just "audacity %F"
This is the only application I can find like this
I am intrigued!
I was wondering why audacity is slow to launch
=20
I found that its command line in the properties dialog is
=20
env UBUNTU_MENUPROXY=3D0 audacity %F
=20
I would expect just "audacity %F"
=20
This is the only application I can find like this
=20
I am intrigued!
The command as you've pasted it above either sets or modifies a
GTK-specific environment variable to indicate that the application must
not export its menu to the panel, and must therefore continue to show
its menu inside of the application window itself.
I do not know whether this command was specifically created by the
Mageia developers or whether it's an upstream thing that they've
adopted.
Many distributions source their packages from other distributions. For instance, PCLinuxOS sources from Mageia, from Fedora, from openSUSE, and
from Ubuntu. Manjaro mainly sources from Arch, but also contains some
fonts from Ubuntu and some openSUSE stuff with regard to the KDE
integration of browsers [*] and of LibreOffice.
[*] There is a fully KDE-integrated version of Firefox available from
one of the Manjaro folks, but I don't know whether he's an official
Manjaro developer.
It's called Plasmafox, and apart from supporting the KDE global menu
I was wondering why audacity is slow to launch
I found that its command line in the properties dialog is
env UBUNTU_MENUPROXY=0 audacity %F
I would expect just "audacity %F"
This is the only application I can find like this
I am intrigued!
Setting one environment variable has negligible impact. In the case of audacity, start it from a konsole and it's debug output will be visible.
It shows that audacity is checking for various files that it is not
finding. They are for different types of sound systems.
It appears the delay is coming from it looking to see if alternatives
to alsa are present in the system, rather then relying on the system
settings only.
On 28/8/19 6:02 am, David W. Hodgins wrote:
Setting one environment variable has negligible impact. In the case of
audacity, start it from a konsole and it's debug output will be visible.
It shows that audacity is checking for various files that it is not
finding. They are for different types of sound systems.
It appears the delay is coming from it looking to see if alternatives
to alsa are present in the system, rather then relying on the system
settings only.
OK! audacity does work OK which is a relief
ATT Aragorn
A very clear explanation for the env variable.
Thanks
Does it mean that nowadays, even Audacity expects us to be using Ubuntu?
On Wed, 28 Aug 2019 23:51:46 +1000, Doug Laidlaw wrote:
Does it mean that nowadays, even Audacity expects us to be using Ubuntu?
Audacity does no such thing.
If it was, you would see the variable name in the results from the
string /usr/bin/audacity
command.
On 29/8/19 12:06 am, Bit Twister wrote:
On Wed, 28 Aug 2019 23:51:46 +1000, Doug Laidlaw wrote:
Does it mean that nowadays, even Audacity expects us to be using Ubuntu?
Audacity does no such thing.
If it was, you would see the variable name in the results from the
strings /usr/bin/audacity
command.
I never know what will be a string, and what won't.
But I was really
wondering whether it would show up in the "echo ENVIRONMENT" command,
or some variety of it.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 296 |
Nodes: | 16 (2 / 14) |
Uptime: | 76:06:16 |
Calls: | 6,657 |
Calls today: | 3 |
Files: | 12,203 |
Messages: | 5,332,734 |
Posted today: | 1 |