skazochnij@warsong ~ $ gnome-session
gnome-session[8348]: libupower-glib-WARNING: Couldn't connect to system bus: 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.
gnome-session[8348]: WARNING: Could not connect to ConsoleKit: 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.
gnome-session[8348]: WARNING: Could not connect to ConsoleKit: 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.
GNOME_KEYRING_CONTROL=/tmp/keyring-KYkcSt
GPG_AGENT_INFO=/tmp/keyring-KYkcSt/gpg:0:1
GNOME_KEYRING_PID=8362
GNOME_KEYRING_CONTROL=/tmp/keyring-KYkcSt
GPG_AGENT_INFO=/tmp/keyring-KYkcSt/gpg:0:1
SSH_AUTH_SOCK=/tmp/keyring-KYkcSt/ssh
GNOME_KEYRING_CONTROL=/tmp/keyring-KYkcSt
GPG_AGENT_INFO=/tmp/keyring-KYkcSt/gpg:0:1
SSH_AUTH_SOCK=/tmp/keyring-KYkcSt/ssh
GNOME_KEYRING_CONTROL=/tmp/keyring-KYkcSt
GPG_AGENT_INFO=/tmp/keyring-KYkcSt/gpg:0:1
SSH_AUTH_SOCK=/tmp/keyring-KYkcSt/ssh

(gnome-settings-daemon:8359): libupower-glib-WARNING **: Couldn't connect to system bus: 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.
gnome-session[8348]: WARNING: Application 'gnome-settings-daemon.desktop' killed by signal