two pulseaudio processes

classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

two pulseaudio processes

rgfoiugztfgvbhjk
Hi,

I am using Pulseaudio in testing.

Playing sound through the laptop built-in sound card is working fine.
But I also have a Bluetooth Headset (Phillips SHB9100), This is where the Problems occur.

root@schenker:/home/ich# ps aux | grep pulse
Debian-+  1266  0.0  0.0 590568  1652 ?        S<l  Nov24   0:00 /usr/bin/pulseaudio --start --log-target=syslog
Debian-+  1273  0.0  0.0 122664     0 ?        S    Nov24   0:00 /usr/lib/pulseaudio/pulse/gconf-helper
ich       1456  0.1  0.1 589100  4960 ?        S<l  Nov24   4:13 /usr/bin/pulseaudio --start --log-target=syslog
ich       1479  0.0  0.0 122664     0 ?        S    Nov24   0:00 /usr/lib/pulseaudio/pulse/gconf-helper
root     10111  0.0  0.0  11132   880 pts/0    S+   13:09   0:00 grep pulse

There are two pulseaudio processes, one for me, and one for "Debian-+", a user I couldnt find any notice of anywhere, neither in /etc/passwd, nor on the Internet. (Did you know you can't Google for "Debian-+"?).

This Situation has been like this for quite some time, but I could just kill the Debian-+ pulse Process, and Instantly my Headphones would work via bluetooth and show up in the Pavucontrol.

But since maybe a week or so this changed, so now a new Pulseaudio Process is started the moment I kill the old one:

root@schenker:/home/ich# ps aux | grep pulse
Debian-+  1266  0.0  0.0 590568  1652 ?        S<l  Nov24   0:00 /usr/bin/pulseaudio --start --log-target=syslog
Debian-+  1273  0.0  0.0 122664     0 ?        S    Nov24   0:00 /usr/lib/pulseaudio/pulse/gconf-helper
ich       1456  0.1  0.1 589100  4960 ?        S<l  Nov24   4:13 /usr/bin/pulseaudio --start --log-target=syslog
ich       1479  0.0  0.0 122664     0 ?        S    Nov24   0:00 /usr/lib/pulseaudio/pulse/gconf-helper
root     10111  0.0  0.0  11132   880 pts/0    S+   13:09   0:00 grep pulse
root@schenker:/home/ich# kill 1266
root@schenker:/home/ich# ps aux | grep pulse
ich       1456  0.1  0.1 589100  5956 ?        S<l  Nov24   4:21 /usr/bin/pulseaudio --start --log-target=syslog
ich       1479  0.0  0.0 122664     0 ?        S    Nov24   0:00 /usr/lib/pulseaudio/pulse/gconf-helper
Debian-+ 10382  0.2  0.1 358088  7456 ?        S<l  13:16   0:00 /usr/bin/pulseaudio --start --log-target=syslog
Debian-+ 10384  0.0  0.1 122664  5072 ?        S    13:16   0:00 /usr/lib/pulseaudio/pulse/gconf-helper
root     10395  0.0  0.0  11132   932 pts/0    S+   13:16   0:00 grep pulse

The connection to the Headphones still gets lost shortly (beep), but then it does not connect with my pulseaudio process (at least not always, maybe sometimes).

Does anybody know who Debian-+ is, why he is starting pulseaudio and using my headsets, and if this is a bug that should be reported against pulseaudio or something else?

Thanks for your help.

Reply | Threaded
Open this post in threaded view
|

Re: two pulseaudio processes

cbannister
On Thu, Nov 26, 2015 at 01:22:25PM +0100, rgfoiugztfgvbhjk wrote:
> Does anybody know who Debian-+ is, why he is starting pulseaudio and
> using my headsets, and if this is a bug that should be reported
> against pulseaudio or something else?

If you purge pulseaudio, does everything work as you want?

If you actually need pulseaudio, then I'd report the bug against the
pulseaudio package.

--
"If you're not careful, the newspapers will have you hating the people
who are being oppressed, and loving the people who are doing the
oppressing." --- Malcolm X

Reply | Threaded
Open this post in threaded view
|

Re: two pulseaudio processes

Gabriel Corona-2
In reply to this post by rgfoiugztfgvbhjk
> Does anybody know who Debian-+ is, why he is starting pulseaudio and
> using my headsets, and if this is a bug that should be reported
> against pulseaudio or something else?

"Debian-+" is used by ps to tell you that the the user name was
truncated and beginning with "Debian-":

$ ps -O user,uid,sid -e | grep pulse | grep Debian
 1137 Debian-+   115  1136 S ?        00:00:00 /usr/bin/pulseaudio --start --log-target=syslog
 1149 Debian-+   115  1136 S ?        00:00:00 /usr/lib/pulseaudio/pulse/gconf-helper

The user is Debian-gdm which is used by Debian for GDM:

$ cat /etc/passwd | grep 115
Debian-gdm:x:115:122:Gnome Display Manager:/var/lib/gdm3:/bin/false

On my machine (testing), those two processes are the only remaining
parts of a session of Debian-gdm. I'm not sure if this is a bug of
pulseaudio, gdm, logind or something else.

--
Gabriel

Reply | Threaded
Open this post in threaded view
|

Re: two pulseaudio processes

Mart van de Wege
In reply to this post by rgfoiugztfgvbhjk
rgfoiugztfgvbhjk <[hidden email]> writes:

> Hi,
>
> I am using Pulseaudio in testing.
>
> Playing sound through the laptop built-in sound card is working fine.
> But I also have a Bluetooth Headset (Phillips SHB9100), This is where the Problems occur.
>
> root@schenker:/home/ich# ps aux | grep pulse
> Debian-+ 1266 0.0 0.0 590568 1652 ?  S<l Nov24 0:00
> /usr/bin/pulseaudio --start --log-target=syslog
> Debian-+ 1273 0.0 0.0 122664 0 ?  S Nov24 0:00
> /usr/lib/pulseaudio/pulse/gconf-helper
> ich 1456 0.1 0.1 589100 4960 ?  S<l Nov24 4:13 /usr/bin/pulseaudio
> --start --log-target=syslog
> ich 1479 0.0 0.0 122664 0 ?  S Nov24 0:00
> /usr/lib/pulseaudio/pulse/gconf-helper
> root     10111  0.0  0.0  11132   880 pts/0    S+   13:09   0:00 grep pulse
>
> There are two pulseaudio processes, one for me, and one for
> "Debian-+", a user I couldnt find any notice of anywhere, neither in
> /etc/passwd, nor on the Internet. (Did you know you can't Google for
> "Debian-+"?).
>
Here's a tip to find usernames that ps truncates:

getent passwd | grep <username>

If I do that on my box, I find Debian-exim and Debian-gdm.

Can you do the same on your box and see what you get? If you get the
same, then I suspect that Debian-gdm is starting your pulse process for
you. I wonder if that is not a bug, as pulse should run as a user,
AFAIK.

Mart

--
"We will need a longer wall when the revolution comes."
    --- AJS, quoting an uncertain source.

Reply | Threaded
Open this post in threaded view
|

Re: two pulseaudio processes

David Wright-3
On Fri 27 Nov 2015 at 11:57:22 (+0100), Mart van de Wege wrote:

> rgfoiugztfgvbhjk <[hidden email]> writes:
> > I am using Pulseaudio in testing.
> >
> > Playing sound through the laptop built-in sound card is working fine.
> > But I also have a Bluetooth Headset (Phillips SHB9100), This is where the Problems occur.
> >
> > root@schenker:/home/ich# ps aux | grep pulse
> > Debian-+ 1266 0.0 0.0 590568 1652 ?  S<l Nov24 0:00
> > /usr/bin/pulseaudio --start --log-target=syslog
> > Debian-+ 1273 0.0 0.0 122664 0 ?  S Nov24 0:00
> > /usr/lib/pulseaudio/pulse/gconf-helper
> > ich 1456 0.1 0.1 589100 4960 ?  S<l Nov24 4:13 /usr/bin/pulseaudio
> > --start --log-target=syslog
> > ich 1479 0.0 0.0 122664 0 ?  S Nov24 0:00
> > /usr/lib/pulseaudio/pulse/gconf-helper
> > root     10111  0.0  0.0  11132   880 pts/0    S+   13:09   0:00 grep pulse
> >
> > There are two pulseaudio processes, one for me, and one for
> > "Debian-+", a user I couldnt find any notice of anywhere, neither in
> > /etc/passwd, nor on the Internet. (Did you know you can't Google for
> > "Debian-+"?).
> >
> Here's a tip to find usernames that ps truncates:
>
> getent passwd | grep <username>
>
> If I do that on my box, I find Debian-exim and Debian-gdm.
>
> Can you do the same on your box and see what you get? If you get the
> same, then I suspect that Debian-gdm is starting your pulse process for
> you. I wonder if that is not a bug, as pulse should run as a user,
> AFAIK.

Alternatively, give ps some elbow-room as in

$ ps -A -o user:20,cmd

man ps is useful, though somewhat confusing because of the variety of
option styles available.

Cheers,
David.

Reply | Threaded
Open this post in threaded view
|

Re: two pulseaudio processes

Mart van de Wege
In reply to this post by cbannister
Chris Bannister <[hidden email]> writes:

> On Thu, Nov 26, 2015 at 01:22:25PM +0100, rgfoiugztfgvbhjk wrote:
>> Does anybody know who Debian-+ is, why he is starting pulseaudio and
>> using my headsets, and if this is a bug that should be reported
>> against pulseaudio or something else?
>
> If you purge pulseaudio, does everything work as you want?
>

Look, either there is a bug in play here or a misconfiguration. Purging
pulseaudio is merely papering over a problem, it's not a solution.

> If you actually need pulseaudio, then I'd report the bug against the
> pulseaudio package.

Given that parent apparently wants to be able to switch between normal
sound output and a headset, I'd say it is fairly obvious there is a need
for pulseaudio, as that is one of its use cases.

Mart

--
"We will need a longer wall when the revolution comes."
    --- AJS, quoting an uncertain source.

Reply | Threaded
Open this post in threaded view
|

Re: two pulseaudio processes

cbannister
On Sat, Nov 28, 2015 at 12:33:33PM +0100, Mart van de Wege wrote:

> Chris Bannister <[hidden email]> writes:
>
> > On Thu, Nov 26, 2015 at 01:22:25PM +0100, rgfoiugztfgvbhjk wrote:
> >> Does anybody know who Debian-+ is, why he is starting pulseaudio and
> >> using my headsets, and if this is a bug that should be reported
> >> against pulseaudio or something else?
> >
> > If you purge pulseaudio, does everything work as you want?
> >
>
> Look, either there is a bug in play here or a misconfiguration. Purging
> pulseaudio is merely papering over a problem, it's not a solution.

Listen, sound was working fine for me but after an upgrade sound stopped
working. I found pulseaudio installed so I purged it and sound worked
again, so sorry but it is a solution.

> > If you actually need pulseaudio, then I'd report the bug against the
> > pulseaudio package.
>
> Given that parent apparently wants to be able to switch between normal
> sound output and a headset, I'd say it is fairly obvious there is a need
> for pulseaudio, as that is one of its use cases.

*sigh* I can listen to audio via a headset or the internal speakers
without pulseaudio so I don't know what you are implying.

--
"If you're not careful, the newspapers will have you hating the people
who are being oppressed, and loving the people who are doing the
oppressing." --- Malcolm X

Reply | Threaded
Open this post in threaded view
|

Re: two pulseaudio processes

rgfoiugztfgvbhjk
In reply to this post by Gabriel Corona-2
Hi, thanks a lot for your answers.

In fact, it is a bug in gdm3, #805414 ( https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805414 ) to be precise.
And what to do to work around it is described here: https://wiki.debian.org/BluetoothUser/a2dp
I wrote the /var/lib/gdm3/.config/pulse/client.conf file, and now my headset works the moment it is turned on


On 11/27/15 09:55, Gabriel Corona wrote:

>> Does anybody know who Debian-+ is, why he is starting pulseaudio and
>> using my headsets, and if this is a bug that should be reported
>> against pulseaudio or something else?
>
> "Debian-+" is used by ps to tell you that the the user name was
> truncated and beginning with "Debian-":
>
> $ ps -O user,uid,sid -e | grep pulse | grep Debian
>  1137 Debian-+   115  1136 S ?        00:00:00 /usr/bin/pulseaudio --start --log-target=syslog
>  1149 Debian-+   115  1136 S ?        00:00:00 /usr/lib/pulseaudio/pulse/gconf-helper
>
> The user is Debian-gdm which is used by Debian for GDM:
>
> $ cat /etc/passwd | grep 115
> Debian-gdm:x:115:122:Gnome Display Manager:/var/lib/gdm3:/bin/false
>
> On my machine (testing), those two processes are the only remaining
> parts of a session of Debian-gdm. I'm not sure if this is a bug of
> pulseaudio, gdm, logind or something else.
>

Reply | Threaded
Open this post in threaded view
|

Re: two pulseaudio processes

Mart van de Wege
In reply to this post by cbannister
Chris Bannister <[hidden email]> writes:

> On Sat, Nov 28, 2015 at 12:33:33PM +0100, Mart van de Wege wrote:
>> Chris Bannister <[hidden email]> writes:
>>
>> > On Thu, Nov 26, 2015 at 01:22:25PM +0100, rgfoiugztfgvbhjk wrote:
>> >> Does anybody know who Debian-+ is, why he is starting pulseaudio and
>> >> using my headsets, and if this is a bug that should be reported
>> >> against pulseaudio or something else?
>> >
>> > If you purge pulseaudio, does everything work as you want?
>> >
>>
>> Look, either there is a bug in play here or a misconfiguration. Purging
>> pulseaudio is merely papering over a problem, it's not a solution.
>
> Listen, sound was working fine for me but after an upgrade sound stopped
> working. I found pulseaudio installed so I purged it and sound worked
> again, so sorry but it is a solution.
>

And OP has no problem with sound under pulseaudio, as long as there is
only one instance running. Since there is supposed to be only one
instance, blindly purging pulseaudio is cargo-cult troubleshooting.

>> > If you actually need pulseaudio, then I'd report the bug against the
>> > pulseaudio package.
>>
>> Given that parent apparently wants to be able to switch between normal
>> sound output and a headset, I'd say it is fairly obvious there is a need
>> for pulseaudio, as that is one of its use cases.
>
> *sigh* I can listen to audio via a headset or the internal speakers
> without pulseaudio so I don't know what you are implying.

With a bluetooth headset like OP? I doubt it.

I am not implying, I am stating right out you are projecting an
irrational dislike of pulseaudio on OPs problem, which is *NOT* helpful.

Mart

--
"We will need a longer wall when the revolution comes."
    --- AJS, quoting an uncertain source.