On Fri, May 06, 2022 at 08:33:49PM +0200, Giovanni Biscuolo wrote: > What's relevant is that lxsession does not have a proper XDG_DATA_DIRS
You might be misreading things. > Sorry I made confusion: I'm not concerned about LXTerminal (or other > terminals), it's just that I need a terminal to check my Xsession > environment via CLI Yeah, but you assumed that the environment you saw in your terminal would be identical to the environment seen by whatever is building this menu. That may not be the case. The first thing you need to do is figure out what process is actually making that menu. I doubt very much that it's "lxsession". Once you figure that out, then you can see what environment that process started with (from /proc) and then try to figure out how it got that way. Plus whatever else you need to know. Up above, you mentioned that "lxsession does not have a proper XDG_DATA_DIRS", but that's not necessarily unexpected. /proc only shows you what the *initial* environment is. It's the environment that was given to the process by its parent. Processes can change their own environment, with the intent of passing new variables/values down to their children. This is extremely common with shell scripts, for example. Those changes to the running process's copy of the environment will not be visible in /proc. In the case of lxsession, you may be seeing the initial environment of the session, *before* it dotted in your .profile stuff. Possibly. (I'm still not 100% clear on the relationship between the X session launched by the display manager, and this "lxsession".)
