我描述了我到底做了什么:
首先,我安装了debian10-netinstall。
然后我通过“Tasksel”命令安装了Gnome。
然后我使用这个教程来安装vnc服务器。然后我通过命令tightvncserver -geometry 1024x720 :1启动vncserver,下面是输出:
New 'X' desktop is debian:1
Starting applications specified in /home/parsa/.vnc/xstartup
Log file is /home/parsa/.vnc/debian:1.log下面是~/..vnc/debian:1. the:
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正如您在最后一行中所看到的,有一个错误。
我通过注释这个文件中包含“-登录”的行来修正这个问题:) /usr/bin/x-terminal-emulator
然后重新启动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然后让我们再次查看日志文件。
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)现在错误已经消失,我连接到vncserver,这些行出现在日志中:
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我在vnc浏览器中看到一个带有黑色X光标的灰色屏幕:

你能帮我解决这个问题吗?
我已经搜索了很多这个rfbProcessClientNormalMessage: ignoring unknown encoding错误,但是我找不到解决方案。
顺便说一句,这是我的~/.vnc/xstartup:
#!/bin/shxrdb $HOME/.Xresources
xsetroot -solid grey
x-terminal-emulator -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &
# x-window-manager &
gnome-session &谢谢。
发布于 2019-12-27 22:47:16
为了克服这个问题,我使用了一个旧的解决方案中的~/.vnc/xstartup:
#!/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
xsetroot -solid grey &
vncconfig -iconic &而且起作用了。
发布于 2020-11-19 06:16:53
这个问题是关于使用gnome 3的debian的,但是其他的答案主要是关于使用xfce的debian。这个问题花了我很多时间。最后这位医生救了我。我使用debian 10安装了gnome,tigervnc作为vnc服务器。
#install vnc servrer
sudo apt install tigervnc-standalone-server
#start vncserver and allow remote login
vncserver -localhost no :1
#check the port listen stat
netstat -tul | grep 5901您可以使用tiger vnc查看器使用:1或:5901连接vnc服务器。
记住:1.在启动vnc服务器之前注销当前用户。2.在公共网络中应使用ssh隧道,而不要使用-localhost no。
#https://www.digitalocean.com/community/tutorials/how-to-install-and-configure-vnc-on-debian-10
ssh -L 5901:127.0.0.1:5901 -C -N -l loginuser your_server_ip使用localhost:1或localhost:5901连接到vnc服务器
更多内容:您可以看到文档https://help.ubuntu.com/community/VNC/Servers来查看如何在引导时启动TigerVNC vncserver。
发布于 2019-10-03 12:17:10
在尝试从VNC到Debian 10时也出现了同样的问题。
显然,Debian 10使用Wayland和VNC有一些问题。
我的解决办法是让Wayland瘫痪。为此,编辑/etc/gdm3/daemon.conf并取消对行的注释
#WaylandEnable=false所以相反,它会读到
WaylandEnable=false然后重新启动服务器,启动VNC服务器,我可以连接到它。
https://unix.stackexchange.com/questions/543864
复制相似问题