Error initializing vnc client

Guacamole

Namespaces

Page actions

A Linux desktop in a browser

Contents

Overview

Guacamole is a program to control a Linux desktop over the network in a browser.

Sometimes in your Linux life, you need to control your servers in the internet with a graphical user interface. This is tedious when you are behind a corporate firewall blocking ssh requests to the public internet. Typical corporate firewalls only allow proxified client access to port 80, 8080 and 443 in the public internet. One way to go is to use a browser to display a Linux desktop. The solution is guacamole.

Quickstart

This will show you

• how to install guacamole 1.3.0 on Ubuntu (tested with 20.04)
• how to make this configuration survive a reboot
• how to secure transmission with SSL
• how to make the website accessible from behind a firewall (port 80 or 443)

Here’s what you do as root user:

• install software that we will need later:

configure VNC server

Guacamole does the communication between a VNC server and the web browser. So whatever you see in VNC will be in the browser. In this example let’s use xfce as desktop environment:

• install xfce:

• activate it for your VNC:

deploy guacamole client

• download the guacamole webapp from http://sourceforge.net/projects/guacamole/files/current/binary/
• deploy it

• surf to http://localhost:8080/guacamole
• although login is not yet possible your browser will show a login screen like that:

install guacamole server

• install some dependencies that the server will need to build with vnc support:

• download guacamole-server from http://sourceforge.net/projects/guacamole/files/current/source/
• unpack it, in this example 1.3.0:

• build the server:

• the following step is ugly; installation and binary do not completely fit so we must do that:

• now we start the guacamole daemon:

configure guacamole

• create a folder for guacamole’s configuration:

• create a file /etc/guacamole/guacamole.properties with the content

• create a file /etc/guacamole/user-mapping.xml with the content

configure tomcat

• find out your tomcat’s user directory:

in this case it is /usr/share/tomcat9

• create a folder .guacamole in your tomcat’s user directory:

• link guacamole.properties into your tomcat’s user directories’ guacamole folder

finishing

• start a vnc server, as password set password (the vnc password given in user-mappings.xml)

• point your browser to http://localhost:8080/guacamole
• log in as user, password password (the user given in user-mappings.xml)
• you should see a screen like this:

Now when you click on «Default» you will see your VNC desktop in your browser.

secure transmission

Set up apache for https so your passwords are not transmitted unencrypted over the internet

make it work from behind a firewall

Most companies will have an internet proxy that does not allow users to access port 8080 on a server outside the company network. So you need a reverse proxy that tells apache if someone calls http://yourserver.yourdomain/guacamole this is forwarded to http://yourserver.yourdomain:8080 internally. To do this,

• edit /etc/sysconfig/apache2 and add the following words to APACHE_MODULES: proxy proxy_http. In the end your line may read like this:

• edit /etc/apache2/default-server.conf, add a block

Persist it

You want your configuration to survive a reboot so add the following line to /etc/crontab:

TroubleShooting

invalid login

• now the problem is that tomcat does not know where to find the Authentication class:

is not in /etc/guacamole/guacamole.properties

• so add it
• cat /etc/passwd gives me a line

• works now. So the thing is:
  • take care that it is called guacamole and not guacamole-0.8.3 (sure?)
  • make sure the classpath in /etc/guacamole/guacamole.properties is correct, e.g.

Server error

• now I got a server error so I straced guacd:

so the problem is that libguac-client-vnc.so is missing.

• downloaded java version 1.7.45 and compiled guacamole-client using mvn. But there was no *.so* file in it
• so installed libvncserver-dev and rebuild and reinstalled guacamole-server
• and there it is, libguac-client-vnc.so
• now the error message changed from «server error» to «unauthorized»

Failed to load

When logging in I got an error message

Solution was to:

Error initializing VNC client

After logging in I got the error message

Solution was to start

Could not connect

If you surf to the page and get an error message like

It probably means that tomcat is not running. It must be possible to connect to port 8080, a java process for tomcat must be running.

Источник

Apache Guacamole Discussion

HTML5 Clientless Remote Desktop

Forums

Real VNC error

I got the following error, «Error initializing VNC client» when I try to connect to Real VNC server on my ubuntu 12.10 from Windows 7 SP1.

