Session qui se ferme toute seule

loubrix · Le 19/01/2011, à 22:23

Bonsoir,
petit problème et je vois pas comment identifier le fautif; assez souvent (environ une fois par semaine), ma session se ferme toute seule; ça se produit toujours quand je ne suis pas devant l'ordi, je reviens et je me retrouve devant l'écran de Gdm...
exemple: aujourd'hui, j'étais AFK de 18h30 à 20h00, et quand je suis revenu, l'écran Gdm attendait le mot de passe. seul Chromium (le browser, pas le jeu) était ouvert à mon départ, et RSSowl était iconifié, en plus de Mail-notification.
voici xsession-errors.old:

(exe:2199): Gdk-WARNING **: XID collision, trouble ahead

(exe:2199): Gdk-WARNING **: XID collision, trouble ahead

(exe:2199): Gdk-WARNING **: XID collision, trouble ahead

(exe:2199): Gdk-WARNING **: XID collision, trouble ahead

(exe:2199): Gdk-WARNING **: XID collision, trouble ahead

(exe:2199): Gdk-WARNING **: XID collision, trouble ahead

(exe:2199): Gdk-WARNING **: XID collision, trouble ahead

(exe:2199): Gdk-WARNING **: XID collision, trouble ahead

(exe:2199): Gdk-WARNING **: XID collision, trouble ahead

(exe:2199): Gdk-WARNING **: XID collision, trouble ahead

(exe:2199): Gdk-WARNING **: XID collision, trouble ahead

(exe:2199): Gdk-WARNING **: XID collision, trouble ahead

(exe:2199): Gdk-WARNING **: XID collision, trouble ahead

(exe:2199): Gdk-WARNING **: XID collision, trouble ahead

(exe:2199): Gdk-WARNING **: XID collision, trouble ahead

(exe:2199): Gdk-WARNING **: XID collision, trouble ahead

(exe:2199): Gdk-WARNING **: XID collision, trouble ahead

(exe:2199): Gdk-WARNING **: XID collision, trouble ahead

(exe:2199): Gdk-WARNING **: XID collision, trouble ahead

(exe:2199): Gdk-WARNING **: XID collision, trouble ahead

(exe:2199): Gdk-WARNING **: XID collision, trouble ahead

(exe:2199): Gdk-WARNING **: XID collision, trouble ahead

(exe:2199): Gdk-WARNING **: XID collision, trouble ahead

(exe:2199): Gdk-WARNING **: XID collision, trouble ahead

(exe:2199): Gdk-WARNING **: XID collision, trouble ahead

(exe:2199): Gdk-WARNING **: XID collision, trouble ahead

(exe:2199): Gdk-WARNING **: XID collision, trouble ahead

(exe:2199): Gdk-WARNING **: XID collision, trouble ahead

(exe:2199): Gdk-WARNING **: XID collision, trouble ahead

(exe:2199): Gdk-WARNING **: XID collision, trouble ahead

(exe:2199): Gdk-WARNING **: XID collision, trouble ahead

(exe:2199): Gdk-WARNING **: XID collision, trouble ahead

(exe:2199): Gdk-WARNING **: XID collision, trouble ahead

(exe:2199): Gdk-WARNING **: XID collision, trouble ahead

(exe:2199): Gdk-WARNING **: XID collision, trouble ahead

(exe:2199): Gdk-WARNING **: XID collision, trouble ahead

(exe:2199): Gdk-WARNING **: XID collision, trouble ahead
XIO:  fatal IO error 104 (Connection reset by peer) on X server ":0.0"
      after 141029 requests (141028 known processed) with 0 events remaining.
[2109:2109:28285500740:ERROR:chrome/browser/browser_main_gtk.cc(36)] X IO Error detected
[2199:2199:28285582954:ERROR:app/x11_util.cc(65)] X IO Error detected
[8093:8093:28285583063:ERROR:app/x11_util.cc(65)] X IO Error detected
gkrellm: Fatal IO error 104 (Connexion ré-initialisée par le correspondant) on X server :0.0.
gnome-settings-daemon: Fatal IO error 11 (Ressource temporairement non disponible) on X server :0.0.
applet.py: Fatal IO error 11 (Ressource temporairement non disponible) on X server :0.0.
polkit-gnome-authentication-agent-1: Fatal IO error 11 (Ressource temporairement non disponible) on X server :0.0.
nautilus: Fatal IO error 11 (Ressource temporairement non disponible) on X server :0.0.
gnome-panel: Fatal IO error 11 (Ressource temporairement non disponible) on X server :0.0.
mail-notification: Fatal IO error 11 (Ressource temporairement non disponible) on X server :0.0.
gnome-screensaver: Fatal IO error 11 (Ressource temporairement non disponible) on X server :0.0.
update-notifier: Fatal IO error 11 (Ressource temporairement non disponible) on X server :0.0.
RSSOwl: Fatal IO error 11 (Ressource temporairement non disponible) on X server :0.0.
fslint-gui: Fatal IO error 11 (Ressource temporairement non disponible) on X server :0.0.
gnome-power-manager: Fatal IO error 11 (Ressource temporairement non disponible) on X server :0.0.
geeqie-standard: Fatal IO error 11 (Ressource temporairement non disponible) on X server :0.0.
gnome-session: Fatal IO error 11 (Ressource temporairement non disponible) on X server :0.0.
nm-applet: Fatal IO error 11 (Ressource temporairement non disponible) on X server :0.0.
Avertissement du gestionnaire de fenêtres : Erreur fatale d'E/S 11 (Ressource temporairement non disponible) sur le visuel « :0.0 ».
gdu-notification-daemon: Fatal IO error 11 (Ressource temporairement non disponible) on X server :0.0.
bluetooth-applet: Fatal IO error 11 (Ressource temporairement non disponible) on X server :0.0.
evolution-alarm-notify: Fatal IO error 11 (Ressource temporairement non disponible) on X server :0.0.

(gnome-panel:1887): GLib-GObject-CRITICAL **: g_object_run_dispose: assertion `G_IS_OBJECT (object)' failed

(j'ai enlevé l'activité non pertinente de la journée)
le xession-errors en cours depuis que je suis rentré:

/etc/gdm/Xsession: Beginning session setup...
Setting IM through im-switch for locale=fr_FR.
Start IM through /etc/X11/xinit/xinput.d/all_ALL linked to /etc/X11/xinit/xinput.d/default.
GNOME_KEYRING_CONTROL=/tmp/keyring-NNu88z
GNOME_KEYRING_CONTROL=/tmp/keyring-NNu88z
SSH_AUTH_SOCK=/tmp/keyring-NNu88z/ssh
GNOME_KEYRING_CONTROL=/tmp/keyring-NNu88z
SSH_AUTH_SOCK=/tmp/keyring-NNu88z/ssh

(polkit-gnome-authentication-agent-1:18301): GLib-GObject-WARNING **: cannot register existing type `_PolkitError'

