Script ajout utilisateur, pb ouverture session

Support Debian
#1

Bonjour,

j’ai script qui crée des utilisateurs sur plusieurs postes de ma salle:

une fois le script exécuté, La connexion ssh ou en terminale est opérationnelle, par contre la connexion via gdm reste figé, cad qu’on passe l’authentification, mais l’interface graphique reste figée sur l’image de fond d’écran (l’utilisateur n’a pas accès au menu)

Le premier utilisateur crée lors de l’installation du système a une connexion (ssh, terminal, gdm) classique…

j’ai regardé les fichiers de log, mais rien ne me saute aux yeux

Voici par exemple le contenu de auth.log pour une connexion gdm qui est restée bloquée :

Sep 9 16:32:08 A-207-17 gdm3][4619]: pam_unix(gdm3:session): session opened for user sisr by (uid=0) Sep 9 16:32:08 A-207-17 gdm3][4619]: pam_ck_connector(gdm3:session): nox11 mode, ignoring PAM_TTY :0 Sep 9 16:32:08 A-207-17 gdm-welcome][4568]: pam_unix(gdm-welcome:session): session closed for user Debian-gdm Sep 9 16:32:08 A-207-17 polkitd(authority=local): Unregistered Authentication Agent for unix-session:/org/freedesktop/ConsoleKit/Session5 (system bus name :1.79, object path /org/gnome/PolicyKit1/AuthenticationAgent, locale fr_FR.UTF-8) (disconnected from bus) Sep 9 16:32:09 A-207-17 polkitd(authority=local): Registered Authentication Agent for unix-session:/org/freedesktop/ConsoleKit/Session6 (system bus name :1.94 [/usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1], object path /org/gnome/PolicyKit1/AuthenticationAgent, locale fr_FR.UTF-8)

et là pour auth.log, une connexion gdm qui a réussie :

Sep 9 15:50:06 A-207-17 gdm3][4404]: pam_unix(gdm3:session): session opened for user slam by (uid=0) Sep 9 15:50:06 A-207-17 gdm3][4404]: pam_ck_connector(gdm3:session): nox11 mode, ignoring PAM_TTY :0 Sep 9 15:50:06 A-207-17 gdm-welcome][4353]: pam_unix(gdm-welcome:session): session closed for user Debian-gdm Sep 9 15:50:06 A-207-17 polkitd(authority=local): Unregistered Authentication Agent for unix-session:/org/freedesktop/ConsoleKit/Session8 (system bus name :1.116, object path /org/gnome/PolicyKit1/AuthenticationAgent, locale fr_FR.UTF-8) (disconnected from bus) Sep 9 15:50:08 A-207-17 polkitd(authority=local): Registered Authentication Agent for unix-session:/org/freedesktop/ConsoleKit/Session9 (system bus name :1.132 [/usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1], object path /org/gnome/PolicyKit1/AuthenticationAgent, locale fr_FR.UTF-8)

et là pour auth.log de nouveau, une connexion ssh réussie du compte qui avait bloqué en gdm: Sep 9 16:34:32 A-207-17 sshd[4810]: Accepted password for sisr from 172.18.130.21 port 54849 ssh2 Sep 9 16:34:32 A-207-17 sshd[4810]: pam_unix(sshd:session): session opened for user sisr by (uid=0)

Extrait du fichier messages :

Sep 9 15:59:35 A-207-17 rsyslogd-2177: imuxsock begins to drop messages from pid 3224 due to rate-limiting Sep 9 15:59:39 A-207-17 rsyslogd-2177: imuxsock lost 59 messages from pid 3224 due to rate-limiting Sep 9 16:07:26 A-207-17 kernel: [ 503.678485] dconf-service[3594] trap int3 ip:7fc764a08491 sp:7fff3aeabf80 error:0 Sep 9 16:07:28 A-207-17 kernel: [ 506.270128] dconf-service[3630] trap int3 ip:7f1c61510491 sp:7ffff6b08a40 error:0 Sep 9 16:31:54 A-207-17 rsyslogd-2177: imuxsock begins to drop messages from pid 4578 due to rate-limiting Sep 9 16:31:54 A-207-17 kernel: [ 1968.355613] [drm] nouveau 0000:01:00.0: PMFB0_SUBP0: 0x037f0040 Sep 9 16:31:54 A-207-17 kernel: [ 1968.355616] [drm] nouveau 0000:01:00.0: PMFB0_SUBP1: 0x037f0000 Sep 9 16:32:08 A-207-17 rsyslogd-2177: imuxsock lost 63 messages from pid 4578 due to rate-limiting Sep 9 16:32:09 A-207-17 pulseaudio[4722]: [pulseaudio] pid.c: Stale PID file, overwriting. Sep 9 16:32:09 A-207-17 kernel: [ 1983.323504] dconf-service[4791] trap int3 ip:7f264fe73491 sp:7fff51ea61e0 error:0

