You are not logged in.

Pages: 1

#1 2024-01-24 18:19:45

vaace
Member
Registered: 2024-01-23
Posts: 4

[SOLVED] User 1000 broken, can't login on TTY-1, can't start X

A short backstory: I tried to edit fstab to mount an NTFS hard drive (it contains all my media) into a folder in my home directory. That failed miraculously and I got thrown into emergency shell, where I reverted the change in fstab. After reboot:

1) I can't log in on TTY-1 as user 1000 (session opens and closes immediately, see the log snippet below);

2) I can log in as root, create a new user and even start X and WM as that test user;

3) I can log in on TTY-2 as user 1000, but X won't start

I made no changes in any config files besides adding an fstab entry.

Now, I found a crude solution (back up home directory, purge user, create a new user with that backup home directory), but I'm genuinely curious about what happened there, so I ask for assistance in maybe actually fixing it.

Boot log snippet related to login process:

Jan 23 20:52:06 vaace-arch login[536]: pam_unix(login:session): session opened for user vaace(uid=1000) by vaace(uid=0)
Jan 23 20:52:06 vaace-arch systemd-logind[492]: New session 1 of user vaace.
Jan 23 20:52:06 vaace-arch systemd[1]: Created slice User Slice of UID 1000.
Jan 23 20:52:06 vaace-arch systemd[1]: Starting User Runtime Directory /run/user/1000...
Jan 23 20:52:06 vaace-arch systemd[1]: Finished User Runtime Directory /run/user/1000.
Jan 23 20:52:06 vaace-arch systemd[1]: Starting User Manager for UID 1000...
Jan 23 20:52:06 vaace-arch (systemd)[580]: pam_warn(systemd-user:setcred): function=[pam_sm_setcred] flags=0x8002 service=[systemd-user] terminal=[] user=[vaace] ruser=[<unknown>] rhost=[<unknown>]
Jan 23 20:52:06 vaace-arch (systemd)[580]: pam_unix(systemd-user:session): session opened for user vaace(uid=1000) by vaace(uid=0)
Jan 23 20:52:06 vaace-arch systemd[580]: Queued start job for default target Main User Target.
Jan 23 20:52:06 vaace-arch systemd-journald[295]: /var/log/journal/2f1472974f01481990bcfa7cb2d10953/user-1000.journal: Journal file uses a different sequence number ID, rotating.
Jan 23 20:52:06 vaace-arch login[536]: LOGIN ON tty1 BY vaace
Jan 23 20:52:06 vaace-arch systemd[580]: Created slice User Application Slice.
Jan 23 20:52:06 vaace-arch systemd[580]: Reached target Paths.
Jan 23 20:52:06 vaace-arch systemd[580]: Reached target Timers.
Jan 23 20:52:06 vaace-arch systemd[580]: Starting D-Bus User Message Bus Socket...
Jan 23 20:52:06 vaace-arch systemd[580]: Listening on GnuPG network certificate management daemon.
Jan 23 20:52:06 vaace-arch systemd[580]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Jan 23 20:52:06 vaace-arch systemd[580]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Jan 23 20:52:06 vaace-arch systemd[580]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Jan 23 20:52:06 vaace-arch systemd[580]: Listening on GnuPG cryptographic agent and passphrase cache.
Jan 23 20:52:06 vaace-arch systemd[580]: Listening on GnuPG public key management service.
Jan 23 20:52:06 vaace-arch systemd[580]: Listening on p11-kit server.
Jan 23 20:52:06 vaace-arch systemd[580]: Listening on PipeWire Multimedia System Sockets.
Jan 23 20:52:06 vaace-arch systemd[580]: Listening on Sound System.
Jan 23 20:52:06 vaace-arch systemd[580]: Listening on D-Bus User Message Bus Socket.
Jan 23 20:52:06 vaace-arch systemd[580]: Reached target Sockets.
Jan 23 20:52:06 vaace-arch systemd[580]: Reached target Basic System.
Jan 23 20:52:06 vaace-arch systemd[1]: Started User Manager for UID 1000.
Jan 23 20:52:06 vaace-arch systemd[580]: Starting Update XDG user dir configuration...
Jan 23 20:52:06 vaace-arch systemd[1]: Started Session 1 of User vaace.
Jan 23 20:52:06 vaace-arch systemd[580]: Finished Update XDG user dir configuration.
Jan 23 20:52:06 vaace-arch systemd[580]: Reached target Main User Target.
Jan 23 20:52:06 vaace-arch systemd[580]: Startup finished in 160ms.
Jan 23 20:52:08 vaace-arch systemd[580]: Created slice User Core Session Slice.
Jan 23 20:52:08 vaace-arch systemd[580]: Starting D-Bus User Message Bus...
Jan 23 20:52:08 vaace-arch dbus-broker-launch[629]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +31: Eavesdropping is deprecated and ignored
Jan 23 20:52:08 vaace-arch dbus-broker-launch[629]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +33: Eavesdropping is deprecated and ignored
Jan 23 20:52:08 vaace-arch systemd[580]: Started D-Bus User Message Bus.
Jan 23 20:52:08 vaace-arch dbus-broker-launch[629]: Ready
Jan 23 20:52:09 vaace-arch login[536]: pam_unix(login:session): session closed for user vaace
Jan 23 20:52:09 vaace-arch systemd[1]: getty@tty1.service: Deactivated successfully.
Jan 23 20:52:09 vaace-arch systemd[1]: session-1.scope: Deactivated successfully.
Jan 23 20:52:09 vaace-arch systemd[1]: session-1.scope: Consumed 1.871s CPU time.
Jan 23 20:52:09 vaace-arch systemd-logind[492]: Session 1 logged out. Waiting for processes to exit.
Jan 23 20:52:09 vaace-arch systemd[1]: getty@tty1.service: Scheduled restart job, restart counter is at 1.
Jan 23 20:52:09 vaace-arch systemd[1]: Started Getty on tty1.
Jan 23 20:52:09 vaace-arch systemd-logind[492]: Removed session 1.
Jan 23 20:52:09 vaace-arch systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Jan 23 20:52:19 vaace-arch systemd[1]: Stopping User Manager for UID 1000...
Jan 23 20:52:19 vaace-arch systemd[580]: Activating special unit Exit the Session...
Jan 23 20:52:19 vaace-arch systemd[580]: Stopped target Main User Target.
Jan 23 20:52:19 vaace-arch systemd[580]: Stopped target Basic System.
Jan 23 20:52:19 vaace-arch systemd[580]: Stopped target Paths.
Jan 23 20:52:19 vaace-arch systemd[580]: Stopped target Sockets.
Jan 23 20:52:19 vaace-arch systemd[580]: Stopped target Timers.
Jan 23 20:52:19 vaace-arch systemd[580]: Closed GnuPG network certificate management daemon.
Jan 23 20:52:19 vaace-arch systemd[580]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
Jan 23 20:52:19 vaace-arch systemd[580]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
Jan 23 20:52:19 vaace-arch systemd[580]: Closed GnuPG cryptographic agent (ssh-agent emulation).
Jan 23 20:52:19 vaace-arch systemd[580]: Closed GnuPG cryptographic agent and passphrase cache.
Jan 23 20:52:19 vaace-arch systemd[580]: Closed GnuPG public key management service.
Jan 23 20:52:19 vaace-arch systemd[580]: Closed p11-kit server.
Jan 23 20:52:19 vaace-arch systemd[580]: Closed PipeWire Multimedia System Sockets.
Jan 23 20:52:19 vaace-arch systemd[580]: Closed Sound System.
Jan 23 20:52:19 vaace-arch dbus-broker[630]: Dispatched 128 messages @ 1(±2)μs / message.
Jan 23 20:52:19 vaace-arch systemd[580]: Stopping D-Bus User Message Bus...
Jan 23 20:52:19 vaace-arch systemd[580]: Stopped D-Bus User Message Bus.
Jan 23 20:52:19 vaace-arch systemd[580]: Removed slice User Core Session Slice.
Jan 23 20:52:19 vaace-arch systemd[580]: Closed D-Bus User Message Bus Socket.
Jan 23 20:52:19 vaace-arch systemd[580]: Removed slice User Application Slice.
Jan 23 20:52:19 vaace-arch systemd[580]: Reached target Shutdown.
Jan 23 20:52:19 vaace-arch systemd[580]: Finished Exit the Session.
Jan 23 20:52:19 vaace-arch systemd[580]: Reached target Exit the Session.
Jan 23 20:52:19 vaace-arch (sd-pam)[582]: pam_warn(systemd-user:setcred): function=[pam_sm_setcred] flags=0x8004 service=[systemd-user] terminal=[] user=[vaace] ruser=[<unknown>] rhost=[<unknown>]
Jan 23 20:52:19 vaace-arch systemd[1]: user@1000.service: Deactivated successfully.
Jan 23 20:52:19 vaace-arch systemd[1]: Stopped User Manager for UID 1000.
Jan 23 20:52:19 vaace-arch systemd[1]: Stopping User Runtime Directory /run/user/1000...
Jan 23 20:52:19 vaace-arch systemd[1]: run-user-1000.mount: Deactivated successfully.
Jan 23 20:52:19 vaace-arch systemd[1]: user-runtime-dir@1000.service: Deactivated successfully.
Jan 23 20:52:19 vaace-arch systemd[1]: Stopped User Runtime Directory /run/user/1000.
Jan 23 20:52:19 vaace-arch systemd[1]: Removed slice User Slice of UID 1000.
Jan 23 20:52:19 vaace-arch systemd[1]: user-1000.slice: Consumed 2.048s CPU time.
Jan 23 20:52:29 vaace-arch systemd[1]: systemd-hostnamed.service: Deactivated successfully.
Jan 23 21:07:00 vaace-arch systemd[1]: Starting Cleanup of Temporary Directories...
Jan 23 21:07:00 vaace-arch systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully.
Jan 23 21:07:00 vaace-arch systemd[1]: Finished Cleanup of Temporary Directories.
Jan 23 21:07:20 vaace-arch login[647]: pam_unix(login:session): session opened for user vaace(uid=1000) by vaace(uid=0)
Jan 23 21:07:20 vaace-arch systemd-logind[492]: New session 3 of user vaace.
Jan 23 21:07:20 vaace-arch systemd[1]: Created slice User Slice of UID 1000.
Jan 23 21:07:20 vaace-arch systemd[1]: Starting User Runtime Directory /run/user/1000...
Jan 23 21:07:20 vaace-arch systemd[1]: Finished User Runtime Directory /run/user/1000.
Jan 23 21:07:20 vaace-arch systemd[1]: Starting User Manager for UID 1000...
Jan 23 21:07:20 vaace-arch (systemd)[688]: pam_warn(systemd-user:setcred): function=[pam_sm_setcred] flags=0x8002 service=[systemd-user] terminal=[] user=[vaace] ruser=[<unknown>] rhost=[<unknown>]
Jan 23 21:07:20 vaace-arch (systemd)[688]: pam_unix(systemd-user:session): session opened for user vaace(uid=1000) by vaace(uid=0)
Jan 23 21:07:20 vaace-arch systemd[688]: Queued start job for default target Main User Target.
Jan 23 21:07:20 vaace-arch systemd[688]: Created slice User Application Slice.
Jan 23 21:07:20 vaace-arch systemd[688]: Reached target Paths.
Jan 23 21:07:20 vaace-arch systemd[688]: Reached target Timers.
Jan 23 21:07:20 vaace-arch systemd[688]: Starting D-Bus User Message Bus Socket...
Jan 23 21:07:20 vaace-arch systemd[688]: Listening on GnuPG network certificate management daemon.
Jan 23 21:07:20 vaace-arch systemd[688]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Jan 23 21:07:20 vaace-arch systemd[688]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Jan 23 21:07:20 vaace-arch systemd[688]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Jan 23 21:07:20 vaace-arch systemd[688]: Listening on GnuPG cryptographic agent and passphrase cache.
Jan 23 21:07:20 vaace-arch systemd[688]: Listening on GnuPG public key management service.
Jan 23 21:07:20 vaace-arch systemd[688]: Listening on p11-kit server.
Jan 23 21:07:20 vaace-arch systemd[688]: Listening on PipeWire Multimedia System Sockets.
Jan 23 21:07:20 vaace-arch systemd[688]: Listening on Sound System.
Jan 23 21:07:20 vaace-arch systemd[688]: Listening on D-Bus User Message Bus Socket.
Jan 23 21:07:20 vaace-arch systemd[688]: Reached target Sockets.
Jan 23 21:07:20 vaace-arch systemd[688]: Reached target Basic System.
Jan 23 21:07:20 vaace-arch systemd[1]: Started User Manager for UID 1000.
Jan 23 21:07:20 vaace-arch systemd[688]: Starting Update XDG user dir configuration...
Jan 23 21:07:20 vaace-arch systemd[1]: Started Session 3 of User vaace.

