Ah..... the blank screen. My experience is this has to do with sessions, and who's logged into them.
If I use a networked Keyboard/Vid/Mouse and log in to my X11 or Wayland session, and then attempt to use VNC to get a display there as well, then the VNC session is black. It turns out the VNC session is *working*, you just can't see anything. By working I mean launching a program or moving the mouse does both functions. They just show up on the other active sessions screen (IIRC). I dealt with this by only having one session active, which in my case, had the VNC session preferred. Eventually I dealt with it by booting in server mode, where my VGA connector I use with the KVM is always just an ASCII console. Prior to figuring out how to have my OS automatically start the VNC server I would ssh to the unit, start the VNC server, and then use VNC client. This allowed the VNC client session to get my GDM login screen, and to get a KDE desktop. On Wed, Nov 8, 2023 at 1:11 AM Tomas Kuchta <[email protected]> wrote: > On Tue, Nov 7, 2023, 23:33 Robert Detjens <[email protected]> wrote: > > > > > > > > > In both cases, I installed: zypper/dnf install tigervnc and I got the > > > latest version. > > > > Fedora has the server and client in separate packages -- `tigervnc` and > > `tigervnc-server`. The server package has the server service (tounge > > twister, > > heh) at `/usr/lib/systemd/system/[email protected]`. > > > > Thank you - I overlooked the tigervnc-server package + had invisible typo > in username. > > I can start the service and connect to it. Now I need to figure out why the > session is blank - likely something to do with Wayland. > > Thanks again, Tomas > > > >