I have attached the syslog as below:
Jul 9 16:30:43 demo-ubuntu guacd [17912] : Protocol «vnc» selected
Jul 9 16:30:43 demo-ubuntu guacd [17912] : VNC server supports protocol version 4.1 (viewer 3.8)
Jul 9 16:30:43 demo-ubuntu guacd [17912] : We have 2 security types to read
Jul 9 16:30:43 demo-ubuntu guacd [17912] : 0) Received security type 5
Jul 9 16:30:43 demo-ubuntu guacd [17912] : 1) Received security type 129
Jul 9 16:30:43 demo-ubuntu guacd [17912] : Unknown authentication scheme from VNC server: 5, 129
Jul 9 16:30:43 demo-ubuntu guacd [17912] : Error instantiating client: UNKNOWN STATUS CODE:

Following is my user-mapping.xml

guacd-hostname: localhost
guacd-port: 4822

auth-provider: net.sourceforge.guacamole.net.basic.BasicFileAuthenticationProvider
basic-user-mapping: /etc/guacamole/user-mapping.xml

Any issues on how to resolved this?
Greatly appreciated.

Jul 9 16:30:43 demo-ubuntu guacd [17912] : We have 2 security types to read
Jul 9 16:30:43 demo-ubuntu guacd [17912] : 0) Received security type 5
Jul 9 16:30:43 demo-ubuntu guacd [17912] : 1) Received security type 129
Jul 9 16:30:43 demo-ubuntu guacd [17912] : Unknown authentication scheme from VNC server: 5, 129

It looks like RealVNC is configured to use an authentication scheme not supported by libvncclient.

What type of authentication did you set up when configuring RealVNC?

At the first place, i’m using unix password. I have now set the authentication to «None». It is still not functioning.

If you’re still seeing an error like you see above («Unknown authentication scheme . «), then there must still be something non-standard enabled within RealVNC, otherwise the authentication scheme would be known to libvncclient.

According to http://www.realvnc.com/support/nomatchingsec.html it could be because encryption is enabled within RealVNC (encryption is a non-standard extension of VNC).

Can you post your logs after setting authentication to «None»? Can you describe what is enabled on RealVNC?

After messing around, I was able to get pass the previous log error.

I have attached the VNC setting.

Attached is the log:
Jul 10 11:06:24 demo-ubuntu guacd [18823] : Protocol «vnc» selected
Jul 10 11:06:24 demo-ubuntu guacd [18823] : VNC server supports protocol version 4.1 (viewer 3.8)
Jul 10 11:06:24 demo-ubuntu guacd [18823] : We have 5 security types to read
Jul 10 11:06:24 demo-ubuntu guacd [18823] : 0) Received security type 6
Jul 10 11:06:24 demo-ubuntu guacd [18823] : 1) Received security type 130
Jul 10 11:06:24 demo-ubuntu guacd [18823] : 2) Received security type 1
Jul 10 11:06:24 demo-ubuntu guacd [18823] : Selecting security type 1 (2/5 in the list)
Jul 10 11:06:24 demo-ubuntu guacd [18823] : 3) Received security type 5
Jul 10 11:06:24 demo-ubuntu guacd [18823] : 4) Received security type 129
Jul 10 11:06:24 demo-ubuntu guacd [18823] : Selected Security Scheme 1
Jul 10 11:06:24 demo-ubuntu guacd [18823] : No authentication needed
Jul 10 11:06:24 demo-ubuntu guacd [18823] : VNC authentication succeeded
Jul 10 11:06:24 demo-ubuntu guacd [18823] : Desktop name «demo-ubuntu»
Jul 10 11:06:24 demo-ubuntu guacd [18823] : Connected to VNC server, using protocol version 3.8
Jul 10 11:06:24 demo-ubuntu guacd [18823] : VNC server default format:
Jul 10 11:06:24 demo-ubuntu guacd [18823] : 32 bits per pixel.
Jul 10 11:06:24 demo-ubuntu guacd [18823] : Least significant byte first in each pixel.
Jul 10 11:06:24 demo-ubuntu guacd [18823] : TRUE colour: max red 255 green 255 blue 255, shift red 16 green 8 blue 0
Jul 10 11:06:24 demo-ubuntu guacd [18823] : Starting client

On my client screen, I was struck at the message, «Connected, waiting for first update.» Any idea what went wrong?