Extrait du fichier syslog: Sep 9 16:32:09 A-207-17 kernel: [ 1983.323504] dconf-service[4791] trap int3 ip:7f264fe73491 sp:7fff51ea61e0 error:0 Sep 9 16:34:24 A-207-17 minissdpd[3115]: device not found for removing : uuid:ac9b0519-992f-4639-8fc9-d986790235ea::urn:schemas-upnp-org:service:RenderingControl:1 Sep 9 16:34:24 A-207-17 minissdpd[3115]: 4 devices removed (good-bye!) Sep 9 16:34:24 A-207-17 minissdpd[3115]: device not found for removing : uuid:ac9b0519-992f-4639-8fc9-d986790235ea::urn:schemas-upnp-org:device:MediaRenderer:1 Sep 9 16:34:24 A-207-17 minissdpd[3115]: device not found for removing : uuid:ac9b0519-992f-4639-8fc9-d986790235ea Sep 9 16:34:24 A-207-17 minissdpd[3115]: device not found for removing : uuid:ac9b0519-992f-4639-8fc9-d986790235ea::upnp:rootdevice Sep 9 16:34:27 A-207-17 minissdpd[3115]: device not found for removing : uuid:ac9b0519-992f-4639-8fc9-d986790235ea::upnp:rootdevice Sep 9 16:34:27 A-207-17 minissdpd[3115]: device not found for removing : uuid:ac9b0519-992f-4639-8fc9-d986790235ea Sep 9 16:34:27 A-207-17 minissdpd[3115]: device not found for removing : uuid:ac9b0519-992f-4639-8fc9-d986790235ea::urn:schemas-upnp-org:device:MediaRenderer:1 Sep 9 16:34:27 A-207-17 minissdpd[3115]: device not found for removing : uuid:ac9b0519-992f-4639-8fc9-d986790235ea::urn:schemas-upnp-org:service:RenderingControl:1

si qqn a une idée, à part passer sur les machines, ce qui prendra peut-être moins de temps que de continuer à chercher, mais qui reste plus frustrant…

#2

Bonjour,

Et que dit le Xorg.0.log ? et /$home/$user/.xsession-errors ?

As-tu essayé de te connecter en console avec l’un de ces utilisateurs et de lancer startx ?

Usti

#3

que donne

#4

tail Xorg.0.log [ 1430.097] (II) NOUVEAU(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e) [ 1430.097] (II) NOUVEAU(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e) [ 1430.097] (II) NOUVEAU(0): Modeline "1280x960"x0.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e) [ 1430.097] (II) NOUVEAU(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e) [ 1430.097] (II) NOUVEAU(0): Modeline "1440x900"x0.0 88.75 1440 1488 1520 1600 900 903 909 926 +hsync -vsync (55.5 kHz e) [ 1430.097] (II) NOUVEAU(0): Modeline "1600x1200"x0.0 162.00 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (75.0 kHz e) [ 1430.097] (II) NOUVEAU(0): Modeline "1680x1050"x0.0 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +hsync -vsync (64.7 kHz e) [ 1430.097] (II) NOUVEAU(0): Modeline "1920x1080"x60.0 172.80 1920 2040 2248 2576 1080 1081 1084 1118 -hsync +vsync (67.1 kHz e) [ 4967.516] (II) AIGLX: Suspending AIGLX clients for VT switch [ 4967.516] (II) NOUVEAU(0): NVLeaveVT is called.