Log files:
1) Working system before it broke:
https://0x0.st/HGBv.txt

2) Broken system:
https://0x0.st/HGBe.txt

3) A bit broken system (current state):
https://0x0.st/HGB_.txt

4) Xorg log file upon trying to start it:
https://0x0.st/HGLa.0.log

5) And, finally (since I made a mistake of running pacman while root on TTY), /var/log/pacman.log:
https://0x0.st/HGLB.log

Last edited by vaace (2024-01-24 21:43:12)

Offline

#2 2024-01-24 19:11:27

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 25,232

Re: [SOLVED] User 1000 broken, can't login on TTY-1, can't start X

Everything dies quickly, but correctly, so system state looks fine, but your login shell likely tries to run something bogus.

What are you trying to start when starting x and how are you doing so? Post your users shell init files and .xinitrc if you happen to use startx. Elaborate on your NTFS fail, what exactly did you edit where and how?

Last edited by V1del (2024-01-24 19:12:06)

Offline

#3 2024-01-24 19:36:33

Scimmia
Fellow
Registered: 2012-09-01
Posts: 13,727

Re: [SOLVED] User 1000 broken, can't login on TTY-1, can't start X

Check permissions on your home dir

Offline

#4 2024-01-24 20:20:16

vaace
Member
Registered: 2024-01-23
Posts: 4

