All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: perex@perex.cz, tiwai@suse.com, alsa-devel@alsa-project.org
Subject: 4.14-rc2: audio stopped working?
Date: Fri, 29 Sep 2017 13:25:18 +0200	[thread overview]
Message-ID: <20170929112518.GA15736@amd> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 511 bytes --]

Hi!

I've had sound problems in chromium for long long time. It produces
choppy auduo just after boot and then it works, probably after
chromium restart. May have something to do with pulseaudio. Not sure.

Anyway... sound in flightgear usually worked, and now it does
not. mplayer works, chromium works (sometimes choppy, as usual).

Any ideas?
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



             reply	other threads:[~2017-09-29 11:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-29 11:25 Pavel Machek [this message]
2017-09-29 18:15 ` 4.14-rc2: audio stopped working? Pavel Machek

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=20170929112518.GA15736@amd \
    --to=pavel@ucw.cz \
    --cc=alsa-devel@alsa-project.org \
    --cc=perex@perex.cz \
    --cc=tiwai@suse.com \
    /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.
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.