Источник

guacamole cant connect to vnc

i have succesfully installed guacamole on my ubuntu server and i can connect to a rdp and ssh connections but i cant connect to a vnc connection

my vnc connection is my centos desktop and everytime i try connect to it i get this error — error initializing vnc client

its the same machine where when i create a ssh connection i can connect to it no problem but vnc it comes up with an error

i have installed a vnc server and i can connect to it from a vnc client via this 172.16.9.5:2

Popular Topics in Web Browser

i added in my user-mapping.xml file all the param names eg hostname/port but the one param i was forgetting was the «password» and to test what port the vnc server was using on my pfsense firewall i ran an «nmap» command to the servers ip to list all the open ports on that host and one of the ports was vnc port 5901

i used syslog to list all the events and worked it out from there

Thanks for sharing the fix.

This topic has been locked by an administrator and is no longer open for commenting.

To continue this discussion, please ask a new question.

Read these next.

poor wifi, school’s third floor

I work as a help desk technician at a high school for a school district. Teachers/students on the building’s third floor have been reporting poor wifi, with their Chromebooks/laptops etc experiencing slow connectivity and random disconnections. We hav.

Need help crafting a job posting for an IT Pro

I’d really appreciate some thoughts and advice. I’m looking to hire an IT pro to be our resident go-to for all things IT (device support, SQL Server, network admin, etc) but who also is interested in learning — or even has some experience in — the.

Snap! — AI Eye Contact, Mine Batteries, Headset-free Metaverse, D&D Betrayal

