Re: file fmutil

Only setting PATH in bashrc is a major source for problems on Linux. And it has been so for ever.

In most cases a PATH change in backrc will never be seen by a GUI programme that is opened via a menu or by double clicking a file. Basis env var 101.

On the other hand a gui that is started from a terminal will inherit the envs from the terminal and (if bash) thus also from bashrc.

Often the recommendation is to also have the PATH setting in dot profile (which is one of the start up scripts run at login, and thus at the top of the env hiraki)

But it of course also depend on the system at hand. THe above observations should be correct for Debian based systems.

(it is a very frequent error)



Lars Madsen
Programmør

Institut for Matematik
Aarhus Universitet

person.au.dk/daleif@math<https://person.au.dk/daleif@math>

________________________________
From: tex-live <[email protected]> on behalf of [email protected] <[email protected]>
Sent: 28 November 2025 05:41
To: [email protected] <[email protected]>
Subject: Re: file fmutil

On Wed, Nov 26, 2025 at 09:36:05PM -0500, Greg Bennett wrote:

> Here is a copy of my current path from echo $PATH:
> /usr/local/texlive/2025/bin/x86_64-linux:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin

...

> However if I run from the command line, all is well. There are only
> references to texlive.

This may be an effect of the horribly baroque rules for which startup
scripts are sourced by shells (and /especially/ bash).

Where do you set the PATH you show above? In ~/.bashrc or in
~/.bash_profile or somewhere else?

Depending on your environment, distro etc. shells spawned indirectly
by GUI programs do not always get the benefit of these startup
scripts.

Maybe the next step in testing should be to run TeXstudio itself from
the command line (ie. from inside an xterm or such), instead of
clicking an icon or whatever.

--
Ian