On Wed, 2020-12-23 at 18:15 +1000, Michael D. Setzer II via users wrote:
On 22 Dec 2020 at 23:04, Samuel Sieb wrote:

Subject:                Re: vncserver program disappered on FC32??
To:                     Community support for Fedora users
<users@lists.fedoraproject.org>
From:                   Samuel Sieb <samuel@sieb.net>
Date sent:              Tue, 22 Dec 2020 23:04:46 -0800
Send reply to:          Community support for Fedora users
<users@lists.fedoraproject.org>

On 12/22/20 10:06 PM, Michael D. Setzer II wrote:
On 22 Dec 2020 at 20:28, Samuel Sieb wrote:
On 12/22/20 8:13 PM, Michael D. Setzer II wrote:
Problem is: If it works, you can no longer locally log into that user id,
since it is configured for only the vnc session on that user??

That doesn't make sense.  Can you explain what you mean?

Never said it made sense. Just what it is.

If you set up a user account they way they say. It will start a vnc session
on boot up with that user and that port. You can then vnc into the
computer on that port and use the computer.

If you try to log in locally on that computer with that user id, the log in
doesn't work, and it goes immediately back to the log in screen..

Oh, that's what you mean.  I thought you meant you couldn't ssh into it
using that user or something like that.  Ok, then that's just the same
thing that you were saying further down.  You can't have multiple
graphical sessions for the same user.  It just doesn't work.  Have you
ever been able to do that with vncserver?  It's never worked for me.  Or
it sort of worked briefly, but sooner or later things go badly wrong.

I think if you try and run a local session and vnc session with both using
gnome desktop there are issues with it. But I always run the vnc session
with the xfce desktop and never had a problem. I've also had no problem
running xfce locally with a vnc xfce session. Seems gnome is doing
something with dbus, and causes a conflict with both sessions trying to
use the same dbus settings??

My situation is similar, except that I use MATE exclusively. I am trying to understand why the upstream maintainer's solution allows only a single TigerVNC logon using a particular UserID. In other words, if I have a local USER-A and a TigerVNC USER-A, if one is logged on the other cannot. Does this mean that a TigerVNC USER-A will not have access to local USER-A's home directory, and vice versa. If so, this is ludicrous.

If TigerVNC has been so badly mangled in the name of systemd support, what alternative VNC can folks recommend in its place? I seriously need one to support development of virtual machines hosted on a server with huge storage, and the local console of that storage machine is not in a suitable place for development.

--Doc Savage
    Fairview Heights, IL