I have a virtual machine with CentOS 7 at school, but I need to work from home. So, I followed a tutorial to install Gnome and another to create a VNC server, all this to install TeamViewer. Then, I install TeamViewer 11, but when I open it, it says the famous message: Not ready, Please check your connection I tried to input proxy settings, but it didn't save the changes, so I had to edit the global.conf file. I know that the proxy is well in the system because I can navigate; I can even ping 178.77.120.1, and it works. But the problem still remains. Then, searching the web, I saw I could change the SELinux config to permissive. I do that in another virtual machine, and that works, but it doesn't work on my machine. It has a Wine problem. I try to fix it using the following: # setsebool -P mmap_low_allowed 1 but that doesn't work. Another solution was to add to mdns4 to host in /etc/nsswitch.conf, but it doesn't work. So I decide to uninstall, using: rpm -qa | grep teamviewer rpm -e But when I installed TeamViewer again, it loaded the proxy settings, so I think it didn't completely remove them. Here's today's log Start: 2016/09/08 08:37:06.584 (UTC-5:00) Version: 11.0.57095 ID: 0 Loglevel: LogAll (0) License: 0 Server: master14.teamviewer.com IC: 0 CPU: x86 Family 6 Model 45 Stepping 7, GenuineIntel CPU extensions: p8 OS: Lx CentOS 7 (Core) (32-bit) IP: xx.xx.xxx.xxx Proxy-Settings: Type=0 IP= User= AppPath: C:\TeamViewer\TeamViewer.exe UserAccount: root 2016/09/08 08:37:06.588 8 29 GX2 AutoLogin::Login: enabled: 0 2016/09/08 08:37:06.803 8 29 GX2 CMain::LoadResourceDLLs(): No custom resource dll found 2016/09/08 08:37:06.805 8 29 GX2 Win32_GUI::FontReallyExists: 'Segoe UI' found 0 matches. 2016/09/08 08:37:06.805 8 29 GX2 Win32_GUI::FontReallyExists: 'Liberation Sans' found 4 matches. 2016/09/08 08:37:06.814 8 29 GX2 InterProcessBase::StartTcpCommunicationInternal(): setting m_NetworkConnector to new TCP connector 2016/09/08 08:37:06.814 8 29 GX2 Opening local TCP connection to 127.0.0.1:5942 2016/09/08 08:37:06.815 8 29 GX2 Local TCP connection established 2016/09/08 08:37:06.815 8 29 GX2 Process ID: L 32511 / W 8 2016/09/08 08:37:06.902 8 29 GX2 SettingsIPCReception receive a SYNCHRONISE Settings command : UserSettings 2016/09/08 08:37:06.904 8 29 GX2 Received Control_InitIPC_Response processtype=1 2016/09/08 08:37:06.904 8 29 GX2 Received Control_InitIPC_Response runningProcesses=3 2016/09/08 08:37:06.904 8 29 GX2 Control_InitIPC_Response: all processes 3 completely initialized 2016/09/08 08:37:06.940 8 29 GX2!! ProxySearch.GetProxiesFromPAC: WinHttpGetProxyForUrl(WPAD) failed for URL 'http://www.teamviewer.com/ ' with error 12166, Errorcode=12166 2016/09/08 08:37:06.944 8 29 GX2!! ProxySearch.GetProxiesFromPAC: WinHttpGetProxyForUrl(WPAD) failed for URL 'https://www.teamviewer.com:443/ ' with error 12166, Errorcode=12166 2016/09/08 08:37:06.944 8 29 GX2 ProxySearch: found WinHTTP proxy: http//10.20.4.15:3128 2016/09/08 08:37:06.946 32646 4091542336 QX2 SessionBusWatcher: suitable bus found with address "unix:abstract=/tmp/dbus-LumdutjnU5,guid=8c230a14389528c505b45eeb57d008e6" 2016/09/08 08:37:07.070 8 9 GX2!! GetSimpleDisplayCertNameFromFile: File 'C:\TeamViewer\tv_w32.dll' does not exist., Errorcode=2 2016/09/08 08:37:07.070 8 9 GX2!! VerifyTeamViewerSignature() : WinVerifyTrust failed, result=2, Errorcode=2 2016/09/08 08:37:07.070 8 9 GX2!! MachineHooks: Library not found, Errorcode=2 2016/09/08 08:37:07.074 8 9 GX2 MachineID m=0 - 1 2016/09/08 08:37:07.077 8 9 GX2 TVUpdate::Init() Version-URL: download.teamviewer.com/download/update/ Update-URL: download.teamviewer.com/download/update/ 2016/09/08 08:37:07.077 8 9 GX2 TVUpdate::Init() Preview Channel Number : 1 2016/09/08 08:37:07.165 8 9 GX2!! TVW Wine: SetWindowManagerClassHint: No such window, Errorcode=120 2016/09/08 08:37:07.195 8 9 GX2!! TVW Wine: SetWindowManagerClassHint: No such window 2016/09/08 08:37:07.199 8 9 GX2!! TVW Wine: SetWindowManagerClassHint: No such window 2016/09/08 08:37:07.218 8 9 GX2 ManagerHolderStateMachine: Switching from None to NotReady 2016/09/08 08:37:07.219 8 21 GX2 ChatManager::ChatManager: created 2016/09/08 08:37:07.219 8 21 GX2 ChatManager::Factory: ChatManager created 2016/09/08 08:37:07.219 8 21 GX2 IncomingBetterChatCommandHandler::IncomingBetterChatCommandHandler: created 2016/09/08 08:37:07.219 8 21 GX2 IncomingChatCommandRegistration::Start: registering for ready state properties 2016/09/08 08:37:07.220 8 9 GX2!! DragDropRegistration: could not register window, HR=80040155 2016/09/08 08:37:07.222 8 9 GX2!! BuddyWindow.LoadWindowPosUnscaled: bad lexical cast 2016/09/08 08:37:07.227 8 9 GX2 AccountLoginGUI::CreateLoginKey(): [OnlineState] System is set to Visible. 2016/09/08 08:37:07.234 8 9 GX2!! TVW Wine: SetWindowManagerClassHint: No such window, Errorcode=120 2016/09/08 08:37:07.272 8 9 GX2 CMainWindow::ShouldShowDynamicPassword(): dynPw=1 allowIncoming=1 id=0 ka=0 lanAllowed=0 lanOnly=0 networkState=1 showDynPwd=0 2016/09/08 08:37:07.278 8 9 GX2!! ServerControl: RegisterPowerSettingNotification failed with error 0 2016/09/08 08:37:07.323 32645 139768218244864 gX2 PulseAudio: Connected to server 'unix:/run/user/0/pulse/native' (protocol version 30, library version 6.0.0 2016/09/08 08:37:07.324 32645 139768311990016 gX2 PulseAudio: Connection established 2016/09/08 08:37:07.456 8 33 GX2!! WineMixer: Unable to initialise mixer -1 -1 2016/09/08 08:37:07.456 32645 139768218244864 gX2 PulseAudio: Exit main loop (0), err=-2 2016/09/08 08:37:36.780 8 9 GX2 CMainWindow::InitCloseTV(): Prepare to close TeamViewer 2016/09/08 08:37:36.780 8 9 GX2!! ServerControl: UnregisterPowerSettingNotification failed with error 0 2016/09/08 08:37:36.781 8 9 GX2!! TVW Wine: SetWindowManagerClassHint: No such window 2016/09/08 08:37:36.785 8 9 GX2 Chat::Stop: Stopping chat 2016/09/08 08:37:36.785 8 9 GX2 Chat::Stop: Cancelling of Start 2016/09/08 08:37:36.786 8 9 GX2 ChatManager::UnregisterIncomingCommandRegistration: destroying incomingCommandRegistration 2016/09/08 08:37:36.786 8 9 GX2 IncomingChatCommandRegistration::Stop: disconnecting ready state properties 2016/09/08 08:37:36.787 8 9 GX2 ChatManager::Close 2016/09/08 08:37:36.787 8 9 GX2 ChatManager::UnregisterIncomingCommandRegistration: destroying incomingCommandRegistration 2016/09/08 08:37:36.787 8 9 GX2 ChatManager::ClearAccountChat: clearPersistently = 0 2016/09/08 08:37:36.788 8 9 GX2 ChatManager::ClearNonAccountChat 2016/09/08 08:37:36.789 8 9 GX2 ChatManager::~ChatManager: destroyed 2016/09/08 08:37:36.789 8 9 GX2 IncomingBetterChatCommandHandler::IncomingBetterChatCommandHandler: destroyed 2016/09/08 08:37:36.789 8 9 GX2!! MainWindow.OnDestroy: WTSUnRegisterSessionNotification failed with error 0 2016/09/08 08:37:36.792 8 9 GX2 CMainWindow::OnDestroy(): Closing TeamViewer 2016/09/08 08:37:36.907 32645 139768235030272 gX2 XClipboard: Shutting down event loop 2016/09/08 08:37:36.955 32645 139768525608768 gX2 TVGuiSlave.64: Terminated 2016/09/08 08:37:37.008 8 9 GX2!! ConfigurationHub::HandleRegistrationResponse(): registering for feature 1 failed with error 2 2016/09/08 08:37:37.008 8 9 GX2!! ConfigurationHub::HandleRegistrationResponse(): registering for feature 1 failed with error 2 2016/09/08 08:37:37.009 5552 4147260224 S CInterProcessNetwork: Received DisconnectIPC from processID 32511 (ProcessType: 2 in Session 2) with reason 1 2016/09/08 08:37:37.009 5552 4147260224 S Process 32511 in session 2 has terminated 2016/09/08 08:37:37.009 5552 4147260224 S TerminalServer::ProcessTerminated_Finalize: process 32511 terminated 2016/09/08 08:37:37.009 5552 4147260224 S SysSessionInfoManager: updating session information for session 2 from GUI 2016/09/08 08:37:37.009 5552 4094196544 S XSession: 2 [SysSession 2 [type=1 tty=4294967295 pseudotty=1 info=1 id= user=root state=unknown active=0 reliable=0]] 2016/09/08 08:37:37.009 5552 4094196544 S Updated sessions: [ 1 ] [ 2 root ] [ 9 ] 2016/09/08 08:37:37.009 5552 4094196544 S UpdateOnlineState m_ManualStop 2016/09/08 08:37:37.010 8 22 GX2 CTcpProcessConnector::HandleRead(): Socket gracefully closed (PID=5552) 2016/09/08 08:37:37.010 8 22 GX2 CTcpProcessConnector::CloseConnection(): PID=5552 2016/09/08 08:37:37.010 8 22 GX2! InterProcessBase::EventFunctionInternal(): IPC-Connection Closed 2016/09/08 08:37:37.010 8 22 GX2 CTcpProcessConnector::CloseConnection(): PID=5552 2016/09/08 08:37:37.010 8 22 GX2 CTcpProcessConnector::CloseConnection(): Shutdown socket returned error 10058: Unknown error 2016/09/08 08:37:37.010 5552 4147260224 S CTcpProcessConnector::HandleRead(): Socket gracefully closed (PID=32511) 2016/09/08 08:37:37.010 5552 4147260224 S CTcpProcessConnector::CloseConnection(): PID=32511 2016/09/08 08:37:37.010 5552 4147260224 S CInterProcessNetwork::NewInterProcessDataAvailable(): ConnectionClosed session=2 ptype=2 2016/09/08 08:37:37.010 5552 4147260224 S UpdateOnlineState m_ManualStop 2016/09/08 08:37:37.010 5552 4147260224 S CTcpProcessConnector::CloseConnection(): Shutdown socket returned error 107: Transport endpoint is not connected 2016/09/08 08:37:37.011 8 22 GX2!! CTcpProcessConnector::CloseConnection(): Shutdown socket returned error 10009: Unknown error, Errorcode=317 2016/09/08 08:37:37.012 8 9 GX2 interprocessbase::SecureNetwork destroyed 2016/09/08 08:37:37.013 8 9 GX2 TVW Terminating GUI slave 2016/09/08 08:37:37.013 8 9 GX2 Wine: Wine DLL freed 2016/09/08 08:37:37.015 32646 4113962752 QX2 TVGuiDelegate: Terminated

