hello DRC,
unfortunately, the problem still occurs without $XAUTHORITY.
This morning I was only able to test with a VM, would it make a difference?
Many Thanks and Best Regards!
Felix
DRC schrieb am Freitag, 19. Januar 2024 um 21:28:25 UTC+1:
I still can't reliably reproduce the issue on my machine, but I am
suspicious that it might have something to do with the XAUTHORITY
environment variable. In a local session, XAUTHORITY is set to
/run/user/501/gdm/Xauthority. If XAUTHORITY is set, then vncserver
instructs Xvnc to use that X authority file, and it wouldn't surprise me if
GDM does something to that file when you log out. Can you try the
following when launching a TurboVNC session from the local session?
unset XAUTHORITY
/opt/TurboVNC/bin/vncserver
That should simulate what happens in an SSH session. If that resolves the
issue, then vncserver probably just needs to ignore XAUTHORITY.
This would also explain why you don't see the problem with lightdm.
lightdm sets XAUTHORITY to ~/.Xauthority, which is the traditional X
authority location that doesn't rely upon systemd.
--
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/a522ed0e-cd95-40f2-962f-40439ca5342fn%40googlegroups.com.
