* Juha Jäykkä [2016-12-22 21:30 +]:
> > > So in short, it's either all or nothing? I.e. if I want *some* programs,
> > > which are linked against libpulse0,
> > Hmm, are there applications which need pulseaudio to work? I do have
>
> There are, but probably best not mentioned aloud lest Stal
> > So in short, it's either all or nothing? I.e. if I want *some* programs,
> > which are linked against libpulse0,
> Hmm, are there applications which need pulseaudio to work? I do have
There are, but probably best not mentioned aloud lest Stallman smites us. :)
> a system which works fine with
* Juha Jäykkä [2016-12-22 20:30 +]:
> > > > I think the only chance to run alsamixer without starting pulse is
> > > > to pulseaudio -k and autospawn pulse.
> > > Is this not a bug?
> > Starting pulseaudio automagic is a feature implemented in pulseaudio;-)
>
> So in short, it's either all o
> > > I think the only chance to run alsamixer without starting pulse is
> > > to pulseaudio -k and autospawn pulse.
> > Is this not a bug?
> Starting pulseaudio automagic is a feature implemented in pulseaudio;-)
So in short, it's either all or nothing? I.e. if I want *some* programs, which
are
* Juha Jäykkä [2016-12-21 21:21 +]:
> > I think the only chance to run alsamixer without starting pulse is
> > to pulseaudio -k and autospawn pulse.
>
> Is this not a bug?
Starting pulseaudio automagic is a feature implemented in pulseaudio;-)
Elimar
--
Numeric stability is probably not
> I think the only chance to run alsamixer without starting pulse is
> to pulseaudio -k and autospawn pulse.
Is this not a bug?
Cheers,
Juha
* Juha Jäykkä [2016-12-18 23:02 +]:
> > > I think pulseaudio gets started by libasound.so.2 when it parses
> > > alsa.conf.d because pulseaudio has placed the above file there.
> > If pulsaudio is installed it runs as a per user session by default.
>
> I think you might have misunderstood th
> > I think pulseaudio gets started by libasound.so.2 when it parses
> > alsa.conf.d because pulseaudio has placed the above file there.
> If pulsaudion is installed it runs as a per user session by default.
I think you might have misunderstood the problem. Disabling pulseaudio's
autospawn does n
* Juha Jäykkä [2016-11-26 19:09 +]:
[...]
> I think pulseaudio gets started by libasound.so.2 when it parses alsa.conf.d
> because pulseaudio has placed the above file there.
If pulsaudion is installed it runs as a per user session by default.
To prevent starting pulse just
$ echo "autospa
> What do you want to tell me here? It seems your pulseaudio
> installation is a bit buggy. I can't reproduce.
Apart from the bit about /usr/bin/pulseaudio being a script which simply
records that pulseaudio has been started and then execs /usr/bin/
pulseaudio.real, pulseaudio and alsamixer are p
Control: tags -1 unreproducible
* Juha Jäykkä [2016-11-20 18:15 +]:
> > alsamixer doesn't fire up any puls daemon. Please check whether
> > puls is running before starting alsamixer.
>
> It should not, but it certainly does:
>
> juhaj@meissa 18:07:16 ~> ps -flyu juhaj|grep pulseau
> S juha
> alsamixer doesn't fire up any puls daemon. Please check whether
> puls is running before starting alsamixer.
It should not, but it certainly does:
juhaj@meissa 18:07:16 ~> ps -flyu juhaj|grep pulseau
S juhaj 9740 9724 0 99 19 2204 3488 - 18:07 pts/400:00:00
grep pulseau
Toda
* Juha Jäykkä [2016-11-20 10:12 +]:
> Package: alsa-utils
> Version: 1.0.28-1
> Severity: normal
> File: /usr/bin/alsamixer
>
> Dear Maintainer,
>
> Running "alsamixer -c0" in order to adjust the ALSA mixer levels causes
> pulseaudio daemon to start. This is not just wrong and unexpected, b
Package: alsa-utils
Version: 1.0.28-1
Severity: normal
File: /usr/bin/alsamixer
Dear Maintainer,
Running "alsamixer -c0" in order to adjust the ALSA mixer levels causes
pulseaudio daemon to start. This is not just wrong and unexpected, but
also causes unwanted side-effects in other programs, like
14 matches
Mail list logo