7 Feb
2019
7 Feb
'19
6:06 p.m.
More details:
There are a lot of discussion whether *dm should or not source
/etc/profile. in other words whether a graphical session is OR NOT a
login session. For example, Lightdm does not, but gdm3 does.
I run Debian Stretch, use some Trinity apps and I already set up
/etc/X11/Xsession.d/40x11-common_xsessionrc to source /etc/profile:
-----8<-----
# This file is sourced by Xsession(5), not executed.
if [ -e /etc/profile ]; then
. /etc/profile
fi
#Source user defined xsessionrc (locales and other environment variables)
if [ -r "$USERXSESSIONRC" ]; then
. "$USERXSESSIONRC"
fi
-----8<-----
But I wonder how Trinity tells its apps are in /opt/trinity/bin.
My only hope, is to add this to
/etc/X11/Xsession.d/40x11-common_xsessionrc (or add 40x11-trinity file
to all of my systems that run lightdm, should I???):
if [ -e /opt/trinity/bin ]; then
. /opt/trinity/bin
fi
Nicolas
On 07/02/2019 18:55, Pisini, John wrote:
https://www.computerhope.com/issues/ch001647.htm
The above should work.
On Thu, Feb 7, 2019 at 12:49 PM Nicolas Bercher via trinity-users
<trinity-users(a)lists.pearsoncomputing.net
<mailto:trinity-users@lists.pearsoncomputing.net>> wrote:
Hi,
Does anyone have clear explanations on how to make lightdm aware of
Trinity's binary path /opt/trinity/bin?
Thanks a lot,
Nicolas
---------------------------------------------------------------------
To unsubscribe, e-mail:
trinity-users-unsubscribe(a)lists.pearsoncomputing.net
<mailto:trinity-users-unsubscribe@lists.pearsoncomputing.net>
For additional commands, e-mail:
trinity-users-help(a)lists.pearsoncomputing.net
<mailto:trinity-users-help@lists.pearsoncomputing.net>
Read list messages on the web archive:
http://trinity-users.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
--
John Pisini
Systems Administrator
TFCCS
617-450-3988
Disclaimer for email:
The information contained in this electronic message and any attachments
to this message is intended for the exclusive use of the addressee(s)
and may contain confidential or privileged information. This email is
not intended to, and shall not, constitute an electronic signature
giving rise to a binding legal contract, unless expressly stated
otherwise in the body of the email by the sender.