(polkit-gnome-authentication-agent-1:18301): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
** Message: adding killswitch idx 0 state KILLSWITCH_STATE_UNBLOCKED
** Message: killswitch 0 is KILLSWITCH_STATE_UNBLOCKED
** Message: killswitches state KILLSWITCH_STATE_UNBLOCKED
** (bluetooth-applet:18298): DEBUG: Unhandled UUID 00005001-0000-1000-8000-0002ee000001 (0x5001)
** (bluetooth-applet:18298): DEBUG: Unhandled UUID 00005002-0000-1000-8000-0002ee000001 (0x5002)
** (bluetooth-applet:18298): DEBUG: Unhandled UUID 00005003-0000-1000-8000-0002ee000001 (0x5003)
** (bluetooth-applet:18298): DEBUG: Unhandled UUID 00005557-0000-1000-8000-0002ee000001 (0x5557)
** (bluetooth-applet:18298): DEBUG: Unhandled UUID 00005601-0000-1000-8000-0002ee000001 (0x5601)
** Message: killswitch 0 is KILLSWITCH_STATE_UNBLOCKED
** Message: killswitches state KILLSWITCH_STATE_UNBLOCKED
** Message: applet now removed from the notification area
Initializing nautilus-gdu extension
** Message: applet now embedded in the notification area

** (gnome-settings-daemon:18274): WARNING **: Got less number of items in credentials hash table than expected!
** (update-notifier:18567): DEBUG: aptdaemon on bus: 0
** (update-notifier:18567): DEBUG: Skipping reboot required

(exe:18697): Gdk-WARNING **: XID collision, trouble ahead

(exe:18697): Gdk-WARNING **: XID collision, trouble ahead

(exe:18697): Gdk-WARNING **: XID collision, trouble ahead

(exe:18697): Gdk-WARNING **: XID collision, trouble ahead

(exe:18697): Gdk-WARNING **: XID collision, trouble ahead

(exe:18697): Gdk-WARNING **: XID collision, trouble ahead

(exe:18697): Gdk-WARNING **: XID collision, trouble ahead

(exe:18697): Gdk-WARNING **: XID collision, trouble ahead

(exe:18697): Gdk-WARNING **: XID collision, trouble ahead

hélas, je ne trouve aucun programme tournant avec le PID 18697...
le /var/log/messages contient quelques lignes qui correspondent niveau horaires:

