You are not logged in.
Hi,
I borked my installation so I tried rolling back with snapper. After doing that, I got the errors in the title. I cannot even log in. How do I fix this? I can still share logs since /var/log is a different subvolume. Help is appreciated.
Edit: I can log in but now I'm stuck at a loading screen.
Last edited by fire100265 (2020-12-11 05:49:26)
Offline
Can someone please help me? My system doesn't work at all and nothing is helping.
Offline
boot to multi-user.target , see https://wiki.archlinux.org/index.php/Sy … _boot_into
login as root, post journalctl -b . see https://wiki.archlinux.org/index.php/Li … in_clients
Are you using X or wayland ?
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Thank you very much for your reply. I couldn't reply earlier because it was quite late in my country when you replied. Here's my journalctl: ix.io/2H5U . I use X, not Wayland.
Offline
What is the output of
SYSTEMD_LOG_LEVEL=debug /usr/lib/systemd/systemd-logindOffline
ix.io/2H61
Offline
logind succeeded but its strange that cgroup is not mounted, might be a side-effect of an earlier failure.
What is the output of:
mount
pacman -Qs linuxLast edited by loqs (2020-12-08 01:27:22)
Offline
Mount: ix.io/2H6b
pacman -Qs linux: ix.io/2H6d
Offline
Still not clear what the cause is. Please add the boot parameter systemd.log_level=debug while keeping systemd.unit=multi-user.target. this will produce a very verbose log. Post the output of `journalctl -b` from that boot, it may be too big for the pastebin.
Offline
I am very sorry but the file is too big for pastebin and just copying it here. What can I do?
Offline
Will the pastebin accept 1000 lines?
journalctl -b -1 -n 1000Offline
Yeah it does. Here's the link: ix.io/2H6S
Edit: should I just backup /home and reinstall? I'm not sure if the problem can even be discovered.
Last edited by fire100265 (2020-12-08 05:42:45)
Offline
At this point I think reinstalling is best. Should I do it? Is it still possible for you guys to help me?
Offline
Please have some patience.
When booting to multi-user you can log in and upload log files , so basic functionality is ok.
loqs asked that log for a reason, give him time to investigate it .
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
i am very sorry that i sound impatient. i am just worried about my pc.
Offline
The log unfortunately missed the start of boot and services were already being restarted.
Strange the log was flagged as malware http://ix.io/2H6S now returns paste removed (malware) (please dont do this)
Lone_Wolf any ideas?
Offline
A shot in the dark
# stat /
# stat /usr/lib/systemd/systemd-logindInofficial first vice president of the Rust Evangelism Strike Force
Offline
Strange the log was flagged as malware http://ix.io/2H6S now returns paste removed (malware) (please dont do this)
Still works for me, I've copied it to my pastebin account* , https://pastebin.com/2Z4AwqZ0
as for ideas :
test with a freshly created user to verify if this is systemwide or user-specific ?
* yes, I know it needs javascript enabled and often gives unwanted ads.
With noscript, ublock origin, canvasblocker and cookie autodelete it works fine for me.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
How did such a verbose log miss something? Anyway, here is stat /:
ix.io/2Her
Here is my stat logind:
ix.io/2Heo
I don't think it's a problem with users since root also cannot login in graphical.target. I can try though.
Edit: I got the same errors with the new user. Startx doesn't work for any user and no-one can login in graphical.target. I think these problems might be related to permissions since normal users cannot shutdown the pc while root can do it.
Last edited by fire100265 (2020-12-09 04:08:24)
Offline
I think these problems might be related to permissions since normal users cannot shutdown the pc while root can do it.
Those shutdown options for users are set in polkit and executed by systemd-logind .
create /etc/X11/Xwrapper.config with this content :
# Xorg.wrap configuration file
needs_root_rights = yesthen try startx -- -vt7 as user.
That should make sure X starts with root rights and logind integration is disabled .
post /var/log/Xorg.0.log .
Last edited by Lone_Wolf (2020-12-09 10:26:39)
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Thank you for your reply. I'm not sure if this is expected but I didn't get any windows. Here is my log:
ix.io/2HhA
Offline
I am very sorry for asking but is it better if I just reinstall Arch?
Edit: I feel that I should include the status of systemd-logind.service. here is the link:
ix.io/2Ho4
Last edited by fire100265 (2020-12-10 06:48:51)
Offline
Thank you very much to all of you who tried to help me. I think it's best to reinstall Arch with my /home backup. I'll mark the thread as Solved.
Offline
It does look like the problems run to deep to solve in a reasonable amount of time / effort.
Should something similar happen, it may be better to try to solve the issue before restoring a snapshot.
If the problems start after an update , downgrading may be a better option .
See https://wiki.archlinux.org/index.php/Do … g_packages
Edit: typos
Last edited by Lone_Wolf (2020-12-11 12:52:28)
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Thank you for trying to help me. The problem started after I ran rmlint on /. That was not a good idea at all and I only found out after running it.
Offline