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).

**Hello, to day i tried to install kali Linux in my windows 10** i need any help please ┌──(root💀DESKTOP-KN54U4A)-[~] └─# kex -start ***output:*** Error connecting to the KeX server. Please try "kex start" to start the service. If the server fails to start, please try "kex kill" or restart your WSL2 session and try again. ┌──(leader㉿DESKTOP-KN54U4A)-[~] └─$ kex -s ***Output*** Error connecting to the KeX server. Please try "kex start" to start the service. If the server fails to start, please try "kex kill" or restart your WSL2 session and try again. and i get message Sayes: TigerVNC Viewr: Unable to connect to socket: connection refused (10061) ┌──(leader㉿DESKTOP-KN54U4A)-[~] └─$ kex kill ***Output*** tigervncserver: No matching VNC server running for this user! tigervncserver: No matching VNC server running for this user! tigervncserver: No matching VNC server running for this user! tigervncserver: No matching VNC server running for this user ! ┌──(root💀DESKTOP-KN54U4A)-[~] └─# vncserver ***output:*** Killing Xtigervnc process ID 13260... success! =================== tail /root/.vnc/DESKTOP-KN54U4A.localdomain:5901.log =================== Xvnc TigerVNC 1.11.0 - built 2021-03-22 21:21 Copyright (C) 1999-2020 TigerVNC Team and many others (see README.rst) See https://www.tigervnc.org for information on TigerVNC. Underlying X server release 12010000, The X.Org Foundation Mon Jul 12 18:37:40 2021 vncext: VNC extension running! vncext: Listening for VNC connections on local interface(s), port 5901 vncext: created VNC server for screen 0 Mon Jul 12 18:38:11 2021 ComparingUpdateTracker: 0 pixels in / 0 pixels out ComparingUpdateTracker: (1:-nan ratio) ============================================================================================ vncserver: /usr/bin/Xtigervnc did not start up, please look into '/root/.vnc/DESKTOP-KN54U4A.localdomain:5901.log' to determine the reason! -1 ┌──(root💀DESKTOP-KN54U4A)-[~] └─# tail /root/.vnc/DESKTOP-KN54U4A.localdomain:5901.log ***output:*** Mon Jul 12 18:37:40 2021 vncext: VNC extension running! vncext: Listening for VNC connections on local interface(s), port 5901 vncext: created VNC server for screen 0 Mon Jul 12 18:38:11 2021 ComparingUpdateTracker: 0 pixels in / 0 pixels out ComparingUpdateTracker: (1:-nan ratio) ┌──(root💀DESKTOP-KN54U4A)-[~] └─# vncserver --list ***Output:*** TigerVNC server sessions: X DISPLAY # RFB PORT # PROCESS ID SERVER **i need some help to that please :D and sorry 4 bad English :) all what i need is open kex -sl in my machine**

I’m having trouble launching the desktop environment for noVNC. After setting up and trying to run the VNC server, I receive the following error root@localhost:~# vncserver :2 New Xtigervnc server 'localhost:2 (root)' on port 5902 for display:2. Use xtigervncviewer -SecurityTypes VncAuth -passwd /tmp/tigervnc.okGWtL/passwd :2 to connect to the VNC server. =================== tail /root/.vnc/localhost:2.log =================== Session startup via '/root/.vnc/xstartup' cleanly exited too early (< 3 seconds)! Maybe try something simple first, e.g., tigervncserver -xstartup /usr/bin/xterm The X session cleanly exited! Killing Xtigervnc process ID 16190... success! root@localhost:~# Only the default tigervncserver works. I’ve tried different desktop environments, including XFCE, GNOME, and others, but nothing seems to work. The session always exits too early.

So my team is building a few Autodesk Flame systems using Rocky Linux 9.3 that we would like to be able to access using VNC. We installed x11VNC but are only able to access it remotely if we start and enable the vnc app after it has turned on using a local monitor and keyboard, defeating the purpose. How do we configure the x11vnc.service in order to be able to access it with VNC without having to first go and start the app manually and locally? Would also like to be able to 'log off' the Rocky Linux 9.3 system and still see its login screen in order to switch users while connected through VNC remotely. Here is my x11vnc.service file: [Unit] Description=VNC server for the current X11 session After=display-manager.service [Service] ExecStart=/usr/bin/x11vnc -auth guess -cursor arrow -display :0 -forever -loop -noallinput -nobell -nodpms -noipv6 -nomodtweak -nopw -norc -nossl -noxdamage -noxfixes -noxkb -noxrecord -o /var/log/x11vnc.log -reopen -repeat -rfbauth /root/.vnc/x11vnc.passwd -rfbport 5900 -rfbversion 3.8 -shared Restart=on-failure RestartSec=3 [Install] WantedBy=graphical.target Thank you soo much for anybody who can help me solve this issue. Ill be forever in your debt.

