So I very much would like to be able to remote to a fedora 31 (soon to be 32) workstation.

I've always been able to do this until one of the fedora upgrades I did a ways back wayland rolled out. I didn't even know I was broken until I went to do this and it didn't work.

Basically it's the black screen, I tried doing this via tigervnc server and using a vnc client, I've tried just enabling the remote desktop in the settings on my fedora workstation, just about every combo I could think of. several vnc clients, mac's remote desktop tool, etc.

What I do know is that if I am completely logged off my workstation like if it's fresh boot I have been successful in logging in and getting in. The issue is if any user is logged into the workstation and any other user tries to log into it your credentials are accepted but after that you get a black screen and are unable to do anything.

This always worked prior to wayland. My situation is a bit abnormal as I have 3 workstations, 1 windows, 1 fedora, and 1 MacOS (High Sierra). I can interchange what I'm doing on one based on the platform I'm developing on at the time. It's real handy to be able to remote from one to the other for various things. Everyone plays nice in this eco-system except for fedora (wayland). Since the fedora workstation is currently my primary it's not a huge deal. But I'm fixing to change that and would very much like to fix this issue.

I really do not want to go Ubuntu where this just seems to work as my product is Redhat based, and I do not want to backwards to CentOS 7 (pre wayland on 8) as I like having the newer packages. What would the collective suggest?
thx

Fedora has always been the testing/experimental release from RH. Versions and updates break things all the time, while being internally consistent. I would look at the VNC server and VNC configuration on that machine.

Expect stable and LTS distributions to be more consistent in behavior, shorter life tools like Fedora should be expected to change behavior often. It is what they are for!

I'm guessing here, but it seems likely that Wayland is the culprit. Have you tried running GNOME in an X session? I have not seen a similar problem with the Fedora 32 Mate spin, but it uses X, not Wayland.

I want to say this broke when wayland was first introduced. and it's some sort of security thing I *think*.

so if I start my workstation up, and the I remote into from another machine, do some work and then log off and close the session. I can not login to the workstation being directly on the machine. It just takes my password and then comes right back to the login screen.

If I log in to machine directly I can not login remotely even if I log out.

In both cases to switch the login methodology I have to reboot the machine.

I have tried tigervnc server and a few different vnc clients. I have also used my Mac's microsoft remote desktop to connect directly to the machine. ALL of them behave in this same manner.

I have tried logging in to my workstation using gnome classic and then remote over to it and it's the same behavior. So if my machine is strictly headless I'm fine as I would never log directly into the workstation, it's definitely a weird situation but it's been consistent for me over the last several iterations of fedora.