I don't know how to see that process' logs. Maybe some magic journalctl
option. Is it possible that it's starting as a systemd user service?
Then `journalctl --user -eu pulseaudio` would work... But starting pulse
like that doesn't seem to work for me.
On 09/05/17 21:13, Mark Gardner wrote:
David,
On Tue, May 9, 2017 at 2:59 PM, David Izquierdo <theco...@gmail.com> wrote:
If you run `pulseaudio -k`, does it kill it?
No:
$ pulseaudio -k
E: [pulseaudio] main.c: Failed to kill daemon: No such process
But the daemon is running as me:
$ ps aux | grep pulseaudio
user
2572 0.0 0.0 490632 10540 ? Sl 14:55 0:00 /nix/store/
a72z0gasiv1145ygyijzgdra921pkk60-pulseaudio-10.0/bin/pulseaudio --start
--log-target=syslog
user
2604 0.0 0.0 118264 5756 ? S 14:55 0:00 /nix/store/
a72z0gasiv1145ygyijzgdra921pkk60-pulseaudio-10.0/libexec/pulse/gconf-helper
Once dead, what does it log if you run `pulseaudio` and then try to use
pavucontrol or other program?
I killed it by hand:
$ sudo kill 2572 2604
$ mpv foobar.mp3 # plays
$ pavucontrol # Works!
Going to try a reboot to see if it still works... Back to the previous
behavior until I kill them then start up something that uses pulseaudio.
Making progress. Thanks David.
Mark
_______________________________________________
nix-dev mailing list
nix-dev@lists.science.uu.nl
https://mailman.science.uu.nl/mailman/listinfo/nix-dev
