From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0000051]: system crashes running aplay as unprivileged user on a US428. No sound except very occasional <.5 sec bursts
Date: Wed, 14 Sep 2005 15:47:20 +0200 [thread overview]
Message-ID: <bafe463cbb9eafa485053f4608de0c93@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=51>
======================================================================
Reported By: marqrdt
Assigned To: karsten
======================================================================
Project: ALSA - driver
Issue ID: 51
Category: USB - usb-usx2y
Reproducibility: sometimes
Severity: crash
Priority: normal
Status: assigned
Distribution: Fedora Core 1
Kernel Version: 2.4.22-1.2115.nptl (stock Fedora kernel)
======================================================================
Date Submitted: 02-11-2004 15:39 CET
Last Modified: 09-14-2005 15:47 CEST
======================================================================
Summary: system crashes running aplay as unprivileged user on
a US428. No sound except very occasional <.5 sec bursts
Description:
running the following command will cause a system crash +50% of the time:
aplay -v -D plug:hw:USX2Y music/wav/chant-reverb.wav
It runs file using the ALSA driver for the internal ALI5451 card.
Also, no sound comes out of the US428 except for very occasional <.5
bursts (never more than once per sound file). Headphones hooked to phone
jack, ext. speaker hooked to line-out.
No audio capture.
======================================================================
----------------------------------------------------------------------
karsten - 10-01-04 01:28
----------------------------------------------------------------------
please recheck snd-usb-usx2y version 0.8.0, which I posted to the
alsa-devel list.
----------------------------------------------------------------------
jdthood - 09-14-05 15:47
----------------------------------------------------------------------
Submitter: Is this problem fixed in more recent ALSA versions?
Issue History
Date Modified Username Field Change
======================================================================
02-11-04 15:39 marqrdt New Issue
02-11-04 17:27 marqrdt Issue Monitored: marqrdt
02-11-04 20:09 karsten Note Added: 0000221
03-18-04 14:13 piem Note Added: 0000641
10-01-04 01:28 karsten Note Added: 0001991
09-14-05 15:47 jdthood Note Added: 0006158
======================================================================
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server.
Download it for free - -and be entered to win a 42" plasma tv or your very
own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
next reply other threads:[~2005-09-14 13:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-14 13:47 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-03-22 2:20 [ALSA - driver 0000051]: system crashes running aplay as unprivileged user on a US428. No sound except very occasional <.5 sec bursts bugtrack
2004-09-30 23:28 bugtrack
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=bafe463cbb9eafa485053f4608de0c93@bugtrack.alsa-project.org \
--to=bugtrack@alsa-project.org \
--cc=alsa-devel@alsa-project.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.
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.