无法通过VNC启动gnome终端：
无法通过VNC启动gnome终端：
提问于 2020-01-28 14:10:37
我使用的是Ubuntu18.04.3LTS(机器实际上是运行在VMware ESXi上的VM )，我的VNC .xstartup文件包含以下行：
#!/bin/sh
gnome-panel &
gnome-settings-daemon &
metacity &
nautilus &使用以下命令通过VNC连接到桌面时，无法在VNC会话中打开终端会话：
vncserver :36 -geometry 1920x1080 -depth 16 -pixelformat rgb565
下面是我的VNC会话的相应日志文件：
"28/01/20 16:59:12 Xvnc version TightVNC-1.3.10
28/01/20 16:59:12 Copyright (C) 2000-2009 TightVNC Group
28/01/20 16:59:12 Copyright (C) 1999 AT&T Laboratories Cambridge
28/01/20 16:59:12 All Rights Reserved.
28/01/20 16:59:12 See http://www.tightvnc.com/ for information on TightVNC
28/01/20 16:59:12 Desktop name 'X' (ubuntu-server:36)
28/01/20 16:59:12 Protocol versions supported: 3.3, 3.7, 3.8, 3.7t, 3.8t
28/01/20 16:59:12 Listening for VNC connections on TCP port 5936
Font directory '/usr/share/fonts/X11/75dpi/' not found - ignoring
Font directory '/usr/share/fonts/X11/100dpi/' not found - ignoring
/home/ayildiz/.vnc/xstartup: line 4: gnome-settings-daemon: command not found
metacity-Message: 16:59:13.508: could not find XKB extension.
(metacity:1210): metacity-WARNING **: 16:59:13.513: Failed to create MetaCompositorXRender: Missing composite extension required for compositing
** (gnome-panel:1208): WARNING **: 16:59:13.655: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files
** (gnome-panel:1208): WARNING **: 16:59:13.692: Error opening directory “/usr/share/gnome-panel/applets”: No such file or directory
Gtk-Message: 16:59:15.152: GtkDialog mapped without a transient parent. This is discouraged.
28/01/20 16:59:22 Got connection from client 192.168.6.52
28/01/20 16:59:22 Using protocol version 3.8
28/01/20 16:59:26 Full-control authentication passed by 192.168.6.52
28/01/20 16:59:26 rfbProcessClientNormalMessage: ignoring unknown encoding 24
28/01/20 16:59:26 rfbProcessClientNormalMessage: ignoring unknown encoding 16
28/01/20 16:59:26 rfbProcessClientNormalMessage: ignoring unknown encoding 22
28/01/20 16:59:26 rfbProcessClientNormalMessage: ignoring unknown encoding 21
28/01/20 16:59:26 rfbProcessClientNormalMessage: ignoring unknown encoding 15
28/01/20 16:59:26 Using zlib encoding for client 192.168.6.52
28/01/20 16:59:26 rfbProcessClientNormalMessage: ignoring unknown encoding -314
28/01/20 16:59:26 Enabling full-color cursor updates for client 192.168.6.52
28/01/20 16:59:26 rfbProcessClientNormalMessage: ignoring unknown encoding -223
28/01/20 16:59:26 Pixel format for client 192.168.6.52:
28/01/20 16:59:26 8 bpp, depth 6
28/01/20 16:59:26 true colour: max r 3 g 3 b 3, shift r 4 g 2 b 0
28/01/20 16:59:27 Using raw encoding for client 192.168.6.52
28/01/20 16:59:27 rfbProcessClientNormalMessage: ignoring unknown encoding 24
28/01/20 16:59:27 rfbProcessClientNormalMessage: ignoring unknown encoding 22
28/01/20 16:59:27 rfbProcessClientNormalMessage: ignoring unknown encoding 21
28/01/20 16:59:27 rfbProcessClientNormalMessage: ignoring unknown encoding 16
28/01/20 16:59:27 rfbProcessClientNormalMessage: ignoring unknown encoding 15
28/01/20 16:59:27 rfbProcessClientNormalMessage: ignoring unknown encoding -314
28/01/20 16:59:27 Enabling full-color cursor updates for client 192.168.6.52
28/01/20 16:59:27 rfbProcessClientNormalMessage: ignoring unknown encoding -223
28/01/20 16:59:27 rfbProcessClientNormalMessage: ignoring unknown encoding 24
28/01/20 16:59:27 rfbProcessClientNormalMessage: ignoring unknown encoding 16
28/01/20 16:59:27 rfbProcessClientNormalMessage: ignoring unknown encoding 22
28/01/20 16:59:27 rfbProcessClientNormalMessage: ignoring unknown encoding 21
28/01/20 16:59:27 rfbProcessClientNormalMessage: ignoring unknown encoding 15
28/01/20 16:59:27 Using zlib encoding for client 192.168.6.52
28/01/20 16:59:27 rfbProcessClientNormalMessage: ignoring unknown encoding -314
28/01/20 16:59:27 Enabling full-color cursor updates for client 192.168.6.52
28/01/20 16:59:27 rfbProcessClientNormalMessage: ignoring unknown encoding -223
28/01/20 16:59:27 Pixel format for client 192.168.6.52:
28/01/20 16:59:27 16 bpp, depth 16, little endian
28/01/20 16:59:27 true colour: max r 31 g 63 b 31, shift r 11 g 5 b 0
28/01/20 16:59:27 no translation needed
Nautilus-Share-Message: 16:59:41.279: Called "net usershare info" but it failed: Failed to execute child process “net” (No such file or directory)
Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0: Error calling StartServiceByName for org.gnome.Terminal: Timeout was reached
"直到昨天，一切都很好，没有这样的问题。我试图重新启动VM和虚拟机管理程序，但是它没有工作。我怎样才能解决这个问题？
这是我通过我的VNC客户端看到的一个例子。
回答 3
Ask Ubuntu用户
发布于 2020-01-28 14:13:58
您正在导出显示服务器吗？
另外，尝试将gnome设置-守护进程放在第一位，并将gnome终端添加到您的vnc启动程序中，看看它是否能在重新启动时启动。
Ask Ubuntu用户
发布于 2020-01-28 16:19:09
终于成功了。
我所做的是运行以下命令(我不能100%确定这是一个解决方案)：
sudo apt-get update
sudo apt-get install --reinstall ubuntu-desktop gnome-panel gnome-settings-daemon metacity nautilus gnome-terminal
sudo apt-get update
sudo apt-get upgradeAsk Ubuntu用户
发布于 2020-08-20 16:43:59
也有同样的问题。使用TigerVNC服务器解决此问题- https://www.cyberciti.biz/faq/install-and-configure-tigervnc-server-on-ubuntu-18-04/
页面原文内容由Ask Ubuntu提供。腾讯云小微IT领域专用引擎提供翻译支持
原文链接：
https://askubuntu.com/questions/1206358
复制相关文章
相似问题
腾讯云开发者