Jan 19 18:43:56 phobos kernel: [28288.020154] cfg80211: Calling CRDA to update world regulatory domain
Jan 19 18:43:58 phobos kernel: [28290.043829] cfg80211: World regulatory domain updated:
Jan 19 18:43:58 phobos kernel: [28290.043836]     (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Jan 19 18:43:58 phobos kernel: [28290.043843]     (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Jan 19 18:43:58 phobos kernel: [28290.043849]     (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Jan 19 18:43:58 phobos kernel: [28290.043855]     (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Jan 19 18:43:58 phobos kernel: [28290.043860]     (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Jan 19 18:43:58 phobos kernel: [28290.043866]     (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Jan 19 20:30:01 phobos pulseaudio[18293]: pid.c: Stale PID file, overwriting.
Jan 19 20:30:06 phobos nautilus: [N-A] Nautilus-Actions Menu Extender 2.30.2 initializing...
Jan 19 20:30:06 phobos nautilus: [N-A] Nautilus-Actions Tracker 2.30.2 initializing...
Jan 19 20:33:20 phobos kernel: [34852.531169] lo: Disabled Privacy Extensions

le daemon.log:

Jan 19 18:43:56 phobos NetworkManager[1048]: <info> (wlan0): device state change: 8 -> 3 (reason 38)
Jan 19 18:43:56 phobos NetworkManager[1048]: <info> (wlan0): deactivating device (reason: 38).
Jan 19 18:43:56 phobos NetworkManager[1048]: <info> (wlan0): canceled DHCP transaction, DHCP client pid 1981
Jan 19 18:43:56 phobos avahi-daemon[1012]: Withdrawing address record for 192.168.1.89 on wlan0.
Jan 19 18:43:56 phobos wpa_supplicant[1055]: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Jan 19 18:43:56 phobos avahi-daemon[1012]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.89.
Jan 19 18:43:56 phobos avahi-daemon[1012]: Interface wlan0.IPv4 no longer relevant for mDNS.
Jan 19 18:43:57 phobos NetworkManager[1048]: <info> Policy set 'Auto eth0' (eth0) as default for IPv4 routing and DNS.
Jan 19 18:43:57 phobos NetworkManager[1048]: <info> Policy set 'Auto eth0' (eth0) as default for IPv4 routing and DNS.
Jan 19 18:43:57 phobos NetworkManager[1048]: <error> [1295459037.580985] [nm-manager.c:1317] user_proxy_init(): could not init user settings proxy: (3) Could not get owner of name 'org.freedesktop.NetworkManagerUserSettings': no such name
Jan 19 18:43:58 phobos gdm-simple-slave[18093]: WARNING: Unable to load file '/etc/gdm/custom.conf': Aucun fichier ou dossier de ce type
Jan 19 18:43:59 phobos acpid: client 1178[0:0] has disconnected
Jan 19 18:43:59 phobos acpid: client connected from 18099[0:0]
Jan 19 18:43:59 phobos acpid: 1 client rule loaded
Jan 19 18:44:01 phobos NetworkManager[1048]: <error> [1295459041.585985] [nm-manager.c:1317] user_proxy_init(): could not init user settings proxy: (3) Could not get owner of name 'org.freedesktop.NetworkManagerUserSettings': no such name
Jan 19 18:44:03 phobos gdm-session-worker[18164]: WARNING: Unable to load file '/etc/gdm/custom.conf': Aucun fichier ou dossier de ce type
Jan 19 18:44:04 phobos rtkit-daemon[1693]: Successfully made thread 18171 of process 18171 (n/a) owned by '113' high priority at nice level -11.
Jan 19 18:44:04 phobos rtkit-daemon[1693]: Supervising 1 threads of 1 processes of 1 users.
Jan 19 18:44:04 phobos gdm-simple-greeter[18161]: Gtk-WARNING: /build/buildd/gtk+2.0-2.22.0/gtk/gtkwidget.c:5684: widget not within a GtkWindow
Jan 19 18:44:04 phobos rtkit-daemon[1693]: Successfully made thread 18174 of process 18171 (n/a) owned by '113' RT at priority 5.
Jan 19 18:44:04 phobos rtkit-daemon[1693]: Supervising 2 threads of 1 processes of 1 users.
Jan 19 18:44:04 phobos rtkit-daemon[1693]: Successfully made thread 18176 of process 18171 (n/a) owned by '113' RT at priority 5.
Jan 19 18:44:04 phobos rtkit-daemon[1693]: Supervising 3 threads of 1 processes of 1 users.
Jan 19 20:09:49 phobos dhclient: DHCPREQUEST of 192.168.1.35 on eth0 to 192.168.1.1 port 67
Jan 19 20:09:49 phobos dhclient: DHCPACK of 192.168.1.35 from 192.168.1.1
Jan 19 20:09:49 phobos NetworkManager[1048]: <info> (eth0): DHCPv4 state changed bound -> renew
Jan 19 20:09:49 phobos NetworkManager[1048]: <info>   address 192.168.1.35
Jan 19 20:09:49 phobos NetworkManager[1048]: <info>   prefix 24 (255.255.255.0)
Jan 19 20:09:49 phobos NetworkManager[1048]: <info>   gateway 192.168.1.1
Jan 19 20:09:49 phobos NetworkManager[1048]: <info>   hostname 'phobos'
Jan 19 20:09:49 phobos NetworkManager[1048]: <info>   nameserver '192.168.1.1'
Jan 19 20:09:49 phobos dhclient: bound to 192.168.1.35 -- renewal in 35185 seconds.
Jan 19 20:29:53 phobos gdm-session-worker[18164]: GLib-GObject-CRITICAL: g_value_get_boolean: assertion `G_VALUE_HOLDS_BOOLEAN (value)' failed
Jan 19 20:29:59 phobos NetworkManager[1048]: <error> [1295465399.468661] [nm-manager.c:1317] user_proxy_init(): could not init user settings proxy: (3) Could not get owner of name 'org.freedesktop.NetworkManagerUserSettings': no such name
Jan 19 20:29:59 phobos NetworkManager[1048]: <error> [1295465399.537209] [nm-manager.c:1317] user_proxy_init(): could not init user settings proxy: (3) Could not get owner of name 'org.freedesktop.NetworkManagerUserSettings': no such name
Jan 19 20:30:01 phobos rtkit-daemon[1693]: Successfully made thread 18293 of process 18293 (n/a) owned by '1000' high priority at nice level -11.
Jan 19 20:30:01 phobos rtkit-daemon[1693]: Supervising 4 threads of 2 processes of 2 users.
Jan 19 20:30:01 phobos rtkit-daemon[1693]: Successfully made thread 18307 of process 18293 (n/a) owned by '1000' RT at priority 5.
Jan 19 20:30:01 phobos rtkit-daemon[1693]: Supervising 5 threads of 2 processes of 2 users.
Jan 19 20:30:01 phobos rtkit-daemon[1693]: Successfully made thread 18308 of process 18293 (n/a) owned by '1000' RT at priority 5.
Jan 19 20:30:01 phobos rtkit-daemon[1693]: Supervising 6 threads of 2 processes of 2 users.
Jan 19 20:30:02 phobos rtkit-daemon[1693]: Successfully made thread 18321 of process 18321 (n/a) owned by '1000' high priority at nice level -11.
Jan 19 20:30:02 phobos rtkit-daemon[1693]: Supervising 7 threads of 3 processes of 2 users.
Jan 19 20:30:03 phobos NetworkManager[1048]: <info> Activation (wlan0) starting connection 'Auto NEUF_BFE4'
Jan 19 20:30:03 phobos NetworkManager[1048]: <info> (wlan0): device state change: 3 -> 4 (reason 0)
Jan 19 20:30:03 phobos NetworkManager[1048]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Jan 19 20:30:03 phobos NetworkManager[1048]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Jan 19 20:30:03 phobos NetworkManager[1048]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Jan 19 20:30:03 phobos NetworkManager[1048]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Jan 19 20:30:03 phobos NetworkManager[1048]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Jan 19 20:30:03 phobos NetworkManager[1048]: <info> (wlan0): device state change: 4 -> 5 (reason 0)
Jan 19 20:30:03 phobos NetworkManager[1048]: <info> Activation (wlan0/wireless): access point 'Auto NEUF_BFE4' has security, but secrets are required.
Jan 19 20:30:03 phobos NetworkManager[1048]: <info> (wlan0): device state change: 5 -> 6 (reason 0)
Jan 19 20:30:03 phobos NetworkManager[1048]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Jan 19 20:30:03 phobos NetworkManager[1048]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Jan 19 20:30:03 phobos NetworkManager[1048]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Jan 19 20:30:03 phobos NetworkManager[1048]: <info> (wlan0): device state change: 6 -> 4 (reason 0)
Jan 19 20:30:03 phobos NetworkManager[1048]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Jan 19 20:30:03 phobos NetworkManager[1048]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Jan 19 20:30:03 phobos NetworkManager[1048]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Jan 19 20:30:03 phobos NetworkManager[1048]: <info> (wlan0): device state change: 4 -> 5 (reason 0)
Jan 19 20:30:03 phobos NetworkManager[1048]: <info> Activation (wlan0/wireless): connection 'Auto NEUF_BFE4' has security, and secrets exist.  No new secrets needed.
Jan 19 20:30:03 phobos NetworkManager[1048]: <info> Config: added 'ssid' value 'NEUF_BFE4'
Jan 19 20:30:03 phobos NetworkManager[1048]: <info> Config: added 'scan_ssid' value '1'
Jan 19 20:30:03 phobos NetworkManager[1048]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
Jan 19 20:30:03 phobos NetworkManager[1048]: <info> Config: added 'psk' value '<omitted>'
Jan 19 20:30:03 phobos NetworkManager[1048]: nm_setting_802_1x_get_pkcs11_engine_path: assertion `NM_IS_SETTING_802_1X (setting)' failed
Jan 19 20:30:03 phobos NetworkManager[1048]: nm_setting_802_1x_get_pkcs11_module_path: assertion `NM_IS_SETTING_802_1X (setting)' failed
Jan 19 20:30:03 phobos NetworkManager[1048]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Jan 19 20:30:03 phobos NetworkManager[1048]: <info> Config: set interface ap_scan to 1
Jan 19 20:30:04 phobos NetworkManager[1048]: <info> (wlan0): supplicant connection state:  disconnected -> scanning
Jan 19 20:30:05 phobos wpa_supplicant[1055]: Trying to associate with e0:a1:d7:01:bf:e8 (SSID='NEUF_BFE4' freq=2462 MHz)
Jan 19 20:30:05 phobos NetworkManager[1048]: <info> (wlan0): supplicant connection state:  scanning -> associating
Jan 19 20:30:05 phobos NetworkManager[1048]: <info> (wlan0): supplicant connection state:  associating -> associated
Jan 19 20:30:05 phobos wpa_supplicant[1055]: Associated with e0:a1:d7:01:bf:e8
Jan 19 20:30:05 phobos NetworkManager[1048]: <info> (wlan0): supplicant connection state:  associated -> 4-way handshake
Jan 19 20:30:05 phobos NetworkManager[1048]: <info> (wlan0): supplicant connection state:  4-way handshake -> group handshake
Jan 19 20:30:05 phobos wpa_supplicant[1055]: WPA: Key negotiation completed with e0:a1:d7:01:bf:e8 [PTK=CCMP GTK=TKIP]
Jan 19 20:30:05 phobos wpa_supplicant[1055]: CTRL-EVENT-CONNECTED - Connection to e0:a1:d7:01:bf:e8 completed (reauth) [id=0 id_str=]
Jan 19 20:30:05 phobos NetworkManager[1048]: <info> (wlan0): supplicant connection state:  group handshake -> completed
Jan 19 20:30:05 phobos NetworkManager[1048]: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'NEUF_BFE4'.
Jan 19 20:30:05 phobos NetworkManager[1048]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
Jan 19 20:30:05 phobos NetworkManager[1048]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
Jan 19 20:30:05 phobos NetworkManager[1048]: <info> (wlan0): device state change: 5 -> 7 (reason 0)
Jan 19 20:30:05 phobos NetworkManager[1048]: <info> Activation (wlan0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Jan 19 20:30:05 phobos NetworkManager[1048]: <info> dhclient started with pid 18342
Jan 19 20:30:05 phobos NetworkManager[1048]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
Jan 19 20:30:05 phobos dhclient: Internet Systems Consortium DHCP Client V3.1.3
Jan 19 20:30:05 phobos dhclient: Copyright 2004-2009 Internet Systems Consortium.
Jan 19 20:30:05 phobos dhclient: All rights reserved.
Jan 19 20:30:05 phobos dhclient: For info, please visit https://www.isc.org/software/dhcp/
Jan 19 20:30:05 phobos dhclient: 
Jan 19 20:30:05 phobos NetworkManager[1048]: <info> (wlan0): DHCPv4 state changed nbi -> preinit
Jan 19 20:30:05 phobos dhclient: Listening on LPF/wlan0/00:15:af:41:fe:e1
Jan 19 20:30:05 phobos dhclient: Sending on   LPF/wlan0/00:15:af:41:fe:e1
Jan 19 20:30:05 phobos dhclient: Sending on   Socket/fallback
Jan 19 20:30:05 phobos dhclient: DHCPREQUEST of 192.168.1.89 on wlan0 to 255.255.255.255 port 67
Jan 19 20:30:05 phobos dhclient: DHCPACK of 192.168.1.89 from 192.168.1.1
Jan 19 20:30:05 phobos dhclient: bound to 192.168.1.89 -- renewal in 40717 seconds.
Jan 19 20:30:05 phobos NetworkManager[1048]: <info> (wlan0): DHCPv4 state changed preinit -> reboot
Jan 19 20:30:05 phobos NetworkManager[1048]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) scheduled...
Jan 19 20:30:05 phobos NetworkManager[1048]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) started...
Jan 19 20:30:05 phobos NetworkManager[1048]: <info>   address 192.168.1.89
Jan 19 20:30:05 phobos NetworkManager[1048]: <info>   prefix 24 (255.255.255.0)
Jan 19 20:30:05 phobos NetworkManager[1048]: <info>   gateway 192.168.1.1
Jan 19 20:30:05 phobos NetworkManager[1048]: <info>   hostname 'phobos'
Jan 19 20:30:05 phobos NetworkManager[1048]: <info>   nameserver '192.168.1.1'
Jan 19 20:30:05 phobos NetworkManager[1048]: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) scheduled...
Jan 19 20:30:05 phobos NetworkManager[1048]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) complete.
Jan 19 20:30:05 phobos NetworkManager[1048]: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) started...
Jan 19 20:30:05 phobos avahi-daemon[1012]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.89.
Jan 19 20:30:05 phobos avahi-daemon[1012]: New relevant interface wlan0.IPv4 for mDNS.
Jan 19 20:30:05 phobos avahi-daemon[1012]: Registering new address record for 192.168.1.89 on wlan0.IPv4.
Jan 19 20:30:06 phobos NetworkManager[1048]: <info> Policy set 'Auto eth0' (eth0) as default for IPv4 routing and DNS.
Jan 19 20:30:06 phobos NetworkManager[1048]: <info> (wlan0): device state change: 7 -> 8 (reason 0)
Jan 19 20:30:06 phobos NetworkManager[1048]: <info> Activation (wlan0) successful, device activated.
Jan 19 20:30:06 phobos NetworkManager[1048]: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) complete.
Jan 19 20:30:07 phobos ntpdate[18422]: step time server 91.189.94.4 offset -0.887301 sec

(la déconnexion à eu lieu à 18h43 semble t'il)
je mets aussi le syslog, mais je vois rien de plus que ce qu'on sait déjà:

Jan 19 18:43:56 phobos NetworkManager[1048]: <info> (wlan0): device state change: 8 -> 3 (reason 38)
Jan 19 18:43:56 phobos NetworkManager[1048]: <info> (wlan0): deactivating device (reason: 38).
Jan 19 18:43:56 phobos NetworkManager[1048]: <info> (wlan0): canceled DHCP transaction, DHCP client pid 1981
Jan 19 18:43:56 phobos avahi-daemon[1012]: Withdrawing address record for 192.168.1.89 on wlan0.
Jan 19 18:43:56 phobos wpa_supplicant[1055]: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Jan 19 18:43:56 phobos kernel: [28287.970247] wlan0: deauthenticating from e0:a1:d7:01:bf:e8 by local choice (reason=3)
Jan 19 18:43:56 phobos kernel: [28288.020136] cfg80211: All devices are disconnected, going to restore regulatory settings
Jan 19 18:43:56 phobos kernel: [28288.020147] cfg80211: Restoring regulatory settings
Jan 19 18:43:56 phobos kernel: [28288.020154] cfg80211: Calling CRDA to update world regulatory domain
Jan 19 18:43:56 phobos avahi-daemon[1012]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.89.
Jan 19 18:43:56 phobos avahi-daemon[1012]: Interface wlan0.IPv4 no longer relevant for mDNS.
Jan 19 18:43:57 phobos NetworkManager[1048]: <info> Policy set 'Auto eth0' (eth0) as default for IPv4 routing and DNS.
Jan 19 18:43:57 phobos NetworkManager[1048]: <info> Policy set 'Auto eth0' (eth0) as default for IPv4 routing and DNS.
Jan 19 18:43:57 phobos NetworkManager[1048]: <error> [1295459037.580985] [nm-manager.c:1317] user_proxy_init(): could not init user settings proxy: (3) Could not get owner of name 'org.freedesktop.NetworkManagerUserSettings': no such name
Jan 19 18:43:58 phobos kernel: [28290.043829] cfg80211: World regulatory domain updated:
Jan 19 18:43:58 phobos kernel: [28290.043836]     (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Jan 19 18:43:58 phobos kernel: [28290.043843]     (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Jan 19 18:43:58 phobos kernel: [28290.043849]     (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Jan 19 18:43:58 phobos kernel: [28290.043855]     (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Jan 19 18:43:58 phobos kernel: [28290.043860]     (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Jan 19 18:43:58 phobos kernel: [28290.043866]     (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Jan 19 18:43:58 phobos gdm-simple-slave[18093]: WARNING: Unable to load file '/etc/gdm/custom.conf': Aucun fichier ou dossier de ce type
Jan 19 18:43:59 phobos acpid: client 1178[0:0] has disconnected
Jan 19 18:43:59 phobos acpid: client connected from 18099[0:0]
Jan 19 18:43:59 phobos acpid: 1 client rule loaded
Jan 19 18:44:00 phobos postfix/master[1471]: reload -- version 2.7.1, configuration /etc/postfix
Jan 19 18:44:01 phobos NetworkManager[1048]: <error> [1295459041.585985] [nm-manager.c:1317] user_proxy_init(): could not init user settings proxy: (3) Could not get owner of name 'org.freedesktop.NetworkManagerUserSettings': no such name
Jan 19 18:44:03 phobos gdm-session-worker[18164]: WARNING: Unable to load file '/etc/gdm/custom.conf': Aucun fichier ou dossier de ce type
Jan 19 18:44:04 phobos rtkit-daemon[1693]: Successfully made thread 18171 of process 18171 (n/a) owned by '113' high priority at nice level -11.
Jan 19 18:44:04 phobos rtkit-daemon[1693]: Supervising 1 threads of 1 processes of 1 users.
Jan 19 18:44:04 phobos gdm-simple-greeter[18161]: Gtk-WARNING: /build/buildd/gtk+2.0-2.22.0/gtk/gtkwidget.c:5684: widget not within a GtkWindow
Jan 19 18:44:04 phobos rtkit-daemon[1693]: Successfully made thread 18174 of process 18171 (n/a) owned by '113' RT at priority 5.
Jan 19 18:44:04 phobos rtkit-daemon[1693]: Supervising 2 threads of 1 processes of 1 users.
Jan 19 18:44:04 phobos rtkit-daemon[1693]: Successfully made thread 18176 of process 18171 (n/a) owned by '113' RT at priority 5.
Jan 19 18:44:04 phobos rtkit-daemon[1693]: Supervising 3 threads of 1 processes of 1 users.
Jan 19 19:17:01 phobos CRON[18192]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Jan 19 20:09:49 phobos dhclient: DHCPREQUEST of 192.168.1.35 on eth0 to 192.168.1.1 port 67
Jan 19 20:09:49 phobos dhclient: DHCPACK of 192.168.1.35 from 192.168.1.1
Jan 19 20:09:49 phobos NetworkManager[1048]: <info> (eth0): DHCPv4 state changed bound -> renew
Jan 19 20:09:49 phobos NetworkManager[1048]: <info>   address 192.168.1.35
Jan 19 20:09:49 phobos NetworkManager[1048]: <info>   prefix 24 (255.255.255.0)
Jan 19 20:09:49 phobos NetworkManager[1048]: <info>   gateway 192.168.1.1
Jan 19 20:09:49 phobos NetworkManager[1048]: <info>   hostname 'phobos'
Jan 19 20:09:49 phobos NetworkManager[1048]: <info>   nameserver '192.168.1.1'
Jan 19 20:09:49 phobos dhclient: bound to 192.168.1.35 -- renewal in 35185 seconds.
Jan 19 20:17:01 phobos CRON[18200]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Jan 19 20:29:53 phobos gdm-session-worker[18164]: GLib-GObject-CRITICAL: g_value_get_boolean: assertion `G_VALUE_HOLDS_BOOLEAN (value)' failed
Jan 19 20:29:59 phobos NetworkManager[1048]: <error> [1295465399.468661] [nm-manager.c:1317] user_proxy_init(): could not init user settings proxy: (3) Could not get owner of name 'org.freedesktop.NetworkManagerUserSettings': no such name
Jan 19 20:29:59 phobos NetworkManager[1048]: <error> [1295465399.537209] [nm-manager.c:1317] user_proxy_init(): could not init user settings proxy: (3) Could not get owner of name 'org.freedesktop.NetworkManagerUserSettings': no such name
Jan 19 20:30:01 phobos rtkit-daemon[1693]: Successfully made thread 18293 of process 18293 (n/a) owned by '1000' high priority at nice level -11.
Jan 19 20:30:01 phobos rtkit-daemon[1693]: Supervising 4 threads of 2 processes of 2 users.
Jan 19 20:30:01 phobos pulseaudio[18293]: pid.c: Stale PID file, overwriting.
Jan 19 20:30:01 phobos rtkit-daemon[1693]: Successfully made thread 18307 of process 18293 (n/a) owned by '1000' RT at priority 5.
Jan 19 20:30:01 phobos rtkit-daemon[1693]: Supervising 5 threads of 2 processes of 2 users.
Jan 19 20:30:01 phobos rtkit-daemon[1693]: Successfully made thread 18308 of process 18293 (n/a) owned by '1000' RT at priority 5.
Jan 19 20:30:01 phobos rtkit-daemon[1693]: Supervising 6 threads of 2 processes of 2 users.
Jan 19 20:30:02 phobos rtkit-daemon[1693]: Successfully made thread 18321 of process 18321 (n/a) owned by '1000' high priority at nice level -11.
Jan 19 20:30:02 phobos rtkit-daemon[1693]: Supervising 7 threads of 3 processes of 2 users.
Jan 19 20:30:02 phobos pulseaudio[18321]: pid.c: Daemon already running.
Jan 19 20:30:03 phobos NetworkManager[1048]: <info> Activation (wlan0) starting connection 'Auto NEUF_BFE4'
Jan 19 20:30:03 phobos NetworkManager[1048]: <info> (wlan0): device state change: 3 -> 4 (reason 0)
Jan 19 20:30:03 phobos NetworkManager[1048]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Jan 19 20:30:03 phobos NetworkManager[1048]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Jan 19 20:30:03 phobos NetworkManager[1048]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Jan 19 20:30:03 phobos NetworkManager[1048]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Jan 19 20:30:03 phobos NetworkManager[1048]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Jan 19 20:30:03 phobos NetworkManager[1048]: <info> (wlan0): device state change: 4 -> 5 (reason 0)
Jan 19 20:30:03 phobos NetworkManager[1048]: <info> Activation (wlan0/wireless): access point 'Auto NEUF_BFE4' has security, but secrets are required.
Jan 19 20:30:03 phobos NetworkManager[1048]: <info> (wlan0): device state change: 5 -> 6 (reason 0)
Jan 19 20:30:03 phobos NetworkManager[1048]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Jan 19 20:30:03 phobos NetworkManager[1048]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Jan 19 20:30:03 phobos NetworkManager[1048]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Jan 19 20:30:03 phobos NetworkManager[1048]: <info> (wlan0): device state change: 6 -> 4 (reason 0)
Jan 19 20:30:03 phobos NetworkManager[1048]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Jan 19 20:30:03 phobos NetworkManager[1048]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Jan 19 20:30:03 phobos NetworkManager[1048]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Jan 19 20:30:03 phobos NetworkManager[1048]: <info> (wlan0): device state change: 4 -> 5 (reason 0)
Jan 19 20:30:03 phobos NetworkManager[1048]: <info> Activation (wlan0/wireless): connection 'Auto NEUF_BFE4' has security, and secrets exist.  No new secrets needed.
Jan 19 20:30:03 phobos NetworkManager[1048]: <info> Config: added 'ssid' value 'NEUF_BFE4'
Jan 19 20:30:03 phobos NetworkManager[1048]: <info> Config: added 'scan_ssid' value '1'
Jan 19 20:30:03 phobos NetworkManager[1048]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
Jan 19 20:30:03 phobos NetworkManager[1048]: <info> Config: added 'psk' value '<omitted>'
Jan 19 20:30:03 phobos NetworkManager[1048]: nm_setting_802_1x_get_pkcs11_engine_path: assertion `NM_IS_SETTING_802_1X (setting)' failed
Jan 19 20:30:03 phobos NetworkManager[1048]: nm_setting_802_1x_get_pkcs11_module_path: assertion `NM_IS_SETTING_802_1X (setting)' failed
Jan 19 20:30:03 phobos NetworkManager[1048]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Jan 19 20:30:03 phobos NetworkManager[1048]: <info> Config: set interface ap_scan to 1
Jan 19 20:30:04 phobos NetworkManager[1048]: <info> (wlan0): supplicant connection state:  disconnected -> scanning
Jan 19 20:30:05 phobos wpa_supplicant[1055]: Trying to associate with e0:a1:d7:01:bf:e8 (SSID='NEUF_BFE4' freq=2462 MHz)
Jan 19 20:30:05 phobos NetworkManager[1048]: <info> (wlan0): supplicant connection state:  scanning -> associating
Jan 19 20:30:05 phobos kernel: [34656.543291] wlan0: authenticate with e0:a1:d7:01:bf:e8 (try 1)
Jan 19 20:30:05 phobos kernel: [34656.545861] wlan0: authenticated
Jan 19 20:30:05 phobos kernel: [34656.545910] wlan0: associate with e0:a1:d7:01:bf:e8 (try 1)
Jan 19 20:30:05 phobos kernel: [34656.548827] wlan0: RX AssocResp from e0:a1:d7:01:bf:e8 (capab=0x411 status=0 aid=1)
Jan 19 20:30:05 phobos kernel: [34656.548837] wlan0: associated
Jan 19 20:30:05 phobos NetworkManager[1048]: <info> (wlan0): supplicant connection state:  associating -> associated
Jan 19 20:30:05 phobos wpa_supplicant[1055]: Associated with e0:a1:d7:01:bf:e8
Jan 19 20:30:05 phobos NetworkManager[1048]: <info> (wlan0): supplicant connection state:  associated -> 4-way handshake
Jan 19 20:30:05 phobos NetworkManager[1048]: <info> (wlan0): supplicant connection state:  4-way handshake -> group handshake
Jan 19 20:30:05 phobos wpa_supplicant[1055]: WPA: Key negotiation completed with e0:a1:d7:01:bf:e8 [PTK=CCMP GTK=TKIP]
Jan 19 20:30:05 phobos wpa_supplicant[1055]: CTRL-EVENT-CONNECTED - Connection to e0:a1:d7:01:bf:e8 completed (reauth) [id=0 id_str=]
Jan 19 20:30:05 phobos NetworkManager[1048]: <info> (wlan0): supplicant connection state:  group handshake -> completed
Jan 19 20:30:05 phobos NetworkManager[1048]: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'NEUF_BFE4'.
Jan 19 20:30:05 phobos NetworkManager[1048]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
Jan 19 20:30:05 phobos NetworkManager[1048]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
Jan 19 20:30:05 phobos NetworkManager[1048]: <info> (wlan0): device state change: 5 -> 7 (reason 0)
Jan 19 20:30:05 phobos NetworkManager[1048]: <info> Activation (wlan0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Jan 19 20:30:05 phobos NetworkManager[1048]: <info> dhclient started with pid 18342
Jan 19 20:30:05 phobos NetworkManager[1048]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
Jan 19 20:30:05 phobos dhclient: Internet Systems Consortium DHCP Client V3.1.3
Jan 19 20:30:05 phobos dhclient: Copyright 2004-2009 Internet Systems Consortium.
Jan 19 20:30:05 phobos dhclient: All rights reserved.
Jan 19 20:30:05 phobos dhclient: For info, please visit https://www.isc.org/software/dhcp/
Jan 19 20:30:05 phobos dhclient: 
Jan 19 20:30:05 phobos NetworkManager[1048]: <info> (wlan0): DHCPv4 state changed nbi -> preinit
Jan 19 20:30:05 phobos dhclient: Listening on LPF/wlan0/00:15:af:41:fe:e1
Jan 19 20:30:05 phobos dhclient: Sending on   LPF/wlan0/00:15:af:41:fe:e1
Jan 19 20:30:05 phobos dhclient: Sending on   Socket/fallback
Jan 19 20:30:05 phobos dhclient: DHCPREQUEST of 192.168.1.89 on wlan0 to 255.255.255.255 port 67
Jan 19 20:30:05 phobos dhclient: DHCPACK of 192.168.1.89 from 192.168.1.1
Jan 19 20:30:05 phobos dhclient: bound to 192.168.1.89 -- renewal in 40717 seconds.
Jan 19 20:30:05 phobos NetworkManager[1048]: <info> (wlan0): DHCPv4 state changed preinit -> reboot
Jan 19 20:30:05 phobos NetworkManager[1048]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) scheduled...
Jan 19 20:30:05 phobos NetworkManager[1048]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) started...
Jan 19 20:30:05 phobos NetworkManager[1048]: <info>   address 192.168.1.89
Jan 19 20:30:05 phobos NetworkManager[1048]: <info>   prefix 24 (255.255.255.0)
Jan 19 20:30:05 phobos NetworkManager[1048]: <info>   gateway 192.168.1.1
Jan 19 20:30:05 phobos NetworkManager[1048]: <info>   hostname 'phobos'
Jan 19 20:30:05 phobos NetworkManager[1048]: <info>   nameserver '192.168.1.1'
Jan 19 20:30:05 phobos NetworkManager[1048]: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) scheduled...
Jan 19 20:30:05 phobos NetworkManager[1048]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) complete.
Jan 19 20:30:05 phobos NetworkManager[1048]: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) started...
Jan 19 20:30:05 phobos avahi-daemon[1012]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.89.
Jan 19 20:30:05 phobos avahi-daemon[1012]: New relevant interface wlan0.IPv4 for mDNS.
Jan 19 20:30:05 phobos avahi-daemon[1012]: Registering new address record for 192.168.1.89 on wlan0.IPv4.
Jan 19 20:30:06 phobos nautilus: [N-A] Nautilus-Actions Menu Extender 2.30.2 initializing...
Jan 19 20:30:06 phobos nautilus: [N-A] Nautilus-Actions Tracker 2.30.2 initializing...
Jan 19 20:30:06 phobos NetworkManager[1048]: <info> Policy set 'Auto eth0' (eth0) as default for IPv4 routing and DNS.
Jan 19 20:30:06 phobos NetworkManager[1048]: <info> (wlan0): device state change: 7 -> 8 (reason 0)
Jan 19 20:30:06 phobos NetworkManager[1048]: <info> Activation (wlan0) successful, device activated.
Jan 19 20:30:06 phobos NetworkManager[1048]: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) complete.
Jan 19 20:30:08 phobos postfix/master[1471]: reload -- version 2.7.1, configuration /etc/postfix
Jan 19 20:30:07 phobos ntpdate[18422]: step time server 91.189.94.4 offset -0.887301 sec
Jan 19 20:33:20 phobos kernel: [34852.531169] lo: Disabled Privacy Extensions

bon je comprend pas tous les logs, donc si quelqu'un peut m'aider; s'il faut autre chose, je fournirai...

d'avance merci

jacobus77 · Le 19/01/2011, à 22:49

Ce qui aurait té bien c'est d'avoir ton Xorg.0.log -> en fait celui précédent ta session courante et qui correspondrait à ta session crashée: Xorg.0.log.old ou Xorg.1.log je ne me rappelle plus.
Possible que tu ais une barette de mémoire qui soit nase ( c'est tjrs possible)
Possible que ce soit chrome qui plante
Possible que Xorg.0.log amènes des infos intéressantes

Je peux me tromper mais les infos pertinentes semblent être celles-ci: ton serveur X plante => redémarrage de session:

XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0"
after 141029 requests (141028 known processed) with 0 events remaining.
[2109:2109:28285500740:ERROR:chrome/browser/browser_main_gtk.cc(36)] X IO Error detected
[2199:2199:28285582954:ERROR:app/x11_util.cc(65)] X IO Error detected
[8093:8093:28285583063:ERROR:app/x11_util.cc(65)] X IO Error detected

loubrix · Le 20/01/2011, à 00:53

oh je suis c..., j'avais oublié le xorg.0.log (le "old" en l'occurence):

[ 28284.594] (WW) RADEON(0): divisor 0 get vblank counter failed: Cannot allocate memory
[ 28284.596] 
Backtrace:
[ 28284.676] 0: /usr/bin/X (xorg_backtrace+0x28) [0x45c448]
[ 28284.676] 1: /usr/bin/X (0x400000+0x5a71d) [0x45a71d]
[ 28284.676] 2: /lib/libpthread.so.0 (0x7f5cffc0e000+0xfb40) [0x7f5cffc1db40]
[ 28284.676] 3: /usr/bin/X (AttendClient+0x4) [0x45aae4]
[ 28284.676] 4: /usr/lib/xorg/modules/extensions/libdri2.so (DRI2SwapComplete+0x13f) [0x7f5cfcfe1c2f]
[ 28284.676] 5: /usr/lib/xorg/modules/drivers/radeon_drv.so (0x7f5cfcad4000+0xd7317) [0x7f5cfcbab317]
[ 28284.676] 6: /usr/lib/xorg/modules/extensions/libdri2.so (DRI2SwapBuffers+0x143) [0x7f5cfcfe1e13]
[ 28284.676] 7: /usr/lib/xorg/modules/extensions/libdri2.so (0x7f5cfcfdf000+0x4009) [0x7f5cfcfe3009]
[ 28284.676] 8: /usr/bin/X (0x400000+0x3f949) [0x43f949]
[ 28284.676] 9: /usr/bin/X (0x400000+0x2184b) [0x42184b]
[ 28284.676] 10: /lib/libc.so.6 (__libc_start_main+0xfe) [0x7f5cfeb79d8e]
[ 28284.677] 11: /usr/bin/X (0x400000+0x213d9) [0x4213d9]
[ 28284.677] Segmentation fault at address 0x2b
[ 28284.677] 
Caught signal 11 (Segmentation fault). Server aborting
[ 28284.677] 
Please consult the The X.Org Foundation support 
     at http://wiki.x.org
 for help. 
[ 28284.690] Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 28284.690] 
[ 28284.800] (II) Power Button: Close
[ 28284.802] (II) UnloadModule: "evdev"
[ 28284.860] (II) Video Bus: Close
[ 28284.861] (II) UnloadModule: "evdev"
[ 28284.913] (II) Power Button: Close
[ 28284.913] (II) UnloadModule: "evdev"
[ 28284.973] (II) Sleep Button: Close
[ 28284.973] (II) UnloadModule: "evdev"
[ 28285.032] (II) USB+PS/2 Optical Mouse: Close
[ 28285.032] (II) UnloadModule: "evdev"
[ 28285.090] (II) ORTEK USB Keyboard Hub: Close
[ 28285.090] (II) UnloadModule: "evdev"
[ 28285.160] (II) ORTEK USB Keyboard Hub: Close
[ 28285.161] (II) UnloadModule: "evdev"
[ 28285.210] (II) Asus Laptop extra buttons: Close
[ 28285.211] (II) UnloadModule: "evdev"
[ 28285.260] (II) AT Translated Set 2 keyboard: Close
[ 28285.260] (II) UnloadModule: "evdev"
[ 28285.375] (II) UnloadModule: "synaptics"
[ 28285.391] (II) AIGLX: Suspending AIGLX clients for VT switch
[ 28285.397]  ddxSigGiveUp: Closing log

