--- Begin Message ---
- To: "Debian Bug Tracking System" <submit@bugs.debian.org>
- Subject: bluez-audio: A bluetooth headset can't be used to record sound.
- From: "Chao-Cheng Wu" <chaocheng.wu@gmail.com>
- Date: Thu, 7 Feb 2008 03:31:02 -0500
- Message-id: <8e65e1570802070031x400484a8oaa19bcf035ccbc2a@mail.gmail.com>
Package: bluez-audio
Version: 3.24-1
Severity: important
Hi,
I've been successfully config my bluetooth headset to playback sound by
using any player I have, such as amarok, mplayer, xmms, but it can't
record sound.
When I use
$ arecord -D bluetooth -f S16_LE | aplay -D bluetooth -f S16_LE
nothing is recorded!
The exactly same bug can also be found from Mandriva Bugzilla in the
following link.
http://qa.mandriva.com/show_bug.cgi?id=37103
According to their thread, this bug has been fix in the bluez cvs, so
please include this patch ASAP. Thanks!
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.22.20071005 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages bluez-audio depends on:
ii libasound2 1.0.15-3 ALSA library
ii libbluetooth2 3.24-1 Library to use the BlueZ Linux Blu
ii libc6 2.7-6 GNU C Library: Shared libraries
ii libdbus-1-3 1.1.2-1 simple interprocess messaging syst
ii libglib2.0-0 2.14.5-2 The GLib library of C routines
ii libgstreamer-plugins-base0 0.10.17-1 GStreamer libraries from the "base
ii libgstreamer0.10-0 0.10.17-1 Core GStreamer libraries and eleme
ii libxml2 2.6.31.dfsg-1 GNOME XML library
bluez-audio recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
- To: Arthur Korn <arthur@korn.ch>
- Cc: 464501-done@bugs.debian.org
- Subject: Re: Bug#464501: [Pkg-bluetooth-maintainers] Bug#464501: bluez-audio: A bluetooth headset can't be used to record sound.
- From: Moritz Muehlenhoff <jmm@inutil.org>
- Date: Thu, 18 Dec 2008 21:24:47 +0100
- Message-id: <20081218202447.GB32549@inutil.org>
- In-reply-to: <4949F291.7040309@korn.ch>
- References: <20080414150220.GA24027@clamp.esaurito.net> <20080414154902.GA9285@turing.prv.korn.ch> <20080414164106.GA12695@turing.prv.korn.ch> <20080414173233.GD23634@clamp.esaurito.net> <20080417144915.GA4797@turing.prv.korn.ch> <20080417160621.GA16574@clamp.esaurito.net> <20080417170303.GB6286@turing.prv.korn.ch> <20080417173434.GA4395@turing.prv.korn.ch> <[🔎] 20081217211724.GA15842@galadriel.inutil.org> <4949F291.7040309@korn.ch>
Arthur Korn wrote:
> Moritz Muehlenhoff wrote:
> >On Thu, Apr 17, 2008 at 07:34:34PM +0200, Arthur Korn wrote:
> >>Arthur Korn schrieb:
> >>>I'll downgrade my kernel now.
> >>Really, with 2.6.22-3-686 the headset works fine which didn't
> >>work with 2.6.24-1-686.
> >
> >Does this error still occur with more recent kernel versions?
>
> I don't know, I've switched back to windows because it seemed I couldn't
> upgrade anything without breaking the headset. I can report that it
> works perfectly fine out of the box with Vista :/.
There's not much point in leaving the bug open, then.
Cheers,
Moritz
--- End Message ---