Wheezy : Ecran noir, curseur clignotant

Bonjour la foule,

Après avoir tenté, en vain, d’installer Nemo comme proposé dans un forum généraliste (fr.comp) en suivant techlw.com/2013/12/install-n … -with.html mes problèmes ont commencé. Déjà l’installation n’a pas abouti.
J’ai donc désinstallé les “résidus” par Synaptic. Mais le mal semblait fait et les premiers problèmes ont été le verrouillage de dossiers et de fichiers quand je tentais de les ouvrir.
Obligé de modifier les droits d’utilisateur (qui était auparavant autorisé en lecture/écriture) pour pouvoir les manipuler. Pas trop gravec mais ch…
Jusqu’à la fin de la journée … suivie d’une tentative de démarrage ce matin : écran noir avec curseur clignotant, impossible d’ouvrir une session normale.
En mode dépannage, startx pour constater que les logs n’avaient, semble-t’il, rien d’anormal. Je veux bien les copier ici … mais c’est long.
Côté affichage, le résultat est le suivant :

root@debian:~# lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09)
root@debian:~# glxinfo | grep direct
direct rendering: Yes

alsa-base.conf est configuré comme suit :

# autoloader aliases
install sound-slot-0 /sbin/modprobe snd-card-0
install sound-slot-1 /sbin/modprobe snd-card-1
install sound-slot-2 /sbin/modprobe snd-card-2
install sound-slot-3 /sbin/modprobe snd-card-3
install sound-slot-4 /sbin/modprobe snd-card-4
install sound-slot-5 /sbin/modprobe snd-card-5
install sound-slot-6 /sbin/modprobe snd-card-6
install sound-slot-7 /sbin/modprobe snd-card-7
# Cause optional modules to be loaded above generic modules
install snd /sbin/modprobe --ignore-install snd && { /sbin/modprobe --quiet snd-ioctl32 ; /sbin/modprobe --quiet snd-seq ; : ; }
install snd-rawmidi /sbin/modprobe --ignore-install snd-rawmidi && { /sbin/modprobe --quiet snd-seq-midi ; : ; }
install snd-emu10k1 /sbin/modprobe --ignore-install snd-emu10k1 && { /sbin/modprobe --quiet snd-emu10k1-synth ; : ; }
# Keep snd-pcsp from beeing loaded as first soundcard
options snd-pcsp index=-2
# Keep snd-usb-audio from beeing loaded as first soundcard
options snd-usb-audio index=-2
# Prevent abnormal drivers from grabbing index 0
options bt87x index=-2
options cx88_alsa index=-2
options snd-atiixp-modem index=-2
options snd-intel8x0m index=-2
options snd-via82xx-modem index=-2
options snd-hda-intel model=generic

Tout cela paraît normal et il ne semble donc pas que l’impossibilité d’ouvrir une session sous x soit due à un problème du côté du chipset graphique.
Comment faire pour tenter de réparer le système, sachant que j’ai naturellement déjà éliminé le dépôt, conseillé pour l’installation de Nemo, du sources.list ?
Ceci étant, je ne suis pas vraiment certain que la tentative d’installation de Nemo soit la cause du problème … coïncidence ?

Salut,

Pourquoi aller chercher un mode d’emploi à base de sudo (comme sous Ubuntu) alors que nemo se trouve dans nos dépôts et s’installe avec apt-get ou aptitude ?

Salut,

J’ai essayé les dépôts avec un sources.list comme suit :

deb http.debian.net/debian wheezy main contrib non-free
deb http.debian.net/debian wheezy-updates main contrib non-free
deb security.debian.org/ wheezy/updates main contrib non-free

… mais ça n’a rien donné.
Et donc …

salut,

dans quel dépot se trouve nemo ?

car moi j’ai rien

michel@debian-netbook:~$ apt-cache policy nemo N: Impossible de trouver le paquet nemo

dans sid, autant pour moi, mais lui est sous wheezy.

Re,

