Heads up for those who are struggling to find Ubiquiti gear in stock.I just found Wifi6 Lites in stock for $99 at store.ui.com. Ubiquiti stuff - ACTUALLY IN STOCK right now! Networking.Now the TigerVNCserver will be invoked and prompt for password. Mostly the options should only show tigervncserver as entries and choose the auto (0) mode by entering 0 for the input prompt Sudo update-alternatives -config vncserver Reconfigure the alternative for vncserver Remove any other vnc server rather than TigerVNCserver Xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" & I have done the following to get the twm desktop manager on vnc screen:
It then prompts me for my password three times - the first to "create a color profile", the second to "refresh the system repositories" and the third to again "create a color profile."Īfter authenticating, it displays the standard display manager screen, but running an application like a terminal or the file manager appears to start, but apparently displays on the console display, not my virtual display. VNCSConnST: Client pixel format depth 24 (32bpp) little-endian rgb888 VNCSConnST: Server default pixel format depth 24 (32bpp) little-endian rgb888 SVeNCrypt: Client requests security type TLSVnc (258) SConnection: Client requests security type VeNCrypt(19) SConnection: Client needs protocol version 3.8 Vncext: Listening for VNC connections on all interface(s), port 5901ĬomparingUpdateTracker: 0 pixels in / 0 pixels outĬonnections: accepted: 68.195.199.42::43322 It then prints the following when I connect: I can connect to the remote machine via ssh as a regular user, then run the following:
One problem I've had is that I've been able to connect and view the remote desktop, but any subsequent windows that were created are displayed on the actual desktop, not my viewer virtual desktop. Is there another solution? Another vncviewer implementation? Perhaps x0vncviewer? deb files are made for 18.04 or when 1.9.x (or higher) is added to Ubuntu's repo, that this issue will just magically go away. I'll also try setting it so all local users require typing a password first. When I get a chance, I can try adding users to my test machine and see if I can get it to fail the same way. I have manually set one program to launch on login for one of my users in Application Autostart (in Session and Startup).I have the production machine set to allow users to log in to the local GUI without typing a password (maybe the gui is started secretly before login because of this?).I haven't yet tried adding more accounts to the test machine. I have more than one user account on the production machine.I ran across the logged-in-locally problem you're describing on my test machine, so I made sure not to log in on my production machine (even tried right after reboot launching the server via ssh then trying to connect), but it's still black.Ī few differences between my test machine and production machine that could be triggering this black screen issue:
that you were also logged into the local GUI when you started the remote session.
Jmadams1, would you mind sharing your xstartup for Mate, so I can compare? I'm assuming the default xstartup is fine (since it was on the other machine), and that I have something else going on. I don't get black (I am able to see the desktop), but the log file has tons of errors (attached). (I'm not sure why the line breaks aren't showing ^) #!/bin/sh unset SESSION_MANAGER unset DBUS_SESSION_BUS_ADDRESS exec startxfce4 I did a bunch of searching and found a different xstartup suggested here instead of the default created the first time vncserver is run:
The text machine is Xubuntu 18.04, and the projection machine is Ubuntu server 18.04 with the Xubuntu desktop added on top (sudo apt-get install xubuntu-desktop) because I wanted to use the server's install wizard to configure RAID. I repeated the same exact TigerVNC install process on my production machine, and when I connect I just get a black screen.
On my testing machine, I was able to connect correctly.
I tried the suggestion in #668 and downloaded unpacked and moved to / I have a production machine (recently built and many hours of configuration have been put into it), so I tried things on a different machine I had sitting around first.