I want to install TigerVNC on my freshly installed CentOS 7 server, version centos-release-7-4.1708.el7.centos.x86_64. So besides other tutorials I've tried already, I followed the Red Hat guide. However with variable error messages depending on the tutorial I never got the service to start. The following is exactly what I did on a new installation of CentOS 7: yum install tigervnc-server cp /usr/lib/systemd/system/vncserver@.service /etc/systemd/system/vncserver@.service vi /etc/systemd/system/vncserver@.service initial file content: [Unit] Description=Remote desktop service (VNC) After=syslog.target network.target [Service] Type=forking User= # Clean any existing files in /tmp/.X11-unix environment ExecStartPre=-/usr/bin/vncserver -kill %i ExecStart=/usr/bin/vncserver %i PIDFile=/home//.vnc/%H%i.pid ExecStop=-/usr/bin/vncserver -kill %i [Install] WantedBy=multi-user.target file content after edit: [Unit] Description=Remote desktop service (VNC) After=syslog.target network.target [Service] Type=forking User=root # Clean any existing files in /tmp/.X11-unix environment ExecStartPre=-/usr/bin/vncserver -kill %i ExecStart=/usr/bin/vncserver %i PIDFile=/home/root/.vnc/%H%i.pid ExecStop=-/usr/bin/vncserver -kill %i [Install] WantedBy=multi-user.target Instructions after file edit: systemctl daemon-reload su - root vncpasswd systemctl start vncserver@:1.service Job for vncserver@:1.service failed because a timeout was exceeded. See "systemctl status vncserver@:1.service" and "journalctl -xe" for details. [root@localhost ~]# systemctl status vncserver@:1.service ● vncserver@:1.service - Remote desktop service (VNC) Loaded: loaded (/etc/systemd/system/vncserver@.service; disabled; vendor preset: disabled) Active: failed (Result: timeout) since Wed 2018-01-03 09:00:17 UTC; 22s ago Process: 2045 ExecStart=/usr/bin/vncserver %i (code=exited, status=0/SUCCESS) Process: 2040 ExecStartPre=/usr/bin/vncserver -kill %i (code=exited, status=2) Jan 03 08:58:50 localhost vncserver: New 'localhost:1 (root)' desktop is localhost:1 Jan 03 08:58:50 localhost vncserver: Creating default startup script /root/.vnc/xstartup Jan 03 08:58:50 localhost vncserver: Creating default config /root/.vnc/config Jan 03 08:58:50 localhost vncserver: Starting applications specified in /root/.vnc/xstartup Jan 03 08:58:50 localhost vncserver: Log file is /root/.vnc/localhost:1.log Jan 03 08:58:50 localhost systemd[1] : PID file /home/root/.vnc/localhost:1.pid not readable (y...art. Jan 03 09:00:17 localhost systemd[1] : vncserver@:1.service start operation timed out. Terminating. Jan 03 09:00:17 localhost systemd[1] : Failed to start Remote desktop service (VNC). Jan 03 09:00:17 localhost systemd[1] : Unit vncserver@:1.service entered failed state. Jan 03 09:00:17 localhost systemd[1] : vncserver@:1.service failed. Hint: Some lines were ellipsized, use -l to show in full. Does anyone have a clue how I can solve this?