nemo: Installé : (aucun) Candidat : 1.8.4-1+b1 Table de version : 1.8.4-1+b1 0 500 http://ftp.de.debian.org/debian/ testing/main amd64 Packages 500 http://ftp.de.debian.org/debian/ unstable/main amd64 Packages

Il ne faut donc pas s’étonner si son fonctionnement est improbable :slightly_smiling:

slt,

oui tu as raison.

[quote] suivie d’une tentative de démarrage ce matin : écran noir avec curseur clignotant, impossible d’ouvrir une session normale.
En mode dépannage, startx pour constater que les logs n’avaient, semble-t’il, rien d’anormal. Je veux bien les copier ici … mais c’est long.[/quote]

As-tu essayé de lancer X depuis un compte utilisateur nouvellement créé ?

Si Xorg se lance, le problème vient sans doute de la session, donc de paramètres de gdm / xinitrc, ou du gestionnaire de session de ton bureau, donc éventuellement voir .xsession-errors

[quote=“Zbf”]
As-tu essayé de lancer X depuis un compte utilisateur nouvellement créé ?[/quote]
Non.

[quote=“Zbf”]
Si Xorg se lance, le problème vient sans doute de la session, donc de paramètres de gdm / xinitrc, ou du gestionnaire de session de ton bureau, donc éventuellement voir .xsession-errors[/quote]
Dans xinitrc, aucun anomalie : il se contente de renvoyer à xsession dont le contenu est :

[code]#!/bin/sh

/etc/X11/Xsession

global Xsession file – used by display managers and xinit (startx)

$Id: Xsession 967 2005-12-27 07:20:55Z dnusinow $

set -e

PROGNAME=Xsession

message () {

pretty-print messages of arbitrary length; use xmessage if it

is available and $DISPLAY is set

MESSAGE="$PROGNAME: $*"
echo “$MESSAGE” | fold -s -w ${COLUMNS:-80} >&2
if [ -n “$DISPLAY” ] && which xmessage > /dev/null 2>&1; then
echo “$MESSAGE” | fold -s -w ${COLUMNS:-80} | xmessage -center -file -
fi
}

message_nonl () {

pretty-print messages of arbitrary length (no trailing newline); use

xmessage if it is available and $DISPLAY is set

MESSAGE="$PROGNAME: $*"
echo -n “$MESSAGE” | fold -s -w ${COLUMNS:-80} >&2;
if [ -n “$DISPLAY” ] && which xmessage > /dev/null 2>&1; then
echo -n “$MESSAGE” | fold -s -w ${COLUMNS:-80} | xmessage -center -file -
fi
}

errormsg () {

exit script with error

message "$*"
exit 1
}

internal_errormsg () {

exit script with error; essentially a “THIS SHOULD NEVER HAPPEN” message

One big call to message() for the sake of xmessage; if we had two then

the user would have dismissed the error we want reported before seeing the

request to report it.

errormsg “$*”
“Please report the installed version of the “x11-common””
“package and the complete text of this error message to”
debian-x@lists.debian.org.”
}

initialize variables for use by all session scripts

OPTIONFILE=/etc/X11/Xsession.options

SYSRESOURCES=/etc/X11/Xresources
USRRESOURCES=$HOME/.Xresources

SYSSESSIONDIR=/etc/X11/Xsession.d
USERXSESSION=$HOME/.xsession
USERXSESSIONRC=$HOME/.xsessionrc
ALTUSERXSESSION=$HOME/.Xsession
ERRFILE=$HOME/.xsession-errors

attempt to create an error file; abort if we cannot

if (umask 077 && touch “$ERRFILE”) 2> /dev/null && [ -w “$ERRFILE” ] &&
[ ! -L “$ERRFILE” ]; then
chmod 600 “$ERRFILE"
elif ERRFILE=$(tempfile 2> /dev/null); then
if ! ln -sf “$ERRFILE” “${TMPDIR:=/tmp}/xsession-$USER”; then
message “warning: unable to symlink “$TMPDIR/xsession-$USER” to”
“”$ERRFILE”; look for session log/errors in"
“”$TMPDIR/xsession-$USER"."
fi
else
errormsg "unable to create X session log/error file; aborting."
fi

