Alors il y a du nouveau !!!! J'ai tente de passer par un autre display (a priori il y a un pb sur le numero 0) et j'ai etait patient 🙂
% startx -- :1
xauth: timeout in locking authority file /home/ibslrmn/condamine/.serverauth.1768
xauth: timeout in locking authority file /home/ibslrmn/condamine/.Xauthority
xauth: timeout in locking authority file /home/ibslrmn/condamine/.Xauthority
xauth: timeout in locking authority file /home/ibslrmn/condamine/.Xauthority
xauth: timeout in locking authority file /home/ibslrmn/condamine/.Xauthority
X.Org X Server 1.11.4
Release Date: 2012-01-27
X Protocol Version 11, Revision 0
Build Operating System: x86-07 2.6.32-220.4.1.el6.x86_64
Current Operating System: Linux gre026891.ibs.fr 3.6.11-4.fc16.i686 #1 SMP Tue Jan 8 21:23:31 UTC 2013 i686
Kernel command line: BOOT_IMAGE=/vmlinuz-3.6.11-4.fc16.i686 root=UUID=08924972-c93c-4a74-9e4a-eda540e55811 ro rd.md=0 rd.lvm=0 rd.dm=0 KEYTABLE=us quiet SYSFONT=latarcyrheb-sun16 rhgb rd.luks=0 LANG=en_US.UTF-8
Build Date: 27 March 2012 05:11:39AM
Build ID: xorg-x11-server 1.11.4-3.fc16
Current version of pixman: 0.24.4
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.1.log", Time: Mon Sep 9 17:35:15 2013
(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(II) [KMS] Kernel modesetting enabled.
gnome-session[1805]: 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-is-accelerated: No hardware 3D support.
gnome-session-check-accelerated: Helper exited with code 256
gnome-session[1805]: WARNING: Session 'gnome' runnable check failed: Exited with code 1
gnome-session[1805]: 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[1805]: 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.
GConf Error: Configuration server couldn't be contacted: D-BUS error: 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.
GConf Error: Configuration server couldn't be contacted: D-BUS error: 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.
GConf Error: Configuration server couldn't be contacted: D-BUS error: 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-nGauuk
GNOME_KEYRING_PID=2020
** Message: couldn't communicate with already running daemon: 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.
** Message: couldn't communicate with already running daemon: 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-pciHBk
GNOME_KEYRING_PID=2029
GNOME_KEYRING_CONTROL=/tmp/keyring-qXlrmk
SSH_AUTH_SOCK=/tmp/keyring-qXlrmk/ssh
GNOME_KEYRING_PID=2033
Failed to get GConf key '/desktop/ibus/general/embed_preedit_text': Configuration server couldn't be contacted: D-BUS error: 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.
GConf Error: Configuration server couldn't be contacted: D-BUS error: 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-nGauuk
GPG_AGENT_INFO=/tmp/keyring-nGauuk/gpg:0:1
gnome-session[1805]: WARNING: Application 'gnome-settings-daemon.desktop' failed to register before timeout
(gnome-settings-daemon:2042): 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[1805]: 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[1805]: WARNING: Application 'pulseaudio.desktop' failed to register before timeout
gnome-session[1805]: WARNING: Application 'gnome-settings-daemon.desktop' killed by signal
Window manager warning: Failed to load theme "Nodoka": Failed to find a valid file for theme Nodoka
** (gnome-panel:2112): WARNING **: Unable to parse mouse modifier 'disabled'
abrt-applet: glib < 2.31 - init threading
Initializing tracker-store...
Creating config directory:'/home/ibslrmn/condamine/.config/tracker'
Initializing tracker-miner-fs...
Creating config directory:'/home/ibslrmn/condamine/.config/tracker'
** (gnome-fallback-mount-helper:2199): DEBUG: Starting automounting manager
(vino-server:2207): EggSMClient-CRITICAL **: egg_sm_client_set_mode: assertion `global_client == NULL || global_client_mode == EGG_SM_CLIENT_MODE_DISABLED' failed
09/09/2013 05:51:57 PM Autoprobing TCP port in (all) network interface
09/09/2013 05:51:57 PM Listening IPv6://[::]:5900
09/09/2013 05:51:57 PM Listening IPv4://0.0.0.0:5900
09/09/2013 05:51:57 PM Autoprobing selected port 5900
09/09/2013 05:51:57 PM Advertising security type: 'TLS' (18)
09/09/2013 05:51:57 PM Re-binding socket to listen for VNC connections on TCP port 5900 in (all) interface
09/09/2013 05:51:57 PM Listening IPv6://[::]:5900
09/09/2013 05:51:57 PM Listening IPv4://0.0.0.0:5900
09/09/2013 05:51:57 PM Clearing securityTypes
09/09/2013 05:51:57 PM Advertising security type: 'TLS' (18)
09/09/2013 05:51:57 PM Clearing securityTypes
09/09/2013 05:51:57 PM Advertising security type: 'TLS' (18)
09/09/2013 05:51:57 PM Advertising authentication type: 'No Authentication' (1)
09/09/2013 05:51:57 PM Re-binding socket to listen for VNC connections on TCP port 5900 in (all) interface
09/09/2013 05:51:57 PM Listening IPv6://[::]:5900
09/09/2013 05:51:57 PM Listening IPv4://0.0.0.0:5900
09/09/2013 05:51:57 PM Clearing securityTypes
09/09/2013 05:51:57 PM Clearing authTypes
09/09/2013 05:51:57 PM Advertising security type: 'TLS' (18)
09/09/2013 05:51:57 PM Advertising authentication type: 'VNC Authentication' (2)
09/09/2013 05:51:57 PM Clearing securityTypes
09/09/2013 05:51:57 PM Clearing authTypes
09/09/2013 05:51:57 PM Advertising security type: 'TLS' (18)
09/09/2013 05:51:57 PM Advertising authentication type: 'VNC Authentication' (2)
09/09/2013 05:51:57 PM Advertising security type: 'VNC Authentication' (2)
(gnome-panel:2112): Gtk-CRITICAL **: gtk_orientable_get_orientation: assertion `GTK_IS_ORIENTABLE (orientable)' failed
(gnome-panel:2112): Gtk-CRITICAL **: gtk_orientable_get_orientation: assertion `GTK_IS_ORIENTABLE (orientable)' failed
Tracker-Message: Setting up monitor for changes to config file:'/home/ibslrmn/condamine/.config/tracker/tracker-miner-fs.cfg'
Could not open log:'/home/ibslrmn/condamine/.local/share/tracker/tracker-miner-fs.log', No such file or directory
All logging will go to stderr
Starting log:
File:'/home/ibslrmn/condamine/.local/share/tracker/tracker-miner-fs.log'
Tracker-Message: Setting up monitor for changes to config file:'/home/ibslrmn/condamine/.config/tracker/tracker-store.cfg'
Tracker-Message: Setting up monitor for changes to config file:'/home/ibslrmn/condamine/.config/tracker/tracker-store.cfg'
Could not open log:'/home/ibslrmn/condamine/.local/share/tracker/tracker-store.log', No such file or directory
All logging will go to stderr
Starting log:
File:'/home/ibslrmn/condamine/.local/share/tracker/tracker-store.log'
09 Sep 2013, 17:52:01: Tracker-Critical **: D-Bus service name:'org.freedesktop.Tracker1' is already taken, perhaps the daemon is already running?
(tracker-store:2123): Tracker-CRITICAL **: D-Bus service name:'org.freedesktop.Tracker1' is already taken, perhaps the daemon is already running?
09 Sep 2013, 17:52:26: GVFS-RemoteVolumeMonitor-Warning **: invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.Private.GduVolumeMonitor: org.freedesktop.DBus.Error.NoReply: 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.% startx -- :1
xauth: timeout in locking authority file /home/ibslrmn/condamine/.serverauth.1768
xauth: timeout in locking authority file /home/ibslrmn/condamine/.Xauthority
xauth: timeout in locking authority file /home/ibslrmn/condamine/.Xauthority
xauth: timeout in locking authority file /home/ibslrmn/condamine/.Xauthority
xauth: timeout in locking authority file /home/ibslrmn/condamine/.Xauthority
X.Org X Server 1.11.4
Release Date: 2012-01-27
X Protocol Version 11, Revision 0
Build Operating System: x86-07 2.6.32-220.4.1.el6.x86_64
Current Operating System: Linux gre026891.ibs.fr 3.6.11-4.fc16.i686 #1 SMP Tue Jan 8 21:23:31 UTC 2013 i686
Kernel command line: BOOT_IMAGE=/vmlinuz-3.6.11-4.fc16.i686 root=UUID=08924972-c93c-4a74-9e4a-eda540e55811 ro rd.md=0 rd.lvm=0 rd.dm=0 KEYTABLE=us quiet SYSFONT=latarcyrheb-sun16 rhgb rd.luks=0 LANG=en_US.UTF-8
Build Date: 27 March 2012 05:11:39AM
Build ID: xorg-x11-server 1.11.4-3.fc16
Current version of pixman: 0.24.4
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.1.log", Time: Mon Sep 9 17:35:15 2013
(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(II) [KMS] Kernel modesetting enabled.
gnome-session[1805]: 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-is-accelerated: No hardware 3D support.
gnome-session-check-accelerated: Helper exited with code 256
gnome-session[1805]: WARNING: Session 'gnome' runnable check failed: Exited with code 1
gnome-session[1805]: 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[1805]: 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.
GConf Error: Configuration server couldn't be contacted: D-BUS error: 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.
GConf Error: Configuration server couldn't be contacted: D-BUS error: 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.
GConf Error: Configuration server couldn't be contacted: D-BUS error: 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-nGauuk
GNOME_KEYRING_PID=2020
** Message: couldn't communicate with already running daemon: 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.
** Message: couldn't communicate with already running daemon: 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-pciHBk
GNOME_KEYRING_PID=2029
GNOME_KEYRING_CONTROL=/tmp/keyring-qXlrmk
SSH_AUTH_SOCK=/tmp/keyring-qXlrmk/ssh
GNOME_KEYRING_PID=2033
Failed to get GConf key '/desktop/ibus/general/embed_preedit_text': Configuration server couldn't be contacted: D-BUS error: 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.
GConf Error: Configuration server couldn't be contacted: D-BUS error: 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-nGauuk
GPG_AGENT_INFO=/tmp/keyring-nGauuk/gpg:0:1
gnome-session[1805]: WARNING: Application 'gnome-settings-daemon.desktop' failed to register before timeout
(gnome-settings-daemon:2042): 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[1805]: 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[1805]: WARNING: Application 'pulseaudio.desktop' failed to register before timeout
gnome-session[1805]: WARNING: Application 'gnome-settings-daemon.desktop' killed by signal
Window manager warning: Failed to load theme "Nodoka": Failed to find a valid file for theme Nodoka
** (gnome-panel:2112): WARNING **: Unable to parse mouse modifier 'disabled'
abrt-applet: glib < 2.31 - init threading
Initializing tracker-store...
Creating config directory:'/home/ibslrmn/condamine/.config/tracker'
Initializing tracker-miner-fs...
Creating config directory:'/home/ibslrmn/condamine/.config/tracker'
** (gnome-fallback-mount-helper:2199): DEBUG: Starting automounting manager
(vino-server:2207): EggSMClient-CRITICAL **: egg_sm_client_set_mode: assertion `global_client == NULL || global_client_mode == EGG_SM_CLIENT_MODE_DISABLED' failed
09/09/2013 05:51:57 PM Autoprobing TCP port in (all) network interface
09/09/2013 05:51:57 PM Listening IPv6://[::]:5900
09/09/2013 05:51:57 PM Listening IPv4://0.0.0.0:5900
09/09/2013 05:51:57 PM Autoprobing selected port 5900
09/09/2013 05:51:57 PM Advertising security type: 'TLS' (18)
09/09/2013 05:51:57 PM Re-binding socket to listen for VNC connections on TCP port 5900 in (all) interface
09/09/2013 05:51:57 PM Listening IPv6://[::]:5900
09/09/2013 05:51:57 PM Listening IPv4://0.0.0.0:5900
09/09/2013 05:51:57 PM Clearing securityTypes
09/09/2013 05:51:57 PM Advertising security type: 'TLS' (18)
09/09/2013 05:51:57 PM Clearing securityTypes
09/09/2013 05:51:57 PM Advertising security type: 'TLS' (18)
09/09/2013 05:51:57 PM Advertising authentication type: 'No Authentication' (1)
09/09/2013 05:51:57 PM Re-binding socket to listen for VNC connections on TCP port 5900 in (all) interface
09/09/2013 05:51:57 PM Listening IPv6://[::]:5900
09/09/2013 05:51:57 PM Listening IPv4://0.0.0.0:5900
09/09/2013 05:51:57 PM Clearing securityTypes
09/09/2013 05:51:57 PM Clearing authTypes
09/09/2013 05:51:57 PM Advertising security type: 'TLS' (18)
09/09/2013 05:51:57 PM Advertising authentication type: 'VNC Authentication' (2)
09/09/2013 05:51:57 PM Clearing securityTypes
09/09/2013 05:51:57 PM Clearing authTypes
09/09/2013 05:51:57 PM Advertising security type: 'TLS' (18)
09/09/2013 05:51:57 PM Advertising authentication type: 'VNC Authentication' (2)
09/09/2013 05:51:57 PM Advertising security type: 'VNC Authentication' (2)
(gnome-panel:2112): Gtk-CRITICAL **: gtk_orientable_get_orientation: assertion `GTK_IS_ORIENTABLE (orientable)' failed
(gnome-panel:2112): Gtk-CRITICAL **: gtk_orientable_get_orientation: assertion `GTK_IS_ORIENTABLE (orientable)' failed
Tracker-Message: Setting up monitor for changes to config file:'/home/ibslrmn/condamine/.config/tracker/tracker-miner-fs.cfg'
Could not open log:'/home/ibslrmn/condamine/.local/share/tracker/tracker-miner-fs.log', No such file or directory
All logging will go to stderr
Starting log:
File:'/home/ibslrmn/condamine/.local/share/tracker/tracker-miner-fs.log'
Tracker-Message: Setting up monitor for changes to config file:'/home/ibslrmn/condamine/.config/tracker/tracker-store.cfg'
Tracker-Message: Setting up monitor for changes to config file:'/home/ibslrmn/condamine/.config/tracker/tracker-store.cfg'
Could not open log:'/home/ibslrmn/condamine/.local/share/tracker/tracker-store.log', No such file or directory
All logging will go to stderr
Starting log:
File:'/home/ibslrmn/condamine/.local/share/tracker/tracker-store.log'
09 Sep 2013, 17:52:01: Tracker-Critical **: D-Bus service name:'org.freedesktop.Tracker1' is already taken, perhaps the daemon is already running?
(tracker-store:2123): Tracker-CRITICAL **: D-Bus service name:'org.freedesktop.Tracker1' is already taken, perhaps the daemon is already running?
09 Sep 2013, 17:52:26: GVFS-RemoteVolumeMonitor-Warning **: invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.Private.GduVolumeMonitor: org.freedesktop.DBus.Error.NoReply: 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.
(tracker-miner-fs:2116): GVFS-RemoteVolumeMonitor-WARNING **: invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.Private.GduVolumeMonitor: org.freedesktop.DBus.Error.NoReply: 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-panel:2112): GVFS-RemoteVolumeMonitor-WARNING **: invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.Private.GduVolumeMonitor: org.freedesktop.DBus.Error.NoReply: 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-panel:2112): WARNING **: Could not ask session manager if shut down is available: Timeout was reached
** (gnome-panel:2112): WARNING **: Error getting property: Timeout was reached
** (gnome-panel:2112): WARNING **: Timeout was reached
** (gnome-panel:2112): WARNING **: Error getting property: Timeout was reached
** (gnome-panel:2112): WARNING **: Timeout was reached% startx -- :1
xauth: timeout in locking authority file /home/ibslrmn/condamine/.serverauth.1768
xauth: timeout in locking authority file /home/ibslrmn/condamine/.Xauthority
xauth: timeout in locking authority file /home/ibslrmn/condamine/.Xauthority
xauth: timeout in locking authority file /home/ibslrmn/condamine/.Xauthority
xauth: timeout in locking authority file /home/ibslrmn/condamine/.Xauthority
X.Org X Server 1.11.4
Release Date: 2012-01-27
X Protocol Version 11, Revision 0
Build Operating System: x86-07 2.6.32-220.4.1.el6.x86_64
Current Operating System: Linux gre026891.ibs.fr 3.6.11-4.fc16.i686 #1 SMP Tue Jan 8 21:23:31 UTC 2013 i686
Kernel command line: BOOT_IMAGE=/vmlinuz-3.6.11-4.fc16.i686 root=UUID=08924972-c93c-4a74-9e4a-eda540e55811 ro rd.md=0 rd.lvm=0 rd.dm=0 KEYTABLE=us quiet SYSFONT=latarcyrheb-sun16 rhgb rd.luks=0 LANG=en_US.UTF-8
Build Date: 27 March 2012 05:11:39AM
Build ID: xorg-x11-server 1.11.4-3.fc16
Current version of pixman: 0.24.4
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.1.log", Time: Mon Sep 9 17:35:15 2013
(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(II) [KMS] Kernel modesetting enabled.
gnome-session[1805]: 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-is-accelerated: No hardware 3D support.
gnome-session-check-accelerated: Helper exited with code 256
gnome-session[1805]: WARNING: Session 'gnome' runnable check failed: Exited with code 1
gnome-session[1805]: 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[1805]: 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.
GConf Error: Configuration server couldn't be contacted: D-BUS error: 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.
GConf Error: Configuration server couldn't be contacted: D-BUS error: 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.
GConf Error: Configuration server couldn't be contacted: D-BUS error: 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-nGauuk
GNOME_KEYRING_PID=2020
** Message: couldn't communicate with already running daemon: 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.
** Message: couldn't communicate with already running daemon: 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-pciHBk
GNOME_KEYRING_PID=2029
GNOME_KEYRING_CONTROL=/tmp/keyring-qXlrmk
SSH_AUTH_SOCK=/tmp/keyring-qXlrmk/ssh
GNOME_KEYRING_PID=2033
Failed to get GConf key '/desktop/ibus/general/embed_preedit_text': Configuration server couldn't be contacted: D-BUS error: 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.
GConf Error: Configuration server couldn't be contacted: D-BUS error: 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-nGauuk
GPG_AGENT_INFO=/tmp/keyring-nGauuk/gpg:0:1
gnome-session[1805]: WARNING: Application 'gnome-settings-daemon.desktop' failed to register before timeout
(gnome-settings-daemon:2042): 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[1805]: 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[1805]: WARNING: Application 'pulseaudio.desktop' failed to register before timeout
gnome-session[1805]: WARNING: Application 'gnome-settings-daemon.desktop' killed by signal
Window manager warning: Failed to load theme "Nodoka": Failed to find a valid file for theme Nodoka
** (gnome-panel:2112): WARNING **: Unable to parse mouse modifier 'disabled'
abrt-applet: glib < 2.31 - init threading
Initializing tracker-store...
Creating config directory:'/home/ibslrmn/condamine/.config/tracker'
Initializing tracker-miner-fs...
Creating config directory:'/home/ibslrmn/condamine/.config/tracker'
** (gnome-fallback-mount-helper:2199): DEBUG: Starting automounting manager
(vino-server:2207): EggSMClient-CRITICAL **: egg_sm_client_set_mode: assertion `global_client == NULL || global_client_mode == EGG_SM_CLIENT_MODE_DISABLED' failed
09/09/2013 05:51:57 PM Autoprobing TCP port in (all) network interface
09/09/2013 05:51:57 PM Listening IPv6://[::]:5900
09/09/2013 05:51:57 PM Listening IPv4://0.0.0.0:5900
09/09/2013 05:51:57 PM Autoprobing selected port 5900
09/09/2013 05:51:57 PM Advertising security type: 'TLS' (18)
09/09/2013 05:51:57 PM Re-binding socket to listen for VNC connections on TCP port 5900 in (all) interface
09/09/2013 05:51:57 PM Listening IPv6://[::]:5900
09/09/2013 05:51:57 PM Listening IPv4://0.0.0.0:5900
09/09/2013 05:51:57 PM Clearing securityTypes
09/09/2013 05:51:57 PM Advertising security type: 'TLS' (18)
09/09/2013 05:51:57 PM Clearing securityTypes
09/09/2013 05:51:57 PM Advertising security type: 'TLS' (18)
09/09/2013 05:51:57 PM Advertising authentication type: 'No Authentication' (1)
09/09/2013 05:51:57 PM Re-binding socket to listen for VNC connections on TCP port 5900 in (all) interface
09/09/2013 05:51:57 PM Listening IPv6://[::]:5900
09/09/2013 05:51:57 PM Listening IPv4://0.0.0.0:5900
09/09/2013 05:51:57 PM Clearing securityTypes
09/09/2013 05:51:57 PM Clearing authTypes
09/09/2013 05:51:57 PM Advertising security type: 'TLS' (18)
09/09/2013 05:51:57 PM Advertising authentication type: 'VNC Authentication' (2)
09/09/2013 05:51:57 PM Clearing securityTypes
09/09/2013 05:51:57 PM Clearing authTypes
09/09/2013 05:51:57 PM Advertising security type: 'TLS' (18)
09/09/2013 05:51:57 PM Advertising authentication type: 'VNC Authentication' (2)
09/09/2013 05:51:57 PM Advertising security type: 'VNC Authentication' (2)
(gnome-panel:2112): Gtk-CRITICAL **: gtk_orientable_get_orientation: assertion `GTK_IS_ORIENTABLE (orientable)' failed
(gnome-panel:2112): Gtk-CRITICAL **: gtk_orientable_get_orientation: assertion `GTK_IS_ORIENTABLE (orientable)' failed
Tracker-Message: Setting up monitor for changes to config file:'/home/ibslrmn/condamine/.config/tracker/tracker-miner-fs.cfg'
Could not open log:'/home/ibslrmn/condamine/.local/share/tracker/tracker-miner-fs.log', No such file or directory
All logging will go to stderr
Starting log:
File:'/home/ibslrmn/condamine/.local/share/tracker/tracker-miner-fs.log'
Tracker-Message: Setting up monitor for changes to config file:'/home/ibslrmn/condamine/.config/tracker/tracker-store.cfg'
Tracker-Message: Setting up monitor for changes to config file:'/home/ibslrmn/condamine/.config/tracker/tracker-store.cfg'
Could not open log:'/home/ibslrmn/condamine/.local/share/tracker/tracker-store.log', No such file or directory
All logging will go to stderr
Starting log:
File:'/home/ibslrmn/condamine/.local/share/tracker/tracker-store.log'
09 Sep 2013, 17:52:01: Tracker-Critical **: D-Bus service name:'org.freedesktop.Tracker1' is already taken, perhaps the daemon is already running?
(tracker-store:2123): Tracker-CRITICAL **: D-Bus service name:'org.freedesktop.Tracker1' is already taken, perhaps the daemon is already running?
09 Sep 2013, 17:52:26: GVFS-RemoteVolumeMonitor-Warning **: invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.Private.GduVolumeMonitor: org.freedesktop.DBus.Error.NoReply: 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.
(tracker-miner-fs:2116): GVFS-RemoteVolumeMonitor-WARNING **: invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.Private.GduVolumeMonitor: org.freedesktop.DBus.Error.NoReply: 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-panel:2112): GVFS-RemoteVolumeMonitor-WARNING **: invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.Private.GduVolumeMonitor: org.freedesktop.DBus.Error.NoReply: 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-panel:2112): WARNING **: Could not ask session manager if shut down is available: Timeout was reached
** (gnome-panel:2112): WARNING **: Error getting property: Timeout was reached
** (gnome-panel:2112): WARNING **: Timeout was reached
** (gnome-panel:2112): WARNING **: Error getting property: Timeout was reached
** (gnome-panel:2112): WARNING **: Timeout was reached
This option is not available. Please see --help for all possible usages.
This option is not available. Please see --help for all possible usages.
This option is not available. Please see --help for all possible usages.
This option is not available. Please see --help for all possible usages.
(tracker-miner-fs:2116): GVFS-RemoteVolumeMonitor-WARNING **: invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.Private.GduVolumeMonitor: org.freedesktop.DBus.Error.NoReply: 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-panel:2112): GVFS-RemoteVolumeMonitor-WARNING **: invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.Private.GduVolumeMonitor: org.freedesktop.DBus.Error.NoReply: 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-panel:2112): WARNING **: Could not ask session manager if shut down is available: Timeout was reached
** (gnome-panel:2112): WARNING **: Error getting property: Timeout was reached
** (gnome-panel:2112): WARNING **: Timeout was reached
** (gnome-panel:2112): WARNING **: Error getting property: Timeout was reached
** (gnome-panel:2112): WARNING **: Timeout was reached
This option is not available. Please see --help for all possible usages.
This option is not available. Please see --help for all possible usages.
Et o joie l'ecran de ma station s'est mis a revivre depuis qqs instants !! enfin a vivoter car il y a un message comme quoi le system (graphic hardware ou pilote) n'est pas capable de delivrer l'experinece complete du gnome3 ... Et effectivement, j'ai donc maintenant a une version du bureau different de celui que j'avais sous F15 ...Ce ne serait donc pas la piste du driver pour acceder totalement au gnome3 qui poserait probleme ?