I am running tigervnc-server on CentOS 6.8, however the gnome desktop won't start for me! I have done a yum groupinstall of "X Window System", "Desktop" and "General Purpose Desktop". On one of my other CentOS VMs (v6.6), installing these packages is sufficient for having the gnome-desktop automatically startup for me when starting a vncserver. I'm running: vncserver :05 -geometry 2048x1024 In /home/user/.vnc/hostname:05.log, I see: vncconfig: unable to open display "hostname:05" xrdb: Connection refused xrdb: Can't open display 'hostname:05' xmodmap: unable to open display 'hostname:05' ** (gnome-session:12313):WARNING **: Cannot open display The VNC server starts, and I'm able to connect via vncviewer, but get a black screen. Is there anything else I can look at to troubleshoot? The log isn't very helpful; I've been googling this problem for days, and haven't found anything that fixes it (Ex: made sure I'm in runlevel 5, I re-installed the desktop packages mentioned above, removed .vnc directory, stepped through xstartup, tried comparing various settings with my other VM where the gnome desktop is working) Anyone know of something else I can look at to troubleshoot this issue? Any other logs, or things to check?

I am trying to figure out how I can VNC to my Ubuntu 19.04 desktop which doesn't have a monitor or keyboard/mouse. I installed Ubuntu 19.04 on an external USB hard drive using my MacBook Air. I then booted Ubuntu on the MacBook Air and installed SSH. Then the above hard drive which has Ubuntu installed was connected to my headless desktop and Ubuntu boots up perfectly and I was able to connect to my Ubuntu desktop via SSH on my MacBook Air. I installed tightvncserver on Ubuntu via SSH and when I connect to Ubuntu via VNC using MacBook Air, I get a grey screen on VNC. Read many articles and tutorials using xserver-xorg-video-dummy and also using dummy plugs for DVI and none of these works. How can I have Ubuntu boot up normally as if it was connected to a monitor and connect to it using VNC? Seems like Ubuntu 19.04 is not booting up the X server window without a monitor connected. Please don't provide solutions that requires using thrid-party desktop environments when Ubuntu already has a perfectly working desktop environment which only functions when monitor is connected. I booted Ubuntu 19.04 on my MacBook Air and logged in with the normal GUI interface. I started tightvncserver and when I login to VNC I also get a grey screen.

I have a dedicated server. There's a VNC Server and I can connect to VNC Server with a VNC Client with port 5901 so it takes me to display :1 when I connect there with a VNC Client. I've read pretty many documents about ssh -L and ssh -R command-line commands, but it's pretty weird, because they have servers and such on their own machines and on their remote machines so I get confused about that where are they even trying to connect and what etc. 1. I have dedicated server with VNC Server, Web Server, Game Server and Firewall. 2. VNC Server is running and TCP/UDP connection has been enabled only to ports of Web Server, SSH, Game Server. 3. I want connect to my VNC Server with my VNC Client (from my own pc), but using a tunneled connection, because people are trying my password too many times or something, because sometimes it says "Too many authentication failures" what a tards they are, because they will never guess the password. Anyways. I have tried similar: ssh root@DEDICATEDIP -L 5901:DEDICATEDIP:5901 ssh root@DEDICATEDIP -R 5901:DEDICATEDIP:5901 I also tried this one (found from this site): ssh -L 5901:localhost:5901 -p 22 root@DEDICATEDIP If I write "su" in SSH and I write my root password I can get in with root account, but when it asks my root password on ssh after trying to fill any of these tunneling commands it says the password is wrong and permission denied? **Edit:** - My PC: PuTTy (SSH Client), VNC Viewer (VNC Client) - Dedibox: VNC Server, GameServer, Web Server, SSH Server ufw status - 22 - ALLOW - Anywhere - 22 - ALLOW OUT - Anywhere VNC Server is running and I can confirm that. If I add 5901 to ALLOW and ALLOW OUT I can simply connect there without a tunneling. 1. (My PC) Open PuTTY 2. (My PC) PuTTY Configuration -> Connection -> SSH -> Tunnels - Source port - Destination [163.xxx.xxx.xxx:5901] - [ADD] 3. Now PuTTY shows "Forwarded ports: " -> "L5902 163.xxx.xxx.xxx:5901" 4. I connect to server with SSH including the Tunnel settings I've configured now. 5. I type "su" and I submit my root password. 6. root@MyBox: /home/sysadmin# (sysadmin is normal user for my box) 7. I type: "ssh root@IP_OF_DEDI -L 127.0.0.1:5902:127.0.0.1:5901" 8. VNC Client keeps connecting for a while. Like (15 seconds) and says: "The connection was refused by the computer"

i have a headless box running bbqlinux that i'm trying to use as an android-studio development box. when i go to launch an .avd in the emulator, i receive this error: Cannot launch AVD in emulator Output: emulator: ERROR: x86 emulation currently requires hardware acceleration! Please ensure KVM is properly installed and usable. CPU acceleration status: This user doesn't have permissions to use KVM (/dev/kvm). this was freaking me out and i spent a good amount of time trying to sure that everything was enabled, installed correctly, permissions set, etc... then: i plugged a screen in and logged directly into the box and bam! it works fine. so my problem is maybe the vncserver? i'm using tigervnc that i set up according to this page: https://wiki.archlinux.org/index.php/Vncserver just in case it helps, my xstartup file is unset SESSION_MANAGER unset DBUS_SESSION_BUS_ADDRESS [ -x /etc/vnc/xstartup ] && exec /etc/vnc/xstartup [ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources vncconfig -iconic & startxfce4 & other than that, i've not changed the default environment hardly at all except to add lighttable, ssh, & vnc. so my question is really - should i not be doing it this way? is there a better workflow or vnc server program for what i'm trying to do? - is there a command switch or option that i missed that maybe enables the hardware acceleration over vnc? thanks!

So I installed a VNC server (Tight VNC) on my workstation 'orac' which is running Debian Jessie with KDE Plasma. And a VNC client (also Tight VNC) on my workstation 'tact' running Debian Stretch with KDE Plasma. I ran vncpasswd on orac to configure the password. I want to use VNC to use 'orac' from 'tact'. From tact I ssh'ed to orac and started the vncserver: jj5@orac:~$ vncserver New 'X' desktop is orac:1 Starting applications specified in /home/jj5/.vnc/xstartup Log file is /home/jj5/.vnc/orac:1.log Then from a console on tact I ran: jj5@tact:~$ vncviewer orac:1 Connected to RFB server, using protocol version 3.8 Enabling TightVNC protocol extensions Performing standard VNC authentication Password: Authentication successful Desktop name "jj5's X desktop (orac:1)" VNC server default format: 32 bits per pixel. Least significant byte first in each pixel. True colour: max red 255 green 255 blue 255, shift red 16 green 8 blue 0 Using default colormap which is TrueColor. Pixel format: 32 bits per pixel. Least significant byte first in each pixel. True colour: max red 255 green 255 blue 255, shift red 16 green 8 blue 0 vncviewer: VNC server closed connection Before vncviewer: VNC server closed connection is reported everything seems to be working smoothly. A window opens, I see KDE Plasma doing it's login/loading thing, then my orac desktop loads, a bunch of default Dolphin windows load, and KDE Plasma starts processing my autostart scripts, so everything seems to be working fine, and then almost as soon as it starts KDE/VNC disappears and shuts down usually with vncviewer: VNC server closed connection but sometimes with vncviewer: read: Connection reset by peer instead. So why is KDE (or VNC?) bailing just as soon as it starts? Any help greatly appreciated! p.s. here's some extra info about the environment on the VNC server (orac): jj5@orac:~/.vnc$ ls -al total 24K drwx------ 2 jj5 jj5 4.0K May 4 17:35 ./ drwxr-xr-x 74 jj5 jj5 4.0K May 4 17:35 ../ -rw-r--r-- 1 jj5 jj5 1.3K May 4 17:36 orac:1.log -rw-r--r-- 1 jj5 jj5 5 May 4 17:35 orac:1.pid -rw------- 1 jj5 jj5 8 May 4 15:52 passwd -rwxr-xr-x 1 jj5 jj5 263 May 4 17:32 xstartup* And the log file says: jj5@orac:~/.vnc$ cat orac\:1.log 04/05/17 17:35:57 Xvnc version TightVNC-1.3.9 04/05/17 17:35:57 Copyright (C) 2000-2007 TightVNC Group 04/05/17 17:35:57 Copyright (C) 1999 AT&T Laboratories Cambridge 04/05/17 17:35:57 All Rights Reserved. 04/05/17 17:35:57 See http://www.tightvnc.com/ for information on TightVNC 04/05/17 17:35:57 Desktop name 'X' (orac:1) 04/05/17 17:35:57 Protocol versions supported: 3.3, 3.7, 3.8, 3.7t, 3.8t 04/05/17 17:35:57 Listening for VNC connections on TCP port 5901 04/05/17 17:36:04 Got connection from client 10.1.1.126 04/05/17 17:36:04 Using protocol version 3.8 04/05/17 17:36:04 Enabling TightVNC protocol extensions 04/05/17 17:36:06 Full-control authentication passed by 10.1.1.126 04/05/17 17:36:06 Pixel format for client 10.1.1.126: 04/05/17 17:36:06 32 bpp, depth 24, little endian 04/05/17 17:36:06 true colour: max r 255 g 255 b 255, shift r 16 g 8 b 0 04/05/17 17:36:06 no translation needed 04/05/17 17:36:06 Using tight encoding for client 10.1.1.126 04/05/17 17:36:06 Using compression level 1 for client 10.1.1.126 04/05/17 17:36:06 Using image quality level 6 for client 10.1.1.126 04/05/17 17:36:06 Enabling X-style cursor updates for client 10.1.1.126 04/05/17 17:36:06 Enabling cursor position updates for client 10.1.1.126 04/05/17 17:36:06 Enabling LastRect protocol extension for client 10.1.1.126 Note that 10.1.1.126 is my VNC client 'tact'. My xstartup script is pretty much just the default one (I don't have an ~/.Xresources file so I removed that from the xrdb command, otherwise it's as-is): jj5@orac:~/.vnc$ cat xstartup #!/bin/sh #xrdb $HOME/.Xresources xrdb xsetroot -solid grey #x-terminal-emulator -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" & #x-window-manager & # Fix to make GNOME work export XKL_XMODMAP_DISABLE=1 /etc/X11/Xsession

I have started vncserver or remote instance with the vncserver command, and now am able to connect to it with VNC client. Unfortunately, I can't start vncconfig due to error No VNC extension on display Everything is happening on VNC. How can it be?

Is it possible to chain multiple ssh connections together with each connection specified as an ssh host? I know it's possible to use the -W flag or nc to do a second hop to another hostname or ip address (see, e.g., https://unix.stackexchange.com/questions/25055/ssh-via-multiple-hosts) . I haven't been able to get this to work the way I want for a couple reasons. First, for the second hop, I want to use a key file stored on the intermediate host, and I don't see a way to specify this with either -W or nc. Second, the final destination has a variable ip address. To deal with this, I have a script running on the destination that writes its ip address to a file stored on the intermediate host and then a script (look_up_ip.sh) on the intermediate host that prints out this ip address. On the intermediate host, I have this entry in ~/.ssh/config: Host destination HostName destination User dest_user IdentityFile ~/.ssh/destination PreferredAuthentications publickey ProxyCommand nc $(look_up_ip.sh %h) %p which allows me to connect to the destination from the intermediate with just ssh destination. What I would like to do is put something in ~/.ssh/config on the first machine to define the destination host (as, e.g., hopped_destination) so that ssh will first connect to the intermediate host and then do ssh destination from there, so I can just do ssh hopped_destination from the first machine and have the intermediate ~/.ssh/config deal with the identity file and ip lookup for the destination. Part of the reason why I want this is that I ultimately want to be able to connect to the destination with VNC using vncviewer -via destination localhost:0, and I want the connection not to be accessible to other users on the intermediate host (as implied in parts of the accepted answer to this question: https://superuser.com/questions/96489/an-ssh-tunnel-via-multiple-hops) . I was hoping that it would be possible to put ssh into ProxyCommand on the first machine with something like: Host destination ProxyCommand ssh -t intermediate_user@intermediate_host ssh destination but I haven't found options that allow something like this to work. I would also welcome any suggestions on better ways to do this (is there a way to get rid of the nc ProxyCommand I am using now?). I could probably work out a script to do the VNC command more directly but that might be more complicated (handling the port forwarding directly and being sure to close things on exit, and being sure not to open a port for all users).