exec >>"$ERRFILE" 2>&1

echo “$PROGNAME: X session started for $LOGNAME at $(date)”

sanity check; is our session script directory present?

if [ ! -d “$SYSSESSIONDIR” ]; then
errormsg "no “$SYSSESSIONDIR” directory found; aborting."
fi

Attempt to create a file of non-zero length in /tmp; a full filesystem can

cause mysterious X session failures. We do not use touch, :, or test -w

because they won’t actually create a file with contents. We also let standard

error from tempfile and echo go to the error file to aid the user in

determining what went wrong.

WRITE_TEST=$(tempfile)
if ! echo “" >>"$WRITE_TEST"; then
message "warning: unable to write to ${WRITE_TEST%/
}; X session may exit”
"with an error"
fi
rm -f “$WRITE_TEST”

use run-parts to source every file in the session directory; we source

instead of executing so that the variables and functions defined above

are available to the scripts, and so that they can pass variables to each

other

SESSIONFILES=$(run-parts --list $SYSSESSIONDIR)
if [ -n “$SESSIONFILES” ]; then
set +e
for SESSIONFILE in $SESSIONFILES; do
. $SESSIONFILE
done
set -e
fi

exit 0

vim:set ai et sts=2 sw=2 tw=80:

[/code]
et il n’y a pas de fichier ni de dossier .xsession-errors dans le compte d’utilisateur.

Suite du précédent message :
J’ai créé un nouveau compte utilisateur, sans succès : le système n’ouvre toujours pas sur une session graphique au démarrage.
lightgdm n’apparaît même pas, toujours un écran noir.
En mode dépannage, je trouve le fichier .xsession-error suivant :

Xsession: X session started for root at Sun Dec  8 15:40:48 CET 2013
localuser:root being added to access control list
/usr/bin/x-session-manager: X server already running on display :0
ssh-agent is already running
xfdesktop[2280]: starting up

(xfwm4:2274): GLib-CRITICAL **: g_str_has_prefix: assertion `prefix != NULL' failed

(xfwm4:2274): xfwm4-WARNING **: The property '/general/double_click_distance' of type int is not supported
xfce4-settings-helper: Another instance is already running. Leaving...

** (update-notifier:2299): WARNING **: not starting for system user


** (nm-applet:2290): WARNING **: Failed to initialize D-Bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory

(polkit-gnome-authentication-agent-1:2306): polkit-gnome-1-WARNING **: Error getting authority: Error initializing authority: Could not connect: No such file or directory

(xfce4-settings-helper:2307): GLib-CRITICAL **: g_str_has_prefix: assertion `prefix != NULL' failed

(xfdesktop:2280): GVFS-RemoteVolumeMonitor-WARNING **: invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.Private.GduVolumeMonitor: org.freedesktop.DBus.Error.Spawn.ChildSignaled: Process /usr/lib/gvfs/gvfs-gdu-volume-monitor received signal 6
system-config-printer-applet: failed to connect to system D-Bus

(Thunar:2278): GVFS-RemoteVolumeMonitor-WARNING **: invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.Private.GduVolumeMonitor: org.freedesktop.DBus.Error.Spawn.ChildSignaled: Process /usr/lib/gvfs/gvfs-gdu-volume-monitor received signal 6

** (xfce4-session:2268): WARNING **: Failed to connect to the system bus : Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
** Message: xfsm-shutdown-helper.c:1590: Using sudo to REBOOT
Xsession: X session started for root at Fri Jan 24 13:48:41 CET 2014
localuser:root being added to access control list
/usr/bin/x-session-manager: X server already running on display :0
ssh-agent is already running
xfdesktop[2327]: starting up

(xfdesktop:2327): GVFS-RemoteVolumeMonitor-WARNING **: invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.Private.GduVolumeMonitor: org.freedesktop.DBus.Error.Spawn.ChildSignaled: Process /usr/lib/gvfs/gvfs-gdu-volume-monitor received signal 6

