.xsession-errors I need some help

[turzin]

Hi, I got this file (.xsession-errors) in my /home/user, and wanted to know if I can fixed some of the errors....(highlighted in colors here)  (for the update-notifier part in marron, I was just wandering if it's normal?)

/etc/X11/gdm/Xsession: Beginning session setup...
/etc/X11/gdm/Xsession: Setup done, will execute: /usr/bin/ssh-agent -- /etc/X11/xdm/Xsession LXDE
localhost being added to access control list
s2u: symbol lookup error: /usr/lib/libnotify.so.1: undefined symbol: gtk_status_icon_get_geometry
cp: impossible d'évaluer « /usr/share/lxde/polkit/polkit-gnome-authentication-agent-1.desktop »: Aucun fichier ou dossier de ce type
There is already an instance of LXPanel.  Now to exit
Obt-Message: Xinerama extension is not present on the server
xscreensaver: 01:48:44: already running on display :0 (window 0xe00001)
 from process 1910 (visiteur@localhost.localdomain).
Warning: bad ps syntax, perhaps a bogus '-'? See http://procps.sf.net/faq.html
waiting to connect repositories
Openbox-Message: Impossible de trouver un fichier de menus valide  « /usr/share/lxde/openbox/menu.xml »
GNOME_KEYRING_CONTROL=/tmp/keyring-AKgkLJ
SSH_AUTH_SOCK=/tmp/keyring-AKgkLJ/ssh
GNOME_KEYRING_CONTROL=/tmp/keyring-AKgkLJ
SSH_AUTH_SOCK=/tmp/keyring-AKgkLJ/ssh
GNOME_KEYRING_CONTROL=/tmp/keyring-AKgkLJ
SSH_AUTH_SOCK=/tmp/keyring-AKgkLJ/ssh
GPG_AGENT_INFO=/tmp/keyring-AKgkLJ/gpg:0:1
GNOME_KEYRING_CONTROL=/tmp/keyring-AKgkLJ
SSH_AUTH_SOCK=/tmp/keyring-AKgkLJ/ssh
GPG_AGENT_INFO=/tmp/keyring-AKgkLJ/gpg:0:1
** (pcmanfm:1907): DEBUG: line = /home/visiteur
** (pcmanfm:1907): DEBUG: line = 0
** (pcmanfm:1907): DEBUG: line = --desktop
** (pcmanfm:1907): DEBUG: line = --show-pref
** (pcmanfm:1907): DEBUG: line = 0
/home/visiteur/.update-notifier-launcher/NUT directory found

Removed this instance of update-notifier from the log (pid 1935)

The following notifier processes will be killed and removed from the log:
   1936 /usr/bin/update-notifier-launcher: line 29: kill: (1936) - Aucun processus de ce type

   1984 /usr/bin/update-notifier-launcher: line 29: kill: (1984) - Aucun processus de ce type

/usr/bin/update-notifier-launcher: line 35: kill: (1983) - Aucun processus de ce type

All pre-existing notifier processes have been killed and removed from the log

This instance of update-notifier-launcher has been logged (pid 1935)
Starting update-notifier..
pop-ups=false
/home/visiteur/.update-notifier-launcher/PID directory found

pid 1986 has been logged for this instance of update-notifier
pop-ups=false
apt-force-yes=false
48
48
Next update time is vendredi févr. 10 at 1:49
update refresh status=true
Active repo: ftp.heanet.ie
PING ftp.heanet.ie (193.1.193.64) 56(84) bytes of data.
64 bytes from ftp.heanet.ie (193.1.193.64): icmp_req=1 ttl=57 time=108 ms

thanks!

[AS]

Hi, I got this file (.xsession-errors) in my /home/user, and wanted to know if I can fixed some of the errors....(highlighted in colors here)  (for the update-notifier part in marron, I was just wandering if it's normal?)

/etc/X11/gdm/Xsession: Beginning session setup...
/etc/X11/gdm/Xsession: Setup done, will execute: /usr/bin/ssh-agent -- /etc/X11/xdm/Xsession LXDE
localhost being added to access control list
s2u: symbol lookup error: /usr/lib/libnotify.so.1: undefined symbol: gtk_status_icon_get_geometry
cp: impossible d'évaluer « /usr/share/lxde/polkit/polkit-gnome-authentication-agent-1.desktop »: Aucun fichier ou
dossier de ce type

Because s2u has been fixed few days ago ... I think your system is not up to date ... try to change repo mirror ...

AS

[TerryN]

Hi, I got this file (.xsession-errors) in my /home/user, and wanted to know if I can fixed some of the errors....(highlighted in colors here)  (for the update-notifier part in marron, I was just wandering if it's normal?)

The update-notifier messages are normal.  In fact, the time to worry is when you DON'T see them as that means that UN has killed an innocent process during start-up 
(Very rare, but does sometimes happen)

Terry.

[turzin]

Thanks guys! 

Because s2u has been fixed few days ago ... I think your system is not up to date ... try to change repo mirror ...

No, my system is not up to date....  I was waiting because of the openbox issues...

[djohnston]

No, my system is not up to date....  I was waiting because of the openbox issues...

Honestly, the Openbox "issue" was a minor one. It's been corrected.