Seit ich ecrypfts installiert habe kann ich mich nicht mehr per GDM einloggen. Ich muss GDm per tty1 killen und dann Gnome manuell mit startx starten. Hat jemand ähnliche Probleme? auth.log
Aug 25 19:27:17 marius-pc gdm[7656]: pam_unix(gdm:session): session opened for user marius by (uid=0) Aug 25 19:27:17 marius-pc gdm[8010]: gnome-keyring-daemon: couldn't lookup keyring component setting: Der Konfigurationsserver konnte nicht kontaktiert werden; mögliche Fehlerquellen sind, dass TCP/IP für ORBit nicht aktiviert ist oder auf Grund eines Systemabsturzes alte NFS-Sperren gesetzt sind. Unter http://www.gnome.org/projects/gconf/ erhalten Sie weitere Informationen (Details - 1: Failed to get connection to session: dbus-launch failed to autolaunch D-Bus session: No protocol specified Aug 25 19:27:17 marius-pc gdm[8010]: Autolaunch error: X11 initialization failed. Aug 25 19:27:17 marius-pc gdm[8010]: )gnome-keyring-daemon: couldn't lookup ssh component setting: Der Konfigurationsserver konnte nicht kontaktiert werden; mögliche Fehlerquellen sind, dass TCP/IP für ORBit nicht aktiviert ist oder auf Grund eines Systemabsturzes alte NFS-Sperren gesetzt sind. Unter http://www.gnome.org/projects/gconf/ erhalten Sie weitere Informationen (Details - 1: Failed to get connection to session: dbus-launch failed to autolaunch D-Bus session: No protocol specified Aug 25 19:27:17 marius-pc gdm[8010]: Autolaunch error: X11 initialization failed. Aug 25 19:27:17 marius-pc gdm[8010]: )gnome-keyring-daemon: couldn't lookup pkcs11 component setting: Der Konfigurationsserver konnte nicht kontaktiert werden; mögliche Fehlerquellen sind, dass TCP/IP für ORBit nicht aktiviert ist oder auf Grund eines Systemabsturzes alte NFS-Sperren gesetzt sind. Unter http://www.gnome.org/projects/gconf/ erhalten Sie weitere Informationen (Details - 1: Failed to get connection to session: dbus-launch failed to autolaunch D-Bus session: No protocol specified Aug 25 19:27:17 marius-pc gdm[8010]: Autolaunch error: X11 initialization failed. Aug 25 19:27:17 marius-pc gdm[8010]: ) Aug 25 19:27:46 marius-pc gdm[8010]: pam_unix(gdm:session): session closed for user marius
Ab circa 19:27:30 habe ich mein Passwort eingegeben.
common-auth
# # /etc/pam.d/common-auth - authentication settings common to all services # # This file is included from other service-specific PAM config files, # and should contain a list of the authentication modules that define # the central authentication scheme for use on the system # (e.g., /etc/shadow, LDAP, Kerberos, etc.). The default is to use the # traditional Unix authentication mechanisms. # # As of pam 1.0.1-4, this file is managed by pam-auth-update by default. # To take advantage of this, it is recommended that you configure any # local modules either before or after the default block, and use # pam-auth-update to manage selection of other modules. See # pam-auth-update(8) for details. # here are the per-package modules (the "Primary" block) auth [success=1 default=ignore] pam_unix.so nullok_secure # here's the fallback if no module succeeds auth requisite pam_deny.so # prime the stack with a positive return value if there isn't one already; # this avoids us returning an error just because nothing sets a success code # since the modules above will each just jump around auth required pam_permit.so # and here are more per-package modules (the "Additional" block) auth optional pam_ecryptfs.so unwrap # end of pam-auth-update config
common-session
# # /etc/pam.d/common-session - session-related modules common to all services # # This file is included from other service-specific PAM config files, # and should contain a list of modules that define tasks to be performed # at the start and end of sessions of *any* kind (both interactive and # non-interactive). # # As of pam 1.0.1-4, this file is managed by pam-auth-update by default. # To take advantage of this, it is recommended that you configure any # local modules either before or after the default block, and use # pam-auth-update to manage selection of other modules. See # pam-auth-update(8) for details. # here are the per-package modules (the "Primary" block) # here's the fallback if no module succeeds # this is obviously a completely redundant line, except that it lets us # handle better the case where there are no "Primary" modules provided session required pam_permit.so # prime the stack with a positive return value if there isn't one already; # this avoids us returning an error just because nothing sets a success code # since the modules above will each just jump around session required pam_permit.so # and here are more per-package modules (the "Additional" block) session required pam_unix.so session optional pam_ecryptfs.so unwrap # end of pam-auth-update config
Hoffe es ist nur ein dummer Tippfehler oder so, falls es dafür onch andere wichtige Daten gibt recihe ich diese schnellstmöglichst nach. Danke im vorraus ☺