From: Pat Suwalski <pat@suwalski.net>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: Werner Almesberger <wa@almesberger.net>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Jamie Lokier <jamie@shareable.org>,
Matthias Schniedermeyer <ms@citd.de>,
Marc Giger <gigerstyle@gmx.ch>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Bug 623] New: Volume not remembered.
Date: Fri, 25 Apr 2003 20:31:41 -0400 [thread overview]
Message-ID: <3EA9D36D.5030104@suwalski.net> (raw)
In-Reply-To: <427040000.1051293569@[10.10.2.4]>
Martin J. Bligh wrote:
> BTW, I realised there's a much simpler solution to the "but there's no
> sound coming out" problem .... xmms and friends should just give the user a
> warning on startup (or on play) if the main volume or pcm channel is at 0
> (or muted).
No. This never happens.
It only complains if it its OSS output plugin cannot communicate with
the kernel.
At least on all the cards I have ever used.
--Pat
next prev parent reply other threads:[~2003-04-26 0:17 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-23 16:23 [Bug 623] New: Volume not remembered Martin J. Bligh
2003-04-23 16:32 ` Marc Giger
2003-04-23 16:45 ` Matthias Schniedermeyer
2003-04-23 16:56 ` Martin J. Bligh
2003-04-23 17:21 ` Matthias Schniedermeyer
2003-04-23 13:26 ` Pat Suwalski
2003-04-23 17:26 ` Martin J. Bligh
2003-04-23 17:45 ` Disconnect
2003-04-23 17:47 ` Matthias Schniedermeyer
2003-04-23 18:44 ` Martin J. Bligh
2003-04-23 17:49 ` Pat Suwalski
2003-04-23 18:56 ` Jörn Engel
2003-04-23 22:17 ` Pavel Machek
2003-04-23 22:35 ` Pat Suwalski
2003-04-23 22:55 ` Pavel Machek
2003-04-24 2:19 ` Werner Almesberger
2003-04-24 2:29 ` Pat Suwalski
2003-04-24 2:34 ` Ben Collins
2003-04-24 7:22 ` Jamie Lokier
2003-04-24 13:31 ` Werner Almesberger
2003-04-24 4:30 ` Valdis.Kletnieks
2003-04-23 23:15 ` Martin J. Bligh
2003-04-23 21:34 ` Werner Almesberger
2003-04-23 21:36 ` Martin J. Bligh
2003-04-23 22:14 ` Werner Almesberger
2003-04-23 22:18 ` Martin J. Bligh
2003-04-23 22:55 ` Werner Almesberger
2003-04-24 0:11 ` Jamie Lokier
2003-04-24 0:43 ` Werner Almesberger
2003-04-24 1:11 ` Jamie Lokier
2003-04-24 1:18 ` Martin J. Bligh
2003-04-24 1:22 ` Pat Suwalski
2003-04-24 2:11 ` Werner Almesberger
2003-04-24 2:40 ` Martin J. Bligh
2003-04-24 3:37 ` Werner Almesberger
2003-04-24 4:47 ` Martin J. Bligh
2003-04-24 13:16 ` Werner Almesberger
2003-04-24 7:14 ` Jamie Lokier
2003-04-24 13:38 ` Werner Almesberger
2003-04-24 13:49 ` Matthias Schniedermeyer
2003-04-24 14:08 ` Pat Suwalski
2003-04-24 14:34 ` Matthias Schniedermeyer
2003-04-24 15:04 ` Werner Almesberger
2003-04-24 15:23 ` Matthias Schniedermeyer
2003-04-24 16:01 ` Werner Almesberger
2003-04-24 16:26 ` Jaroslav Kysela
2003-04-24 21:22 ` Werner Almesberger
2003-04-25 10:03 ` Jaroslav Kysela
2003-04-25 10:30 ` Werner Almesberger
2003-04-24 21:36 ` Jamie Lokier
2003-04-24 23:55 ` Werner Almesberger
2003-04-25 0:05 ` Pat Suwalski
2003-04-25 10:41 ` Werner Almesberger
2003-04-25 10:04 ` Alan Cox
2003-04-25 17:44 ` Werner Almesberger
2003-04-25 17:59 ` Martin J. Bligh
2003-04-26 0:31 ` Pat Suwalski [this message]
2003-04-24 22:51 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2003-04-24 0:31 Ian Kumlien
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=3EA9D36D.5030104@suwalski.net \
--to=pat@suwalski.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=gigerstyle@gmx.ch \
--cc=jamie@shareable.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.com \
--cc=ms@citd.de \
--cc=wa@almesberger.net \
/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.