** (update-notifier:2348): WARNING **: not starting for system user


(polkit-gnome-authentication-agent-1:2358): polkit-gnome-1-WARNING **: Error getting authority: Error initializing authority: Could not connect: No such file or directory

** (nm-applet:2339): WARNING **: Failed to initialize D-Bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
system-config-printer-applet: failed to connect to system D-Bus

(Thunar:2321): GVFS-RemoteVolumeMonitor-WARNING **: invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.Private.GduVolumeMonitor: org.freedesktop.DBus.Error.Spawn.ChildSignaled: Process /usr/lib/gvfs/gvfs-gdu-volume-monitor received signal 6

(thunar-volman:2423): GVFS-RemoteVolumeMonitor-WARNING **: invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.Private.GduVolumeMonitor: org.freedesktop.DBus.Error.Spawn.ChildSignaled: Process /usr/lib/gvfs/gvfs-gdu-volume-monitor received signal 6
thunar-volman: Unsupported USB device type.

(thunar-volman:2427): GVFS-RemoteVolumeMonitor-WARNING **: invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.Private.GduVolumeMonitor: org.freedesktop.DBus.Error.Spawn.ChildSignaled: Process /usr/lib/gvfs/gvfs-gdu-volume-monitor received signal 6
thunar-volman: Unsupported USB device type.

(thunar-volman:2442): GVFS-RemoteVolumeMonitor-WARNING **: invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.Private.GduVolumeMonitor: org.freedesktop.DBus.Error.Spawn.ChildSignaled: Process /usr/lib/gvfs/gvfs-gdu-volume-monitor received signal 6
thunar-volman: Unknown block device type.

(thunar-volman:2449): GVFS-RemoteVolumeMonitor-WARNING **: invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.Private.GduVolumeMonitor: org.freedesktop.DBus.Error.Spawn.ChildSignaled: Process /usr/lib/gvfs/gvfs-gdu-volume-monitor received signal 6

(thunar-volman:2452): GVFS-RemoteVolumeMonitor-WARNING **: invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.Private.GduVolumeMonitor: org.freedesktop.DBus.Error.Spawn.ChildSignaled: Process /usr/lib/gvfs/gvfs-gdu-volume-monitor received signal 6

** (xfce4-session:2313): WARNING **: Failed to connect to the system bus : Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
** Message: xfsm-shutdown-helper.c:1590: Using sudo to POWEROFF
Xsession: X session started for root at Fri Jan 24 14:28:00 CET 2014
localuser:root being added to access control list
/usr/bin/x-session-manager: X server already running on display :0
ssh-agent is already running
xfdesktop[2308]: starting up
xfce4-settings-helper: Another instance is already running. Leaving...

(xfdesktop:2308): GVFS-RemoteVolumeMonitor-WARNING **: invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.Private.GduVolumeMonitor: org.freedesktop.DBus.Error.Spawn.ChildSignaled: Process /usr/lib/gvfs/gvfs-gdu-volume-monitor received signal 6

(polkit-gnome-authentication-agent-1:2346): polkit-gnome-1-WARNING **: Error getting authority: Error initializing authority: Could not connect: No such file or directory

** (update-notifier:2335): WARNING **: not starting for system user


** (nm-applet:2318): WARNING **: Failed to initialize D-Bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
system-config-printer-applet: failed to connect to system D-Bus

(Thunar:2302): GVFS-RemoteVolumeMonitor-WARNING **: invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.Private.GduVolumeMonitor: org.freedesktop.DBus.Error.Spawn.ChildSignaled: Process /usr/lib/gvfs/gvfs-gdu-volume-monitor received signal 6

** (xfce4-session:2294): WARNING **: Failed to connect to the system bus : Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
** Message: xfsm-shutdown-helper.c:1590: Using sudo to REBOOT
Xsession: X session started for root at Fri Jan 24 15:37:00 CET 2014
localuser:root being added to access control list
/usr/bin/x-session-manager: X server already running on display :0
ssh-agent is already running
xfdesktop[2306]: starting up
xfce4-settings-helper: Another instance is already running. Leaving...

