TurboVNC Server (Xvnc) 64-bit v1.2.3 (build 20150713)
Copyright (C) 1999-2015 The VirtualGL Project and many others (see README.txt)
Visit http://www.TurboVNC.org for more information on TurboVNC

15/07/2015 03:38:31 Using auth configuration file /etc/turbovncserver-auth.conf
15/07/2015 03:38:31 Enabled authentication method 'vnc'
15/07/2015 03:38:31 Enabled authentication method 'otp'
15/07/2015 03:38:31 Enabled authentication method 'pam-userpwd'
Couldn't open RGB_DB '/usr/share/X11/rgb'
15/07/2015 03:38:31 Desktop name 'TurboVNC: manjaro-vm-1:1 (username)' (manjaro-vm-1:1)
15/07/2015 03:38:31 Protocol versions supported: 3.3, 3.7, 3.8, 3.7t, 3.8t
15/07/2015 03:38:31 Listening for VNC connections on TCP port 5901
15/07/2015 03:38:31   Interface 0.0.0.0
15/07/2015 03:38:31 Framebuffer: BGRX 8/8/8/8
15/07/2015 03:38:31 VNC extension running!
xsetroot:  unknown color "grey"
gpg-agent[1736]: WARNING: "--write-env-file" is an obsolete option - it has no effect
gpg-agent: a gpg-agent is already running - not starting a new one

(xfce4-session:1725): xfce4-session-WARNING **: gpg-agent returned no PID in the variables

(xfce4-session:1725): xfce4-session-WARNING **: xfsm_manager_load_session: Something wrong with /home/username/.cache/sessions/xfce4-session-manjaro-vm-1:1, Does it exist? Permissions issue?

(xfwm4:1739): xfwm4-WARNING **: The display does not support the XComposite extension.

(xfwm4:1739): xfwm4-WARNING **: The display does not support the XDamage extension.

(xfwm4:1739): xfwm4-WARNING **: The display does not support the XFixes extension.

(xfwm4:1739): xfwm4-WARNING **: Compositing manager disabled.

(xfwm4:1739): xfwm4-WARNING **: Error opening /dev/dri/card0: No such file or directory

(xfsettingsd:1744): xfsettingsd-CRITICAL **: RANDR extension is too old, version 1.1. Display settings won't be applied.

(xfsettingsd:1744): xfsettingsd-CRITICAL **: Your XI is too old (1.3) version 1.4 is required.

(xfsettingsd:1744): xfsettingsd-CRITICAL **: Failed to initialize the Xkb extension.

(xfsettingsd:1744): xfsettingsd-CRITICAL **: Failed to initialize the Accessibility extension.
vmware-user: could not open /proc/fs/vmblock/dev

(polkit-gnome-authentication-agent-1:1752): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:264:30: not a number
process 1754: arguments to dbus_message_new_method_call() were incorrect, assertion "path != NULL" failed in file dbus-message.c line 1340.
This is normally a bug in some application using the D-Bus library.
  D-Bus not built with -rdynamic so unable to print a backtrace

(pamac-tray:1755): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:264:30: not a number
QXcbConnection: Failed to initialize XRandr
Qt: XKEYBOARD extension not present on the X server.

(pa-applet:1760): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:264:30: not a number

(polkit-gnome-authentication-agent-1:1752): Gtk-WARNING **: Theme parsing error: mate-applications.css:37:23: 'none' is not a valid color name

(nm-applet:1782): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:264:30: not a number

(pamac-tray:1755): Gtk-WARNING **: Theme parsing error: mate-applications.css:37:23: 'none' is not a valid color name

(pa-applet:1760): Gtk-WARNING **: Theme parsing error: mate-applications.css:37:23: 'none' is not a valid color name

(nm-applet:1782): Gtk-WARNING **: Theme parsing error: mate-applications.css:37:23: 'none' is not a valid color name

(polkit-gnome-authentication-agent-1:1752): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:264:30: not a number

(polkit-gnome-authentication-agent-1:1752): Gtk-WARNING **: Theme parsing error: mate-applications.css:37:23: 'none' is not a valid color name
Failed to resolve XF86AudioRaiseVolume into a keycode
Failed to resolve XF86AudioLowerVolume into a keycode
Failed to resolve XF86AudioMute into a keycode

** (xfce4-clipman:1749): WARNING **: Clipboard manager is already running.

(nm-applet:1782): GLib-GObject-WARNING **: The property GtkButton:use-stock is deprecated and shouldn't be used anymore. It will be removed in a future version.

(nm-applet:1782): GLib-GObject-WARNING **: The property GtkSettings:gtk-button-images is deprecated and shouldn't be used anymore. It will be removed in a future version.

(nm-applet:1782): GLib-GObject-WARNING **: The property GtkMisc:yalign is deprecated and shouldn't be used anymore. It will be removed in a future version.

(nm-applet:1782): GLib-GObject-WARNING **: The property GtkImage:stock is deprecated and shouldn't be used anymore. It will be removed in a future version.
warning: an instance of the application is already running...

(nm-applet:1782): GLib-GObject-WARNING **: The property GtkSettings:gtk-menu-images is deprecated and shouldn't be used anymore. It will be removed in a future version.
pa_context_get_card_info_by_index() failed

(nm-applet:1782): nm-applet-WARNING **: Failed to register as an agent: (32) An agent with this ID is already registered for this user.

(blueman-applet:1753): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:264:30: not a number

(blueman-applet:1753): Gtk-WARNING **: Theme parsing error: mate-applications.css:37:23: 'none' is not a valid color name

(manjaro-welcome:1751): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:264:30: not a number

