On Sun, 25 Feb 2024 09:11:34 +0100 francis.montag...@inria.fr wrote:
>> So it's only the combination. I did run a strace, but it's not
>> clear what's going on. It almost seems like it's something to do with
>> the ssh agent, but I wasn't motivated enough to really follow it.
I tried to no avail 1) to call xfce4-session through ssh-agent 2) to unset
SSH_AUTH_SOCK SSH_AGENT_PID before calling xfce4-session 3) to chown
root /tmp/.ICE-unix/
I give up trying to allow an xfce session at the console and under VNC.
This is not possible also with MATE: the VNC session, started after the one at
the console, is blocked on:
Could not acquire name on session bus
Close
and then nothing is usable.
As samuel said earlier, having two sessions may:
cause great confusion and weird happenings.
I have a workaround. For years, I use only a VNC session.
When at the console I only connect to it with a vncviewer "session" defined
as:
[Desktop Entry]
Version=1.0
Name=vncviewer1 Session
Exec=vncviewer :1
Icon=
Type=Application
DesktopNames=VNCVIEWER1
otherwise, I connect to it with "vncviewer -via".
I don't need to have GPU acceleration. This may be available with vglrun, when
at the console.
--
francis
--
_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
