Control: tags -1 moreinfo On Sun, Nov 17, 2019, 19:18 Eduard Bloch <e...@gmx.de> wrote:
> Package: pulseaudio > Version: 13.0-3 > Severity: normal > > $ systemctl --user |grep failed > ● pulseaudio.service > loaded failed failed Sound Service > ● pulseaudio.socket > loaded failed failed Sound System > $ systemctl --user status pulseaudio.service > ● pulseaudio.service - Sound Service > Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; > vendor preset: enabled) > Active: failed (Result: exit-code) since Sun 2019-11-17 23:02:42 CET; > 4min 54s ago > Process: 21056 ExecStart=/usr/bin/pulseaudio --daemonize=no > (code=exited, status=1/FAILURE) > Main PID: 21056 (code=exited, status=1/FAILURE) > $ sudo journalctl --user -u pulseaudio > No journal files were found. > -- No entries -- > $ systemctl --user restart pulseaudio > Job for pulseaudio.service failed because the control process exited with > error code. > See "systemctl --user status pulseaudio.service" and "journalctl --user > -xe" for details. > $ systemctl --user status pulseaudio.service > ● pulseaudio.service - Sound Service > Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; > vendor preset: enabled) > Active: failed (Result: exit-code) since Sun 2019-11-17 23:10:32 CET; > 13s ago > Process: 21409 ExecStart=/usr/bin/pulseaudio --daemonize=no > (code=exited, status=1/FAILURE) > Main PID: 21409 (code=exited, status=1/FAILURE) > $ journalctl --user -xe > No journal files were found. > > Am I missing something? How to debug this? > You need to access the journal as root (or add yourself to the systemd-journal group). Please get the logs for the user units (both the service and the socket). Also, have you edited any pulseaudio configuration file? Saludos