[code]cat /home/sisr/.xsession-errors
/etc/gdm3/Xsession: Beginning session setup…
localuser:sisr being added to access control list
openConnection: connect: Aucun fichier ou dossier de ce type
cannot connect to brltty at :0
Can’t save user-dirs.dirs
x-session-manager[14807]: WARNING: GsmSessionSave: Failed to create directory /home/sisr/.config/gnome-session/saved-session: Permission non accordée
x-session-manager[14807]: WARNING: GsmSessionSave: could not create directory for saved session: /home/sisr/.config/gnome-session/saved-session
x-session-manager[14807]: WARNING: Unable to find required component ‘gnome-shell’
x-session-manager[14807]: WARNING: GsmSessionSave: Failed to create directory /home/sisr/.config/gnome-session/saved-session: Permission non accordée
x-session-manager[14807]: WARNING: Unable to find required component ‘gnome-settings-daemon’
x-session-manager[14807]: WARNING: GsmSessionSave: Failed to create directory /home/sisr/.config/gnome-session/saved-session: Permission non accordée
x-session-manager[14807]: CRITICAL: gsm_manager_add_autostart_apps_from_dir: assertion `path != NULL’ failed
GNOME_KEYRING_CONTROL=/home/sisr/.cache/keyring-znguXq
SSH_AUTH_SOCK=/home/sisr/.cache/keyring-znguXq/ssh
GNOME_KEYRING_CONTROL=/home/sisr/.cache/keyring-znguXq
SSH_AUTH_SOCK=/home/sisr/.cache/keyring-znguXq/ssh
GNOME_KEYRING_CONTROL=/home/sisr/.cache/keyring-znguXq
SSH_AUTH_SOCK=/home/sisr/.cache/keyring-znguXq/ssh
GPG_AGENT_INFO=/home/sisr/.cache/keyring-znguXq/gpg:0:1
GNOME_KEYRING_CONTROL=/home/sisr/.cache/keyring-znguXq
SSH_AUTH_SOCK=/home/sisr/.cache/keyring-znguXq/ssh
Initializing tracker-miner-fs…
Initializing tracker-store…
Creating config directory:’/home/sisr/.config/tracker’

(tracker-miner-fs:14915): Tracker-CRITICAL **: Could not create configuration directory

(tracker-miner-fs:14915): GLib-GIO-CRITICAL **: g_file_delete: assertion `G_IS_FILE (file)’ failed
Creating config directory:’/home/sisr/.config/tracker’

(tracker-store:14917): Tracker-CRITICAL **: Could not create configuration directory

(tracker-store:14917): GLib-GIO-CRITICAL **: g_file_delete: assertion `G_IS_FILE (file)’ failed
Creating config directory:’/home/sisr/.config/tracker’

(tracker-store:14917): Tracker-CRITICAL **: Could not create configuration directory

(tracker-store:14917): GLib-GIO-CRITICAL **: g_file_delete: assertion `G_IS_FILE (file)’ failed
Starting log:
File:’/home/sisr/.local/share/tracker/tracker-store.log’
Starting log:
File:’/home/sisr/.local/share/tracker/tracker-miner-fs.log’
x-session-manager[14807]: WARNING: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildSignaled: Process /usr/lib/dconf/dconf-service received signal 5

(gdu-notification-daemon:14909): GduNotification-WARNING **: Error creating directory `/home/sisr/.config/gnome-disk-utility/ata-smart-ignore’: Permission non accordée
Creating config directory:’/home/sisr/.config/tracker’

(tracker-store:14917): Tracker-CRITICAL **: Could not create configuration directory

(tracker-store:14917): GLib-GIO-CRITICAL **: g_file_delete: assertion `G_IS_FILE (file)’ failed
Creating config directory:’/home/sisr/.config/tracker’

(tracker-miner-fs:14915): Tracker-CRITICAL **: Could not create configuration directory

(tracker-miner-fs:14915): GLib-GIO-CRITICAL **: g_file_delete: assertion `G_IS_FILE (file)’ failed
Creating config directory:’/home/sisr/.config/tracker’

(tracker-store:14917): Tracker-CRITICAL **: Could not create configuration directory

(tracker-store:14917): GLib-GIO-CRITICAL **: g_file_delete: assertion `G_IS_FILE (file)’ failed

** (evolution-alarm-notify:14908): WARNING **: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildSignaled: Process /usr/lib/dconf/dconf-service received signal 5
** Message: applet now removed from the notification area
** Message: get_device_class: Unknown device type ‘NMDeviceVlan’

** (nm-applet:14907): CRITICAL **: foo_device_added_cb: assertion `dclass != NULL’ failed
** Message: get_device_class: Unknown device type ‘NMDeviceVlan’

** (nm-applet:14907): CRITICAL **: foo_device_added_cb: assertion `dclass != NULL’ failed
x-session-manager[14807]: Gdk-WARNING: x-session-manager: Fatal IO error 11 (Ressource temporairement non disponible) on X server :0.