(manjaro-welcome:1751): Gtk-WARNING **: Theme parsing error: mate-applications.css:37:23: 'none' is not a valid color name
blueman-applet version 2.0 starting
There is an instance already running
The program 'xfce4-panel' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
  (Details: serial 1007 error_code 2 request_code 137 minor_code 34)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

(xfce4-clipman:1749): Gdk-WARNING **: GdkWindow 0x280001d unexpectedly destroyed

(wrapper-1.0:1834): Gdk-WARNING **: GdkWindow 0x3c00003 unexpectedly destroyed

(pamac-tray:1755): Gdk-WARNING **: GdkWindow 0x4400002 unexpectedly destroyed

(nm-applet:1782): Gdk-WARNING **: GdkWindow 0x4800002 unexpectedly destroyed

(pa-applet:1760): Gdk-WARNING **: GdkWindow 0x4c00002 unexpectedly destroyed

(wrapper-1.0:1807): Gdk-WARNING **: GdkWindow 0x5800003 unexpectedly destroyed

(wrapper-1.0:1841): Gdk-WARNING **: GdkWindow 0x6000003 unexpectedly destroyed
The program 'xfce4-clipman' received an X Window System error.
This probably reflects a bug in the program.
The error was 'RenderBadPicture (invalid Picture parameter)'.
  (Details: serial 301 error_code 137 request_code 137 minor_code 7)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

(pamac-tray:1755): Gdk-ERROR **: The program 'pamac-tray' received an X Window System error.
This probably reflects a bug in the program.
The error was 'RenderBadPicture (invalid Picture parameter)'.
  (Details: serial 256 error_code 137 request_code 137 (RENDER) minor_code 7)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the GDK_SYNCHRONIZE environment
   variable to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

(nm-applet:1782): Gdk-ERROR **: The program 'nm-applet' received an X Window System error.
This probably reflects a bug in the program.
The error was 'RenderBadPicture (invalid Picture parameter)'.
  (Details: serial 249 error_code 137 request_code 137 (RENDER) minor_code 7)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the GDK_SYNCHRONIZE environment
   variable to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

(pa-applet:1760): Gdk-ERROR **: The program 'pa-applet' received an X Window System error.
This probably reflects a bug in the program.
The error was 'RenderBadPicture (invalid Picture parameter)'.
  (Details: serial 259 error_code 137 request_code 137 (RENDER) minor_code 7)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the GDK_SYNCHRONIZE environment
   variable to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
The program 'wrapper-1.0' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 216 error_code 3 request_code 18 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
The program 'wrapper-1.0' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 207 error_code 3 request_code 18 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
The program 'wrapper-1.0' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 648 error_code 3 request_code 2 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
java version "1.7.0_79"
OpenJDK Runtime Environment (IcedTea 2.5.5) (Arch Linux build 7.u79_2.5.5-1-x86_64)
OpenJDK 64-Bit Server VM (build 24.79-b02, mixed mode)
The program 'xfce4-panel' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
  (Details: serial 730 error_code 2 request_code 137 minor_code 34)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

(wrapper-1.0:1886): Gdk-WARNING **: GdkWindow 0x3c00003 unexpectedly destroyed
The program 'wrapper-1.0' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 227 error_code 3 request_code 18 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
The program 'wrapper-1.0' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 127 error_code 3 request_code 18 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

(wrapper-1.0:1887): Gdk-WARNING **: GdkWindow 0x4400003 unexpectedly destroyed
The program 'wrapper-1.0' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 191 error_code 3 request_code 18 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
The program 'xfce4-panel' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
  (Details: serial 730 error_code 2 request_code 137 minor_code 34)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

(wrapper-1.0:1895): Gdk-WARNING **: GdkWindow 0x3c00003 unexpectedly destroyed
The program 'wrapper-1.0' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 227 error_code 3 request_code 18 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
The program 'wrapper-1.0' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 127 error_code 3 request_code 18 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

(wrapper-1.0:1896): Gdk-WARNING **: GdkWindow 0x4400003 unexpectedly destroyed
The program 'wrapper-1.0' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 191 error_code 3 request_code 18 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
The program 'xfce4-panel' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
  (Details: serial 730 error_code 2 request_code 137 minor_code 34)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

(wrapper-1.0:1907): Gdk-WARNING **: GdkWindow 0x3c00003 unexpectedly destroyed
The program 'wrapper-1.0' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 227 error_code 3 request_code 18 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
The program 'wrapper-1.0' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 127 error_code 3 request_code 18 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

(wrapper-1.0:1908): Gdk-WARNING **: GdkWindow 0x4400003 unexpectedly destroyed
The program 'wrapper-1.0' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 191 error_code 3 request_code 18 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
The program 'xfce4-panel' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
  (Details: serial 730 error_code 2 request_code 137 minor_code 34)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

(wrapper-1.0:1916): Gdk-WARNING **: GdkWindow 0x3c00003 unexpectedly destroyed
The program 'wrapper-1.0' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 227 error_code 3 request_code 18 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
The program 'wrapper-1.0' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 127 error_code 3 request_code 18 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

(wrapper-1.0:1917): Gdk-WARNING **: GdkWindow 0x4400003 unexpectedly destroyed
The program 'wrapper-1.0' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 191 error_code 3 request_code 18 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
The program 'xfce4-panel' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
  (Details: serial 730 error_code 2 request_code 137 minor_code 34)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

(wrapper-1.0:1925): Gdk-WARNING **: GdkWindow 0x4400003 unexpectedly destroyed
The program 'wrapper-1.0' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 227 error_code 3 request_code 18 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
The program 'wrapper-1.0' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 127 error_code 3 request_code 18 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

(wrapper-1.0:1926): Gdk-WARNING **: GdkWindow 0x3c00003 unexpectedly destroyed
The program 'wrapper-1.0' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 191 error_code 3 request_code 18 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)