(xfdesktop:2306): GVFS-RemoteVolumeMonitor-WARNING **: invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.Private.GduVolumeMonitor: org.freedesktop.DBus.Error.Spawn.ChildSignaled: Process /usr/lib/gvfs/gvfs-gdu-volume-monitor received signal 6

** (update-notifier:2329): WARNING **: not starting for system user


(polkit-gnome-authentication-agent-1:2338): polkit-gnome-1-WARNING **: Error getting authority: Error initializing authority: Could not connect: No such file or directory

** (nm-applet:2321): WARNING **: Failed to initialize D-Bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
system-config-printer-applet: failed to connect to system D-Bus

** (xfce4-session:2292): WARNING **: Failed to connect to the system bus : Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory

(Thunar:2300): GVFS-RemoteVolumeMonitor-WARNING **: invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.Private.GduVolumeMonitor: org.freedesktop.DBus.Error.Spawn.ChildSignaled: Process /usr/lib/gvfs/gvfs-gdu-volume-monitor received signal 6

(gedit:2473): GVFS-RemoteVolumeMonitor-WARNING **: invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.Private.GduVolumeMonitor: org.freedesktop.DBus.Error.Spawn.ChildSignaled: Process /usr/lib/gvfs/gvfs-gdu-volume-monitor received signal 6

(thunar-volman:2506): GVFS-RemoteVolumeMonitor-WARNING **: invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.Private.GduVolumeMonitor: org.freedesktop.DBus.Error.Spawn.ChildSignaled: Process /usr/lib/gvfs/gvfs-gdu-volume-monitor received signal 6
thunar-volman: Unsupported USB device type.

(thunar-volman:2512): GVFS-RemoteVolumeMonitor-WARNING **: invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.Private.GduVolumeMonitor: org.freedesktop.DBus.Error.Spawn.ChildSignaled: Process /usr/lib/gvfs/gvfs-gdu-volume-monitor received signal 6
thunar-volman: Unsupported USB device type.

(thunar-volman:2527): GVFS-RemoteVolumeMonitor-WARNING **: invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.Private.GduVolumeMonitor: org.freedesktop.DBus.Error.Spawn.ChildSignaled: Process /usr/lib/gvfs/gvfs-gdu-volume-monitor received signal 6
thunar-volman: Unknown block device type.

(thunar-volman:2537): GVFS-RemoteVolumeMonitor-WARNING **: invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.Private.GduVolumeMonitor: org.freedesktop.DBus.Error.Spawn.ChildSignaled: Process /usr/lib/gvfs/gvfs-gdu-volume-monitor received signal 6

(thunar-volman:2540): GVFS-RemoteVolumeMonitor-WARNING **: invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.Private.GduVolumeMonitor: org.freedesktop.DBus.Error.Spawn.ChildSignaled: Process /usr/lib/gvfs/gvfs-gdu-volume-monitor received signal 6

(thunar-volman:2575): GVFS-RemoteVolumeMonitor-WARNING **: invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.Private.GduVolumeMonitor: org.freedesktop.DBus.Error.Spawn.ChildSignaled: Process /usr/lib/gvfs/gvfs-gdu-volume-monitor received signal 6
thunar-volman: Unsupported USB device type.

(thunar-volman:2578): GVFS-RemoteVolumeMonitor-WARNING **: invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.Private.GduVolumeMonitor: org.freedesktop.DBus.Error.Spawn.ChildSignaled: Process /usr/lib/gvfs/gvfs-gdu-volume-monitor received signal 6
thunar-volman: Unsupported USB device type.

(thunar-volman:2594): GVFS-RemoteVolumeMonitor-WARNING **: invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.Private.GduVolumeMonitor: org.freedesktop.DBus.Error.Spawn.ChildSignaled: Process /usr/lib/gvfs/gvfs-gdu-volume-monitor received signal 6
thunar-volman: Unknown block device type.