je n'ai mis que la fin, quand il commence à y avoir des [WW] (le reste concerne le boot); ça me dit que c'est Xorg qui plante, mais ça me dit pas pourquoi...

Pacifick_FR42 · Le 20/01/2011, à 01:00

Quel drivers sont installé (il est possible que le plantage soit dû à l'économiseur d'écran, auquel cas, il fait sélectionner "none" dans les options du screensaver).

loubrix · Le 20/01/2011, à 01:19

aucun driver supplémentaire installé, c'est le driver radeon qui est utilisé (ma carte n'est plus supportée par Ati):

01:00.0 VGA compatible controller: ATI Technologies Inc Mobility Radeon X2300 (prog-if 00 [VGA controller])
    Subsystem: ASUSTeK Computer Inc. Device 1449
    Flags: bus master, fast devsel, latency 0, IRQ 43
    Memory at b0000000 (32-bit, prefetchable) [size=128M]
    I/O ports at a800 [size=256]
    Memory at fa9f0000 (32-bit, non-prefetchable) [size=64K]
    Expansion ROM at fa9c0000 [disabled] [size=128K]
    Capabilities: <access denied>
    Kernel driver in use: radeon
    Kernel modules: radeon

mon screensaver démarre au bout de 5 minutes (c'est "Photopile"), mais d'après mon gestionnaire d'énergie, l'écran se met en veille au bout de 15 minutes; or j'ai laissé l'ordi entre 18h25 et 18h30, et il a planté à 18h43, donc ce serait plutôt à l'arrêt de l'écran (et du screensaver).
d'autre part, en googlant un peu, je me rend compte que beaucoup ont ce genre de problème depuis Juillet (mais jamais complètement identique); les paramètres sont souvent différents, sauf que c'est toujours en 64 bits, et souvent avec Gnome...
est-il possible que ce soit l'arrêt brutal de gnome-screensaver par la coupure de X qui soit la cause de tout ça?

jacobus77 · Le 20/01/2011, à 01:24

-> le coupable c'est surement chrome. Tu peux tenter une mise à jour ou utiliser chromium:
https://launchpad.net/~chromium-daily/+archive/ppa
Si tes bugs disparaissent tu as trouvé le coupable.

PS :les logs ne sont pas assez informatifs, ça dit juste qu'il y a eu un pb avec le serveur graphique (d'où le redemarrage de session).

