Bei pipewire muss jemand anderes helfen, ich hab hier ein gut laufendes pulseaudio.
Da pipewire ja via
systemctl --user start pipewire
gestartet wird köönte es evtl. hieran liegen?
Code
test@Acer:/usr/lib/systemd/system/user@.service.d> systemctl --failed
UNIT LOAD ACTIVE SUB DESCRIPTION
● display-manager.service loaded failed failed X Display Manager
● user@1002.service loaded failed failed User Manager for UID 1002
● user@464.service loaded failed failed User Manager for UID 464
Wird der user@1002.service gebraucht um pipewire auszuführen?
Code
test@Acer:/usr/lib/systemd/system/user@.service.d> systemctl status user@1002.service
× user@1002.service - User Manager for UID 1002
Loaded: loaded (/usr/lib/systemd/system/user@.service; static)
Drop-In: /usr/lib/systemd/system/user@.service.d
└─10-login-barrier.conf, 20-defaults-SUSE.conf
Active: failed (Result: exit-code) since Wed 2024-09-18 17:04:27 CEST; 1h 39min ago
Docs: man:user@.service(5)
Process: 3615 ExecStart=/usr/lib/systemd/systemd --user (code=exited, status=224/PAM)
Main PID: 3615 (code=exited, status=224/PAM)
Sep 18 17:04:27 Acer systemd[1]: Starting User Manager for UID 1002...
Sep 18 17:04:27 Acer (systemd)[3615]: PAM failed: Authentication failure
Sep 18 17:04:27 Acer (systemd)[3615]: pam_warn(systemd-user:account): function=[pam_sm_acct_mgmt] flags=0x8000 service=[systemd-user] terminal=[<unknown>] user=[test] ruser=[<unknown>] rhost=[<unknown>]
Sep 18 17:04:27 Acer (systemd)[3615]: user@1002.service: Failed to set up PAM session: Operation not permitted
Sep 18 17:04:27 Acer (systemd)[3615]: user@1002.service: Failed at step PAM spawning /usr/lib/systemd/systemd: Operation not permitted
Sep 18 17:04:27 Acer systemd[1]: user@1002.service: Main process exited, code=exited, status=224/PAM
Sep 18 17:04:27 Acer systemd[1]: user@1002.service: Failed with result 'exit-code'.
Sep 18 17:04:27 Acer systemd[1]: Failed to start User Manager for UID 1002.
Alles anzeigen
Vielleicht kann hierzu jemand etwas sagen? Wo kann der Fehler liegen?
Gruß
Frank