If I click Yes, it just brings up the message again, and clicking No lets me continue, though I think this is related to whatever's causing the issue. If you suspect the source of the crash is a local extension, applet or desklet, you can disable downloaded add-ons using the checkbox below. You are currently running in fallback mode. Has anyone else ever encountered this before, and have you managed to fix it? Or should I look for another distro that doesn't encounter this issue?ĮDIT: I should mention I get this error message when connect with TightVNC: That is, the desktop icons have disappeared and I can't open neither Chromium or Firefox. I found out that I can open the terminal with ctrl+alt+F1 and use the command "sudo startx" to get me in, however the desktop is now broken. However, when I try to log in to the desktop on the host, it throws me back into the login screen. I can remotely access the Mint desktop fine via TightVNC on my Windows desktop. When you’re ready, click the Connect button.I have no idea how to fix this other than to do a fresh reinstall. For example, Make sure you select the Use SSH or SSL+SSL option before you connect. Under VNC Host:Display, type Replace SSHusername with the username you’d use for your SSH connection, and replace remoteIPaddress with your remote desktop IP address. Open the SSVNC client and, within the main SSVNC client window, fill in the required fields.SSVNC is supported by Windows and Linux operating systems. TigerVNC’s open source credentials, intuitive interface, and exemplary performance during an active connection make it a very capable VNC client for all kinds of remote desktop tasks. One example is SSVNC which, while basic, will tunnel over SSH before making a VNC connection.
Other VNC clients, however, do include SSH tunneling within the client itself. While TightVNC is a popular Windows client for VNC connections, it doesn’t support SSH tunneling within the client itself, requiring you to use PuTTY to make the connection. If your SSH connection is working correctly, TightVNC should load your remote VNC desktop window, ready for you to use.
0 kommentar(er)