Re: [SOLVED] User 1000 broken, can't login on TTY-1, can't start X

~/.xinitrc:

#!/bin/sh

userresources=$HOME/.Xresources
usermodmap=$HOME/.Xmodmap
sysresources=/etc/X11/xinit/.Xresources
sysmodmap=/etc/X11/xinit/.Xmodmap

# merge in defaults and keymaps

if [ -f $sysresources ]; then







    xrdb -merge $sysresources

fi

if [ -f $sysmodmap ]; then
    xmodmap $sysmodmap
fi

if [ -f "$userresources" ]; then







    xrdb -merge "$userresources"

fi

if [ -f "$usermodmap" ]; then
    xmodmap "$usermodmap"
fi

# start some nice programs

if [ -d /etc/X11/xinit/xinitrc.d ] ; then
 for f in /etc/X11/xinit/xinitrc.d/?*.sh ; do
  [ -x "$f" ] && . "$f"
 done
 unset f
fi

exec --no-startup-id picom -b
exec awesome

~/.bashprofile:

#
# ~/.bash_profile
#

[[ -f ~/.bashrc ]] && . ~/.bashrc

if [ -z "$DISPLAY" ] && [ "$XDG_VTNR" = 1 ]; then
  exec startx
fi

~/.bashrc:

#
# ~/.bashrc
#