I am trying to reach a TightVnc server on an Ubuntu machine with VNC Viewer from a Windows machine. TightVnc was already installed, so I started it with: *vncserver :1* If I am connecting to it from a VNC Viewer, i see only a grey background (no gnome desktop): My xstartup file (generated automatically by vncserver): #!/bin/sh xrdb $HOME/.Xresources 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 Someone suggested to change this to (to start gnome explicitly): # Uncomment the following two lines for normal desktop: # unset SESSION_MANAGER # exec /etc/X11/xinit/xinitrc [ -x /etc/vnc/xstartup ] && exec /etc/vnc/xstartup [ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources xsetroot -solid grey vncconfig -iconic & x-terminal-emulator -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" & x-window-manager & gnome-panel & gnome-settings-daemon & metacity & nautilus & The result: Nautilus is started, but no desktop is shown. What am I missing? How can I reach the gnome desktop as well? Thank you for any good suggestions.

I recently found out about ssh config file where one can setup frequently used ssh connections. However, I am having troubles transforming one command which connects my computer to VNCServer running on my server which is hidden behind intermediate server. Basically transform this command (which works):

ssh -t -L port1:localhost:port2 user1@machine1.com ssh -L port2:localhost:port3 user2@machine.com

with vncviewer localhost:0 in separate window, into ssh config file. I managed to create a config which connect to the machine without throwing any Failed to set up port messages, but when I run in separate terminal window

vncviewer localhost:0

I get an error. In case the ~/.ssh/config is set in this way (my own try):

Host machine1
   HostName machine1.com
   User user1
   LocalForward port1 localhost:port2
   RequestTTY force

 Host machine2
   HostName machine2.com
   User user2
   LocalForward port2 localhost:port3
   ProxyJump machine1