loubrix · Le 20/01/2011, à 01:35

c'est déjà Chromium que j'utilise, mais c'est celui des dépots, pas celui du PPA; mais c'est vrai qu'effectivement, j'ai remarqué que ça se produit souvent quand je l'ai laissé ouvert.
j'ai vais essayer de mettre à jour vers le PPA mais j'y crois pas trop, car depuis que j'ai ce problème, Chromium a été mis à jour assez souvent (pas plus tard que ce matin). de toute façon, on ne saura pas aujourd'hui si ça a marché...
je pourrais aussi essayer de ne pas l'utiliser pendant quelques temps pour voir, mais c'est l'horreur (Firefox est trop lent)

Dernière modification par loubrix (Le 20/01/2011, à 01:39)

Pacifick_FR42 · Le 20/01/2011, à 01:37

loubrix a écrit :

aucun driver supplémentaire installé, c'est le driver radeon qui est utilisé (ma carte n'est plus supportée par Ati):
01:00.0 VGA compatible controller: ATI Technologies Inc Mobility Radeon X2300 (prog-if 00 [VGA controller])
    Subsystem: ASUSTeK Computer Inc. Device 1449
    Flags: bus master, fast devsel, latency 0, IRQ 43
    Memory at b0000000 (32-bit, prefetchable) [size=128M]
    I/O ports at a800 [size=256]
    Memory at fa9f0000 (32-bit, non-prefetchable) [size=64K]
    Expansion ROM at fa9c0000 [disabled] [size=128K]
    Capabilities: <access denied>
    Kernel driver in use: radeon
    Kernel modules: radeon