(gnome-settings-daemon:14871): Gdk-WARNING **: gnome-settings-daemon: Fatal IO error 11 (Ressource temporairement non disponible) on X server :0.

(nm-applet:14907): Gdk-WARNING **: nm-applet: Fatal IO error 11 (Ressource temporairement non disponible) on X server :0.

(tracker-miner-fs:14915): GVFS-RemoteVolumeMonitor-WARNING **: Owner :1.11 of volume monitor org.gtk.Private.GduVolumeMonitor disconnected from the bus; removing drives/volumes/mounts

(gdu-notification-daemon:14909): Gdk-WARNING **: gdu-notification-daemon: Fatal IO error 11 (Ressource temporairement non disponible) on X server :0.

(tracker-miner-fs:14915): GVFS-RemoteVolumeMonitor-WARNING **: Owner :1.12 of volume monitor org.gtk.Private.AfcVolumeMonitor disconnected from the bus; removing drives/volumes/mounts

(tracker-miner-fs:14915): GVFS-RemoteVolumeMonitor-WARNING **: Owner :1.13 of volume monitor org.gtk.Private.GPhoto2VolumeMonitor disconnected from the bus; removing drives/volumes/mounts
g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.

Received signal:15->‘Complété’

(tracker-miner-fs:14915): GLib-GIO-CRITICAL **: Error while sending AddMatch() message: La connexion est fermée

(tracker-miner-fs:14915): GLib-GIO-CRITICAL **: Error while sending AddMatch() message: La connexion est fermée

(evolution-alarm-notify:14908): Gdk-WARNING **: evolution-alarm-notify: Fatal IO error 11 (Ressource temporairement non disponible) on X server :0.

(tracker-miner-fs:14915): GLib-GIO-CRITICAL **: Error while sending AddMatch() message: La connexion est fermée
g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.

Received signal:15->'Complété’g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.

OK

OK[/code]

je n’y avais pas pensé, mais j’ai essayé depuis, ça donne la même chose…

la 1er fois, j’ai eu ça :

xauth: file /home/sisr/.Xauthority does not exist | | X: user not authorized to run the X server, aborting. | xinit: giving up | xinit: unable to connect to X server: Connection refused | xinit: server error

mais bon le fichier n’existe pas plus pour un utilisateur où le processus aboutit…

merci

#5

[quote=“agentsteel”]que donne

au début, l’utilisateur n’avait que son propre groupe, j’ai ajouté video,… bref les mêmes groupes que pour le 1er utilisateur, pas mieux

#6

tu t’es bien déconnecté/reconnecté après avoir ajouté les groupes?

#7

oui, même rebooter vu qu’il s’est passé un ou deux jours entre.

#8

Bonjour,

Si startx ne fonctionne pas, c’est plutôt malbarre !

As-tu vérifié les droits sur le répertoire personnel ? Bizarre que l’utilisateur ne puisse pas écrire dans ~/.config !

Usti

#9

Faudrait vérifier les droits sur le home de l’utilisateur…

#10

bon en effet, j’avais vu le pb de droits sur le .config, donc le chown nécessaire…

Un peu piqué par cela, j’ai fait un classique adduser toto depuis un terminal et j’ai constaté exactement le même comportement, à savoir, qu’une fois l’utilisateur crée par le script ou le adduser un ls -al du répertoire utilisateur contient :

drwxr-xr-x 2 sisr sisr 4096 sept. 4 13:47 . drwxr-xr-x 5 root root 4096 sept. 4 13:47 .. -rw-r--r-- 1 sisr sisr 220 déc. 30 2012 .bash_logout -rw-r--r-- 1 sisr sisr 3392 déc. 30 2012 .bashrc -rw-r--r-- 1 sisr sisr 675 déc. 30 2012 .profile

à la première connexion, le répertoire .config est créer avec les droits root:root qui pose le pb

j’ai aussi noté que si le adduser a lieu depuis un terminale virtuel (et donc une session graphique), il n’y a pas ce soucis de droits sur le .config. J’ai pas testé plus loin…

Je me souviens avoir déjà eu ce soucis lors d’une mise à jour via script, ssh d’un OpenOffice sur le backports d’une Squeeze