(process:5921): Gtk-WARNING **: This process is currently running setuid or setgid.
This is not a supported use of GTK+. You must create a helper
program instead. For further details, see:

    http://www.gtk.org/setuid.html

Refusing to initialize GTK+.

(process:5925): Gtk-WARNING **: This process is currently running setuid or setgid.
This is not a supported use of GTK+. You must create a helper
program instead. For further details, see:

    http://www.gtk.org/setuid.html

Refusing to initialize GTK+.
/etc/gdm/Xsession: Beginning session setup...
/etc/profile: 20: [[: not found
SESSION_MANAGER=local/Azexian-Bot:/tmp/.ICE-unix/5918
Checking for Xgl: not present. 
Detected PCI ID for VGA: 03:00.0 0300: 10de:0326 (rev a1) (prog-if 00 [VGA])
Checking for texture_from_pixmap: present. 
Checking for non power of two support: present. 
Checking for Composite extension: present. 
Comparing resolution (1024x768) to maximum 3D texture size (4096): Passed.
Checking for nVidia: present. 

** (x-session-manager:5918): WARNING **: Host name lookup failure on localhost.
Checking for FBConfig: present. 
Checking for Xgl: not present. 
Starting gtk-window-decorator
Initializing gnome-mount extension
** Message: Starting remote desktop server
Unable to open desktop file file:///home/admin-jay/Desktop/gedit.desktop for panel launcher: No such file or directory
Unable to open desktop file file:///home/admin-jay/Desktop/amsn.desktop for panel launcher: No such file or directory
/usr/bin/compiz.real (video) - Warn: No 8 bit GLX pixmap format, disabling YV12 image format
** Message: Failed to load /usr/share/pixmaps/deluge-torrent.xpm into memory: Failed to open file '/usr/share/pixmaps/deluge-torrent.xpm': No such file or directory

** (x-session-manager:5918): WARNING **: Couldn't connect to PowerManager Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

** (x-session-manager:5918): WARNING **: Couldn't connect to PowerManager Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.