Your daily dose of tech news, in brief. Welcome to the Snap! Flashback: January 13, 1874: Adding Machine Patented (Read more HERE.) Bonus Flashback: January 13, 1990: Astronauts awakened to the song Attack of the Killer Tomatoes (Read mor.

Spark! Pro series – 13th January 2023

Happy Friday the 13th! This day has a reputation for being unlucky, but I hope that you’ll be able to turn that around and have a great day full of good luck and good fortune. Whether you’re superstitious or not, .

Источник

Apache Guacamole Discussion

HTML5 Clientless Remote Desktop

Forums

Error initializing VNC client?

I keep getting this error even though I have checked and checked all over again and again that my settings are correct.

Is there anybody who could help whit this issue?

That message indicates an error from libguac-client-vnc, which logs errors and information to syslog. Do you see any errors in syslog when you reproduce this problem?

Yes, there is this kind of logfile:

guacd: Spawning client
guacd: ConnectClientToTcpAddr6: getaddrinfo (No address associated with hostname)
guacd: ConnectToTcpAddr: connect
guacd: Unable to connect to VNC server
guacd: Client retrieval failed
guacd: Spawning client
guacd: Spawning client
guacd: Client retrieval failed
guacd: Spawning client
guacd: ConnectClientToTcpAddr6: getaddrinfo (No address associated with hostname)
guacd: ConnectToTcpAddr: connect
guacd: Unable to connect to VNC server
guacd: Client retrieval failed

Should I edit my etc/hosts file or what should I do?

It sounds like editing your /etc/hosts would help. If the host you’re trying to connect to is truly not in DNS, or you have no DNS, you will need to do this if you wish to refer to it by hostname rather than IP.

I did edit my etc/hosts file, but it did not solve the problem. Same error keeps coming up. Any ideas?

Try pinging the host in question as listed in your user-mapping.xml?

Pinging did work 100%. I think it is some kind of internal error, because when I try to log in guacamole from localhost it still gives same error. In my vncserver I use Debian Wheezy with kvm/qemu and wm is Fluxbox. Client machine have Debian Squeeze with Lxde…. I’m thinking that the .deb packages which I downloaded were for Squeeze? So, should I try to compile Guacamole from source to get it work in Wheezy? Or does it matter, because when I installed the packages it did not gave any errors.

Debian Wheezy actually has all the Guacamole packages in their main repository. You can simply:

and then configure everything.

I highly doubt this is an internal error, and considering the error refers to being unable to resolve a hostname, I doubt this has anything to do with Debian version. The error in the logs is coming from libvncclient (which would have been installed from your distribution’s main repository), not from guacd, libguac-client-vnc, or anything Guacamole-specific.

I would first try using the IP address instead of the hostname, and see if libvncclient likes that.

Thank you for that advice! I normally check from debian packages, but not this time…

Well, I did apt-get install guacamole, but know it says «Error reading basic user mapping file.»

Here are screenshots:

This is the error

Check the permissions of /etc/guacamole/user-mapping.xml. The wheezy packages will make this file group-readable and owned by the group guacamole-web. You will need to add the tomcat6 user to the guacamole-web group so it can read the file.

I did change the permissions, and after a few my own typo fixes I did get it to work finally. Thanks to you!

I think I am some kind of idiot with linux. Even though I have used Debian over five years. So, I’m going to donate a little money to your project. This is so nice! Keep up the good work!

Источник

From Linuxintro

A Linux desktop in a browser

Contents

• 1 Overview
• 2 Quickstart
  • 2.1 configure VNC server
  • 2.2 deploy guacamole client
  • 2.3 install guacamole server
  • 2.4 configure guacamole
  • 2.5 configure tomcat
  • 2.6 finishing
  • 2.7 secure transmission
  • 2.8 make it work from behind a firewall
• 3 Persist it
• 4 TroubleShooting
  • 4.1 invalid login
  • 4.2 Server error
  • 4.3 Failed to load
  • 4.4 Error initializing VNC client
  • 4.5 Could not connect
• 5 See also

Overview

Guacamole is a program to control a Linux desktop over the network in a browser.

Sometimes in your Linux life, you need to control your servers in the internet with a graphical user interface. This is tedious when you are behind a corporate firewall blocking ssh requests to the public internet. Typical corporate firewalls only allow proxified client access to port 80, 8080 and 443 in the public internet. One way to go is to use a browser to display a Linux desktop. The solution is guacamole.

Quickstart

This will show you

• how to install guacamole 1.3.0 on Ubuntu (tested with 20.04)
• how to make this configuration survive a reboot
• how to secure transmission with SSL
• how to make the website accessible from behind a firewall (port 80 or 443)

Here’s what you do as root user:

• install software that we will need later:

apt-get update
apt-get install tomcat9 tightvncserver gcc make xterm

configure VNC server

Guacamole does the communication between a VNC server and the web browser. So whatever you see in VNC will be in the browser. In this example let’s use xfce as desktop environment:

• install xfce:

apt-get install xfce4

• activate it for your VNC:

cd
mkdir .vnc
cat >> .vnc/xstartup <<EOF
#!/bin/sh
xfce4-session || xterm
EOF
chmod 777 .vnc/xstartup

deploy guacamole client

• download the guacamole webapp from http://sourceforge.net/projects/guacamole/files/current/binary/
• deploy it

# mv guacamole-1.3.0.war /var/lib/tomcat9/webapps/guacamole.war

• surf to http://localhost:8080/guacamole
• although login is not yet possible your browser will show a login screen like that:

install guacamole server

• install some dependencies that the server will need to build with vnc support:

apt-get install libvncserver-dev libpng-dev libcairo-dev

• download guacamole-server from http://sourceforge.net/projects/guacamole/files/current/source/
• unpack it, in this example 1.3.0:

tar xvzf guacamole-server-1.3.0.tar.gz

• build the server:

cd guacamole-server-1.3.0
./configure && make -j8 && make install

• the following step is ugly; installation and binary do not completely fit so we must do that:

ln -s /usr/local/lib/libguac.so* /lib
ln -s /usr/local/lib/libguac-client-vnc.so* /lib/

• now we start the guacamole daemon:

# guacd
guacd[17669]: INFO:  Guacamole proxy daemon (guacd) version 0.9.3
guacd[17669]: INFO:  Successfully bound socket to host ::1, port 4822
guacd[17669]: INFO:  Exiting and passing control to PID 17671
root@tstaerk-desktop:/var/log# guacd[17671]: INFO:  Exiting and passing control to PID 17672

configure guacamole

• create a folder for guacamole’s configuration:

mkdir /etc/guacamole

• create a file /etc/guacamole/guacamole.properties with the content

# Hostname and port of guacamole proxy
guacd-hostname: localhost
guacd-port:     4822

# Location to read extra .jar's from
lib-directory:  /var/lib/tomcat9/webapps/guacamole-1.3.0/WEB-INF/classes

# Authentication provider class
auth-provider: net.sourceforge.guacamole.net.basic.BasicFileAuthenticationProvider

# Properties used by BasicFileAuthenticationProvider
basic-user-mapping: /etc/guacamole/user-mapping.xml

• create a file /etc/guacamole/user-mapping.xml with the content

<user-mapping>
   <authorize username="user" password="password">
      <protocol>vnc</protocol>
         <param name="hostname">localhost</param>
         <param name="port">5901</param>
         <param name="password">password</param>
    </authorize>
</user-mapping>

configure tomcat

• find out your tomcat’s user directory:

# cat /etc/passwd|grep tomcat
tomcat6:x:113:116::/usr/share/tomcat9:/bin/false

in this case it is /usr/share/tomcat9

• create a folder .guacamole in your tomcat’s user directory:

mkdir /usr/share/tomcat9/.guacamole

• link guacamole.properties into your tomcat’s user directories’ guacamole folder

ln -s /etc/guacamole/guacamole.properties /usr/share/tomcat9/.guacamole

finishing

• start a vnc server, as password set password (the vnc password given in user-mappings.xml)

vncserver

• point your browser to http://localhost:8080/guacamole
• log in as user, password password (the user given in user-mappings.xml)
• you should see a screen like this:

Now when you click on «Default» you will see your VNC desktop in your browser.

secure transmission

Set up apache for https so your passwords are not transmitted unencrypted over the internet

make it work from behind a firewall

Most companies will have an internet proxy that does not allow users to access port 8080 on a server outside the company network. So you need a reverse proxy that tells apache if someone calls http://yourserver.yourdomain/guacamole this is forwarded to http://yourserver.yourdomain:8080 internally. To do this,

• edit /etc/sysconfig/apache2 and add the following words to APACHE_MODULES: proxy proxy_http. In the end your line may read like this:

APACHE_MODULES="actions alias auth_basic proxy proxy_http authn_file authz_host authz_groupfile authz_default authz_user autoindex cgi dir env expires include log_config mime negotiation setenvif ssl userdir php5"

• edit /etc/apache2/default-server.conf, add a block

<IfModule mod_proxy.c>
<Location /guacamole>
    ProxyPass http://127.0.0.1:8080
</Location>
</IfModule>

Persist it

You want your configuration to survive a reboot so add the following line to /etc/crontab:

@reboot root /usr/local/sbin/guacd &

TroubleShooting

invalid login

• now the problem is that tomcat does not know where to find the Authentication class:

/var/lib/tomcat6/webapps/guacamole/WEB-INF/classes/net/sourceforge/guacamole/net/basic/BasicFileAuthenticationProvider.class

is not in /etc/guacamole/guacamole.properties

• so add it
• cat /etc/passwd gives me a line

tomcat6:x:113:116::/usr/share/tomcat6:/bin/false

ll /usr/share/tomcat6/.guacamole/
total 8
drwxr-xr-x 2 root root 4096 Nov 26 07:58 ./
drwxr-xr-x 6 root root 4096 Nov 26 07:57 ../
lrwxrwxrwx 1 root root   35 Nov 26 07:58 guacamole.properties -> /etc/guacamole/guacamole.properties

• works now. So the thing is:
  • take care that it is called guacamole and not guacamole-0.8.3 (sure?)
  • make sure the classpath in /etc/guacamole/guacamole.properties is correct, e.g.

# Location to read extra .jar's from
lib-directory:  /var/lib/tomcat6/webapps/guacamole/WEB-INF/classes

Server error

• now I got a server error so I straced guacd:

strace -p 15332

and saw

[pid 20344] open("/usr/lib/x86_64-linux-gnu/libguac-client-vnc.so", O_RDONLY) = -1 ENOENT (No such file or directory)

so the problem is that libguac-client-vnc.so is missing.

• downloaded java version 1.7.45 and compiled guacamole-client using mvn. But there was no *.so* file in it
• so installed libvncserver-dev and rebuild and reinstalled guacamole-server
• and there it is, libguac-client-vnc.so
• now the error message changed from «server error» to «unauthorized»

Failed to load

When logging in I got an error message

Failed to execute 'send' on 'XMLHttpRequest': Failed to load 'http://162.209.103.145:8080/guacamole-0.8.3/login'.

Solution was to:

/etc/init.d/tomcat6 restart

Error initializing VNC client

After logging in I got the error message

Error initializing VNC client

Solution was to start

vncserver

Could not connect

If you surf to the page and get an error message like

Unable to connect

It probably means that tomcat is not running. It must be possible to connect to port 8080, a java process for tomcat must be running.

/etc/init.d/tomcat6 status

must deliver something like

* Tomcat servlet engine is running with pid 17546

See also

• connect to a Linux computer
• guacamole 0.8 on SUSE
• guacamole 0.3.0 on Ubuntu 10.04
• cool things
• schedule tAsks
• http://guac-dev.org/Debian%20Install%20Instructions
• ulteo
• http://www.filegott.se/prd/index.php/how-tos/19-how-to-setup-guacamole-in-linux-ubuntu
• http://guac-dev.org/doc/gug/installing-guacamole.html#idp99200

it same version 1.1.0.8 it work for few minutes after that tigervncsever got this msg.
very confuse…

[root@FEL-Server01 .vnc]# service vncserver status
Xvnc dead but subsys locked

vncserver log
Xvnc TigerVNC 1.3.1 — built Mar 19 2014 12:23:55
Copyright (C) 1999-2011 TigerVNC Team and many others (see README.txt)
See http://www.tigervnc.org for information on TigerVNC.
Underlying X server release 11300000, The X.Org Foundation

Initializing built-in extension VNC-EXTENSION
Initializing built-in extension Generic Event Extension
Initializing built-in extension SHAPE
Initializing built-in extension MIT-SHM
Initializing built-in extension XInputExtension
Initializing built-in extension XTEST
Initializing built-in extension BIG-REQUESTS
Initializing built-in extension SYNC
Initializing built-in extension XKEYBOARD
Initializing built-in extension XC-MISC
Initializing built-in extension XFIXES
Initializing built-in extension RENDER
Initializing built-in extension RANDR
Initializing built-in extension COMPOSITE
Initializing built-in extension DAMAGE
Initializing built-in extension MIT-SCREEN-SAVER
Initializing built-in extension DOUBLE-BUFFER
Initializing built-in extension RECORD
Initializing built-in extension DPMS
Initializing built-in extension X-Resource
Initializing built-in extension XVideo
Initializing built-in extension XVideo-MotionCompensation
Initializing built-in extension GLX

Thu Jul 17 22:26:26 2014
vncext: VNC extension running!
vncext: Listening for VNC connections on all interface(s), port 5901
vncext: Listening for HTTP connections on all interface(s), port 5801
vncext: created VNC server for screen 0
GNOME_KEYRING_SOCKET=/tmp/keyring-00yft3/socket
SSH_AUTH_SOCK=/tmp/keyring-00yft3/socket.ssh
GNOME_KEYRING_PID=14715

(polkit-gnome-authentication-agent-1:14761): GLib-GObject-WARNING **: cannot register existing type `_PolkitError’

(polkit-gnome-authentication-agent-1:14761): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0′ failed
Failed to play sound: Not available
W: main.c: This program is not intended to be run as root (unless —system is specified).

** (gnome-user-share:14785): WARNING *: gnome-user-share cannot be started as root for security reasons.
* Message: applet now removed from the notification area
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension
** Message: applet now embedded in the notification area

Thu Jul 17 22:27:52 2014
Connections: accepted: 1.20.26.228::20237
SConnection: Client needs protocol version 3.8
SConnection: Client requests security type VncAuth(2)
VNCSConnST: Server default pixel format depth 24 (32bpp) little-endian rgb888
VNCSConnST: Client pixel format depth 8 (8bpp) color-map

Thu Jul 17 22:27:54 2014
Connections: closed: 1.20.26.228::20237 (Clean disconnection)
SMsgWriter: framebuffer updates 3
SMsgWriter: ZRLE rects 3, bytes 14265
SMsgWriter: raw bytes equivalent 786478, compression ratio 55.133403

Thu Jul 17 22:28:06 2014
Connections: accepted: 1.20.26.228::20206

Thu Jul 17 22:28:07 2014
SConnection: Client needs protocol version 3.8
SConnection: Client requests security type VncAuth(2)
VNCSConnST: Server default pixel format depth 24 (32bpp) little-endian rgb888
VNCSConnST: Client pixel format depth 8 (8bpp) color-map

(nautilus:14740): Nautilus-GDU-WARNING **: unable to query info: The specified location is not supported

Thu Jul 17 22:31:02 2014
Connections: closed: 1.20.26.228::20206 (Clean disconnection)
SMsgWriter: framebuffer updates 20
SMsgWriter: ZRLE rects 46, bytes 33301
SMsgWriter: raw bytes equivalent 1780444, compression ratio 53.465181
XIO: fatal IO error 11 (Resource temporarily unavailable) on X server «:1»

  after 151 requests (151 known processed) with 0 events remaining.

gnome-panel: Fatal IO error 11 (Resource temporarily unavailable) on X server :1.
Window manager warning: gnome-settings-daemon: Fatal IO error 11 (Resource temporarily unavailable) on X server :1.
Fatal IO error 11 (Resource temporarily unavailable) on display ‘:1’.
gnome-session: Fatal IO error 11 (Resource temporarily unavailable) on X server :1.

(gnome-panel:14737): GLib-GObject-CRITICAL **: g_object_run_dispose: assertion `G_IS_OBJECT (object)’ failed
nautilus: Fatal IO error 11 (Resource temporarily unavailable) on X server :1.
gnome-power-manager: Fatal IO error 11 (Resource temporarily unavailable) on X server :1.
bluetooth-applet: Fatal IO error 11 (Resource temporarily unavailable) on X server :1.
polkit-gnome-authentication-agent-1: Fatal IO error 11 (Resource temporarily unavailable) on X server :1.
abrt-applet: Fatal IO error 11 (Resource temporarily unavailable) on X server :1.
gnome-screensaver: Fatal IO error 11 (Resource temporarily unavailable) on X server :1.
gnome-volume-control-applet: Fatal IO error 11 (Resource temporarily unavailable) on X server :1.
gdu-notification-daemon: Fatal IO error 11 (Resource temporarily unavailable) on X server :1.
nm-applet: Fatal IO error 11 (Resource temporarily unavailable) on X server :1.
evolution-alarm-notify: Fatal IO error 11 (Resource temporarily unavailable) on X server :1.
applet.py: Fatal IO error 11 (Resource temporarily unavailable) on X server :1.
gpk-update-icon: Fatal IO error 11 (Resource temporarily unavailable) on X server :1.

Oops!! Failed to start remote desktop service VNC? We can help you with it.

One of the main reasons for the failure to start remote desktop service vnc is related to setting vnc user password.

At Bobcares, we get requests on VNC errors as a part of our Server Management Services.

Today, we’ll see how our Support Engineers fix this.

Failed to start remote desktop service VNC? Reasons are here!

VNC is a graphical desktop-sharing system in order to control another computer remotely. But there are different reasons for VNC service start to fail. Our Support Engineers handled many cases and we found that the two of the main reasons are:

• VNC password not set
• VNC fails to clear the files

Today we are going to discuss how our Support Engineers fix it for our customers.

1. Failed to start VNC occur when password not set

There are situations where customers approach us saying failed to start remote desktop service vnc.  Our Engineers handled such issues recently. When checked we found that the VNC password was not set. So, we set the password for the user- Mynewuser defined in the configuration file and restarted the service. This fixed the issue.

2. VNC failed to clear the files

Recently one of our customers approached us saying that he is getting an error when he starts the VNC service. He also mentioned that he is using TigerVNC.

So our Support Engineers tried starting VNC and we got an error when trying to start VNC service.

Job for vncserver@:X.service failed because a configured resource limit was exceeded. See systemctl status vncserver@:X.service and journalctl -xe for details.

So, we checked in detail and found that tigerVNC failed to clear the files created under /tmp and /tmp/.X11-unix/. So we removed them manually using the command below:

rm -f /tmp/.X11-unix/Y ; where Y is the file to remove.

Then restarted the server using the command:

systemctl start vncserver@:X.service

Note: Fix may vary depending on the OS and VNC (TightVNCTigerVNC, UltraVNC, etc).

[Failed to start remote desktop service VNC? – Our Experts are available 24/7.]

Conclusion

In conclusion the VNC service fails to start in different scenarios. Today, we discussed this topic in detail and saw how our Support Engineers find the fix for different scenarios.

var google_conversion_label = «owonCMyG5nEQ0aD71QM»;