Open terminal. 'printenv PATH'. Keep the terminal open.
Open xfce's "run" dialog (or equivalent -- I'm not an xfce user, so please translate if needed). 'printenv PATH >~/pathlog'.
Now 'cat ~/pathlog' in the terminal.
See?Now everyone try it. Please.
You've just discovered what .bashrc is NOT for..bashrc is only to be used to set the characteristics of an interactive bash session!
and even then, it's still not supposed to be used if said session is the login session.
Obviously, I've been holding on to this one for a long time.
The X session does not reference .bashrc or any shell startup script unless it has been improperly hacked to do so. The terminal has it because it starts an interactive (presumably bash) shell session.
But for many years, everything that needs setting has found its way into .bashrc in many, many distros. VL is certainly not alone. To this day, new applications are developed by whiz-bang linux coders that have in their install instructions " . . . and add this line to your ~/.bashrc".
None of which gets sledgehammer a readable dvi automatically.
For now, any fix will be a plain 'ol hack. A kludge. This one looks pretty good, just scroll up in its thread to understand how to de-edit it and use.https://bbs.archlinux.org/viewtopic.php?pid=1006333#p1006333
At some near point, there needs to be a standard way to get from login to an X session and DE/WM that is consistent across environments and where the basic settings are in the same place for all types of session. But desired differences between environments -- whether they be different shells, twm, or just two slightly different xfce sessions -- need to be allowed for. All in a standard, consistent way.
So for this question, the answer is to find a way to put PATH where XFCE will pick it up. Looks like it doesn't get it from where it is now. If the above link doesn't solve it, you'll need to know how VL gets from gdm to XFCE and throw a PATH in its path.