-
-
Notifications
You must be signed in to change notification settings - Fork 4.4k
Systemd-logind fails #39012
Copy link
Copy link
Closed
Labels
bug 🐛Programming errors, that need preferential fixingProgramming errors, that need preferential fixingloginneeds-reporter-feedback ❓There's an unanswered question, the reporter needs to answerThere's an unanswered question, the reporter needs to answer
Description
systemd version the issue has been seen with
258
Used distribution
Arch Linux
Linux kernel version used
6.16.7-zen1-1-zen
CPU architectures issue was seen on
x86_64
Component
loginctl, systemd
Expected behaviour you didn't see
Systemd-logind starts normally.
It allows Hyprland to start normally.
Unexpected behaviour you saw
Systemd-logind fails due to missing directories in /run after update from 257.9 to 258.
Due to this, Hyprland is unable to start.
Steps to reproduce the problem
Install systemd 258.
Regenerate initramfs and reboot.
Open journal logs.
Also, if running Hyprland, it fails.
Simply downgrading systemd to 257.9 solves the issue and errors from systemd-logind without any other action.
Additional program output to the terminal or log subsystem illustrating the issue
Sep 18 19:59:26 arch-laptop bluetoothd[2347]: profiles/audio/bap.c:bap_adapter_probe() BAP requires ISO Socket which is not enabled
Sep 18 19:59:26 arch-laptop bluetoothd[2347]: bap: Operation not supported (95)
Sep 18 19:59:26 arch-laptop bluetoothd[2347]: Failed to set mode: Rejected (0x0b)
Sep 18 19:59:26 arch-laptop bluetoothd[2347]: Failed to set privacy: Rejected (0x0b)
Sep 18 19:59:27 arch-laptop systemd-logind[2358]: Failed to move '/run/systemd/seats/seat0' into place: No such file or directory
Sep 18 19:59:28 arch-laptop systemd-logind[2358]: Failed to move '/run/systemd/users/968' into place: No such file or directory
Sep 18 19:59:28 arch-laptop systemd-logind[2358]: Failed to move '/run/systemd/users/968' into place: No such file or directory
Sep 18 19:59:28 arch-laptop systemd-logind[2358]: Failed to move '/run/systemd/seats/seat0' into place: No such file or directory
Sep 18 19:59:28 arch-laptop systemd-logind[2358]: Failed to move '/run/systemd/sessions/c1' into place: No such file or directory
Sep 18 19:59:28 arch-laptop systemd-logind[2358]: Failed to move '/run/systemd/users/968' into place: No such file or directory
Sep 18 19:59:28 arch-laptop systemd-logind[2358]: Failed to move '/run/systemd/seats/seat0' into place: No such file or directory
Sep 18 19:59:28 arch-laptop systemd-logind[2358]: Failed to move '/run/systemd/users/968' into place: No such file or directory
Sep 18 19:59:28 arch-laptop systemd-logind[2358]: Failed to move '/run/systemd/sessions/c1' into place: No such file or directory
Sep 18 19:59:28 arch-laptop systemd-logind[2358]: Failed to move '/run/systemd/users/968' into place: No such file or directory
Sep 18 19:59:28 arch-laptop systemd-logind[2358]: Failed to move '/run/systemd/sessions/1' into place: No such file or directory
Sep 18 19:59:28 arch-laptop systemd-logind[2358]: Failed to move '/run/systemd/users/968' into place: No such file or directory
Sep 18 19:59:28 arch-laptop systemd-logind[2358]: Failed to move '/run/systemd/users/968' into place: No such file or directory
Sep 18 19:59:28 arch-laptop systemd-logind[2358]: Failed to move '/run/systemd/sessions/c1' into place: No such file or directory
Sep 18 19:59:28 arch-laptop systemd-logind[2358]: Failed to move '/run/systemd/users/968' into place: No such file or directory
Sep 18 19:59:33 arch-laptop systemd-logind[2358]: Failed to move '/run/systemd/seats/seat0' into place: No such file or directory
Sep 18 19:59:33 arch-laptop systemd-logind[2358]: Failed to move '/run/systemd/users/968' into place: No such file or directory
Sep 18 19:59:33 arch-laptop systemd-logind[2358]: Failed to move '/run/systemd/sessions/c1' into place: No such file or directory
Sep 18 19:59:44 arch-laptop systemd-logind[2358]: Failed to move '/run/systemd/users/1000' into place: No such file or directory
Sep 18 19:59:44 arch-laptop systemd-logind[2358]: Failed to move '/run/systemd/users/1000' into place: No such file or directory
Sep 18 19:59:44 arch-laptop systemd-logind[2358]: Failed to move '/run/systemd/seats/seat0' into place: No such file or directory
Sep 18 19:59:44 arch-laptop systemd-logind[2358]: Failed to move '/run/systemd/sessions/2' into place: No such file or directory
Sep 18 19:59:44 arch-laptop systemd-logind[2358]: Failed to move '/run/systemd/users/1000' into place: No such file or directory
Sep 18 19:59:44 arch-laptop systemd-logind[2358]: Failed to move '/run/systemd/seats/seat0' into place: No such file or directory
Sep 18 19:59:44 arch-laptop systemd-logind[2358]: Failed to move '/run/systemd/users/1000' into place: No such file or directory
Sep 18 19:59:44 arch-laptop systemd-logind[2358]: Failed to move '/run/systemd/sessions/2' into place: No such file or directory
Sep 18 19:59:44 arch-laptop systemd-logind[2358]: Failed to move '/run/systemd/users/1000' into place: No such file or directory
Sep 18 19:59:44 arch-laptop systemd-logind[2358]: Failed to move '/run/systemd/sessions/3' into place: No such file or directory
Sep 18 19:59:44 arch-laptop systemd-logind[2358]: Failed to move '/run/systemd/users/1000' into place: No such file or directory
Sep 18 19:59:45 arch-laptop systemd-logind[2358]: Failed to move '/run/systemd/users/1000' into place: No such file or directory
Sep 18 19:59:45 arch-laptop systemd-logind[2358]: Failed to move '/run/systemd/sessions/2' into place: No such file or directory
Sep 18 19:59:45 arch-laptop systemd-logind[2358]: Failed to move '/run/systemd/users/1000' into place: No such file or directory
Sep 18 20:00:10 arch-laptop systemd-coredump[3317]: Process 3305 (Hyprland) of user 1000 terminated abnormally without generating a coredump.Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bug 🐛Programming errors, that need preferential fixingProgramming errors, that need preferential fixingloginneeds-reporter-feedback ❓There's an unanswered question, the reporter needs to answerThere's an unanswered question, the reporter needs to answer