Dear maintainer,
the latest updates of bluez and blueman-applet in Debian/testing
resolved this issue.
I can now use my A2DP devices again.
Thank you very much.
Adrian Immanuel KIESS
On Tue, 2014-04-29 at 15:12 +, Debian Bug Tracking System wrote:
> Thank you for the additional informati
Hi all,
I feel like this bug is related to these two I reported:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743568
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743569
More specifically to make a bluetooth headset work in A2DP mode I had to
change settings in audio.conf:
SCORouting=PC
Thanks for taking the time to process my bug report.
I was still not able to get bluetooth audio working within Debian/testing.
Thanks.
Adrian
On Mon, Apr 28, 2014 at 11:23 PM, Felipe Sateler wrote:
>
> Hi Adrian,
>
> On Sat, Apr 26, 2014 at 3:00 AM, Adrian Immanuel Kieß
> wrote:
> > With So
Control: reassign -1 bluez/4.101-4.1
Control: retitle -1 bluez: cannot connect without Socket interface
Hi Adrian,
On Sat, Apr 26, 2014 at 3:00 AM, Adrian Immanuel Kieß wrote:
> With Socket=Disabled bluez reports "Stream setup failed" and /var/log/syslog
> reports:
>
> Apr 26 07:56:42 g6 bluetoo
With Socket=Disabled bluez reports "Stream setup failed" and
/var/log/syslog reports:
Apr 26 07:56:42 g6 bluetoothd[9106]: bluetoothd[9106]: Unable to select SEP
Apr 26 07:56:42 g6 bluetoothd[9106]: Unable to select SEP
Apr 26 07:56:42 g6 kernel: [ 876.200899] input: 00:1D:DF:D5:E3:2E as
/devices
On Thu, Apr 24, 2014 at 1:16 AM, Adrian Immanuel Kieß wrote:
> I've redone it following your suggestions.
>
> The pa.log file is attached to this e-mail.
Thanks. I'm a bit stumped as to what this could be. Some googling suggest that:
> I have to add that I have to set Enable=Socket in /etc/bluet
Maybe, according to a post in Ubuntu forums (
http://askubuntu.com/questions/287254/ubuntu-13-04-bluetooth-a2dp-does-not-work/318399#comment443009_318399),
you must prevent pulseaudio from autospawning when it's killed, changing on
/etc/pulse/client.conf "autospawn = yes" to "autospawn = no" and se
On Wed, Apr 23, 2014 at 12:31 AM, Adrian Immanuel Kieß wrote:
> The error message does not seem to get logged to pa.log.
>
> I attached the new pa.log again, but still it just logged the startup of
> pulseaudio. I tried to reconnect the bluetooth audio device several times
> meanwhile.
>
> Syslog
The error message does not seem to get logged to pa.log.
I attached the new pa.log again, but still it just logged the startup of
pulseaudio. I tried to reconnect the bluetooth audio device several times
meanwhile.
Syslog message is still:
Apr 23 05:22:40 g6 kernel: [164196.912874] input: 00:1D:
On Sat, Apr 19, 2014 at 2:13 AM, Adrian Immanuel Kieß wrote:
> Dear Felipe,
>
> I can still reproduce this with pulseaudio 5.0.
>
> The error message is now; taken from /var/log/syslog:
>
> Apr 19 07:10:08 g6 acpid: input device has been disconnected, fd 15
> Apr 19 07:10:17 g6 kernel: [85867.1779
Hi all,
On Sun, Oct 06, 2013 at 10:11:14PM +0200, Olivier Bitsch wrote:
> Package: pulseaudio-module-bluetooth
> Version: 4.0-6+b1
> Severity: normal
> Tags: upstream
>
> I own a Nokia BH-905 bluetooth headset and I can pair it and can use it as
> HSP/HFP telephony without any problem. But I can
Hi guys,
I got A2DP working on Sid, but I don't know what has changed.
I'm using blueman and I can pair my Tracks Air as earphone service (I dont
know if this is the correct translation) and then as audio sink, then using
pavucontrol I change the audio output and profile.
Follow some details about
I'm getting the same results with Tracks Air (the one that comes with Moto
G) on Sid.
Package: pulseaudio
Source: pulseaudio (4.0-6)
Version: 4.0-6+b1
pulseaudio[3307]: [pulseaudio] module-bluetooth-device.c: Profile not
connected, refused to switch profile to a2dp
--
Adriano
Same results with a Sony DR-BTN200 and the same software versions too.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
I'm getting the same results with BH-905 and the same SW versions. It
was working perfectly with previous versions. I wonder if it's working
with other headsets because there are so few reports about identical
problems.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a
Package: pulseaudio
Version: 4.0-6+b1
Followup-For: Bug #725610
Dear Maintainer,
* What led up to the situation?
Switch bluetooth headset to A2DP mode
* What exactly did you do (or not do) that was effective (or
ineffective)?
pavucontrol -> Switch to A2DP mode
* What was
16 matches
Mail list logo