mon screensaver démarre au bout de 5 minutes (c'est "Photopile"), mais d'après mon gestionnaire d'énergie, l'écran se met en veille au bout de 15 minutes; or j'ai laissé l'ordi entre 18h25 et 18h30, et il a planté à 18h43, donc ce serait plutôt à l'arrêt de l'écran (et du screensaver).
d'autre part, en googlant un peu, je me rend compte que beaucoup ont ce genre de problème depuis Juillet (mais jamais complètement identique); les paramètres sont souvent différents, sauf que c'est toujours en 64 bits, et souvent avec Gnome...
est-il possible que ce soit l'arrêt brutal de gnome-screensaver par la coupure de X qui soit la cause de tout ça?

C'est en effet une piste probable, quel Drivers sont installé ? as-tu essayé avec les drivers proprio ? (système>Admin> Pilote propriétaire) ?

Pacifick_FR42 · Le 20/01/2011, à 01:38

jacobus77 a écrit :

-> le coupable c'est surement chrome. Tu peux tenter une mise à jour ou utiliser chromium:
https://launchpad.net/~chromium-daily/+archive/ppa
Si tes bugs disparaissent tu as trouvé le coupable.
PS :les logs ne sont pas assez informatifs, ça dit juste qu'il y a eu un pb avec le serveur graphique (d'où le redemarrage de session).