and ran by running ssh machine2 and then vncviewer localhost:0 in new terminal window the error is "Failed to connect to localhost:0": unable to connect to socket: Connection refused (111). In the case I set it up as mention [here](https://unix.stackexchange.com/questions/303993/reverse-ssh-tunnel-in-with-ssh-config) :

Host machine2
  HostName machine2.com
  User user2
  LocalForward port1 user1@machine1:port2
  LocalForward port2 user2@machine2:port3
  RequestTTY force

I get an error saying The connection was dropped by the server before the session could be established. In both cases I connect to machine2 in terminal window and can browse stuff. But I would like to connect to the vncserver also. Can you please explain what am I doing wrong here? I was consulting these sources when creating any other ssh config: https://linuxize.com/post/using-the-ssh-config-file/ --- beginners guide https://man7.org/linux/man-pages/man1/ssh.1.html --- to look definition of every -t -L I used https://phoenixnap.com/kb/ssh-config --- to translate -t -L to ssh config command https://www.ssh.com/academy/ssh/tunneling-example --- to explain wheter I need LocalForward or Remote Forward

few days ago we updated Debian from old stable to stable (Linux 6.0.0-0.deb11.6-amd64). While updating, machine reboot had to be done, which ended some important processes, such as vncserver, which we used for connecting from local and also remote network (local connection using vncviewer, remotely from PuTTY - Win machines or other utilities - MacOS, specifically I don't know). After restart, I tried to start all virtual desktops manually using vncserver : and server started as expected. This command provided output below: 3NI3X0 New Xtigervnc server ': ()' on port for display :. 3NI3X0 Use xtigervncviewer -SecurityTypes VncAuth -passwd /home//.vnc/passwd : to connect to the VNC server. But we are no more able to connect to virtual VNC desktop using f.e. vncviewer (we do not have xtigervnc SW installed, we used vncviewer and it has always worked). I'm using vncviewer : command to connect. After confirming command error window pops up saying: 'The connection was refused by computer'. I also managed to find vncviewer.log with additional info, please see below: VNC(R) Viewer 6.21.406 (r44671) x86 (Apr 7 2021 10:26:47) Copyright (C) 2002-2020 RealVNC Ltd. RealVNC and VNC are trademarks of RealVNC Ltd and are protected by trademark registrations and/or pending trademark applications in the European Union, United States of America and other jurisdictions. Protected by UK patent 2481870; US patent 8760366; EU patent 2652951. See https://www.realvnc.com for information on VNC. For third party acknowledgements see: https://www.realvnc.com/docs/6/foss.html OS: Debian GNU/Linux 11, Linux 6.0.0, amd64 2023-02-09T10:11:22.902Z vncviewer[]: CModuleHosted: Getting CloudConfig.pkg from built-in resource 2023-02-09T10:11:22.904Z emperor vncviewer[]: VendorConfig: Error in Certificate "CN=GeoTrust Global CA,O=GeoTrust Inc.,C=US": X.509 Error: Certificate expired 2023-02-09T10:11:22.904Z vncviewer[]: VendorConfig: Error in Certificate "CN=GlobalSign,O=GlobalSign,OU=GlobalSign Root CA - R2": X.509 Error: Certificate expired 2023-02-09T10:11:22.910Z vncviewer[]: CModuleHosted: Using business identifier 2023-02-09T10:11:22.940Z vncviewer[]: CModuleCtrlComms: Listening on /tmp/.vnc-/vncviewer.CtrlComms. 2023-02-09T10:11:22.943Z vncviewer[]: GoogleAnalytics: X.509 Error: Certificate expired 2023-02-09T10:11:22.953Z vncviewer[]: CSession: Connecting to : (Chooser for Direct UDP/Direct TCP via proxy settings) 2023-02-09T10:11:22.956Z vncviewer[]: CSession: connection error: connect: Connection refused (111) 2023-02-09T10:11:22.956Z vncviewer[]: CConnection: close: [System-111] The connection was refused by the computer Surprisingly, while connecting from remote network (i.e. non-local), virtual desktop works just fine. Same with SSH connection - it is able to connect to using ssh command, but we also need GUI for some tasks. I did not find any relevant informations on how to solve this issue and in our team we really need it for work purposes. Do you think, that we need some kind of new autentification keys to be able to connect from local network? I will be more than happy, if you could give me some relevant informations, which could lead to solving this issue. Have a nice day.

I have a main Raspberry Pi in one room and a second one in other room. My software is running on the main Pi and i'd like the second one to just mirror the first one. RealVNC is fine, but i can't figure out how to make the second Pi (the one with Viewer) to connect automatically on startup. Any help is appreciated.

I'm following this guide to setup VNC server in my Ubuntu arm64 machine (specifically, armbian 64-bit). There's one problem I found with it so far. When I start the VNC server using vncserver :1 -localhost no command, it didn't work and crashed after I tried to access the session from a VNC client. But, when I tried with LD_PRELOAD=/lib/aarch64-linux-gnu/libgcc_s.so.1 vncserver :1 -localhost no command I found here , it's started to work. Now I want to manage this as system service using systemctl command. So, I have this unit file: [Unit] Description=Start TightVNC server at startup After=syslog.target network.target [Service] Type=forking User=zulh Group=zulh WorkingDirectory=/home/zulh PIDFile=/home/zulh/.vnc/%H:%i.pid ExecStartPre=-/usr/bin/vncserver -kill :%i > /dev/null 2>&1 ExecStart="LD_PRELOAD=/lib/aarch64-linux-gnu/libgcc_s.so.1 /usr/bin/vncserver -depth 24 -geometry 1280x800 -localhost no :%i" ExecStop=/usr/bin/vncserver -kill :%i [Install] WantedBy=multi-user.target Now when I ran... $ sudo systemctl daemon-reload $ sudo systemctl enable vncserver@1.service $ vncserver -kill :1 $ sudo systemctl start vncserver@1 ...I got this: $ sudo systemctl status vncserver@1 ● vncserver@1.service - Start TightVNC server at startup Loaded: bad-setting (Reason: Unit vncserver@1.service has a bad unit file setting.) Active: failed (Result: timeout) since Sat 2022-04-16 17:34:44 +08; 3min 42s ago Apr 16 17:33:13 armbian gnome-session: gnome-session-binary: CRITICAL: We failed, but the fail whale is dead. Sorry.... Apr 16 17:33:13 armbian gnome-session-binary: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly Apr 16 17:33:13 armbian gnome-session-binary: CRITICAL: We failed, but the fail whale is dead. Sorry.... Apr 16 17:34:41 armbian systemd[1] : vncserver@1.service: start operation timed out. Terminating. Apr 16 17:34:44 armbian systemd[1] : vncserver@1.service: Failed with result 'timeout'. Apr 16 17:34:44 armbian systemd[1] : Failed to start Start TightVNC server at startup. Apr 16 17:34:49 armbian systemd[1] : /etc/systemd/system/vncserver@.service:13: Neither a valid executable name nor an absolute path: LD_PRELOAD=/lib/aarch64-linux-gnu/libgcc_s.s> Apr 16 17:34:49 armbian systemd[1] : vncserver@1.service: Unit configuration has fatal error, unit will not be started. Apr 16 17:38:00 armbian systemd[1] : /etc/systemd/system/vncserver@.service:13: Neither a valid executable name nor an absolute path: LD_PRELOAD=/lib/aarch64-linux-gnu/libgcc_s.s> Apr 16 17:38:00 armbian systemd[1] : vncserver@1.service: Unit configuration has fatal error, unit will not be started. What should I do to fix this?

The goal is to provide resolution X and Y as arguments to the script ./res_set.sh 1920 1080 and gtf, xrandr --newmode and --addmode will be executed according to the script. #!/usr/bin/env bash if [ "$1" == "-h" ]; then echo "Usage: basename $0 [X co-ordinate] [Y co-ordinate]" exit 0 fi echo "X Co-ordinate"; echo $1; echo "Y Co-ordinate"; echo $2; echo "Are you sure? [Y/N]"; read input; if [ $input == "y" ]; then gtf $1 $2 60 > kar1.txt #To get modeline sed -n '3 p' kar1.txt > kar2.txt #Select Line 2 grep -o -E '["_x.0-9 ]+' kar2.txt > kar3.txt #Filter result wo_filter=$(perl -p -e 's/(?:_60.00)//g' kar3.txt | grep "\S"); filter=$(grep "\S" kar3.txt); fil_resolution=$(grep -o -P '(?<=").*(?=")' <<< $wo_filter) resolution=$(grep -o -P '(?<=").*(?=")' kar3.txt) echo "Filter: $filter"; echo "Wo_filter: $wo_filter"; echo "Resolution: $resolution"; echo "Filted_Resolution: $fil_resolution"; var=$(xrandr --newmode $wo_filter) xrandr --addmode default $fil_resolution #rm -v kar* else exit; fi This creates xrandr --newmode but fails to add the mode --addmode in the resolution list while using this script. I get xrandr:Cannot find mode. But it works and adds to the mode list if xrandr --newmode and --addmode commands are executed individually. This is the output of xrandr | tail My thoughts are : Are *$variables* are in different datatype and spoiling my result? How will I be able to verify the data type of variables here or in bash (does it matter)?

I'm using VNC remote desktop to visually access a remote Ubuntu 18.04 machine with a xfce4 GUI. VNC works fine. SSH shell works fine. The 2 programs with a graphic UI I'd like to launch are nedit (a visual editor, compiled) and Unity (a game dev IDE). They both have the +x permissions, which I can see in the shell. In VNC, when I click "Properties", I don't see a "Run this as a program" option on either of them, just write/read. When I double click on an either "executable" in VNC's file manager, I get some odd message "Unable to set the xfce4 Display Settings" as if the "executables" were arguments for "Start with a Display". When installing, I saw the Unity GUI in VNC briefly, so I know running Unity is technically possible. The content of ~/.vnc/xstartup: #!/bin/bash xrdb $HOME/.Xresources startxfce4 &

On a centOS 7 remote server I have installed tigervnc. On Windows the viewer I am using is RealVNC Viewer. The configuration at /etc/systemd/system/vncserver@\:1.service

[Unit]
Description=Remote desktop service (VNC)
After=syslog.target network.target

 

[Service]
Type=forking
ExecStartPre=/bin/sh -c '/usr/bin/vncserver -kill %i > /dev/null 2>&1 || :'
ExecStart=/sbin/runuser -l root -c "/usr/bin/vncserver -geometry 1920x1080"
PIDFile=/root/.vnc/%H%i.pid
ExecStop=/bin/sh -c '/usr/bin/vncserver -kill %i > /dev/null 2>&1 || :'

 

[Install]
WantedBy=multi-user.target

The configuration at /root/.vnc/config

## Supported server options to pass to vncserver upon invocation can be listed
## in this file. See the following manpages for more: vncserver(1) Xvnc(1).
## Several common ones are shown below. Uncomment and modify to your liking.
##
# securitytypes=vncauth,tlsvnc
# desktop=sandbox
geometry=1980x1080
# localhost
# alwaysshared

When I connect to the server, the display is not what I expected. It's simply too small to use. I have tried changing the scaling but that didn't help. The scaling would help but the remote display is not in the center of the screen. So when I changed the scaling to 200%, it becomes "hidden".

I am trying to access my centos machine through VNC viewer after sucessfull login its showing blue screen with one clock ,Just for your reference see below image Not sure what wrong with the setup. Can someone please help me ?

First, I use putty to log in my server computer with vnc4server -geometry 1920x1080. Then I got my port number is 1. The system on my server computer is ubuntu 16.04. Then I use vncviewer to log with 192.168.106.29:1 This is the result:  This is my xstartup file: unset DBUS_SESSION_BUS_ADDRESS [ -x /etc/vnc/xstartup ] && exec /etc/vnc/xstartup [ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources xsetroot -solid grey vncconfig -iconic & x-terminal-emulator -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" & x-window-manager & mate-session & This is the scw4750:1.log file:

Wed Sep 19 09:33:05 2018

 vncext:      VNC extension running!
 vncext:      Listening for VNC connections on port 5901
 vncext:      created VNC server for screen 0

error opening security policy file /etc/X11/xserver/SecurityPolicy

Could not init font path element /usr/X11R6/lib/X11/fonts/Speedo/, removing from list!

usage: xsetroot [options]
  where options are:
  -display    or   -d 
  -fg    or   -foreground 
  -bg    or   -background 
  -rv   or   -reverse
  -def   or   -default
  -name 
  -cursor  
  -cursor_name 
  -xcf  
  -solid 
  -gray   or   -grey
  -bitmap 
  -mod  
  -help
  -version

mate-session: WARNING: Could not make bus activated clients aware of XDG_CURRENT_DESKTOP=MATE environment variable: Failed to connect to socket /tmp/dbus-X9hRhuXJuM: Connection refused

mate-session: WARNING: Could not make bus activated clients aware of DISPLAY=:1 environment variable: Failed to connect to socket /tmp/dbus-X9hRhuXJuM: Connection refused

mate-session: WARNING: Could not make bus activated clients aware of MATE_DESKTOP_SESSION_ID=this-is-deprecated environment variable: Failed to connect to socket /tmp/dbus-X9hRhuXJuM: Connection refused
mate-session: dconf-WARNING: failed to commit changes to dconf: Could not connect: Connection refused

mate-session: WARNING: Could not make bus activated clients aware of SESSION_MANAGER=local/scw4750:@/tmp/.ICE-unix/3764,unix/scw4750:/tmp/.ICE-unix/3764 environment variable: Failed to connect to socket /tmp/dbus-X9hRhuXJuM: Connection refused

(x-window-manager:3763): xfwm4-WARNING **: The display does not support the XComposite extension.

(x-window-manager:3763): xfwm4-WARNING **: The display does not support the XDamage extension.

(x-window-manager:3763): xfwm4-WARNING **: The display does not support the XFixes extension.

(x-window-manager:3763): xfwm4-WARNING **: Compositing manager disabled.
Failed to parse arguments: Unknown option --login

(x-window-manager:3763): xfwm4-WARNING **: Cannot find visual format on screen 0

(x-window-manager:3763): xfwm4-WARNING **: Failed to connect to session manager: Failed to connect to the session manager: SESSION_MANAGER environment variable not defined
Wed Sep 19 09:36:10 2018
 Connections: accepted: 0.0.0.0::55352
 SConnection: Client needs protocol version 3.8
 SConnection: Client requests security type VncAuth(2)

Wed Sep 19 09:36:14 2018
 Connections: closed: 0.0.0.0::55352 (Clean disconnection)

Wed Sep 19 09:36:19 2018
 Connections: accepted: 0.0.0.0::55357
 SConnection: Client needs protocol version 3.8
 SConnection: Client requests security type VncAuth(2)

Wed Sep 19 09:36:27 2018
 VNCSConnST:  Server default pixel format depth 16 (16bpp) little-endian rgb565
 VNCSConnST:  Client pixel format depth 6 (8bpp) rgb222
 VNCSConnST:  Client pixel format depth 16 (16bpp) little-endian rgb565

I'm trying to use SSH to connect to a VNC. When I enter the password, it just hangs with not an error message nor anything at all. How can I solve this

ssh -L 5901:localhost:5901 -C -N -l root 192.168.1.10
root@192.168.1.10's password:

I am on a linux system and using vncviewer to connect to other linux servers. On my home system, I use setxkbmap to remap caps to control, like any decent human being: setxkbmap -option caps:ctrl_modifier When I run vncviewer, I find that my caps key does nothing in my VNC windows, so I can't remap it. If I run xev in the VNC remote system, then there are no keycaps or activity from pressing the capslock. It's just thrown away. I have the 'GrabKeyboard' option set to 1, so it should be sending all my keyboard events to the remote server, but it's not happening. How can I figure out either how to send the control mapping of my keyboard to the remote server, or at least send the caps lock event so I can remap it on the remote server?

Is there a way to change the background in the vnc

I am attending a course in which the software (cadence) is installed on the university unix server. To have access the following instruction is shared by the course team. I am using a MAC system. Steps to setup account for MAC users: 1- Open terminal: %ssh -Y @somename.universityname.edu 2- Create your session by: %vncserver -geometry 1920x1080 3- Make sure to have checked/killed all your previous sessions (keeping one) by: %vncserver -list %vncserver -kill : 100XX 4- Exit from the connection: %exit 5- Type: %ssh –L 150XX:localhost:150XX –N –f –l somename.universityname.edu and type your password 6- Go to vncviewer and type: localhost:150XX This was supposed to fire up my VNCviewer and it was working fine until I forgot the password I setup in the 5th step. I tried to remove the password by rm .vnc/passwd and later using vncpasswd. It shows the following Further (this time recording my own password) whenever I am trying to type the password (new one, and I have done it multiple times so I am sure there's no extra character) in it still says permission denied. It would be really helpful if I receive your guidance on how to correct this.

I am running Debian (Stretch) with XFCE and many applications do not appear in the menu (in my case Whisker Menu). As an example, I often run remote sessions using VNC and at the moment I can only start the VNC viewer from the terminal. Ideally it would have an icon/item so that not only it would be visible in the menu, but I could also select it as a 'favourite' (easy-to-reach) item in the Whisker Menu. Sticking with the example case, the VNC viewer is from an 'official' package: $ sudo apt --reinstall install tigervnc-viewer Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 1 not upgraded. Need to get 168 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://mirrorservice.org/sites/ftp.debian.org/debian stretch/main amd64 tigervnc-viewer amd64 1.7.0+dfsg-7 [168 kB] Fetched 168 kB in 0s (642 kB/s) (Reading database ... 669847 files and directories currently installed.) Preparing to unpack .../tigervnc-viewer_1.7.0+dfsg-7_amd64.deb ... Unpacking tigervnc-viewer (1.7.0+dfsg-7) over (1.7.0+dfsg-7) ... Processing triggers for man-db (2.7.6.1-2) ... Setting up tigervnc-viewer (1.7.0+dfsg-7) ... so is there a way to have it as an 'official' application in the Whisker Menu?

I'm using VNC Viewer 5.3.2 (r19179) x64 on a Windows 10 machine to connect to a VNC Server (Virtual Mode) 5.3.2 (r19476) x64 running on SUSE Linux Enterprise Server 11. My issue is concerning copy and paste. I'm aware that Linux have two different clipboard, PRIMARY and CLIPBOARD. If I select some text, it get sent to PRIMARY and I may be able to paste it using the third button mouse, or using SHIFT+INSERT. However, selecting text should not override the CLIPBOARD. CLIPBOARD is used when user is selecting text, THEN copying it using CTRL-C or right-click copy. After this, if I paste using CTRL-V, it should paste what reside in CLIPBOARD, no matter if I selected some text (altered PRIMARY) between the copy and paste operation. When I connect to my remote machine using VNC, all this is working perfectly fine: I can copy some text with CTRL-C, then select anything and paste with CTRL-V to paste what I copied with CTRL-C. However, if I copy some text outside VNC Viewer, i.e. some text in a Notepad on my local machine (Windows 10) then select some text in my remote machine (SLES 11) and try to paste it over, it paste what I just selected, even if I use CTRL-V. At this moment, PRIMARY and CLIPBOARD get messed up up in my remote machine until I close the session and open a new one. This means, if I select some text and do a CTRL-V, it paste the text I just selected. This become really annoying since if I want to copy something then paste it over something else, the system paste what I just selected and I loose the CTRL-C I just made. I don't know whether the selected text gets send to CLIPBOARD or PRIMARY or if the CTRL-V is now pasting from PRIMARY or CLIPBOARD, but there is something messed up. I'm aware VNC Viewer used to have an option called SendPrimary which could potentially resolve my issue (see this ), but I can't find this option in VNC Viewer 5.3.2.