[SOLVED] Autologin problems

phoenix · 2015-05-25 16:23:31

I'm trying to setup a automatic login according to the wiki, but all i get is a black screen where there was previously the login prompt
It happens with the multi.user as well as with the graphical boot targets. I run lvm2 inside a LUKS container.
Any help appreciated.

Last edited by phoenix (2015-08-24 12:05:57)

phoenix · 2015-08-16 10:53:09

after trying one more time i get a systemd error:
Failed to start Getty on tty1

the wiki needs to be updated because the method in it is missing some steps or simply doesn't work

Slithery · 2015-08-16 11:24:39

Can you post the contents of your /etc/systemd/system/getty@tty1.service.d/override.conf please.

You did remember to replace username with your actual username didn't you?

Trilby · 2015-08-16 11:43:56

phoenix wrote:

the wiki needs to be updated because the method in it is missing some steps or simply doesn't work

This is the wrong way to ask a question. While this is always a possibility, jumping to this conclusion rather than suspecting that you are doing something wrong is counter productive. What's described in the wiki works fine for pretty much everyone else.

That said, there was a recent issue with one version of logind where the first login would work, but subsequent autostarting of X could fail. But this was solved by an update, and the symptoms were very different. Please describe exactly what you have done to set this up.

phoenix · 2015-08-16 12:15:25

slithery wrote:

Can you post the contents of your /etc/systemd/system/getty@tty1.service.d/override.conf please.
You did remember to replace username with your actual username didn't you?

yes, i typed my username correctly
the content of my override.conf was the same as in the wiki (except the username part)
just to clarify, should i change the boot target or not? because the wiki doesn't make it clear.

Trilby · 2015-08-16 12:18:06

The instructions will work for multiuser target or graphical target - but it doesn't seem there'd be any point in using them for graphical target. Is/was your graphical target working before you started doing this? What is your graphical target supposed to do? Do you run a display manager? An improperly configured graphical target *might* be the cause of the blank screen you described.

Please describe exactly what you have done so far to configure your start up process.

phoenix · 2015-08-16 12:50:19

I use the graphical target with no display manager, and i get the command-line login prompt. After i type my username and password, the X server and my desktop environment start automatically

Last edited by phoenix (2015-08-16 12:50:34)

Trilby · 2015-08-16 12:53:26

If the graphical target is not doing anything, then there is no point keeping it around. I'd disable it. But if it really isn't doing anything, then it also shouldn't do any harm.

Raynman · 2015-08-16 13:26:47

So you have a failing service, but I don't see anything like systemctl status output?

It doesn't seem to hurt anyone (so changing it probably won't help you), but I wonder why the wiki replaces the $TERM in the upstream service* with a baud_rate argument for the virtual console (unnecessary according to the man page) and a hardcoded "linux".

* current version anyway; maybe the wiki is based on an older revision?

phoenix · 2015-08-16 13:55:38

Raynman wrote:

So you have a failing service, but I don't see anything like systemctl status output?

It only fails when i try to autologin, otherwise it works. After further investigating the journal i found this (the config had Type=simple argument in this case):

systemd[1]: getty@tty1.service: Start request repeated too quickly.
systemd[1]: Failed to start Getty on tty1.
systemd[1]: getty@tty1.service: Failed with result 'start-limit'.

Regarding the graphical target, it looks like it's the default for kde/plasma5, as that is what was set when i installed the system.

Trilby · 2015-08-16 14:10:41

phoenix wrote:

Regarding the graphical target, it looks like it's the default for kde/plasma5, as that is what was set when i installed the system.

Eh, what? So you are not using archlinux?

phoenix · 2015-08-16 14:44:06

Trilby wrote:

Eh, what? So you are not using archlinux?

lol, of course i use arch
According to the wiki it's a systemd default: https://wiki.archlinux.org/index.php/Sy … _boot_into

Head_on_a_Stick · 2015-08-17 13:33:42

Autologin won't work unless the default.target is set to multi-user:

# systemctl set-default multi-user.target

EDIT: http://forums.debian.net/viewtopic.php?f=16&t=123694

Last edited by Head_on_a_Stick (2015-08-17 13:34:38)

phoenix · 2015-08-24 11:54:50

Thanks for the link Head_on_a_Stick!

I finally got it working after following the instructions from the debian forums.
Editing /etc/systemd/system/getty.target.wants/getty@tty1.service directly and setting the target to multi.user.

I'm wondering why the drop-in file has "%I 38400 linux" arguments, while the default "%I $TERM"...

I think the wiki needs to explicitly state that autologin needs multi.user target.

Thanks for everyones input.

Arch Linux

#1 2015-05-25 16:23:31

[SOLVED] Autologin problems

#2 2015-08-16 10:53:09

Re: [SOLVED] Autologin problems

#3 2015-08-16 11:24:39

Re: [SOLVED] Autologin problems

#4 2015-08-16 11:43:56

Re: [SOLVED] Autologin problems

#5 2015-08-16 12:15:25

Re: [SOLVED] Autologin problems

#6 2015-08-16 12:18:06

Re: [SOLVED] Autologin problems

#7 2015-08-16 12:50:19

Re: [SOLVED] Autologin problems

#8 2015-08-16 12:53:26

Re: [SOLVED] Autologin problems

#9 2015-08-16 13:26:47

Re: [SOLVED] Autologin problems

#10 2015-08-16 13:55:38

Re: [SOLVED] Autologin problems

#11 2015-08-16 14:10:41

Re: [SOLVED] Autologin problems

#12 2015-08-16 14:44:06

Re: [SOLVED] Autologin problems

#13 2015-08-17 13:33:42

Re: [SOLVED] Autologin problems

#14 2015-08-24 11:54:50

Re: [SOLVED] Autologin problems

Board footer