Intéressant, qu'es-ce qui te fais penser ça ?

loubrix · Le 20/01/2011, à 01:44

as-tu essayé avec les drivers proprio ?

je ne peux pas, Ati n'en fait plus pour ma carte graphique (ce qui est aberrant pour un laptop qui a 3 ans)

Intéressant, qu'es-ce qui te fais penser ça ?

c'est vrai que rien n'indique que Chromium soit coupable, mais comme il était ouvert à chaque fois que ça s'est produit, ça laisse à réfléchir...

Pacifick_FR42 · Le 20/01/2011, à 01:46

J'ignorai qu'un navigateur puisse planter un server X... des drivers mal adapté, un screensaver, oui, mais un navigateur... jamais vu (je dis pas que c'est impossible... )

loubrix · Le 20/01/2011, à 01:50

ben je connais pas assez les liens entre les logiciels et l'environnement, mais je suppose que tout logiciel graphique (et qui donc utilise les librairies liées à X) peut faire planter le serveur graphique; ceci dit je peux me tromper...

Pacifick_FR42 · Le 20/01/2011, à 01:55

Non, tu as tout à fait raison, mais le plus souvent, c'est dû au drivers graphique...

jacobus77 · Le 20/01/2011, à 02:05

Ca n'a rien d'impossible ! surtout pour chrome et bientot pour firefox 4.
C'est sur que ca implique les drivers graphiques mais c'est chrome qui les utlisent: soit de manière non approprié soit en reposant sur des fonctionnalités bugguées dans les drivers libres.
Aprés c'est toi qui voit mais je pense qu'il est plus facile de mettre à jour chrome ou de passer à chromium que d'installer les derniers drivers libres (mesa, ddx,kernel...), notes que tu peux tester avec les ppa xorg edgers avec leur noyau 2.6.37 fourni, ca doit prendre 10 min à installer.

loubrix · Le 20/01/2011, à 02:12

je vais déjà essayer les PPA de Chromium, en prenant la version beta (la version stable est la même que celle des dépots universe); je vais aussi voir ce que ça dit si je désactive la mise en veille de l'écran ou/et Gnome-screensaver.
j'aurais surement pas la réponse tout de suite: ça n'arrive pas tous les jours...
je ferai ça demain, il fera jour; merci et je vous tient au courant

Pacifick_FR42 · Le 20/01/2011, à 02:15

jacobus77 a écrit :

Ca n'a rien d'impossible ! surtout pour chrome et bientot pour firefox 4.
C'est sur que ca implique les drivers graphiques mais c'est chrome qui les utlisent: soit de manière non approprié soit en reposant sur des fonctionnalités bugguées dans les drivers libres.
Aprés c'est toi qui voit mais je pense qu'il est plus facile de mettre à jour chrome ou de passer à chromium que d'installer les derniers drivers libres (mesa, ddx,kernel...), notes que tu peux tester avec les ppa xorg edgers avec leur noyau 2.6.37 fourni, ca doit prendre 10 min à installer.

Très juste... sauf si ça vient du screensaver (qui est mon favori ) on aura sans doute la réponse très bientôt !

Ubuntu-fr

Navigation

Liens de recherche

Annonce

#1 Le 19/01/2011, à 22:23

Session qui se ferme toute seule

#2 Le 19/01/2011, à 22:49

Re : Session qui se ferme toute seule

#3 Le 20/01/2011, à 00:53

Re : Session qui se ferme toute seule

#4 Le 20/01/2011, à 01:00

Re : Session qui se ferme toute seule

#5 Le 20/01/2011, à 01:19

Re : Session qui se ferme toute seule

#6 Le 20/01/2011, à 01:24

Re : Session qui se ferme toute seule

#7 Le 20/01/2011, à 01:35

Re : Session qui se ferme toute seule

#8 Le 20/01/2011, à 01:37

Re : Session qui se ferme toute seule

#9 Le 20/01/2011, à 01:38

Re : Session qui se ferme toute seule

#10 Le 20/01/2011, à 01:44

Re : Session qui se ferme toute seule

#11 Le 20/01/2011, à 01:46

Re : Session qui se ferme toute seule

#12 Le 20/01/2011, à 01:50

Re : Session qui se ferme toute seule

#13 Le 20/01/2011, à 01:55

Re : Session qui se ferme toute seule

#14 Le 20/01/2011, à 02:05

Re : Session qui se ferme toute seule

#15 Le 20/01/2011, à 02:12

Re : Session qui se ferme toute seule

#16 Le 20/01/2011, à 02:15

Re : Session qui se ferme toute seule

Pied de page des forums