From: Oleg Pykhalov <go.wigust@gmail.com>
To: Pierre Neidhardt <ambrevar@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Multiple pulseaudio process after re-loging
Date: Wed, 06 Jun 2018 12:33:54 +0300 [thread overview]
Message-ID: <87po14ntrx.fsf@gmail.com> (raw)
In-Reply-To: <87zi0c59fo.fsf@gmail.com> (Pierre Neidhardt's message of "Sun, 03 Jun 2018 14:41:31 +0200")
[-- Attachment #1: Type: text/plain, Size: 965 bytes --]
Hello Pierre,
Pierre Neidhardt <ambrevar@gmail.com> writes:
[…]
> I'd put the blame on conky / Pulseaudio for now :)
I have a different Pulseaudio behavior. Sometimes I use a program which
does not use Pulseaudio but Alsa, then I need to start Pulseaudio
manually if there is no program which produces a sound, e.g. with
‘pulsemixer’. In ‘pulsemixer’ I'll have ‘PROGRAM_NAME: AudioStream’
string after launching Alsa only program, which means I can contol Alsa
only program with Pulseaudio. If I don't run Pulseaudio manually, then
Alsa only program will still a device until the program will be killed.
I don't use any desktop environment, which usually run Pulseaudio
automatically as I know.
Does Conky show you a Pulseaudio current volume? Conky probably runs
Pulseaudio to do it. Also, it will be better to test a Pulseaudio
behavior in a clean environment, e.g. by using a window manager like
Ratpoison.
Oleg.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2018-06-06 9:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-23 6:40 Multiple pulseaudio process after re-loging Pierre Neidhardt
2018-04-23 18:43 ` Leo Famulari
2018-04-24 6:33 ` Pierre Neidhardt
2018-04-27 3:43 ` Chris Marusich
2018-05-20 12:55 ` Pierre Neidhardt
2018-05-20 13:43 ` Pierre Neidhardt
2018-06-03 1:07 ` Chris Marusich
2018-06-03 12:41 ` Pierre Neidhardt
2018-06-06 9:33 ` Oleg Pykhalov [this message]
2018-06-06 9:37 ` Pierre Neidhardt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87po14ntrx.fsf@gmail.com \
--to=go.wigust@gmail.com \
--cc=ambrevar@gmail.com \
--cc=help-guix@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.