Monday, April 29, 2024
 Popular · Latest · Hot · Upcoming
2
rated 0 times [  2] [ 0]  / answers: 1 / hits: 817  / 2 Years ago, mon, january 31, 2022, 11:19:28

I found out that user 109 launches pulseaudio on startup, which blocks mine:



petr@sova:~$ ps -ef | grep pulseaudio
109 1515 1 1 15:23 ? 00:00:00 /usr/bin/pulseaudio --start --log-target=syslog
petr 2344 1 0 15:24 ? 00:00:00 /usr/bin/pulseaudio --start --log-target=syslog
petr 2807 2757 0 15:24 pts/1 00:00:00 grep --color=auto pulseaudio


Because of that, I can't access the sound card and get dummy outputs only. Once I kill the 109's process, everything works fine.



Who is user 109 and how do I prevent him from launching pulseaudio? My suspicion is that it's somehow connected to LightDM.



EDIT:



petr@sova:~$ cat /etc/passwd | grep 109
speech-dispatcher:x:109:29:Speech Dispatcher,,,:/var/run/speech-dispatcher:/bin/sh

More From » 13.04

 Answers
4

You can check the file /etc/passwd to find out the username.



$ cat /etc/passwd | grep 109
speech-dispatcher:x:109:29:Speech Dispatcher,,,:/var/run/speech-dispatcher:/bin/sh


This tells us that user id 109 corresponds with the username 'speech-dispatcher'. This user's home directory is '/var/run/speech-dispatcher'.



There's also a package speed-dispatcher. It provides a high-level interface to Text-to-Speech systems according to its homepage, so it seems logical a program using this interface needs access to pulseaudio.



Find out what program is using speed-dispatcher and why it's spawning its own pulseaudio session.



Going from the links above I'd start looking at the configuration of desktop accessibility related applications.


[#31273] Wednesday, February 2, 2022, 2 Years  [reply] [flag answer]
Only authorized users can answer the question. Please sign in first, or register a free account.
lawain

Total Points: 150
Total Questions: 106
Total Answers: 101

Location: China
Member since Mon, Aug 22, 2022
2 Years ago
;