From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - lib 0000565]: Bug reported to gnomemeeting team
Date: Mon, 14 Feb 2005 16:20:47 +0100 [thread overview]
Message-ID: <8f1b09eeddd4aeebcb95d2f2bc17b695@bugtrack.alsa-project.org> (raw)
The following issue has been RESOLVED.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=565>
======================================================================
Reported By: mirko
Assigned To: tiwai
======================================================================
Project: ALSA - lib
Issue ID: 565
Category: pcm - digital audio
Reproducibility: always
Severity: crash
Priority: normal
Status: resolved
Resolution: fixed
Fixed in Version:
======================================================================
Date Submitted: 10-04-2004 14:35 CEST
Last Modified: 02-14-2005 16:20 CET
======================================================================
Summary: Bug reported to gnomemeeting team
Description:
http://bugzilla.gnome.org/show_bug.cgi?id=153770
D. Sandras says it's a big-endian/little-endian problem and suggested to
report it here.
======================================================================
----------------------------------------------------------------------
jdthood - 02-13-05 11:03
----------------------------------------------------------------------
I believe that this bug was closed by the 1.0.8 release. See Debian bug
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=245040.
----------------------------------------------------------------------
tiwai - 02-14-05 16:20
----------------------------------------------------------------------
OK, let's close this one, then. Please open if the problem persists.
Issue History
Date Modified Username Field Change
======================================================================
10-04-04 14:35 mirko New Issue
10-04-04 15:01 jcdutton Note Added: 0002010
10-04-04 15:58 tiwai Note Added: 0002011
10-17-04 15:13 jdthood Note Added: 0002192
10-18-04 18:03 tiwai Note Added: 0002198
02-13-05 11:03 jdthood Note Added: 0003582
02-14-05 16:20 tiwai Status new => resolved
02-14-05 16:20 tiwai Resolution open => fixed
02-14-05 16:20 tiwai Assigned To => tiwai
02-14-05 16:20 tiwai Note Added: 0003596
======================================================================
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next reply other threads:[~2005-02-14 15:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-14 15:20 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-07-08 8:35 [ALSA - lib 0000565]: Bug reported to gnomemeeting team bugtrack
2005-02-13 10:03 bugtrack
2004-10-18 16:03 bugtrack
2004-10-17 13:13 bugtrack
2004-10-04 13:58 bugtrack
2004-10-04 13:01 bugtrack
2004-10-04 12:35 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=8f1b09eeddd4aeebcb95d2f2bc17b695@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox