advisortore.blogg.se

Open in terminal killed silently in vnc
Open in terminal killed silently in vnc








open in terminal killed silently in vnc

The "DISPLAYMANAGER=" setting will normally be set to either gdm (for GNOME) or kdm4 (for KDE4). In this file look for the following entries: Using your favorite editor open the following file: Both selections can be found in the"Network Services" section of YaST. If this information is not displayed then it would indicate that the "Remote Administration (VNC)" selection in YaST has not been configured or the the xinetd service has been disabled (which can also be checked in YaST).

open in terminal killed silently in vnc

The following should be displayed (other than a different PID which is fine): Use the following command to verify that port 5901 is in a listening state and is owned by xinetd: If not, leave the firewall disabled until troubleshooting is complete. Test the VNC connection again to see if there is any change. Run the status command again to verify it is now "unused". If it is "running" then shut down the firewall with this command: This will return the status of the firewall as either "unused" or "running" (the status shows up on the very right hand side of the terminal). The instructions below will require being logged in as the root user at a command line terminal.īy default the firewall is enabled and will block the VNC communication unless the box was checked in the YaST configuration for Remote Administration to open the port.Įven if it was checked it's always a good idea to disable the firewall to rule it out. These steps are not intended for troubleshooting a VNC server that is being started outside of the YaST configuration. Troubleshooting steps for VNC connection when "Remote Administration (VNC)" has been enabled in YaST.










Open in terminal killed silently in vnc