(thunar-volman:2599): GVFS-RemoteVolumeMonitor-WARNING **: invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.Private.GduVolumeMonitor: org.freedesktop.DBus.Error.Spawn.ChildSignaled: Process /usr/lib/gvfs/gvfs-gdu-volume-monitor received signal 6

(thunar-volman:2609): GVFS-RemoteVolumeMonitor-WARNING **: invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.Private.GduVolumeMonitor: org.freedesktop.DBus.Error.Spawn.ChildSignaled: Process /usr/lib/gvfs/gvfs-gdu-volume-monitor received signal 6
thunar-volman: Unsupported USB device type.

(thunar-volman:2612): GVFS-RemoteVolumeMonitor-WARNING **: invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.Private.GduVolumeMonitor: org.freedesktop.DBus.Error.Spawn.ChildSignaled: Process /usr/lib/gvfs/gvfs-gdu-volume-monitor received signal 6
thunar-volman: Unsupported USB device type.

(thunar-volman:2628): GVFS-RemoteVolumeMonitor-WARNING **: invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.Private.GduVolumeMonitor: org.freedesktop.DBus.Error.Spawn.ChildSignaled: Process /usr/lib/gvfs/gvfs-gdu-volume-monitor received signal 6
thunar-volman: Unknown block device type.

(thunar-volman:3199): GVFS-RemoteVolumeMonitor-WARNING **: invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.Private.GduVolumeMonitor: org.freedesktop.DBus.Error.Spawn.ChildSignaled: Process /usr/lib/gvfs/gvfs-gdu-volume-monitor received signal 6

** (xfce4-session:2292): WARNING **: Failed to connect to the system bus : Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
** Message: xfsm-shutdown-helper.c:1590: Using sudo to REBOOT
Xsession: X session started for root at Fri Jan 24 17:58:19 CET 2014
localuser:root being added to access control list
/usr/bin/x-session-manager: X server already running on display :0
ssh-agent is already running
xfdesktop[2306]: starting up
xfce4-settings-helper: Another instance is already running. Leaving...

(xfdesktop:2306): GVFS-RemoteVolumeMonitor-WARNING **: invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.Private.GduVolumeMonitor: org.freedesktop.DBus.Error.Spawn.ChildSignaled: Process /usr/lib/gvfs/gvfs-gdu-volume-monitor received signal 6

** (nm-applet:2320): WARNING **: Failed to initialize D-Bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory

** (update-notifier:2333): WARNING **: not starting for system user


(polkit-gnome-authentication-agent-1:2347): polkit-gnome-1-WARNING **: Error getting authority: Error initializing authority: Could not connect: No such file or directory
system-config-printer-applet: failed to connect to system D-Bus

(xfce4-notes:2361): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

(xfce4-notes:2361): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

(thunar-volman:2397): GVFS-RemoteVolumeMonitor-WARNING **: invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.Private.GduVolumeMonitor: org.freedesktop.DBus.Error.Spawn.ChildSignaled: Process /usr/lib/gvfs/gvfs-gdu-volume-monitor received signal 6
thunar-volman: Unsupported USB device type.

(thunar-volman:2403): GVFS-RemoteVolumeMonitor-WARNING **: invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.Private.GduVolumeMonitor: org.freedesktop.DBus.Error.Spawn.ChildSignaled: Process /usr/lib/gvfs/gvfs-gdu-volume-monitor received signal 6
thunar-volman: Unsupported USB device type.

(thunar-volman:2419): GVFS-RemoteVolumeMonitor-WARNING **: invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.Private.GduVolumeMonitor: org.freedesktop.DBus.Error.Spawn.ChildSignaled: Process /usr/lib/gvfs/gvfs-gdu-volume-monitor received signal 6
thunar-volman: Unknown block device type.

(thunar-volman:2424): GVFS-RemoteVolumeMonitor-WARNING **: invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.Private.GduVolumeMonitor: org.freedesktop.DBus.Error.Spawn.ChildSignaled: Process /usr/lib/gvfs/gvfs-gdu-volume-monitor received signal 6

