Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I initially installed VNC4SERVER to run Guacamole (render VM through browser) on an AWS EC2 Linux (Ubuntu 12.04) instance. It worked fine and then I shutdown the instance. After a few days I started it again, and then I noticed VNC not working properly.

I went into terminal and checked it out, and here were the logs:

  GNU nano 2.2.6                               File: /root/.vnc/ip-10-148-67-7:2.log                                                                    

04/06/13 17:28:46 Xvnc version TightVNC-1.3.9
04/06/13 17:28:46 Copyright (C) 2000-2007 TightVNC Group
04/06/13 17:28:46 Copyright (C) 1999 AT&T Laboratories Cambridge
04/06/13 17:28:46 All Rights Reserved.
04/06/13 17:28:46 See http://www.tightvnc.com/ for information on TightVNC
04/06/13 17:28:46 Desktop name 'X' (ip-10-148-67-7:2)
04/06/13 17:28:46 Protocol versions supported: 3.3, 3.7, 3.8, 3.7t, 3.8t
04/06/13 17:28:46 Listening for VNC connections on TCP port 5902
Font directory '/usr/share/fonts/X11/Type1/' not found - ignoring
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 :2
gnome-session[3440]: WARNING: GSIdleMonitor: IDLETIME counter not found
gnome-session-is-accelerated: No composite extension.
gnome-session-check-accelerated: Helper exited with code 256
gnome-session[3440]: WARNING: Session 'gnome-classic' runnable check failed: Exited with code 1

Can anyone help? Any piece of information or advice would be highly appreciated.

share|improve this question
These logs do not give much clue to me. can you try to restart your session see if that works ? – Raza Jun 4 '13 at 17:53
define restart session. I've killed vncserver (vncserver -kill :1 or any number) many times and started it again and again. The logs all say the same thing, the same as above. – AnimaSola Jun 4 '13 at 17:57
Yes, I meant the same. vncserver -kill :1 what error message do you get on the viewer side? can you enable debug log by run the vnc server and viewer with -Log flag like vncserver -Log=*:stderr:100 and vncviwer -Log=*:stderr:100 – Raza Jun 4 '13 at 18:07

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.