# If not running interactively, don't do anything
[[ $- != *i* ]] && return

alias ls='ls --color=auto'
alias grep='grep --color=auto'
PS1='[\u@\h \W]\$ '

Offline

#5 2024-01-24 20:26:27

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,048

Re: [SOLVED] User 1000 broken, can't login on TTY-1, can't start X

You're never gonna reach "exec awesome", so if picom fails your session ends there.
Edit: worse, the exec statement is bogus, likely some copypasta from an i3 config?

Last edited by seth (2024-01-24 20:28:17)

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#6 2024-01-24 21:22:18

vaace
Member
Registered: 2024-01-23
Posts: 4

Re: [SOLVED] User 1000 broken, can't login on TTY-1, can't start X

seth wrote:

You're never gonna reach "exec awesome", so if picom fails your session ends there.
Edit: worse, the exec statement is bogus, likely some copypasta from an i3 config?

The --no-startup-id part, yeah. The '-b' I took from picom's wiki page

Offline

#7 2024-01-24 21:32:43

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,048

Re: [SOLVED] User 1000 broken, can't login on TTY-1, can't start X

So what's the result if you comment that line?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#8 2024-01-24 21:40:19

vaace
Member
Registered: 2024-01-23
Posts: 4

Re: [SOLVED] User 1000 broken, can't login on TTY-1, can't start X

seth wrote:

You're never gonna reach "exec awesome", so if picom fails your session ends there.
Edit: worse, the exec statement is bogus, likely some copypasta from an i3 config?

Well, I'll be damned. You were on point, sir!
Never would've thought that was the actual reason, given that I managed to boot several times without a hitch with this line present.

Marking this as solved!

edit: Oh, right. I changed it to

exec picom &

and it worked like a charm. Thank you so much!

Last edited by vaace (2024-01-24 21:41:35)

Offline

#9 2024-01-24 22:11:13

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,048

Re: [SOLVED] User 1000 broken, can't login on TTY-1, can't start X

The exec there won't harm anymore (b/c of the forking "&") but is still pointless, remove it.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

Pages: 1

Board footer

Powered by FluxBB