From: Pierre Neidhardt <ambrevar@gmail.com>
To: Chris Marusich <cmmarusich@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Multiple pulseaudio process after re-loging
Date: Sun, 20 May 2018 14:55:24 +0200 [thread overview]
Message-ID: <87zi0upjur.fsf@gmail.com> (raw)
In-Reply-To: <87in8d2u27.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1122 bytes --]
I've investigated further to come up with a more precise recipe:
- Start the machine afresh.
- Log in, play some music, everything is fine (only one pulseaudio
process, no crackles.)
- Log out and relog _as fast as possible_ (if possible, enter the
credentials in SLiM in less than 2-3 seconds).
- 4 pulseaudio processes are up. Sound is crackling when not playing
anything. It stops crackling when I play something.
- Log out again and relog (no need to be fast). This time only one
process is up but the sound is still crackling. Killing the process
fixes it.
- On subsequent logouts+logins, the issue does not seem to be
reproducible. I have to reboot.
Another clue:
After a fresh boot, the first time I log out I can see from a TTY that 3
pulseaudio processes are now running.
If I wait some seconds, they all eventually die and I can login without
sound issue.
Subsequent logouts won't spawn those 3 processes.
If however I follow the above receipe and log back in fast enough, an
additional process is spawned (which is normal) but the 3 processes remain.
Puzzling...
--
Pierre Neidhardt
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2018-05-20 12:55 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 [this message]
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
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=87zi0upjur.fsf@gmail.com \
--to=ambrevar@gmail.com \
--cc=cmmarusich@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.