I'm wondering if you could perform an experiment for me. First configure
your system so that it experiences this issue. Then edit
/opt/TurboVNC/bin/xstartup.turbovnc, replace "--exit-with-session" with
"--exit-with-x11", and see if the issue still reproduces. This is just a
hunch.
On Monday, January 22, 2024 at 1:43:39 PM UTC-5 DRC wrote:
> Sounds good. I will revisit if I am ever able to reproduce the issue.
>
>
> On 1/22/24 1:35 PM, Felix Natter wrote:
>
> hello DRC,
>
> thanks for the reply. I tried unsetting SYSTEMD_EXEC_PID and also
> SYSTEMD_EXEC_PID and XAUTHORITY, but get the same result
> (G3_G3_gdm).
> Since you have no further ideas (and I have lightdm-mate or locking instead
> of logout as workarounds), I think I will give this up.
>
> Many Thanks!!
> Felix
>
>
> DRC schrieb am Montag, 22. Januar 2024 um 17:30:48 UTC+1:
>
>> The most relevant comparisons are g3_g3_gdm.envlog vs.
>> mate_g3_lightdm.envlog and g3_mate_gdm.envlog vs. mate_mate_lightdm.envlog,
>> since they compare the same window manager running in TurboVNC with an
>> always-failing vs. an always-successful configuration.
>>
>> Comparing g3_g3_gdm.envlog vs. mate_g3_lightdm.envlog, nothing really
>> stands out except:
>>
>> - XAUTHORITY=/run/user/{uid}/gdm/Xauthority in the failing configuration
>> vs. XAUTHORITY=~/.Xauthority in the successful configuration.
>> - XDG_CONFIG_DIRS and XDG_DATA_DIRS contain /etc/xdg/xdg-ubuntu-xorg in
>> the failing configuration vs. /usr/share/ubuntu in the successful
>> configuration.
>> - SYSTEMD_EXEC_PID is set in the failing configuration.
>> - SSH_AGENT_LAUNCHER is set in the failing configuration (but I don't see
>> how that could matter.)
>> - Some XDG_ display manager variables are set in the successful
>> configuration (but I don't see how that could matter.)
>>
>> Comparing g3_mate_gdm.envlog vs. mate_mate_lightdm.envlog, nothing
>> really stands out except:
>>
>> - GNOME_SHELL_SESSION_MODE, GNOME_TERMINAL_SCREEN, and
>> GNOME_TERMINAL_SERVICE are set in the failing configuration (but MATE
>> doesn't use any of those.)
>> - XAUTHORITY=/run/user/{uid}/gdm/Xauthority in the failing configuration
>> vs. XAUTHORITY=~/.Xauthority in the successful configuration.
>> - XDG_CONFIG_DIRS and XDG_DATA_DIRS contain /etc/xdg/xdg-ubuntu-xorg in
>> the failing configuration.
>> - SYSTEMD_EXEC_PID is set in the failing configuration.
>> - SSH_AGENT_LAUNCHER is set in the failing configuration (but I don't see
>> how that could matter.)
>>
>> Comparing the sometimes-failing configuration (g3_mate_lightdm.envlog)
>> vs. an equivalent always-successful configuration
>> (mate_mate_lightdm.envlog), nothing really stands out except:
>> - GNOME_SHELL_SESSION_MODE, GNOME_TERMINAL_SCREEN, and
>> GNOME_TERMINAL_SERVICE are set in the failing configuration (but MATE
>> doesn't use any of those.)
>> - XDG_CONFIG_DIRS and XDG_DATA_DIRS contain /etc/xdg/xdg-ubuntu-xorg in
>> the failing configuration.
>> - SYSTEMD_EXEC_PID is set in the failing configuration.
>> - SSH_AGENT_LAUNCHER is set in the failing configuration (but I don't see
>> how that could matter.)
>> - Some XDG_ display manager variables are set in the successful
>> configuration (but I don't see how that could matter.)
>>
>> The next thing I would try is unsetting SYSTEMD_EXEC_PID before invoking
>> /opt/TurboVNC/bin/vncserver. (Be sure to verify that it remains unset
>> inside of the TurboVNC session.) If that doesn't change the situation,
>> then try removing /etc/xdg/xdg-ubuntu-xorg from XDG_CONFIG_DIRS and
>> XDG_DATA_DIRS (but I doubt that will matter.) Unfortunately, I have no
>> other ideas.
>>
>> DRC
>>
>> On 1/21/24 9:41 AM, Felix Natter wrote:
>>
>> hello DRC,
>>
>> the sorted environment logs _within_ TVNC sessions are
>> attached (PHYSICAL_VNC_DISPLAYMANAGER.envlog):
>>
>> g3_g3_gdm.envlog: FAILS
>> g3_mate_gdm.envlog: FAILS
>> g3_mate_lightdm.envlog: FAILS (not always!)
>> mate_g3_lightdm.envlog: SUCCEEDS
>> mate_mate_lightdm.envlog: SUCCEEDS
>>
>> I hope I got it right this time.
>>
>> Many Thanks and Best Regards!
>> Felix
>>
>> DRC schrieb am Samstag, 20. Januar 2024 um 17:39:00 UTC+1:
>>
>> To be clear, when I talked about starting a session from SSH, I meant
>> connecting directly to the system using SSH, not doing 'ssh localhost' from
>> the local session. However, I'm not sure if that matters.
>>
>> The value of XDG_SESSION_TYPE should always be x11 in a TurboVNC session,
>> so I suspect that you recorded the environment variables too early. The
>> only difference that matters is the difference between the environment
>> variables inside of a TurboVNC session that fails vs. a TurboVNC session
>> that succeeds. Please record the environment variables inside of the
>> TurboVNC sessions and pipe them through 'sort' before diffing them. It
>> would also be more meaningful to compare a failing vs. successful
>> configuration using the same window manager, i.e. the difference between
>> TurboVNC/GNOME sessions that succeed vs. fail and the difference between
>> TurboVNC/MATE sessions that succeed vs. fail.
>>
>> --
>>
>> 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 turbovnc-user...@googlegroups.com.
>>
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/turbovnc-users/06e641ac-f8d8-42fc-b903-686b519f78e9n%40googlegroups.com
>>
>> <https://groups.google.com/d/msgid/turbovnc-users/06e641ac-f8d8-42fc-b903-686b519f78e9n%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>> --
> 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 turbovnc-user...@googlegroups.com.
>
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/turbovnc-users/94ab41f9-5cb0-48bb-b9bc-b31e15c7fb8an%40googlegroups.com
>
> <https://groups.google.com/d/msgid/turbovnc-users/94ab41f9-5cb0-48bb-b9bc-b31e15c7fb8an%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
>
--
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 turbovnc-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/turbovnc-users/83ee81c9-169b-4438-8cd9-04ba8ad4834cn%40googlegroups.com.
