Your message dated 17 Nov 2001 21:36:19 -0500
with message-id <[EMAIL PROTECTED]>
and subject line fixed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 27 Dec 1998 20:47:24 +0000
Received: (qmail 15732 invoked from network); 27 Dec 1998 20:47:23 -0000
Received: from smtp6.teleport.com (192.108.254.45)
by master.debian.org with SMTP; 27 Dec 1998 20:47:23 -0000
Received: (qmail 7398 invoked from network); 27 Dec 1998 20:47:10 -0000
Received: from user1.teleport.com ([EMAIL PROTECTED])
by smtp6.teleport.com with SMTP; 27 Dec 1998 20:47:10 -0000
Received: (from [EMAIL PROTECTED])
by user1.teleport.com (8.8.7/8.8.4)
id MAA21222; Sun, 27 Dec 1998 12:47:10 -0800 (PST)
Date: Sun, 27 Dec 1998 12:47:10 -0800 (PST)
From: David Palmer <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Message-ID: <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Package: saytime
Version 1.0-5
PROBLEM
Running "saytime" results in a short "blurp" noise, then exists without
printing errors.
NOTE: This could be a driver bug; I'm not sure.
ENVIRONMENT
Intel x86 (Pentium 166MMX) computer
PCI Ensonic Soundscape audio card
Debian GNU/Linux 2.0 (stable)
Kernel 2.1.132 and 2.1.123 (unstable)
es1370.o sound driver (experimental)
No, I can't seem to get the OSS sscape.o module to work with my card
(sigh).
MORE INFO
x11amp and mpg123 work under both kernels. Thus, I suspect saytime is
broken.
I found that write() to /dev/audio returns EBUSY instead of 0 when
the output buffer is full. saytime.c expects to see a 0, and returns an
error message otherwise. Is this correct behaviour for the driver? I
know that saytime's use of write is poorly done.
Fixing this in saytime.c mostly solves the problem under 2.1.123, but not
under 2.1.132. If I knew which is at fault, I'd be happy to make a
patch for either es1370.c or saytime.c. It'd be fun. :+>
Dave
---------------------------------------
Received: (at 31214-done) by bugs.debian.org; 18 Nov 2001 02:35:37 +0000
>From [EMAIL PROTECTED] Sat Nov 17 20:35:37 2001
Return-path: <[EMAIL PROTECTED]>
Received: from sushi.toad.net [162.33.130.105]
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 165Ho1-0003Gd-00; Sat, 17 Nov 2001 20:35:37 -0600
Received: from core19d151.dynamic-dialup.toad.net ([EMAIL PROTECTED]
[162.33.189.151])
by sushi.toad.net (8.11.6/8.11.6) with ESMTP id fAI2ZZX00849
for <[EMAIL PROTECTED]>; Sat, 17 Nov 2001 21:35:35 -0500
Subject: fixed
From: Thomas Hood <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Mailer: Evolution/0.99.0 (Preview Release)
Date: 17 Nov 2001 21:36:19 -0500
Message-Id: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Delivered-To: [EMAIL PROTECTED]
This is no longer a problem with recent
ALSA drivers.