I am using remote desktop on a windows machine to connect to a CentOS 7 machine running a Xrdp server. Recently I had a problem with an application, where the avaialable openGL version (2.1) was not enough and it suggested either updating it, or using VNC. While trying to make a VNC connection to work I made several updates inlcuding a Kernel update. I could not get the turboVNC to work at the same time than Xrdp, and damaged the settings somehow. Now, when I connect to the Xrdp session the Gnome shell window is very small and has a weird aspect ratio, making it unusable (see picture below, the black area is the the size of my screen). Even if logged out of the gnome session, where I am able to select other shell (KDE, for example) I still have the same window size. Since I could not find a similar problem, I am not sure what is causing the problem. How could I return the size of the window to its original shape and size?

I'm looking for a way to create a VNC console user that executes the command screen or bash immediately after logging in so they get their own restricted shell for executing commands etc. Screen/bash will be pre-configured to handle all security issues. The VNC console also has to terminate once the user types the exit/logout command as I don't want them to access the rest of the system. I have already looked through the documentation of TigerVNC and TightVNC but couldn't find anything useful. If this is not possible with VNC, a SSH console can work as well. The server's OS is CentOS.

On my VM I have installed Oracle Linux 9.6 without any desktop environment, so everything I have there is accessible through CLI. I would like to run Oracle Database GUI installer on that server by executing /uo1/app/oracle/product/19.0.0/dbhome_1/runInstaller and to do that I would like to use TigerVNC alongside with xterm. To do so on the server I have installed the packages:

dnf install tigervnc-server xterm

Then I can run VNC session in old-fashioned way by executing this command:

vncserver -geometry 1024x768

I can connect to the VNC session on port 5901 using Remmina and quick VNC connection. However, the command vncserver seems to be obsolete and will be removed in next versions of Oracle Linux. In the message shown after executing the vncserver command there is an information to use more modern approach with systemd. My goal is to switch to this more modern method, but I've got a trouble there, because I don't know how the session should be properly configured when on my VM I don't have any desktop environment. In the config file /etc/tigervnc/vncserver-config-defaults there is really important setting called session and by default it is set to gnome: session=gnome When I leave it as it is and try to run the VNC using command sudo systemctl start vncserver@:1 I receive an error indicating that GNOME desktop session hasn't been configured on my server (which is obvious and intended).

Could not find session desktop file /usr/share/xsessions/gnome.desktop at /usr/libexec/vncserver line 322.
Could not load configured desktop session gnome
Could not find a desktop session to run

I will be thankful for tips how to configure TigerVNC on my Oracle Linux 9.6 using systemd to run GUI Oracle Database installer from there assuming, that there isn't any desktop environment.

I installed VNC server on a CentOS machine. I set up a user, and then enabled the VNC server for them on startup following these steps: https://www.digitalocean.com/community/tutorials/how-to-install-and-configure-vnc-remote-access-for-the-gnome-desktop-on-centos-7 . I can successfully log into the machine over VNC, but it appears that the VNC users are not sharing the same session... as if I log into the physical machine and start up a process, when the VNC connection is made, nothing is active on the desktop at all. What did I do wrong? I need VNC to allow users to log in and remotely debug software which may or may not have been started by someone logged into the physical machine

I use VNC (RealVNC "VNC Viewer" app) on my Mac to connect to Linux desktops: Fedora 35 & Ubuntu 21. They both are using GNOME desktop: 41.1 for Fedora, and 40.5 for Ubuntu I recently discovered that **the 10-key (numeric) part of my Mac keyboard no longer works on either desktop when connected via VNC**. These are both physical machines, but I have not yet tried actually connecting the same keyboard to the Linux machines yet since I need the VNC connection to work. I have disabled "Mouse Keys" but this has no effect and did not resolve the issue. Is this a bug in GNOME perhaps? Worth mentioning that the 10-key does work in Windows and macOS when connected via VNC. Also, for whatever reason the 10-key **does** work in the calculator app in Linux, but nothing else. When trying to use the 10-key to enter numbers in a text editor app I just get the "ding" error sound. When trying to use it in the terminal it prints outs all caps letters: for example - 123456789 shows: [me@fedora35 ~]$ BDECA I have reloaded the OS and the issue persists - this is a problem with my CLIENT machine (macOS), not the Linux VNC server (Fedora, Ubuntu, etc).

