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!


--
faeychild
Running plasmashell 5.15.4 on 5.2.7-desktop-1.mga7 kernel.
Mageia release 7 (Official) for x86_64 installed via Mageia-6-x86_64-DVD.iso


--- MBSE BBS v1.0.7.12 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On Tue, 27 Aug 2019 18:00:58 +1000, faeychild wrote:

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!

$ type audacity
audacity is /usr/bin/audacity

A quick use of the "strings" command

$ strings /usr/bin/audacity | grep UBUNTU

indicates it is a waste of

$ time "env UBUNTU_MENUPROXY=0"
bash: env UBUNTU_MENUPROXY=0: command not found

real 0m0.001s
user 0m0.001s
sys 0m0.000s
time.

--- MBSE BBS v1.0.7.12 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 27.08.2019 at 18:00, faeychild scribbled:

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!

Ubuntu's native desktop environment is GNOME, and up until a few
versions ago, Unity. Both GNOME and Unity =E2=80=94 which was actually jus=
t a
drop-in replacement environment for GNOME Shell =E2=80=94 export the application's menu into the panel at the top of the screen. KDE Plasma
can do that too, albeit that the mechanism is slightly different
between how KDE Plasma does it and how GNOME/Unity did it.

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. =20

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. =20

It's called Plasmafox, and apart from supporting the KDE global menu
and the Qt-/KDE-native file open dialog =E2=80=94 which the openSUSE ve= rsion
of Firefox also has =E2=80=94 it has also been tweaked for privacy. For
instance, it reports its User-Agent as running on Windows 10 so as
to minimize the browser fingerprinting foorprint, and like Waterfox,
it does not contain any of the telemetry stuff. It also defaults to
DuckDuckGo as the search engine, whereas Firefox proper defaults to
Google because of a business deal between Google and Mozilla.
=20
--=20
With respect,
=3D Aragorn =3D


--- MBSE BBS v1.0.7.12 (GNU/Linux-x86_64)
* Origin: A noiseless patient Strider (2:250/1@fidonet)

On Tue, 27 Aug 2019 08:21:13 -0400, Aragorn <[email protected]> wrote:

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.

It's present in the Mageia 6 kde/plasma menu too. According to the
changelog Mageia added the patch from Ubuntu in June 2017 to fix a
GUI menu display problem.

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.

That is not quite accurate. Packages are not shared between distributions,
just patches to fix bugs.

Package sources come from the developer of the package. In the case of audacity, that's https://www.audacityteam.org/

When a distribution first adds a new package, the source comes from the developer of the package. The spec file used to create a package from
the source will either be written from scratch, or sourced from another distribution and then customized to suit the present distribution.

After that the only thing that gets shared between distributions are
patches to fix bugs. Whoever develops a patch will do so on what ever distribution they prefer to use. All other distributions will copy the
patch from that distribution, either directly or from another distribution
that has already copied the patch.

When people refer to "upstream" in bug reports, they are normally referring
to the developer of the package source.

One case that's a bit different is distribution developed packages such
as rpmdrake. It was first developed by a team working for Mandrake. It's
now been forked by Mageia, so in this case the upstream for the package
source is the Mageia distribution rather then a site maintained by it's developers.

[*] 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

That's a fork. :-)

Regards, Dave Hodgins

--
Change [email protected] to [email protected] for
email replies.

--- MBSE BBS v1.0.7.12 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On Tue, 27 Aug 2019 04:00:58 -0400, faeychild <[email protected]> wrote:

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.

Regards, Dave Hodgins

--
Change [email protected] to [email protected] for
email replies.

--- MBSE BBS v1.0.7.12 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

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


--
faeychild
Running plasmashell 5.15.4 on 5.2.7-desktop-1.mga7 kernel.
Mageia release 7 (Official) for x86_64 installed via Mageia-6-x86_64-DVD.iso


--- MBSE BBS v1.0.7.12 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 28/8/19 1:59 pm, faeychild wrote:

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?


--- MBSE BBS v1.0.7.12 (GNU/Linux-x86_64)
* Origin: Aioe.org NNTP Server (2:250/1@fidonet)

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.

--- MBSE BBS v1.0.7.12 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

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
string /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.

Doug.

--- MBSE BBS v1.0.7.12 (GNU/Linux-x86_64)
* Origin: Aioe.org NNTP Server (2:250/1@fidonet)

On Thu, 29 Aug 2019 00:59:49 +1000, Doug Laidlaw wrote:

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.

Me thinks you need to run the command
man strings

But I was really
wondering whether it would show up in the "echo ENVIRONMENT" command,

That would be echo $environment_variable_of_interest_here

or some variety of it.

That command would be "env" or "env | grep environment_variable_of_interest_here"


--- MBSE BBS v1.0.7.12 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)