Debian 9 login loop
Clash Royale CLAN TAG#URR8PPP
I have a Debian Stretch system running kernel 4.18.0-2 stuck in a "login loop": user can successfully authenticate but is immediately dumped back to the login screen. Logging in as root works fine and root is able to start an X session. Some dotfiles implicated in other login troubles (e.g. ~/.Xauthority) are owned by the user. I am also not using the processor mentioned here 356738.
How should I proceed troubleshooting this?
Excerpt from journald:
login[732]: pam_unix(login:session): session opened for user user by LOGIN(uid=0)
systemd[1]: Created slice system-userx2druntimex2ddir.slice.
systemd[1]: Started /run/user/1000 mount wrapper.
systemd[1]: Created slice User Slice of UID 1000.
systemd[1]: Starting User Manager for UID 1000...
systemd-logind[667]: New session 1 of user user.
systemd[1]: Started Session 1 of user user.
systemd[1241]: pam_unix(systemd-user:session): session opened for user user by (uid=0)
systemd[1241]: Listening on GnuPG network certificate management daemon.
systemd[1241]: Reached target Paths.
systemd[1241]: Starting D-Bus User Message Bus Socket.
systemd[1241]: Listening on Sound System.
systemd[1241]: Listening on GnuPG cryptographic agent and passphrase cache.
systemd[1241]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
systemd[1241]: Listening on GnuPG cryptographic agent and passphrase cache access for web browser).
systemd[1241]: Reached target Timers.
systemd[1241]: Listening on GnuPG cryptographic agent (ssh-agent emulation)
systemd[1241]: Listening on D-Bus User Message Bus Socket.
systemd[1241]: Reached target Sockets.
systemd[1241]: Teached target Basic System.
systemd[1241]: Teached target Default.
systemd[1241]: Startup finished in 28ms.
systemd[1]: Started User Manager for UID 1000.
login[732]: pam_unix(login:session): session closed for user user
systemd[1]: getty@tty1.service: Service has no hold-off time (RestartSec=0), scheduling restart.
systemd[1]: getty@tty1.service: Scheduled restart job, restart counter is at 1.
systemd[1]: Stopped Getty on tty1
systemd-logind[667]: Session 1 logged out. Waiting for processes to exit.
systemd[1]: Started Getty on tty1.
systemd-logind[667]: Removed session 1.
Edit: problem has resolved itself for now. Not sure what the cause was or how it was fixed but I'll post updates if it comes back.
debian boot login
asked Dec 10 at 20:11
ramblenode
585
add a comment |
I have a Debian Stretch system running kernel 4.18.0-2 stuck in a "login loop": user can successfully authenticate but is immediately dumped back to the login screen. Logging in as root works fine and root is able to start an X session. Some dotfiles implicated in other login troubles (e.g. ~/.Xauthority) are owned by the user. I am also not using the processor mentioned here 356738.
How should I proceed troubleshooting this?
Excerpt from journald:
login[732]: pam_unix(login:session): session opened for user user by LOGIN(uid=0)
systemd[1]: Created slice system-userx2druntimex2ddir.slice.
systemd[1]: Started /run/user/1000 mount wrapper.
systemd[1]: Created slice User Slice of UID 1000.
systemd[1]: Starting User Manager for UID 1000...
systemd-logind[667]: New session 1 of user user.
systemd[1]: Started Session 1 of user user.
systemd[1241]: pam_unix(systemd-user:session): session opened for user user by (uid=0)
systemd[1241]: Listening on GnuPG network certificate management daemon.
systemd[1241]: Reached target Paths.
systemd[1241]: Starting D-Bus User Message Bus Socket.
systemd[1241]: Listening on Sound System.
systemd[1241]: Listening on GnuPG cryptographic agent and passphrase cache.
systemd[1241]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
systemd[1241]: Listening on GnuPG cryptographic agent and passphrase cache access for web browser).
systemd[1241]: Reached target Timers.
systemd[1241]: Listening on GnuPG cryptographic agent (ssh-agent emulation)
systemd[1241]: Listening on D-Bus User Message Bus Socket.
systemd[1241]: Reached target Sockets.
systemd[1241]: Teached target Basic System.
systemd[1241]: Teached target Default.
systemd[1241]: Startup finished in 28ms.
systemd[1]: Started User Manager for UID 1000.
login[732]: pam_unix(login:session): session closed for user user
systemd[1]: getty@tty1.service: Service has no hold-off time (RestartSec=0), scheduling restart.
systemd[1]: getty@tty1.service: Scheduled restart job, restart counter is at 1.
systemd[1]: Stopped Getty on tty1
systemd-logind[667]: Session 1 logged out. Waiting for processes to exit.
systemd[1]: Started Getty on tty1.
systemd-logind[667]: Removed session 1.
Edit: problem has resolved itself for now. Not sure what the cause was or how it was fixed but I'll post updates if it comes back.
debian boot login
asked Dec 10 at 20:11
ramblenode
585
2
If you create a new user, can that user log in? Goal is to determine if the system is broken or if that particular user account is broken (e.g., say a bash login file causing the shell to exit)
– derobert
Dec 10 at 20:24
I'd check that user's shell in /etc/passwd.
– Tomasz
Dec 10 at 20:42
add a comment |
I have a Debian Stretch system running kernel 4.18.0-2 stuck in a "login loop": user can successfully authenticate but is immediately dumped back to the login screen. Logging in as root works fine and root is able to start an X session. Some dotfiles implicated in other login troubles (e.g. ~/.Xauthority) are owned by the user. I am also not using the processor mentioned here 356738.
How should I proceed troubleshooting this?
Excerpt from journald:
login[732]: pam_unix(login:session): session opened for user user by LOGIN(uid=0)
systemd[1]: Created slice system-userx2druntimex2ddir.slice.
systemd[1]: Started /run/user/1000 mount wrapper.
systemd[1]: Created slice User Slice of UID 1000.
systemd[1]: Starting User Manager for UID 1000...
systemd-logind[667]: New session 1 of user user.
systemd[1]: Started Session 1 of user user.
systemd[1241]: pam_unix(systemd-user:session): session opened for user user by (uid=0)
systemd[1241]: Listening on GnuPG network certificate management daemon.
systemd[1241]: Reached target Paths.
systemd[1241]: Starting D-Bus User Message Bus Socket.
systemd[1241]: Listening on Sound System.
systemd[1241]: Listening on GnuPG cryptographic agent and passphrase cache.
systemd[1241]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
systemd[1241]: Listening on GnuPG cryptographic agent and passphrase cache access for web browser).
systemd[1241]: Reached target Timers.
systemd[1241]: Listening on GnuPG cryptographic agent (ssh-agent emulation)
systemd[1241]: Listening on D-Bus User Message Bus Socket.
systemd[1241]: Reached target Sockets.
systemd[1241]: Teached target Basic System.
systemd[1241]: Teached target Default.
systemd[1241]: Startup finished in 28ms.
systemd[1]: Started User Manager for UID 1000.
login[732]: pam_unix(login:session): session closed for user user
systemd[1]: getty@tty1.service: Service has no hold-off time (RestartSec=0), scheduling restart.
systemd[1]: getty@tty1.service: Scheduled restart job, restart counter is at 1.
systemd[1]: Stopped Getty on tty1
systemd-logind[667]: Session 1 logged out. Waiting for processes to exit.
systemd[1]: Started Getty on tty1.
systemd-logind[667]: Removed session 1.
Edit: problem has resolved itself for now. Not sure what the cause was or how it was fixed but I'll post updates if it comes back.
debian boot login
asked Dec 10 at 20:11
ramblenode
585
I have a Debian Stretch system running kernel 4.18.0-2 stuck in a "login loop": user can successfully authenticate but is immediately dumped back to the login screen. Logging in as root works fine and root is able to start an X session. Some dotfiles implicated in other login troubles (e.g. ~/.Xauthority) are owned by the user. I am also not using the processor mentioned here 356738.
How should I proceed troubleshooting this?
Excerpt from journald:
login[732]: pam_unix(login:session): session opened for user user by LOGIN(uid=0)
systemd[1]: Created slice system-userx2druntimex2ddir.slice.
systemd[1]: Started /run/user/1000 mount wrapper.
systemd[1]: Created slice User Slice of UID 1000.
systemd[1]: Starting User Manager for UID 1000...
systemd-logind[667]: New session 1 of user user.
systemd[1]: Started Session 1 of user user.
systemd[1241]: pam_unix(systemd-user:session): session opened for user user by (uid=0)
systemd[1241]: Listening on GnuPG network certificate management daemon.
systemd[1241]: Reached target Paths.
systemd[1241]: Starting D-Bus User Message Bus Socket.
systemd[1241]: Listening on Sound System.
systemd[1241]: Listening on GnuPG cryptographic agent and passphrase cache.
systemd[1241]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
systemd[1241]: Listening on GnuPG cryptographic agent and passphrase cache access for web browser).
systemd[1241]: Reached target Timers.
systemd[1241]: Listening on GnuPG cryptographic agent (ssh-agent emulation)
systemd[1241]: Listening on D-Bus User Message Bus Socket.
systemd[1241]: Reached target Sockets.
systemd[1241]: Teached target Basic System.
systemd[1241]: Teached target Default.
systemd[1241]: Startup finished in 28ms.
systemd[1]: Started User Manager for UID 1000.
login[732]: pam_unix(login:session): session closed for user user
systemd[1]: getty@tty1.service: Service has no hold-off time (RestartSec=0), scheduling restart.
systemd[1]: getty@tty1.service: Scheduled restart job, restart counter is at 1.
systemd[1]: Stopped Getty on tty1
systemd-logind[667]: Session 1 logged out. Waiting for processes to exit.
systemd[1]: Started Getty on tty1.
systemd-logind[667]: Removed session 1.
Edit: problem has resolved itself for now. Not sure what the cause was or how it was fixed but I'll post updates if it comes back.
debian boot login
debian boot login
asked Dec 10 at 20:11
ramblenode
585
asked Dec 10 at 20:11
ramblenode
585
edited Dec 12 at 18:20
asked Dec 10 at 20:11
ramblenode
585
asked Dec 10 at 20:11
ramblenode
585
asked Dec 10 at 20:11
ramblenode
585
585
2
If you create a new user, can that user log in? Goal is to determine if the system is broken or if that particular user account is broken (e.g., say a bash login file causing the shell to exit)
– derobert
Dec 10 at 20:24
I'd check that user's shell in /etc/passwd.
– Tomasz
Dec 10 at 20:42
add a comment |
2
If you create a new user, can that user log in? Goal is to determine if the system is broken or if that particular user account is broken (e.g., say a bash login file causing the shell to exit)
– derobert
Dec 10 at 20:24
I'd check that user's shell in /etc/passwd.
– Tomasz
Dec 10 at 20:42
2
2
If you create a new user, can that user log in? Goal is to determine if the system is broken or if that particular user account is broken (e.g., say a bash login file causing the shell to exit)
– derobert
Dec 10 at 20:24
If you create a new user, can that user log in? Goal is to determine if the system is broken or if that particular user account is broken (e.g., say a bash login file causing the shell to exit)
– derobert
Dec 10 at 20:24
I'd check that user's shell in /etc/passwd.
– Tomasz
Dec 10 at 20:42
I'd check that user's shell in /etc/passwd.
– Tomasz
Dec 10 at 20:42
add a comment |
active
oldest
votes
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f487197%2fdebian-9-login-loop%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f487197%2fdebian-9-login-loop%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
2
If you create a new user, can that user log in? Goal is to determine if the system is broken or if that particular user account is broken (e.g., say a bash login file causing the shell to exit)
– derobert
Dec 10 at 20:24
I'd check that user's shell in /etc/passwd.
– Tomasz
Dec 10 at 20:42