I need to access a remote machine via a high latency, slow connection. It uses x11vnc and I want it to broadcast video in much lower quality than what's actually on the screen. First thing that comes to mind is to use less colours (e.g. 8 bit), but it can be anything, as long as the remote machine is responsive even though it may, for example, show a large rich-colour desktop image (which I don't need to see anyway). Something [like this](https://superuser.com/questions/411058/setting-up-tightvnc-for-8-bit-pixels) , except for x11vnc. I will, however, appreciate keeping all the text sharp because, I work with the terminal. Here's what I tried: - use -notruecolor, found here http://www.karlrunge.com/x11vnc/x11vnc_opts.html - use -speeds dsl, found here https://ubuntuforums.org/showthread.php?t=1331555 - try setting 8 bit video using -rawfb, found here https://linux.die.net/man/1/x11vnc - enable -ncache 10 as per https://feeding.cloud.geek.nz/posts/high-latency-vnc-tech-support/ , but got [this issue](https://github.com/novnc/noVNC/issues/525) I'm using the built-in Screen Sharing app, which [seems to be almost the only option](http://web.archive.org/web/20180324015551/http://www.davidtheexpert.com/post.php?id=5) on Mac OS. I'm out of ideas. Please help.

Is there any way to remote control GRUB? I am interested in not having to walk to the machine when it reboots. As such, I am only interested in non-virtualized solutions. In particular, I want remote access to the GRUB console. The ability to select an entry, or edit the options, or even do something completely new. In short, full control. I would be interested in solutions involving VNC, SSH, telnet, or even raw network connections (via netcat or the like). Or something else if there is such a (software) solution. (Security is not *yet* a concern.) Note that I'm not interested in remote control of the booted OS. I also want more direct control than grub-reboot provides. Since everyone is suggesting it: I am **not** interested in a device specific **hardware** solution. I want something I can install on dozens of machines in their GRUB configuration to allow their GRUB boots to be remote controlled.

I would like to run an Ubuntu (18.0.4) desktop with no monitor/keyboard attached, and access it via VNC (or Remote Desktop) from a Windows 10 Pro machine. I have installed VNC Viewer on Windows and enabled remote access from Linux. It all works, but not until I log on to the Linux box from an actual keyboard - which defeats the purpose. In other words, Linux will let me log in remotely only after I am logged in physically. I followed instructions to set up Linux for remote access , including the bit about "allowing unencrypted connections", but then I realized that those are instructions for allowing an external user to view/control *the same session* as a logged-on user, as opposed to allowing an external user to start their own session. What do I need to do to have the Linux-side start up and be ready for connections without the need to attach a physical keyboard? For instance, perhaps I need to make sure that VNC Server starts as soon as the Linux machine boots, etc. It does not need to be VNC. I can work in the Windows remote desktop window as well. I just want to access this Linux machine without attaching a keyboard/mouse/monitor.

I'm planning to migrate to Debian 13. I currently use a touchscreen device on Gnome on Xorg (not wayland) because I rely on VNC (specifically x11vnc) to monitor remote desktop sessions. Unfortunately touchscreens seem [pretty broken](https://gitlab.gnome.org/GNOME/mutter/-/issues/3484) in the latest mutter (window manager) with Xorg . Since that issue affects Ubuntu 24.04 LTS and is 10 months old, I'm not expecting it to get fixed soon. Therefore, I have to migrate to wayland. However x11vnc doesn't work on wayland. I've tried a few others: tigervnc-scraping-server, wayvnc, but I can't get a connection with any of them. I think my best shot is gnome-remote-desktop which advertises VNC support, but this seems to be built with VNC disabled. I can tell because grdctl only shows options for RDP:

$ grdctl --help
Usage: grdctl [OPTIONS...] COMMAND [SUBCOMMAND]
Comamnds: 
  rdp
    set-port
    enable
    disable 
    ...

Options: 
  --headless
  ...

How can I get VNC to work with Wayland?

I am trying to set up a vnc connection between 2 computers, but am having trouble so far. In order to **understand the concept**, I am now simply trying to start a vnc server (using x11vnc) and connect to it using ssvnc **on the same computer** This page supposedly explains how to do so. Apparently, starting a vnc server should be as simple as downloading x11vnc and using the command x11vnc -display :0 The same page also contains a link to download ssvnc, that can be used as a vnc client (link here for your convenience ) It states that in order to connect using the vnc client, suffice to unpack the tar.gz directory, then run ./ssvnc/Unix/ssvnc. Then, I start ssvnc and type in user@localhost such as follow: However when i press connect, a xterm windows appears, with the following message: The x11vnc docs mentions that a common gotcha is to set the Xauth - I tried to do that by re-running the server with x11vnc -display :0 -auth /home/user/.Xauthority But I received the same error message. Anyone can help me out here with that basic test / problem?

There're color artifacts when connecting from Windows remote desktop client to Xrdp on a CentOS box. I want to check whether the underlying Xvnc will have same artifacts. Xvnc is running: LISTEN 0 5 127.0.0.1:5911 *:* users:(("Xvnc",pid=10260,fd=7)) I forward the port: ssh root@funktest -L 5911:localhost:5911 And connect with tightvnc vncviewer.exe to localhost:11. It is asking for the password I don't know. In /etc/xrdp/xrdp.ini there's the block: [Xvnc] name=Xvnc lib=libvnc.so username=ask password=ask What does ask mean? What's the default password used by xrdp?