/etc/gdm/Xsession: Beginning session setup...
Failure: Module initalization failed
/etc/gdm/Xsession: Setup done, will execute: /usr/bin/ssh-agent -- gnome-session
GNOME_KEYRING_CONTROL=/tmp/keyring-OVMbGk
GPG_AGENT_INFO=/tmp/keyring-OVMbGk/gpg:0:1
GNOME_KEYRING_CONTROL=/tmp/keyring-OVMbGk
GPG_AGENT_INFO=/tmp/keyring-OVMbGk/gpg:0:1
GNOME_KEYRING_CONTROL=/tmp/keyring-OVMbGk
GPG_AGENT_INFO=/tmp/keyring-OVMbGk/gpg:0:1
GNOME_KEYRING_CONTROL=/tmp/keyring-OVMbGk
GPG_AGENT_INFO=/tmp/keyring-OVMbGk/gpg:0:1
SSH_AUTH_SOCK=/tmp/keyring-OVMbGk/ssh

(gnome-settings-daemon:6690): keybindings-plugin-WARNING **: Key binding (screenreader) is incomplete

(gnome-settings-daemon:6690): keybindings-plugin-WARNING **: Key binding (magnifier) is incomplete

(gnome-settings-daemon:6690): keybindings-plugin-WARNING **: Key binding (onscreenkeyboard) is incomplete
Failure: Module initalization failed
Failed to play sound: File or data not found
** Message: applet now removed from the notification area
      JS LOG: GNOME Shell started at Sun Jun 05 2011 00:48:38 GMT+0300 (EEST)
** Message: applet now embedded in the notification area
Window manager warning: CurrentTime used to choose focus window; focus window may not be correct.
Window manager warning: Got a request to focus the no_focus_window with a timestamp of 0.  This shouldn't happen!
** (nm-applet:6741): WARNING **: handle_property_changed: failed to update property 'dhcp6-config' of object type NMDeviceWifi.
Window manager warning: Log level 16: handle_property_changed: failed to update property 'dhcp6-config' of object type NMDeviceWifi.
Window manager warning: Got a request to focus 0x2400005 (ioni@ioni-) with a timestamp of 0.  This shouldn't happen!

(gnome-shell:6721): Clutter-CRITICAL **: clutter_actor_queue_relayout: assertion `CLUTTER_IS_ACTOR (self)' failed
err:ole:CoGetClassObject class {77f10cf0-3db5-4966-b520-b7c54fd35ed6} not registered
err:ole:CoGetClassObject class {77f10cf0-3db5-4966-b520-b7c54fd35ed6} not registered
err:ole:create_server class {77f10cf0-3db5-4966-b520-b7c54fd35ed6} not registered
fixme:ole:CoGetClassObject CLSCTX_REMOTE_SERVER not supported
err:ole:CoGetClassObject no class object {77f10cf0-3db5-4966-b520-b7c54fd35ed6} could be created for context 0x17
fixme:winmm:MMDRV_Exit Closing while ll-driver open
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1800003 (Contact Li)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory

** (nm-applet:6741): WARNING **: handle_property_changed: failed to update property 'dhcp4-config' of object type NMDeviceWifi.

** (nm-applet:6741): WARNING **: handle_property_changed: failed to update property 'active-access-point' of object type NMDeviceWifi.

** (nm-applet:6741): WARNING **: handle_property_changed: failed to update property 'ip6-config' of object type NMDeviceWifi.

** (nm-applet:6741): WARNING **: handle_property_changed: failed to update property 'ip4-config' of object type NMDeviceWifi.
Window manager warning: Log level 16: handle_property_changed: failed to update property 'dhcp4-config' of object type NMDeviceWifi.
Window manager warning: Log level 16: handle_property_changed: failed to update property 'active-access-point' of object type NMDeviceWifi.
Window manager warning: Log level 16: handle_property_changed: failed to update property 'ip6-config' of object type NMDeviceWifi.
Window manager warning: Log level 16: handle_property_changed: failed to update property 'ip4-config' of object type NMDeviceWifi.
gnome-session[6656]: Gdk-WARNING: The program 'gnome-session' received an X Window System error.
This probably reflects a bug in the program.
The error was 'XI_BadDevice (invalid Device parameter)'.
  (Details: serial 165 error_code 149 request_code 141 minor_code 48)
  (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.)


(gnome-screensaver:6743): Gdk-WARNING **: The program 'gnome-screensaver' received an X Window System error.
This probably reflects a bug in the program.
The error was 'XI_BadDevice (invalid Device parameter)'.
  (Details: serial 1526 error_code 149 request_code 141 minor_code 48)
  (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.)


(empathy:6880): Gdk-WARNING **: The program 'empathy' received an X Window System error.
This probably reflects a bug in the program.
The error was 'XI_BadDevice (invalid Device parameter)'.
  (Details: serial 12302 error_code 149 request_code 141 minor_code 48)
  (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.)


(nm-applet:6741): Gdk-WARNING **: The program 'nm-applet' received an X Window System error.
This probably reflects a bug in the program.
The error was 'XI_BadDevice (invalid Device parameter)'.
  (Details: serial 6116 error_code 149 request_code 141 minor_code 48)
  (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.)


(gdu-notification-daemon:6734): Gdk-WARNING **: The program 'gdu-notification-daemon' received an X Window System error.
This probably reflects a bug in the program.
The error was 'XI_BadDevice (invalid Device parameter)'.
  (Details: serial 138 error_code 149 request_code 141 minor_code 48)
  (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.)


(gnome-terminal:6827): Gdk-WARNING **: The program 'gnome-terminal' received an X Window System error.
This probably reflects a bug in the program.
The error was 'XI_BadDevice (invalid Device parameter)'.
  (Details: serial 28306 error_code 149 request_code 141 minor_code 48)
  (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.)

xchat: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
      after 11 requests (11 known processed) with 0 events remaining.
Window manager warning: Log level 16: gnome-shell: Fatal IO error 0 (Success) on X server :0.


(gnome-settings-daemon:6690): Gdk-WARNING **: The application 'gnome-settings-daemon' lost its connection to the display :0;
most likely the X server was shut down or you killed/destroyed
the application.

[1307224116,000,xklavier.c:xkl_engine_start_listen/] 	The backend does not require manual layout management - but it is provided by the application
[1307224116,000,gkbd-status.c:gkbd_status_set_current_page_for_group/] 	Page for group 0 is not ready
[1307224116,000,gkbd-status.c:gkbd_status_set_current_page_for_group/] 	Page for group 0 is not ready
[1307224116,000,gkbd-status.c:gkbd_status_set_current_page_for_group/] 	Page for group 0 is not ready
[1307224116,000,gkbd-status.c:gkbd_status_set_current_page_for_group/] 	Page for group 0 is not ready
<unknown>: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
gnome-shell-calendar-server[6755]: Lost (or failed to acquire) the name org.gnome.Shell.CalendarServer - exiting
g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
thunderbird-bin: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
The application 'firefox' lost its connection to the display :0;
most likely the X server was shut down or you killed/destroyed
the application.

(gnome-power-manager:6742): Gdk-WARNING **: The application 'gnome-power-manager' lost its connection to the display :0;
most likely the X server was shut down or you killed/destroyed
the application.