(soffice:2382): GVFS-RemoteVolumeMonitor-WARNING **: invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.Private.GduVolumeMonitor: org.freedesktop.DBus.Error.Spawn.ChildSignaled: Process /usr/lib/gvfs/gvfs-gdu-volume-monitor received signal 6

** (xfce4-session:2292): WARNING **: Failed to connect to the system bus : Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
** Message: xfsm-shutdown-helper.c:1590: Using sudo to REBOOT
Xsession: X session started for root at Sat Jan 25 18:02:18 CET 2014
localuser:root being added to access control list
/usr/bin/x-session-manager: X server already running on display :0
ssh-agent is already running

(xfwm4:2327): GLib-GObject-WARNING **: /tmp/buildd/glib2.0-2.33.12+really2.32.4/./gobject/gvalue.c:185: cannot initialize GValue with type `gint', the value has already been initialized as `gint'
xfdesktop[2336]: starting up
xfce4-settings-helper: Another instance is already running. Leaving...

(xfdesktop:2336): GVFS-RemoteVolumeMonitor-WARNING **: invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.Private.GduVolumeMonitor: org.freedesktop.DBus.Error.Spawn.ChildSignaled: Process /usr/lib/gvfs/gvfs-gdu-volume-monitor received signal 6

(xfce4-notes:2344): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

(xfce4-notes:2344): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

** (update-notifier:2358): WARNING **: not starting for system user


** (nm-applet:2352): WARNING **: Failed to initialize D-Bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory

(polkit-gnome-authentication-agent-1:2369): polkit-gnome-1-WARNING **: Error getting authority: Error initializing authority: Could not connect: No such file or directory
system-config-printer-applet: failed to connect to system D-Bus

(Thunar:2330): GVFS-RemoteVolumeMonitor-WARNING **: invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.Private.GduVolumeMonitor: org.freedesktop.DBus.Error.Spawn.ChildSignaled: Process /usr/lib/gvfs/gvfs-gdu-volume-monitor received signal 6

(soffice:2417): GVFS-RemoteVolumeMonitor-WARNING **: invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.Private.GduVolumeMonitor: org.freedesktop.DBus.Error.Spawn.ChildSignaled: Process /usr/lib/gvfs/gvfs-gdu-volume-monitor received signal 6

(gedit:2456): GVFS-RemoteVolumeMonitor-WARNING **: invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.Private.GduVolumeMonitor: org.freedesktop.DBus.Error.Spawn.ChildSignaled: Process /usr/lib/gvfs/gvfs-gdu-volume-monitor received signal 6

(gedit:2473): GVFS-RemoteVolumeMonitor-WARNING **: invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.Private.GduVolumeMonitor: org.freedesktop.DBus.Error.Spawn.ChildSignaled: Process /usr/lib/gvfs/gvfs-gdu-volume-monitor received signal 6

Ouaip, mais c’est un démarrage sous root qui date du [mono]Sun Dec 8 15:40:48 CET 2013[/mono].

D’ailleurs j’ai crû lire que démarrer X en étant root déréglait certaines permissions (si qqn lit et a les infos, sinon essayer de retrouver le topic sur ce forum).

Quel est le problème exactement, tu n’arrives pas du tout à lancer startx, ou c’est juste que (je cite) le système n’ouvre toujours pas sur une session graphique au démarrage ?

Salut,

J’ai suivis ce fil également (comme tous d’ailleurs)

Flatté le kabot … te chantes t-il ?

[quote=“Zbf”]
Quel est le problème exactement, tu n’arrives pas du tout à lancer startx, ou c’est juste que (je cite) le système n’ouvre toujours pas sur une session graphique au démarrage ?[/quote]
Comme écrit dans le message initial, le système reste figé sur un écran noir avec un curseur clignotant dans le coin supérieur gauche de l’écran quand je choisis une session “normale” et n’arrive donc plus à afficher le gestionnaire de sessions qui, sur cette bécane, est lightdm.
Impossible de lancer x à ce moment-là, même en ligne de commande.
Je ne sais faire un startx qu’en session de dépannage, sous root.

