Hi, I will do some more testing but the system is pretty stock Ubuntu 22.04.5. and can't think of any settings that would affect this. The TurboVNC version is 'TurboVNC Server v3.2.91 (build 20251222)'. The /etc/turbovncserver.conf has only 'wm' and 'resolution' set. I found out if I log in with SSH and start a session by running the 'vncserver'-command, the session inherits the correct environmental variables. So when the session starts it never sources /etc/profile or ~/.profile. However it sources /etc/bash.bashrc and ~/.bashrc. To me this indicates the session starts somehow as "non-login"-type if you get what I mean. I will let you know if I find out more.
keskiviikko 4. helmikuuta 2026 klo 16.47.35 UTC+2 DRC kirjoitti: > I can't reproduce the issue. For me, /etc/profile is sourced properly > for all connections made through the Session Manager. Is there > additional information that might help me reproduce the problem, such as > a special configuration on the host? > > DRC > > > On 2/3/26 4:16 AM, Kimmo wrote: > > Clarification to the original post: > > > > The shells inside all sessions are actually 'non-login' type, but the > > sessions started using Session Manager don't source '/etc/profile'. > > This causes some environmental variables set using '/etc/profile' not > > to load. > > > > What would be the most elegant way to source '/etc/profile' for new > > session while using Session Manager? > > > -- You received this message because you are subscribed to the Google Groups "TurboVNC User Discussion/Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/turbovnc-users/05966ad9-4c6f-4428-a547-90dedb3f1e54n%40googlegroups.com.
