You are not logged in.
When trying to use autologin feature it will not log me in when the computer starts up.
However, if I login as root and restart the lightdm service it logs me in automatically.
Whats up with that ?
This is my lightdm.log when I just boot my computer and it won't automatically log me in:
[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Starting Light Display Manager 1.16.6, UID=0 PID=263
[+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
[+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+0.01s] DEBUG: Registered seat module xlocal
[+0.01s] DEBUG: Registered seat module xremote
[+0.01s] DEBUG: Registered seat module unity
[+0.03s] DEBUG: Monitoring logind for seats
[+0.03s] DEBUG: New seat added from logind: seat0
[+0.03s] DEBUG: Seat seat0: Loading properties from config section Seat:*
[+0.03s] DEBUG: Seat seat0: Starting
[+0.03s] DEBUG: Seat seat0: Creating user session
[+0.24s] DEBUG: Loading users from org.freedesktop.Accounts
[+0.24s] DEBUG: User /org/freedesktop/Accounts/User1000 added
[+0.25s] DEBUG: Seat seat0: Creating display server of type wayland
[+0.25s] DEBUG: Could not run plymouth --ping: Failed to execute child process "plymouth" (No such file or directory)
[+0.25s] DEBUG: Using VT 7
[+0.26s] DEBUG: Seat seat0: Display server ready, starting session authentication
[+0.26s] DEBUG: Session pid=305: Started with service 'lightdm-autologin', username 'shell'
[+0.26s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.26s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0
[+0.33s] DEBUG: Session pid=305: Authentication complete with return value 0: Success
[+0.33s] DEBUG: Seat seat0: Session authenticated, running command
[+0.33s] DEBUG: Registering session with bus path /org/freedesktop/DisplayManager/Session0
[+0.33s] DEBUG: Session pid=305: Running command /etc/lightdm/Xsession gnome-session --session=gnome-wayland
[+0.33s] DEBUG: Creating shared data directory /var/lib/lightdm-data/shell
[+0.33s] DEBUG: Session pid=305: Logging to .xsession-errors
[+0.47s] DEBUG: Activating VT 7
[+0.48s] DEBUG: Activating login1 session c1
[+0.48s] DEBUG: Seat seat0 changes active session to c1
[+0.48s] DEBUG: Session c1 is already active
[+1.14s] DEBUG: Session pid=305: Exited with return value 0
[+1.14s] DEBUG: Seat seat0: Session stopped
[+1.14s] DEBUG: Seat seat0: Stopping display server, no sessions require it
[+1.14s] DEBUG: Seat seat0: Display server stopped
[+1.14s] DEBUG: Seat seat0: Active display server stopped, starting greeter
[+1.14s] DEBUG: Seat seat0: Creating greeter session
[+1.14s] DEBUG: Seat seat0: Creating display server of type x
[+1.14s] DEBUG: Using VT 8
[+1.14s] DEBUG: Seat seat0: Starting local X display on VT 8
[+1.14s] DEBUG: DisplayServer x-0: Logging to /var/log/lightdm/x-0.log
[+1.14s] DEBUG: DisplayServer x-0: Writing X server authority to /run/lightdm/root/:0
[+1.14s] DEBUG: DisplayServer x-0: Launching X Server
[+1.14s] DEBUG: Launching process 372: /usr/sbin/X :0 -seat seat0 -auth /run/lightdm/root/:0 -nolisten tcp vt8 -novtswitch
[+1.14s] DEBUG: DisplayServer x-0: Waiting for ready signal from X server :0
[+1.14s] DEBUG: Releasing VT 7
[+1.21s] DEBUG: Seat seat0 changes active session to
[+1.21s] CRITICAL: session_get_login1_session_id: assertion 'session != NULL' failed
[+4.43s] DEBUG: Got signal 10 from process 372
[+4.43s] DEBUG: DisplayServer x-0: Got signal from X server :0
[+4.43s] DEBUG: DisplayServer x-0: Connecting to XServer :0
[+4.43s] DEBUG: Seat seat0: Display server ready, starting session authentication
[+4.43s] DEBUG: Session pid=510: Started with service 'lightdm-greeter', username 'lightdm'
[+4.45s] DEBUG: Session pid=510: Authentication complete with return value 0: Success
[+4.45s] DEBUG: Seat seat0: Session authenticated, running command
[+4.45s] DEBUG: Session pid=510: Running command /usr/sbin/lightdm-gtk-greeter
[+4.45s] DEBUG: Creating shared data directory /var/lib/lightdm-data/lightdm
[+4.45s] DEBUG: Session pid=510: Logging to /var/log/lightdm/x-0-greeter.log
[+4.52s] DEBUG: Activating VT 8
[+4.52s] DEBUG: Activating login1 session c2
[+4.52s] DEBUG: Seat seat0 changes active session to c2
[+4.52s] DEBUG: Session c2 is already active
[+4.79s] DEBUG: Session pid=510: Greeter connected version=1.16.6 resettable=false
[+5.01s] DEBUG: Session pid=510: Greeter start authentication for shell
[+5.01s] DEBUG: Session pid=560: Started with service 'lightdm', username 'shell'
[+5.02s] DEBUG: Session pid=560: Got 1 message(s) from PAM
[+5.02s] DEBUG: Session pid=510: Prompt greeter with 1 message(s)And this is lightdm.log when I as root do a: systemctl restart lightdm.service
and it works as it should. Ie logging me in automatically.
+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Starting Light Display Manager 1.16.6, UID=0 PID=643
[+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
[+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+0.00s] DEBUG: Registered seat module xlocal
[+0.00s] DEBUG: Registered seat module xremote
[+0.00s] DEBUG: Registered seat module unity
[+0.01s] DEBUG: Monitoring logind for seats
[+0.01s] DEBUG: New seat added from logind: seat0
[+0.01s] DEBUG: Seat seat0: Loading properties from config section Seat:*
[+0.01s] DEBUG: Seat seat0: Starting
[+0.01s] DEBUG: Seat seat0: Creating user session
[+0.01s] DEBUG: Loading users from org.freedesktop.Accounts
[+0.01s] DEBUG: User /org/freedesktop/Accounts/User1000 added
[+0.01s] DEBUG: Seat seat0: Creating display server of type wayland
[+0.01s] DEBUG: Could not run plymouth --ping: Failed to execute child process "plymouth" (No such file or directory)
[+0.01s] DEBUG: Using VT 7
[+0.01s] DEBUG: Seat seat0: Display server ready, starting session authentication
[+0.01s] DEBUG: Session pid=651: Started with service 'lightdm-autologin', username 'shell'
[+0.01s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.02s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0
[+0.04s] DEBUG: Session pid=651: Authentication complete with return value 0: Success
[+0.04s] DEBUG: Seat seat0: Session authenticated, running command
[+0.04s] DEBUG: Registering session with bus path /org/freedesktop/DisplayManager/Session0
[+0.04s] DEBUG: Session pid=651: Running command /etc/lightdm/Xsession gnome-session --session=gnome-wayland
[+0.04s] DEBUG: Creating shared data directory /var/lib/lightdm-data/shell
[+0.04s] DEBUG: Session pid=651: Logging to .xsession-errors
[+0.06s] DEBUG: Activating VT 7
[+0.07s] DEBUG: Activating login1 session c5
[+0.08s] DEBUG: Seat seat0 changes active session to c5
[+0.08s] DEBUG: Session c5 is already activeAnd the same exact thing happens with GDM.
Do tell if you want more logs.
Thanks in regards
Offline
I think you should be able to enable auto login via your display manager. Try logging in 'manually' and navigate to the user account settings and select auto-login. Have you enabled 'lightdm.service' ?
Offline
I think you should be able to enable auto login via your display manager. Try logging in 'manually' and navigate to the user account settings and select auto-login. Have you enabled 'lightdm.service' ?
The service is enabled, otherwise it won't start lightdm at boot.
And clicking auto-login in gnome makes no difference.
Offline
[+0.25s] DEBUG: Seat seat0: Creating display server of type wayland .. snip... [+1.14s] DEBUG: Seat seat0: Creating display server of type x ...snip...[+0.01s] DEBUG: Session pid=651: Started with service 'lightdm-autologin', username 'shell'
Defo some (user? wayland?) related weirdness going on - what do your lightdm.conf and greeter conf look like?
Offline
Here is the confs, with comments and all ![]()
lightdm.conf:
#
# General configuration
#
# start-default-seat = True to always start one seat if none are defined in the configuration
# greeter-user = User to run greeter as
# minimum-display-number = Minimum display number to use for X servers
# minimum-vt = First VT to run displays on
# lock-memory = True to prevent memory from being paged to disk
# user-authority-in-system-dir = True if session authority should be in the system location
# guest-account-script = Script to be run to setup guest account
# logind-check-graphical = True to on start seats that are marked as graphical by logind
# log-directory = Directory to log information to
# run-directory = Directory to put running state in
# cache-directory = Directory to cache to
# sessions-directory = Directory to find sessions
# remote-sessions-directory = Directory to find remote sessions
# greeters-directory = Directory to find greeters
# backup-logs = True to move add a .old suffix to old log files when opening new ones
#
[LightDM]
#start-default-seat=true
greeter-user=lightdm
#minimum-display-number=0
#minimum-vt=7
#lock-memory=true
#user-authority-in-system-dir=false
#guest-account-script=guest-account
#logind-check-graphical=false
#log-directory=/var/log/lightdm
run-directory=/run/lightdm
#cache-directory=/var/cache/lightdm
#sessions-directory=/usr/share/lightdm/sessions:/usr/share/xsessions:/usr/share/wayland-sessions
#remote-sessions-directory=/usr/share/lightdm/remote-sessions
#greeters-directory=/usr/share/lightdm/greeters:/usr/share/xgreeters
#backup-logs=true
#
# Seat configuration
#
# Seat configuration is matched against the seat name glob in the section, for example:
# [Seat:*] matches all seats and is applied first.
# [Seat:seat0] matches the seat named "seat0".
# [Seat:thin-client*] matches all seats that have names that start with "thin-client".
#
# type = Seat type (xlocal, xremote)
# pam-service = PAM service to use for login
# pam-autologin-service = PAM service to use for autologin
# pam-greeter-service = PAM service to use for greeters
# xserver-command = X server command to run (can also contain arguments e.g. X -special-option)
# xmir-command = Xmir server command to run (can also contain arguments e.g. Xmir -special-option)
# xserver-layout = Layout to pass to X server
# xserver-config = Config file to pass to X server
# xserver-allow-tcp = True if TCP/IP connections are allowed to this X server
# xserver-share = True if the X server is shared for both greeter and session
# xserver-hostname = Hostname of X server (only for type=xremote)
# xserver-display-number = Display number of X server (only for type=xremote)
# xdmcp-manager = XDMCP manager to connect to (implies xserver-allow-tcp=true)
# xdmcp-port = XDMCP UDP/IP port to communicate on
# xdmcp-key = Authentication key to use for XDM-AUTHENTICATION-1 (stored in keys.conf)
# unity-compositor-command = Unity compositor command to run (can also contain arguments e.g. unity-system-compositor -special-option)
# unity-compositor-timeout = Number of seconds to wait for compositor to start
# greeter-session = Session to load for greeter
# greeter-hide-users = True to hide the user list
# greeter-allow-guest = True if the greeter should show a guest login option
# greeter-show-manual-login = True if the greeter should offer a manual login option
# greeter-show-remote-login = True if the greeter should offer a remote login option
# user-session = Session to load for users
# allow-user-switching = True if allowed to switch users
# allow-guest = True if guest login is allowed
# guest-session = Session to load for guests (overrides user-session)
# session-wrapper = Wrapper script to run session with
# greeter-wrapper = Wrapper script to run greeter with
# guest-wrapper = Wrapper script to run guest sessions with
# display-setup-script = Script to run when starting a greeter session (runs as root)
# display-stopped-script = Script to run after stopping the display server (runs as root)
# greeter-setup-script = Script to run when starting a greeter (runs as root)
# session-setup-script = Script to run when starting a user session (runs as root)
# session-cleanup-script = Script to run when quitting a user session (runs as root)
# autologin-guest = True to log in as guest by default
# autologin-user = User to log in with by default (overrides autologin-guest)
# autologin-user-timeout = Number of seconds to wait before loading default user
# autologin-session = Session to load for automatic login (overrides user-session)
# autologin-in-background = True if autologin session should not be immediately activated
# exit-on-failure = True if the daemon should exit if this seat fails
#
[Seat:*]
#type=xlocal
pam-service=lightdm
pam-autologin-service=lightdm-autologin
pam-greeter-service=lightdm-greeter
#xserver-command=X
#xmir-command=Xmir
#xserver-layout=
#xserver-config=
#xserver-allow-tcp=false
#xserver-share=true
#xserver-hostname=
#xserver-display-number=
#xdmcp-manager=
#xdmcp-port=177
#xdmcp-key=
#unity-compositor-command=unity-system-compositor
#unity-compositor-timeout=60
#greeter-session=example-gtk-gnome
#greeter-hide-users=false
#greeter-allow-guest=true
#greeter-show-manual-login=false
#greeter-show-remote-login=true
#user-session=default
#allow-user-switching=true
#allow-guest=true
#guest-session=
session-wrapper=/etc/lightdm/Xsession
#greeter-wrapper=
#guest-wrapper=
#display-setup-script=
#display-stopped-script=
#greeter-setup-script=
#session-setup-script=
#session-cleanup-script=
autologin-guest=false
autologin-user=shell
autologin-user-timeout=0
autologin-in-background=false
#autologin-session=
#exit-on-failure=false
#
# XDMCP Server configuration
#
# enabled = True if XDMCP connections should be allowed
# port = UDP/IP port to listen for connections on
# listen-address = Host/address to listen for XDMCP connections (use all addresses if not present)
# key = Authentication key to use for XDM-AUTHENTICATION-1 or blank to not use authentication (stored in keys.conf)
#
# The authentication key is a 56 bit DES key specified in hex as 0xnnnnnnnnnnnnnn. Alternatively
# it can be a word and the first 7 characters are used as the key.
#
[XDMCPServer]
#enabled=false
#port=177
#listen-address=
#key=
#
# VNC Server configuration
#
# enabled = True if VNC connections should be allowed
# command = Command to run Xvnc server with
# port = TCP/IP port to listen for connections on
# listen-address = Host/address to listen for VNC connections (use all addresses if not present)
# width = Width of display to use
# height = Height of display to use
# depth = Color depth of display to use
#
[VNCServer]
#enabled=false
#command=Xvnc
#port=5900
#listen-address=
#width=1024
#height=768
#depth=8# LightDM GTK+ Configuration
# Available configuration options listed below.
#
# Appearance:
# theme-name = GTK+ theme to use
# icon-theme-name = Icon theme to use
# background = Background file to use, either an image path or a color (e.g. #772953)
# user-background = false|true ("true" by default) Display user background (if available)
# transition-duration = Length of time (in milliseconds) to transition between background images ("500" by default)
# transition-type = ease-in-out|linear|none ("ease-in-out" by default)
#
# Fonts:
# font-name = Font to use
# xft-antialias = false|true Whether to antialias Xft fonts
# xft-dpi = Resolution for Xft in dots per inch (e.g. 96)
# xft-hintstyle = none|slight|medium|hintfull What degree of hinting to use
# xft-rgba = none|rgb|bgr|vrgb|vbgr Type of subpixel antialiasing
#
# Login window:
# active-monitor = Monitor to display greeter window (name or number). Use #cursor value to display greeter at monitor with cursor. Can be a semicolon separated list
# position = x y ("50% 50%" by default) Login window position
# default-user-image = Image used as default user icon, path or #icon-name
# hide-user-image = false|true ("false" by default)
#
# Panel:
# panel-position = top|bottom ("top" by default)
# clock-format = strftime-format string, e.g. %H:%M
# indicators = semi-colon ";" separated list of allowed indicator modules. Built-in indicators include "~a11y", "~language", "~session", "~power", "~clock", "~host", "~spacer". Unity indicators can be represented by short name (e.g. "sound", "power"), service file name, or absolute path
#
# Accessibility:
# a11y-states = states of accessibility features: "name" - save state on exit, "-name" - disabled at start (default value for unlisted), "+name" - enabled at start. Allowed names: contrast, font, keyboard, reader.
# keyboard = command to launch on-screen keyboard (e.g. "onboard")
# keyboard-position = x y[;width height] ("50%,center -0;50% 25%" by default) Works only for "onboard"
# reader = command to launch screen reader (e.g. "orca")
#
# Security:
# allow-debugging = false|true ("false" by default)
# screensaver-timeout = Timeout (in seconds) until the screen blanks when the greeter is called as lockscreen
#
# Template for per-monitor configuration:
# [monitor: name]
# background = overrides default value
# user-background = overrides default value
# laptop = false|true ("false" by default) Marks monitor as laptop display
# transition-duration = overrides default value
#
[greeter]
#background=
#user-background=
#theme-name=
#icon-theme-name=
#font-name=
#xft-antialias=
#xft-dpi=
#xft-hintstyle=
#xft-rgba=
#indicators=
#clock-format=
#keyboard=
#reader=
#position=
#screensaver-timeout=Last edited by theailer (2016-01-08 14:34:57)
Offline
Here is the confs, with comments and all
Yeah thanks - I love scrolling...
autologin-user=shell
Is your user really "shell"?
Last edited by satanselbow (2016-01-08 17:34:08)
Offline
theailer wrote:Here is the confs, with comments and all
Yeah thanks - I love scrolling...
theailer wrote:autologin-user=shellIs your user really "shell"?
Haha. I was editing it out but then I thought about human error and that I might delete something important for debugging ![]()
Yup, my user is really shell.
Easier to type than theailer
Last edited by theailer (2016-01-08 23:08:51)
Offline