Salut,

1 - Lancer une session de dépannage
2 - # exit
3 - se logger en user
4 - startx :slightly_smiling:

Salut,

Ne peut plus accèder au GUI après une connection en ROOT

[quote=“etxeberrizahar”]X et root, mélange potentiellement toxique …

Quand on a besoin de X avec les autorisations de root (synaptic,gparted, etherape,…) lancer une session X sous le compte root n’est pas nécessaire. On peut s’appuyer sur gksu

$ gksu synaptic
$ gksu gparted

Lorsque root pose ses griffes sur X, il arrive que les autorisations sur le fichier .Xauthority en soient affectées empechant les connexions ultérieures en tant que $USER.
Vérifie les propriétés de .Xauthority.

$ ls -l /home/*/.Xauthority

Il ne doit pas appartenir à root:root. Il doit appartenir à user:user.
Pour en changer le propriétaire, [mono]# chown[/mono]

Voir aussi xorg.conf en $HOME. S’il existe, le comparer à celui de /etc/X11. Le renommer le temps de tester,[mono]$ mv xorg.conf glorx.fonc[/mono][/quote]

Salut,

[quote=“ggoodluck47”]
1 - Lancer une session de dépannage
2 - # exit
3 - se logger en user
4 - startx :slightly_smiling:[/quote]
Tu penses bien que j’ai déja essayé, c’était même ma 1ère tentative de récupérer le système.
En vain : j’aboutis au même résultat : curseur clignotant sur écran noir.

C’est pas l’impression que j’en avais eu :laughing:

C’est pas l’impression que j’en avais eu :laughing:[/quote]

???

Merci Belzébuth :wink:

@docanski2,
Commencer par résoudre le problème avec un simple startx en user, pas la peine de chercher du côté de lightdm pour le moment (celui-ci n’est pas sollicité par startx).

Par contre pour comprendre ce qui cloche dans la session graphique, startx en simple user, idéalement sur un nouveau compte utilisateur, car ça discrimine encore d’autres sources potentielles de problèmes.

Et finalement quand tu en es là, tu peux inspecter un peu plus facilement

  • si le problème vient de Xorg
  • ou si le problème vient de l’environnement de bureau

Mais sinon ton symptome me rappelle celui qu’on a quand la session graphique se relance non pas sur le VT 7 mais le VT 8 (quand X a été lancé 2 fois), mais je ne comprend pas pourquoi ça arriverait en session simple utilisateur, sans lightdm, et simplement avec startx.

[quote=“Zbf”]
@docanski2,
Commencer par résoudre le problème avec un simple startx en user[/quote]
Déjà répondu plus haut que cela n’aboutit pas : impossible de me “logger” en “user”

Ni après avoir créé un nouveau compte utilisateur : déjà répondu plus haut aussi.

[quote=“Zbf”]
Et finalement quand tu en es là, tu peux inspecter un peu plus facilement

  • si le problème vient de Xorg
  • ou si le problème vient de l’environnement de bureau[/quote]
    Encore faudrait-il que je puisse arriver à ouvrir une session “utilisateur” … : le démarrage (enfin … la tentative de démarrage) se bloque chaque fois après quelques tests (lan, wlan, etc …) sur un curseur clignotant quand j’envoye un “exit” dans le but de me “logger” en “user”.

Il faudrait l’expliquer plus clairement car mon cerveau n’a pas encore recollé les morceaux de la veille.

Le démarrage se bloque après des tests Lan/Wlan ? Je ne vois pas de quoi il s’agit… DHCP se lance pendant la phase d’init, et NetworkManager éventuellement pendant la session graphique, est-ce ça ?

Je ne vois pas non plus pourquoi tu dois envoyer “exit” pour te connecter en user, si tu démarres Linux en mode mono-utilisateur, tu dois juste avoir l’invite de commande au démarrage, donc pouvoir entrer ton nom d’utilisateur, et taper startx à partir de là.