I am attempting to set up an AWS EC2 Debian 9 instance [using this image](https://aws.amazon.com/marketplace/pp/B073HW9SP3) . I have the image up and running and can connect via VNC using 'tightvncserver'. My problem is exactly the same as described in [this Ubuntu Stack Exchange question](https://askubuntu.com/questions/898035/how-to-configure-vnc-server-to-get-full-gnome-desktop) . I can not seem to get Gnome desktop to display 'nicely' as it does on the [gnome website](https://www.gnome.org/wp-content/uploads/2017/04/featured-image@2x-1.png) . Just like the Ubuntu question, when I load up the VNC connection I am faced with a grey background, a simple menu bar and originally no terminal option until I created a menu item for it following [this question](https://forums.linuxmint.com/viewtopic.php?t=280636) . My /home/username/.vnc/xstartup is as follows:

#!/bin/sh

unset SESSION_MANAGER
unset DBUS_SESSION_BUS_ADDRESS
startxfce4 &

[ -x /etc/vnc/xstartup ] && exec /etc/vnc/xstartup
[ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources
vncconfig -iconic &

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
gnome-panel &
gnome-settings-daemon &
metacity &
nautilus &

The question on Ubuntu Stack Exchange is very similar to mine; How do I correctly configure Gnome with VNC to display the nice Gnome desktop as per the Gnome site? **Note:** I do not wish to use an application such as TeamViewer, however other terminal-only options are welcome as I need to be able to use a terminal on one machine to open the GUI of the EC2 instance, without installing software.

I tried to make my tightvncserver start at boot on parabola arch Gnu/Linux in an auto GUI login setup using the wiki and by creating x0vncserver.service systemd unit following that and then systemctl enable x0vncserver.service but when I boot/reboot, I see no vnc server active and then checking I see this

# systemctl status x0vncserver.service
* x0vncserver.service - Remote desktop service (VNC)
   Loaded: loaded (/etc/systemd/system/x0vncserver.service; enabled; vendor preset: disabled)
   Active: inactive (dead) since Sat 2017-07-01 20:42:55 +06; 1min 34s ago
  Process: 302 ExecStart=/usr/bin/sh -c /usr/bin/x0vncserver -display :0 -rfbport 5900 -passwordfile /home/peruvian/.vnc/passwd & (code=exited, status=0/SUCCESS)

Jul 01 20:42:52 sky systemd[1] : Starting Remote desktop service (VNC)...
Jul 01 20:42:55 sky systemd[1] : Started Remote desktop service (VNC).

and my

# journalctl -xe | grep vnc
-- Subject: Unit x0vncserver.service has begun start-up
-- Unit x0vncserver.service has begun starting up.
-- Subject: Unit x0vncserver.service has finished start-up
-- Unit x0vncserver.service has finished starting up.
Jul 01 20:47:08 sky systemd[1] : x0vncserver.service: Main process exited, code=exited, status=1/FAILURE
Jul 01 20:47:08 sky systemd[1] : x0vncserver.service: Unit entered failed state.
Jul 01 20:47:08 sky systemd[1] : x0vncserver.service: Failed with result 'exit-code'.

But if I run the command systemctl start x0vncserver.service or systemctl restart x0vncserver.service after loading the desktop, it works without any issue as the # systemctl status x0vncserver.serviceshows

# systemctl status x0vncserver.service
* x0vncserver.service - Remote desktop service (VNC)
   Loaded: loaded (/etc/systemd/system/x0vncserver.service; enabled; vendor preset: disabled)
   Active: active (running) since Sat 2017-07-01 20:56:53 +06; 2s ago
  Process: 924 ExecStart=/usr/bin/sh -c /usr/bin/x0vncserver -display :0 -rfbport 5900 -passwordfile /home/peruvian/.vnc/passwd & (code=exited, status=0/SUCCESS)
 Main PID: 925 (x0vncserver)
    Tasks: 1 (limit: 4915)
   CGroup: /system.slice/x0vncserver.service
           `-925 /usr/bin/x0vncserver -display :0 -rfbport 5900 -passwordfile /home/peruvian/.vnc/passwd

Jul 01 20:56:53 sky systemd[1] : Starting Remote desktop service (VNC)...
Jul 01 20:56:53 sky systemd[1] : Started Remote desktop service (VNC).

and my default.target is

# systemctl get-default       
graphical.target

I guess the service starts earlier than it supposed to and fails due to lack of resources at boot.

I describe what I exactly did : First , I installed debian10-netinstall. Then I installed Gnome via 'Tasksel' command. Then I used this Tutorial for installing vnc server. Then I start vncserver via this command tightvncserver -geometry 1024x720 :1 and here is the output : New 'X' desktop is debian:1 Starting applications specified in /home/parsa/.vnc/xstartup Log file is /home/parsa/.vnc/debian:1.log And here is the ~/.vnc/debian:1.log : parsa@debian:~$ tail -f .vnc/debian\:1.log 26/09/19 11:41:12 Xvnc version TightVNC-1.3.9 26/09/19 11:41:12 Copyright (C) 2000-2007 TightVNC Group 26/09/19 11:41:12 Copyright (C) 1999 AT&T Laboratories Cambridge 26/09/19 11:41:12 All Rights Reserved. 26/09/19 11:41:12 See http://www.tightvnc.com/ for information on TightVNC 26/09/19 11:41:12 Desktop name 'X' (debian:1) 26/09/19 11:41:12 Protocol versions supported: 3.3, 3.7, 3.8, 3.7t, 3.8t 26/09/19 11:41:12 Listening for VNC connections on TCP port 5901 # Failed to parse arguments: Unknown option --login As you can see in the last line there is an Error. I fixed that by commenting the line contains "--login" in this file :)) /usr/bin/x-terminal-emulator Then I restarted the vncserver : parsa@debian:~$ tightvncserver -kill :1 Killing Xtightvnc process ID 910 parsa@debian:~$ tightvncserver -geometry 1024x720 :1 New 'X' desktop is debian:1 Starting applications specified in /home/parsa/.vnc/xstartup Log file is /home/parsa/.vnc/debian:1.log Then again lets see the log file tail -f .vnc/debian\:1.log # watch_established: "/org/gnome/desktop/interface/" (establishing: 1) # watch_established: "/org/gnome/settings-daemon/peripherals/mouse/" (establishing: 1) # watch_established: "/org/gnome/desktop/sound/" (establishing: 1) # watch_established: "/org/gnome/desktop/privacy/" (establishing: 1) # watch_established: "/org/gnome/desktop/wm/preferences/" (establishing: 1) # watch_established: "/org/gnome/settings-daemon/plugins/xsettings/" (establishing: 1) # watch_established: "/org/gnome/desktop/a11y/" (establishing: 1) # watch_fast: "/org/gnome/terminal/legacy/" (establishing: 0, active: 0) # unwatch_fast: "/org/gnome/terminal/legacy/" (active: 0, establishing: 1) # watch_established: "/org/gnome/terminal/legacy/" (establishing: 0) Now that the error is gone, I connect to vncserver , and these lines appear in the log : 26/09/19 12:18:05 Got connection from client 192.168.1.131 26/09/19 12:18:05 Using protocol version 3.8 26/09/19 12:18:05 Full-control authentication passed by 192.168.1.131 26/09/19 12:18:05 rfbProcessClientNormalMessage: ignoring unknown encoding 24 26/09/19 12:18:05 rfbProcessClientNormalMessage: ignoring unknown encoding 16 26/09/19 12:18:05 rfbProcessClientNormalMessage: ignoring unknown encoding 22 26/09/19 12:18:05 rfbProcessClientNormalMessage: ignoring unknown encoding 21 26/09/19 12:18:05 rfbProcessClientNormalMessage: ignoring unknown encoding 15 26/09/19 12:18:05 Using zlib encoding for client 192.168.1.131 26/09/19 12:18:05 rfbProcessClientNormalMessage: ignoring unknown encoding -314 26/09/19 12:18:05 Enabling full-color cursor updates for client 192.168.1.131 26/09/19 12:18:05 rfbProcessClientNormalMessage: ignoring unknown encoding -223 26/09/19 12:18:05 Pixel format for client 192.168.1.131: 26/09/19 12:18:05 8 bpp, depth 6 26/09/19 12:18:05 true colour: max r 3 g 3 b 3, shift r 4 g 2 b 0 26/09/19 12:18:05 Using raw encoding for client 192.168.1.131 26/09/19 12:18:05 rfbProcessClientNormalMessage: ignoring unknown encoding 24 26/09/19 12:18:05 rfbProcessClientNormalMessage: ignoring unknown encoding 22 26/09/19 12:18:05 rfbProcessClientNormalMessage: ignoring unknown encoding 21 26/09/19 12:18:05 rfbProcessClientNormalMessage: ignoring unknown encoding 16 26/09/19 12:18:05 rfbProcessClientNormalMessage: ignoring unknown encoding 15 26/09/19 12:18:05 rfbProcessClientNormalMessage: ignoring unknown encoding -314 26/09/19 12:18:05 Enabling full-color cursor updates for client 192.168.1.131 26/09/19 12:18:05 rfbProcessClientNormalMessage: ignoring unknown encoding -223 26/09/19 12:18:05 rfbProcessClientNormalMessage: ignoring unknown encoding 24 26/09/19 12:18:05 rfbProcessClientNormalMessage: ignoring unknown encoding 16 26/09/19 12:18:05 rfbProcessClientNormalMessage: ignoring unknown encoding 22 26/09/19 12:18:05 rfbProcessClientNormalMessage: ignoring unknown encoding 21 26/09/19 12:18:05 rfbProcessClientNormalMessage: ignoring unknown encoding 15 26/09/19 12:18:05 Using zlib encoding for client 192.168.1.131 26/09/19 12:18:05 rfbProcessClientNormalMessage: ignoring unknown encoding -314 26/09/19 12:18:05 Enabling full-color cursor updates for client 192.168.1.131 26/09/19 12:18:05 rfbProcessClientNormalMessage: ignoring unknown encoding -223 26/09/19 12:18:05 Pixel format for client 192.168.1.131: 26/09/19 12:18:05 32 bpp, depth 24, little endian 26/09/19 12:18:05 true colour: max r 255 g 255 b 255, shift r 16 g 8 b 0 26/09/19 12:18:05 no translation needed and I see a gray screen in the vnc viewer with a black X cursor : Could you please help me to fix this problem ? I have googled this rfbProcessClientNormalMessage: ignoring unknown encoding error a lot but I couldn't find a solution. here is my ~/.vnc/xstartup by the way : #!/bin/shxrdb $HOME/.Xresources xsetroot -solid grey x-terminal-emulator -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" & # x-window-manager & gnome-session & Thank you.

I'm trying to create a ubuntu noble container (it has to be ubuntu noble due to another software's compatibility constraints) with a gui capable of running Gazebo, a robot simulation. For Gazebo, I need a working OpenGL setup (using mesa). As of now, though, my attempts to verify my setup with glxinfo fail due to some odd error:

root@554bf70792e2:/# glxinfo
name of display: :1
Error: couldn't find RGB GLX visual or fbconfig

I've done a ton of searching online and tried many solutions but none of them seemed to work. Can anyone help me out? # Further context: I'm running this on an apple silicon macbook (M3). Dockerfile:

FROM --platform=linux/arm64 ubuntu:noble

# ---------- Set Up VNC Server ----------

# Install Necessary Debian Packages
ENV DEBIAN_FRONTEND=noninteractivex
RUN apt update && \
    apt upgrade -y && \
    apt install -y xfce4 xfce4-goodies tightvncserver dbus-x11

# Add vncuser
RUN useradd -m vncuser && echo "vncuser:password" | chpasswd

# Switch to vncuser
USER vncuser

# Set up VNC password

RUN mkdir -p ~/.vnc && \
    echo "password" | vncpasswd -f > ~/.vnc/passwd && \
    chmod 600 ~/.vnc/passwd

# Set the default desktop environment to XFCE
RUN echo "#!/bin/bash\nXvfb :1 -screen 0 1280x720x24 &\nstartxfce4 &" > ~/.vnc/xstartup && \
    chmod +x ~/.vnc/xstartup && \
    touch ~/.Xauthority

# Switch back to root
USER root

# Expose VNC port
EXPOSE 5901

# Set environment variables
ENV DISPLAY=:1 \
    XDG_RUNTIME_DIR=/tmp/runtime-root \
    LIBGL_ALWAYS_SOFTWARE=1

# Mesa and other libraries
RUN apt update && apt install -y \
    libgl1-mesa-dri \
    libglx-mesa0 \
    libegl-mesa0 \
    mesa-vulkan-drivers \
    libosmesa6 \
    mesa-utils \
    xvfb \
    pciutils

vnc-start.sh:

su - vncuser -c "
export USER=vncuser
export DISPLAY=:1
vncserver -geometry 1280x720 -depth 24 :1
xhost +"

docker-compose.yml:

services:
  gprp:
    build: .
    container_name: gprp
    command: tail -f /dev/null
    ports:
      - "5901:5901"
    volumes:
      - .:/workspace

To start the container, I run docker-compose build and docker-compose up -d, then (within the container) run vnc-start.sh and glxinfo.

For some reason, I can't for the life of me cannot start vncserver to start at boot. I'm using this guide and as per the link, here's my constructed systemd file for it [Unit] Description=Start TightVNC server at startup After=syslog.target network.target [Service] Type=forking User= Group= WorkingDirectory=/home/ PIDFile=/home//.vnc/%H:%i.pid ExecStartPre=/usr/bin/vncserver -kill :%i > /dev/null 2>&1 ExecStart=/usr/bin/vncserver -depth 24 -geometry 1280x800 -localhost no :%i ExecStop=/usr/bin/vncserver -kill :%i [Install] WantedBy=multi-user.target trying to start it via systemctl fails and checking the status shows this: × vncserver@1.service - Remote desktop service (VNC) Loaded: loaded (/etc/systemd/system/vncserver@1.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Thu 2024-05-09 15:57:31 PDT; 11s ago Process: 64087 ExecStartPre=/bin/sh -c /usr/bin/vncserver -kill 1 > /dev/null 2>&1 || : (code=exited, status=0/SUCCESS) Process: 64091 ExecStart=/usr/bin/vncserver -geometry 1800x1000 -depth 16 -dpi 120 -alwaysshared -localhost no 1 (code=exited, status=1/FAILURE) CPU: 234ms Also, it says: > vncserver@1.service: Failed with result 'exit-code'. Journalctl says this: ░░ An ExecStart= process belonging to unit vncserver@1.service has exited. ░░ ░░ The process' exit code is 'exited' and its exit status is 1. May 09 15:57:31 MBP systemd[1] : vncserver@1.service: Failed with result 'exit-code'. ░░ Subject: Unit failed ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ The unit vncserver@1.service has entered the 'failed' state with result 'exit-code'. May 09 15:57:31 MBP systemd[1] : Failed to start Remote desktop service (VNC). ░░ Subject: A start job for unit vncserver@1.service has failed ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ A start job for unit vncserver@1.service has finished with a failure. ░░ ░░ The job identifier is 6471 and the job result is failed.

### Setup My goal is to use a web browser in a VNC session. I followed this page to install tightvncserver with xfce4. The session works fine, i.e. I am able to open all other GUI programs. I ran apt install firefox and snap install brave. Connection is via SSH jump and then port forwarding between localhost of both client and server. ### Symptoms When I try to launch browsers from GUI, nothing happens. On the command line I get for Firefox:

Client is not authorized to connect to ServerError: cannot open display: :1.0

And for Brave:

Client is not authorized to connect to Server[11997:11997:0704/151224.702071:ERROR:ozone_platform_x11.cc(247)] Missing X server or $DISPLAY
[11997:11997:0704/151224.702198:ERROR:env.cc(226)] The platform failed to initialize.  Exiting.
[0704/151224.705242:ERROR:ptracer.cc(567)] ptrace: Input/output error (5)
[0704/151224.705436:ERROR:ptracer.cc(567)] ptrace: Input/output error (5)
[0704/151224.742590:ERROR:elf_dynamic_array_reader.h(64)] tag not found
[0704/151224.753358:ERROR:file_io_posix.cc(144)] open /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq: No such file or directory (2)
[0704/151224.753382:ERROR:file_io_posix.cc(144)] open /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq: No such file or directory (2)
/snap/brave/166/opt/brave.com/brave/brave-browser: line 48: 11997 Trace/breakpoint trap   (core dumped) "$HERE/brave" "$@"

### Things I tried On Redhat bugzilla they say to run firefox -no-remote. Same issue as before in my case. I found a lot of related answers, but none seem the same. But they have problems with X11, too. So I try some ideas I read there. $XAUTHORITY is empty. $DISPLAY is :1.0. I try xauth list, because ~/.Xauthority exists:

host:1  MIT-MAGIC-COOKIE-1  f91ec0372bd83eb72b686a16530ebb43
[five times the line above]
host/unix:1  MIT-MAGIC-COOKIE-1  f91ec0372bd83eb72b686a16530ebb43

Just in case, I try to set the environment variable:

export XAUTHORITY=c441e3e34e057b5a868d5520dc47e7f4

Still the same error. But echo $XAUTHORITY shows the cookie. Also Gilles states here that ~/.Xauthority is used, when it is not set. The cookie values differ, because I restarted xvncserver and deleted+recreated ~/.Xauthority before I wrote this. Arch wiki lists : xhost +si:localuser:$USER. I did it for my user and root. As far as I understand, this lowers security, but many answers use it as a quick fix. In my case, it throws:

localuser:root being added to access control list
X Error of failed request:  BadValue (integer parameter out of range for operation)
  Major opcode of failed request:  109 (X_ChangeHosts)
  Value in failed request:  0x5
  Serial number of failed request:  6
  Current serial number in output stream:  8

I am not sure if the error even relates to my problem. The same issue is caused by bugs or when the system is build wronlgy . Both things I cannot change at the moment. By now, I am bit clueless: - What is my problem? - How can I solve it? If someone knows a solution it would be great. But my priority is to have a *browser inside a VNC session*, so any kind of workaround would also be appreciated. I also tried to enable SSH X11Forwarding in sshd_config. It did not work. I think this is unrelated, as I use VNC instead of ssh -X option.

I use a vnc (tightvncserver) connection: Devuan/aarch64 and Armbian(Debian)/armfh (hosts) thru Win10/TigerVNC (client). Since the upgrade of the underlying base to Debian Bookworm, xscreensaver and any other locker fail to run for the same reason:

xscreensaver --no-splash
xscreensaver: 12:09:54: XInput extension missing

xtrlock -f
xtrlock (version 2.15): No X Input extension

I reached out the **Xscreensaver** developer, and he told me the Debian package brings with it all the necessary dependencies, and he doesn't know where the problem is. I also installed a bunch of additional packages but nothing has changed:

libx11-xcb1/stable-security,now 2:1.8.4-2+deb12u2 arm64 [installed,automatic]
libxcb-damage0/stable,now 1.15-1 arm64 [installed,automatic]
libxcb-dri2-0/stable,now 1.15-1 arm64 [installed,automatic]
libxcb-dri3-0/stable,now 1.15-1 arm64 [installed,automatic]
libxcb-glx0/stable,now 1.15-1 arm64 [installed,automatic]
libxcb-icccm4/stable,now 0.4.1-1.1 arm64 [installed,automatic]
libxcb-image0/stable,now 0.4.0-2 arm64 [installed,automatic]
libxcb-keysyms1/stable,now 0.4.0-1+b2 arm64 [installed,automatic]
libxcb-present0/stable,now 1.15-1 arm64 [installed,automatic]
libxcb-randr0/stable,now 1.15-1 arm64 [installed,automatic]
libxcb-render-util0/stable,now 0.3.9-1+b1 arm64 [installed,automatic]
libxcb-render0/stable,now 1.15-1 arm64 [installed,automatic]
libxcb-screensaver0/stable,now 1.15-1 arm64 [installed]
libxcb-shape0/stable,now 1.15-1 arm64 [installed,automatic]
libxcb-shm0/stable,now 1.15-1 arm64 [installed,automatic]
libxcb-sync1/stable,now 1.15-1 arm64 [installed,automatic]
libxcb-util1/stable,now 0.4.0-1+b1 arm64 [installed,automatic]
libxcb-xfixes0/stable,now 1.15-1 arm64 [installed,automatic]
libxcb-xinerama0/stable,now 1.15-1 arm64 [installed,automatic]
libxcb-xinput0/stable,now 1.15-1 arm64 [installed,automatic]
libxcb-xkb1/stable,now 1.15-1 arm64 [installed,automatic]
libxcb1-dev/stable,now 1.15-1 arm64 [installed,automatic]
libxcb1/stable,now 1.15-1 arm64 [installed,automatic]

On Bullseye, xscreensaver and other lockers were working just fine, I can't figure out how to fix this, thanks!

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.

Using tightvncserver, how do I load gnome-session over a VNC session? tried editing ~/.vnc/xstartup with gnome-session & but the screen stays gray. --- What I tried: unset SESSION_MANAGER exec /etc/X11/xinit/xinitrc export $(dbus-launch) gnome-session & --- If I try startxfce4 & without specifying anything else I have no issues and I can use the system, however I don't like the look of default xfce and would prefer gnome. OS: debian bookworm, default gnome version (43), tightvncserver

I created systemd unit for x0vncserver like this [Unit] Description=Remote desktop service (VNC) After=graphical.target [Service] Type=forking User=user ExecStart=/usr/bin/sh -c '/usr/bin/x0vncserver -display :0 -rfbport 5900 -passwordfile /home/user/.vnc/passwd &' [Install] WantedBy=multi-user.target and enabled it to run but it fails. Then I realized as I am trying to load the original desktop using x0vncserver, I can only do that after loading the desktop itself completely. So I have to set the system unit to run after loading the desktop but how? Or any timed way to set it up? Though it may be possible by using desktop session tools but any systemd way solution? and my default.target is

# systemctl get-default       
graphical.target

i remotely connect to my Virtual Machine Manager thru VNC client (MobaXTerm) to TightVNC (on the Debian host) on Win10. however, when i spin up a vm, the guest does not respond to any keyboard or mouse input. only the direcly-connected-to-server USB keyboard can be redirected. in the machine config, i've added the Avocent USB Composite Device to USB Hardware, i've tried adding additional USB redirects, but to no avail. i've seen that there are several posts on similar issues, none of which provided anything useful; probably because they are working directly on the machine. i have no such luxury down the line. i need to be able to manage this from my Win10 machine remotely, thus the VNC wrinkle... which, to my mind, shouldn't be much of a wrinkle at all. so flow-wise, it looks like this:

+-------+            +---------------------------+
|       |            |                   +----+  |
| win10 | --(VNC)--> | VMhost (VMM)  --> | VM |  |
|       |            |   Debian11        +----+  |
+-------+            +---------------------------+

so how do i get my inputs to flow down to the VM at the end? i apologize if i am missing something simple, because this seems a pretty simple setup... :P EDIT: i read a couple posts indicating that the native TightVNC should be replaced with TigerVNC due to the way QEMU remaps key inputs...? is this valid? i'd hate to tear it out only to introduce more issues.

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?

I am trying to run kex --win -s in kali linux in order to get the GUI but I am getting an error message:

Error: unable to connect socket: connection refused(10061)

Can you help I have tried the following:

Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux

dism.exe /online /enable-feature /featurename:VirtualMachinePlatform /all /norestart

dism.exe /online /enable-feature /featurename:Microsoft-Windows-Subsystem-Linux /all /norestart

wsl --set-default-version 2

wsl --set-version kali-linux 2

sudo apt install -y kali-win-kex



kex --win -s

Start the vncserver to accept connection from all network address:

vncserver -localhost no

Check the status of the kex again by:

kex --status

It should now list the vnc sessions Type the following command to start the kali windows:

kex --win -sl

If I run vncserver -localhost no I get the following:

Killing Xtigervnc process ID 29... success!

tail /home/vi/.vnc/Vik.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 May 24 18:42:53 2021
 vncext:      VNC extension running!
 vncext:      Listening for VNC connections on all interface(s), port 5901
 vncext:      created VNC server for screen 0

Mon May 24 18:43:24 2021
 ComparingUpdateTracker: 0 pixels in / 0 pixels out
 ComparingUpdateTracker: (1:-nan ratio)

vncserver: /usr/bin/Xtigervnc did not start up, please look into '/home/vi/.vnc/Vik.localdomain:5901.log' to determine the reason! -1

Am new to kali linux

I searched pretty thoroughly and I could only find posts in which people have keyboard mappings that are wrong system-wide, however I have a bizarre situation in which most applications work OK, but some are completely wrong: I am running Ubuntu 16.04 server with xfce installed (never had Unity/GNOME). I am running tightserver. I remote in and everything that comes with xfce seems to work. I installed various applications. The following do work: - gedit - firefox - filezilla - gimp The following do not work: - notepadqq - qbittorrent in notepadqq I get the following (left is keypressed, right is key displayed) a=a b=s c=d d=f e=g (if important I will make full list) I feel like there most be something very specific that would cause this, that is I don't think it has anything to do with processor load/hardware glitch/power fluctuation. Why would specific applications behave this way?

I am using Ubuntu 19.04. I want my VNC server on my Ubuntu computer to turn on during boot; I don't have a monitor plugged into it. I want to be able to run the full Ubuntu desktop remotely. I have managed to get my SSH server to work, and I can also get my x11vnc server to display on my Mac VNC client. However, this only works if I manually log in to Ubuntu and run the command

x11vnc -auth guess -forever -loop -noxdamage -repeat -rfbauth /home/USERNAME/.vnc/passwd -rfbport 5900 -share

I am able to create an SSH tunnel on my Mac and connect to it using a localhost:5900 connection. Next, I tried to make x11vnc turn on during boot, so I did the following. 1. sudo nano /lib/systemd/system/x11vnc.service 2. I saved the following text (123 is my gdm UID number)

[Unit]
    Description=Start x11vnc at startup.
    After=multi-user.target
    
    [Service]
    Type=simple
    ExecStart=/usr/bin/x11vnc -loop -forever -bg -rfbport 5900 -xkb -noxrecord -noxfixes -noxdamage -shared -norc -auth /run/user/123/gdm/Xauthority -rfbauth /etc/x11vnc.pass
    
    [Install] 
    WantedBy=multi-user.target

3. I ran the following commands

sudo systemctl enable x11vnc.service
    sudo systemctl daemon-reload
    sudo systemctl start x11vnc.service

4. I rebooted but didn't log in to my Ubuntu computer. 5. I connected to SSH and created a tunnel successfully on my Mac. 6. I tried to connect to the VNC server, but that failed. 7. I then logged into my Ubuntu computer manually. 8. I tried to connect to the VNC server, managed to connect, but it was a black screen. So what I can tell is that the service only started when I log in to the Ubuntu session manually. Is there a way to do what I am trying to achieve? I am willing to use another server as well; I am only using x11vnc so that I wouldn't have to install a new desktop.

Is there a way to change the background in the vnc

I currently trying to migrate from Centos7 to Debian10, but I'm blocked by a different default VNC behaviour. I'm using TigerVncViewer on my Windows and osx clients to connect to my server, and it has a feature called '**resize remote session to local window**'. This means that when the TigerVncViewer appliaction window is resized on the client, the remote screen on the vncserver is resized automatically to the same shape/resolution. This works beautifully out of the box for Centos 7. However, when I connect to a remote Debian 10 server the session remains a fixed size, reshaping the local TigerVncViewer window does not change it. I noticed that Centos7 uses Xnvc under the hood, while Debian10 runs a process called Xtightvnc, perhaps that is why? Does anyone know how to get this VNC auto-resizing feature to work on Debian10, do I need to change some config, or pass a some different args to Xtightvnc when it is started up via the vncserver wrapper? On some of the forums that I searched, people suggest that tightvnc does supports this feature, but it's just not obvious how to enable it. If anyone is interested, I followed these instructions for to set-up [a VNC server on Centos7](https://linuxize.com/post/how-to-install-and-configure-vnc-on-centos-7/) and these instructions [for Debian10](https://www.digitalocean.com/community/tutorials/how-to-install-and-configure-vnc-on-debian-10)

I have two linux machines running Linux Mint 19.3. I just install tightvnc server on one of them from apt. On the other I install remmina and remmina vnc plugin. I run vncserver on the host and it outputs to the console... New 'X' desktop is scott-Z97-HD3:1 Starting applications specified in /etc/X11/Xvnc-session Log file is /home/scott/.vnc/scott-Z97-HD3:1.log I then connect to the server using the other machine on Remmina. It seems to connect fine and enter remote desktop view. Unfortunately, all that is show is a dark background with a window box that displays the text... could not acquire name on session bus When I click the only button that says "logout", it just logs out and kills the client session. Is there something I am missing here for configuration? Here are the logs.. 11/05/19 11:43:32 Xvnc version TightVNC-1.3.10 11/05/19 11:43:32 Copyright (C) 2000-2009 TightVNC Group 11/05/19 11:43:32 Copyright (C) 1999 AT&T Laboratories Cambridge 11/05/19 11:43:32 All Rights Reserved. 11/05/19 11:43:32 See http://www.tightvnc.com/ for information on TightVNC 11/05/19 11:43:32 Desktop name 'X' (scott-Z97-HD3:1) 11/05/19 11:43:32 Protocol versions supported: 3.3, 3.7, 3.8, 3.7t, 3.8t 11/05/19 11:43:32 Listening for VNC connections on TCP port 5901 Font directory '/usr/share/fonts/X11/75dpi/' not found - ignoring Font directory '/usr/share/fonts/X11/100dpi/' not found - ignoring No VNC extension on display :1 11/05/19 11:43:40 Got connection from client 192.168.100.102 11/05/19 11:43:40 Using protocol version 3.8 11/05/19 11:43:40 Full-control authentication passed by 192.168.100.102 11/05/19 11:43:40 Pixel format for client 192.168.100.102: 11/05/19 11:43:40 16 bpp, depth 16, little endian 11/05/19 11:43:40 true colour: max r 31 g 63 b 31, shift r 11 g 5 b 0 11/05/19 11:43:40 Using tight encoding for client 192.168.100.102 11/05/19 11:43:40 rfbProcessClientNormalMessage: ignoring unknown encoding 16 11/05/19 11:43:40 rfbProcessClientNormalMessage: ignoring unknown encoding 9 11/05/19 11:43:40 rfbProcessClientNormalMessage: ignoring unknown encoding -65527 11/05/19 11:43:40 Using compression level 3 for client 192.168.100.102 11/05/19 11:43:40 Using image quality level 7 for client 192.168.100.102 11/05/19 11:43:40 Enabling X-style cursor updates for client 192.168.100.102 11/05/19 11:43:40 Enabling cursor position updates for client 192.168.100.102 11/05/19 11:43:40 rfbProcessClientNormalMessage: ignoring unknown encoding -131072 11/05/19 11:43:40 rfbProcessClientNormalMessage: ignoring unknown encoding -223 11/05/19 11:43:40 Enabling LastRect protocol extension for client 192.168.100.102 11/05/19 11:43:40 rfbProcessClientNormalMessage: ignoring unknown encoding -131071 11/05/19 11:43:40 rfbProcessClientNormalMessage: ignoring unknown encoding -131070 11/05/19 11:43:40 rfbProcessClientNormalMessage: ignoring unknown encoding -131069 11/05/19 11:43:40 rfbProcessClientNormalMessage: ignoring unknown encoding -309 Killing Xtightvnc process ID 14

[According to TigerVNC](https://src.fedoraproject.org/rpms/tigervnc/blob/master/f/HOWTO.md) , you cannot login a VNC session if the same user has already signed in a graphical session. > You will not be able to start a Tigervnc server for a user who is already logged into a graphical session. I know it is caused by Xvnc, which creates a new X server. x0vncserver in comparison can connect to an existing X server. So when I have a login server in GNOME, I will see black screen when I connect to VNC. The same happens vice versa. Would anyone know what is the reason behind that? If Xvnc can create a new X server, why it cannot have independent login? Thank you!

I use vnc over ssh with my Raspberry Pi. It has worked fine for a while, but after following these instructions to set up openvpn on my Raspberry Pi running Raspbian OS. I found that I can no longer access the VNC server on the Raspberry Pi. Forwarding x11 over ssh is working, but apparently, the vnc server cannot get access to its port, and so does not even start. $ sudo systemctl status vncserver-x11-serviced -l ● vncserver-x11-serviced.service - VNC Server in Service Mode daemon Loaded: loaded (/usr/lib/systemd/system/vncserver-x11-serviced.service; enabled) Active: active (running) since Sun 2018-01-21 14:25:11 GMT; 1s ago Main PID: 8896 (vncserver-x11-s) CGroup: /system.slice/vncserver-x11-serviced.service ├─8896 /usr/bin/vncserver-x11-serviced -fg ├─8898 /usr/bin/vncserver-x11-core -service └─8913 /usr/bin/vncagent service 14 Jan 21 14:25:11 raspberrypi vncserver-x11: TcpListenerManager: not accepting connections: failed to listen on at least one address. Jan 21 14:25:11 raspberrypi vncserver-x11: TcpListenerManager: not listening on [::1]::5900: bind: Cannot assign requested address (99) Jan 21 14:25:11 raspberrypi vncserver-x11: TcpListenerManager: not accepting connections: failed to listen on at least one address. Jan 21 14:25:11 raspberrypi vncserver-x11: TcpListenerManager: not listening on [::1]::5900: bind: Cannot assign requested address (99) Jan 21 14:25:11 raspberrypi vncserver-x11: TcpListenerManager: not accepting connections: failed to listen on at least one address. Jan 21 14:25:11 raspberrypi vncserver-x11: TcpListenerManager: not listening on [::1]::5900: bind: Cannot assign requested address (99) Jan 21 14:25:11 raspberrypi vncserver-x11: TcpListenerManager: not accepting connections: failed to listen on at least one address. Jan 21 14:25:11 raspberrypi vncserver-x11: TcpListenerManager: not listening on [::1]::5900: bind: Cannot assign requested address (99) Jan 21 14:25:11 raspberrypi vncserver-x11: TcpListenerManager: not accepting connections: failed to listen on at least one address. Jan 21 14:25:11 raspberrypi vncserver-x11: ConsoleDisplay: Found running X server (pid=1001) There doesn't appear to be anything running on that port. This is the output of lsof: $ sudo lsof -i tcp COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME cupsd 752 root 10u IPv4 13511 0t0 TCP localhost:ipp (LISTEN) cups-brow 756 root 5u IPv4 313573 0t0 TCP localhost:48450->localhost:ipp (CLOSE_WAIT) dnsmasq 914 dnsmasq 5u IPv4 11726 0t0 TCP *:domain (LISTEN) dnsmasq 914 dnsmasq 7u IPv6 11728 0t0 TCP *:domain (LISTEN) sshd 976 root 3u IPv4 11842 0t0 TCP *:2718 (LISTEN) tor 998 debian-tor 4u IPv4 12125 0t0 TCP 192.168.254.159:49042->ks3352401.kimsufi.com:8090 (ESTABLISHED) tor 998 debian-tor 7u IPv4 14489 0t0 TCP localhost:9050 (LISTEN) tor 998 debian-tor 11u IPv4 15915 0t0 TCP 172.94.70.220:47186->166.70.170.234:https (ESTABLISHED) sshd 5550 root 3u IPv4 315897 0t0 TCP 192.168.254.159:2718->192.168.254.47:64500 (ESTABLISHED) sshd 6322 morey 3u IPv4 315897 0t0 TCP 192.168.254.159:2718->192.168.254.47:64500 (ESTABLISHED) sshd 6322 morey 10u IPv4 319584 0t0 TCP localhost:6010 (LISTEN) Here's some other information that might be helpful: $ uname -a Linux raspberrypi 4.9.35-v7+ #1014 SMP Fri Jun 30 14:47:43 BST 2017 armv7l GNU/Linux $ vncserver --help VNC(R) Server 6.1.1 (r28093) ARMv6 (May 19 2017 12:59:35) It seems likely this has to do with either the changes to iptables or the disabling of ip6 in /etc/sysctl.conf, but I don't know how to troubleshoot it. Any ideas would be appreciated.