Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #184565 > unrolled thread

Sudden death of bluetooth headphone connectivity

Back to article view | Back to linux.debian.user

Contents

  Sudden death of bluetooth headphone connectivity Mark Fletcher <mark27q1@gmail.com> - 2017-08-03 14:40 +0200
    Re: Sudden death of bluetooth headphone connectivity stuart watt <dekkzz78@gmail.com> - 2017-08-03 15:10 +0200
      Re: Sudden death of bluetooth headphone connectivity Mark Fletcher <mark27q1@gmail.com> - 2017-08-03 16:20 +0200
        Re: Re: Sudden death of bluetooth headphone connectivity dekkzz78@gmail.com - 2017-08-03 21:30 +0200
          Re: Re: Sudden death of bluetooth headphone connectivity Mark Fletcher <mark27q1@gmail.com> - 2017-08-04 01:20 +0200
            Re: Re: Re: Sudden death of bluetooth headphone connectivity dekkzz78@gmail.com - 2017-08-04 08:50 +0200
    Re: Sudden death of bluetooth headphone connectivity deloptes <deloptes@gmail.com> - 2017-08-03 22:50 +0200
      Re: Sudden death of bluetooth headphone connectivity Mark Fletcher <mark27q1@gmail.com> - 2017-08-04 01:20 +0200
        Re: Sudden death of bluetooth headphone connectivity deloptes <deloptes@gmail.com> - 2017-08-04 01:30 +0200
          Re: Sudden death of bluetooth headphone connectivity Mark Fletcher <mark27q1@gmail.com> - 2017-08-05 04:10 +0200
        Re: Sudden death of bluetooth headphone connectivity Henrique de Moraes Holschuh <hmh@debian.org> - 2017-08-04 01:40 +0200
          Re: Sudden death of bluetooth headphone connectivity Mark Fletcher <mark27q1@gmail.com> - 2017-08-05 05:00 +0200
            Re: Sudden death of bluetooth headphone connectivity David Wright <deblis@lionunicorn.co.uk> - 2017-08-05 06:10 +0200
            Re: Sudden death of bluetooth headphone connectivity deloptes <deloptes@gmail.com> - 2017-08-05 17:30 +0200
              Re: Sudden death of bluetooth headphone connectivity Mark Fletcher <mark27q1@gmail.com> - 2017-08-09 14:30 +0200
                Re: Sudden death of bluetooth headphone connectivity deloptes <deloptes@gmail.com> - 2017-08-09 20:20 +0200
                  Re: Sudden death of bluetooth headphone connectivity Mark Fletcher <mark27q1@gmail.com> - 2017-08-10 02:00 +0200

#184565 — Sudden death of bluetooth headphone connectivity

Hello the list!

Suddenly, earlier this week, my bluetooth headphones stopped working 
with Stretch.

I update weekly, usually on Sundays, and I am not sure because I wasn't 
paying attention whether I had successfully used my headphones before 
the last update I did last Sunday.

They definitely were working properly one week before that, when I used 
them with the computer just before going off on a week-long business 
trip.

Anyway, I use Gnome. When I want to connect the headphones I turn them 
on, click on the network-like icon in the top right of the screen, click 
on "Not in Use" beside the Bluetooth icon, and then click on "Bluetooth 
Settings". (Is there a more efficient, involving fewer clicks, way to 
connect, by the way?)

In Bluetooth Settings I can see my headphones as "BeoPlay H8". If I 
click on them it brings up the window with the slider switch to connect 
them. Normally, what would have happened is that clicking that switch 
would have connected the headphones. WHat happens now is the switch goes 
very briefly to the ON position, and then goes straight back to the OFF 
position. Removing / forgetting the device and re-pairing leads to the 
same result -- pairing is successful, but cannot connect.

With journalctl -f running in a terminal while trying to connect I see 
the following at the moment of clicking the slider switch to connect the 
headphones: a2dp-sink profile connect failed for AA:BB:CC:DD:EE:FF: 
Protocol not available
<bluetooth address elided, it is actually a sensible-looking bluetooth address>

Now, call me a super-sleuth, but I suspect that Protocol Not Available 
error could be something to do with the problem ;)

To re-iterate, this was working until recently, and all I've done is 
install regular updates using apt update / apt upgrade.

Where should I start looking?

[Full disclosure -- I previously had a different problem on upgrading to 
Stretch from Jessie -- see this link for that problem and a link to its 
solution --> https://lists.debian.org/debian-user/2017/06/msg01196.html 
I have never been particularly happy with the solution I linked to in 
that thread, precisely because I was worried it would be damaged by 
updates, but it seems to be intact at this point, so I don't think that 
is what the problem is here]

Thanks in advance if anyone can help me diagnose the sudden loss of the 
a2dp-sink protocol. The headphones work fine with my iPhone, so the 
problem seems to be with the computer, with which they were working fine 
until a bit over a week ago.

Mark

[toc] | [next] | [standalone]

#184568

[Multipart message — attachments visible in raw view] — view raw

On 08/03, Mark Fletcher wrote:
>Hello the list!
>
>Suddenly, earlier this week, my bluetooth headphones stopped working
>with Stretch.
>
>I update weekly, usually on Sundays, and I am not sure because I wasn't
>paying attention whether I had successfully used my headphones before
>the last update I did last Sunday.
>
>They definitely were working properly one week before that, when I used
>them with the computer just before going off on a week-long business
>trip.
>
>Anyway, I use Gnome. When I want to connect the headphones I turn them
>on, click on the network-like icon in the top right of the screen, click
>on "Not in Use" beside the Bluetooth icon, and then click on "Bluetooth
>Settings". (Is there a more efficient, involving fewer clicks, way to
>connect, by the way?)
>
>In Bluetooth Settings I can see my headphones as "BeoPlay H8". If I
>click on them it brings up the window with the slider switch to connect
>them. Normally, what would have happened is that clicking that switch
>would have connected the headphones. WHat happens now is the switch goes
>very briefly to the ON position, and then goes straight back to the OFF
>position. Removing / forgetting the device and re-pairing leads to the
>same result -- pairing is successful, but cannot connect.
>
>With journalctl -f running in a terminal while trying to connect I see
>the following at the moment of clicking the slider switch to connect the
>headphones: a2dp-sink profile connect failed for AA:BB:CC:DD:EE:FF:
>Protocol not available
><bluetooth address elided, it is actually a sensible-looking bluetooth address>
>
>Now, call me a super-sleuth, but I suspect that Protocol Not Available
>error could be something to do with the problem ;)
>
>To re-iterate, this was working until recently, and all I've done is
>install regular updates using apt update / apt upgrade.
>
>Where should I start looking?
>
>[Full disclosure -- I previously had a different problem on upgrading to
>Stretch from Jessie -- see this link for that problem and a link to its
>solution --> https://lists.debian.org/debian-user/2017/06/msg01196.html
>I have never been particularly happy with the solution I linked to in
>that thread, precisely because I was worried it would be damaged by
>updates, but it seems to be intact at this point, so I don't think that
>is what the problem is here]
>
>Thanks in advance if anyone can help me diagnose the sudden loss of the
>a2dp-sink protocol. The headphones work fine with my iPhone, so the
>problem seems to be with the computer, with which they were working fine
>until a bit over a week ago.
>
>Mark
>

Pulseaudio? If so what does pavucontrol say

Did Bluez updates come through? maybe pulseaudio-bluetooth module?

regards...

[toc] | [prev] | [next] | [standalone]

#184574

On Thu, Aug 03, 2017 at 02:03:36PM +0100, stuart watt wrote:
> On 08/03, Mark Fletcher wrote:
> > Hello the list!
> > 
> > Suddenly, earlier this week, my bluetooth headphones stopped working
> > with Stretch.
> > 
> > I update weekly, usually on Sundays, and I am not sure because I wasn't
> > paying attention whether I had successfully used my headphones before
> > the last update I did last Sunday.
> > 
> > They definitely were working properly one week before that, when I used
> > them with the computer just before going off on a week-long business
> > trip.
> > 
> > Anyway, I use Gnome. When I want to connect the headphones I turn them
> > on, click on the network-like icon in the top right of the screen, click
> > on "Not in Use" beside the Bluetooth icon, and then click on "Bluetooth
> > Settings". (Is there a more efficient, involving fewer clicks, way to
> > connect, by the way?)
> > 
> > In Bluetooth Settings I can see my headphones as "BeoPlay H8". If I
> > click on them it brings up the window with the slider switch to connect
> > them. Normally, what would have happened is that clicking that switch
> > would have connected the headphones. WHat happens now is the switch goes
> > very briefly to the ON position, and then goes straight back to the OFF
> > position. Removing / forgetting the device and re-pairing leads to the
> > same result -- pairing is successful, but cannot connect.
> > 
> > With journalctl -f running in a terminal while trying to connect I see
> > the following at the moment of clicking the slider switch to connect the
> > headphones: a2dp-sink profile connect failed for AA:BB:CC:DD:EE:FF:
> > Protocol not available
> > <bluetooth address elided, it is actually a sensible-looking bluetooth address>
> > 
> > Now, call me a super-sleuth, but I suspect that Protocol Not Available
> > error could be something to do with the problem ;)
> > 
> > To re-iterate, this was working until recently, and all I've done is
> > install regular updates using apt update / apt upgrade.
> > 
> > Where should I start looking?
> > 
> > [Full disclosure -- I previously had a different problem on upgrading to
> > Stretch from Jessie -- see this link for that problem and a link to its
> > solution --> https://lists.debian.org/debian-user/2017/06/msg01196.html
> > I have never been particularly happy with the solution I linked to in
> > that thread, precisely because I was worried it would be damaged by
> > updates, but it seems to be intact at this point, so I don't think that
> > is what the problem is here]
> > 
> > Thanks in advance if anyone can help me diagnose the sudden loss of the
> > a2dp-sink protocol. The headphones work fine with my iPhone, so the
> > problem seems to be with the computer, with which they were working fine
> > until a bit over a week ago.
> > 
> > Mark
> > 
> 
> Pulseaudio? If so what does pavucontrol say
> 
> Did Bluez updates come through? maybe pulseaudio-bluetooth module?
> 
> regards...

Of course, pavucontrol says nothing, because the headphones have not 
been able to connect yet. As soon as they connect, the adp_sink error 
disconnects them again, as I described in my original post.

The problem, I've got to think, is upstream of pulseaudio, no?

I don't know if bluez updates came through. There is no 
pulseaudio-bluetooth package in Stretch -- there is a 
pulseaudio-module-bluetooth package, which is installed.

Just to check, I've just done another apt update and then apt list 
--upgradeable to have a look at what would get installed now -- most of 
it is to do with the freerdp security update from earlier this week, 
nothing relating to pulse or bluetooth. 

Thanks again

Mark

[toc] | [prev] | [next] | [standalone]

#184599

[Multipart message — attachments visible in raw view] — view raw

On 08/03, Mark Fletcher wrote:
>On Thu, Aug 03, 2017 at 02:03:36PM +0100, stuart watt wrote:
>> On 08/03, Mark Fletcher wrote:
>> > Hello the list!
>> >
>> > Suddenly, earlier this week, my bluetooth headphones stopped working
>> > with Stretch.
>> >
>> > I update weekly, usually on Sundays, and I am not sure because I wasn't
>> > paying attention whether I had successfully used my headphones before
>> > the last update I did last Sunday.
>> >
>> > They definitely were working properly one week before that, when I used
>> > them with the computer just before going off on a week-long business
>> > trip.
>> >
>> > Anyway, I use Gnome. When I want to connect the headphones I turn them
>> > on, click on the network-like icon in the top right of the screen, click
>> > on "Not in Use" beside the Bluetooth icon, and then click on "Bluetooth
>> > Settings". (Is there a more efficient, involving fewer clicks, way to
>> > connect, by the way?)
>> >
>> > In Bluetooth Settings I can see my headphones as "BeoPlay H8". If I
>> > click on them it brings up the window with the slider switch to connect
>> > them. Normally, what would have happened is that clicking that switch
>> > would have connected the headphones. WHat happens now is the switch goes
>> > very briefly to the ON position, and then goes straight back to the OFF
>> > position. Removing / forgetting the device and re-pairing leads to the
>> > same result -- pairing is successful, but cannot connect.
>> >
>> > With journalctl -f running in a terminal while trying to connect I see
>> > the following at the moment of clicking the slider switch to connect the
>> > headphones: a2dp-sink profile connect failed for AA:BB:CC:DD:EE:FF:
>> > Protocol not available
>> > <bluetooth address elided, it is actually a sensible-looking bluetooth address>
>> >
>> > Now, call me a super-sleuth, but I suspect that Protocol Not Available
>> > error could be something to do with the problem ;)
>> >
>> > To re-iterate, this was working until recently, and all I've done is
>> > install regular updates using apt update / apt upgrade.
>> >
>> > Where should I start looking?
>> >
>> > [Full disclosure -- I previously had a different problem on upgrading to
>> > Stretch from Jessie -- see this link for that problem and a link to its
>> > solution --> https://lists.debian.org/debian-user/2017/06/msg01196.html
>> > I have never been particularly happy with the solution I linked to in
>> > that thread, precisely because I was worried it would be damaged by
>> > updates, but it seems to be intact at this point, so I don't think that
>> > is what the problem is here]
>> >
>> > Thanks in advance if anyone can help me diagnose the sudden loss of the
>> > a2dp-sink protocol. The headphones work fine with my iPhone, so the
>> > problem seems to be with the computer, with which they were working fine
>> > until a bit over a week ago.
>> >
>> > Mark
>> >
>>
>> Pulseaudio? If so what does pavucontrol say
>>
>> Did Bluez updates come through? maybe pulseaudio-bluetooth module?
>>
>> regards...
>
>Of course, pavucontrol says nothing, because the headphones have not
>been able to connect yet. As soon as they connect, the adp_sink error
>disconnects them again, as I described in my original post.
>
>The problem, I've got to think, is upstream of pulseaudio, no?
>
>I don't know if bluez updates came through. There is no
>pulseaudio-bluetooth package in Stretch -- there is a

 >pulseaudio-module-bluetooth package, which is installed.
>
>Just to check, I've just done another apt update and then apt list
>--upgradeable to have a look at what would get installed now -- most of
>it is to do with the freerdp security update from earlier this week,
>nothing relating to pulse or bluetooth.
>
>Thanks again
>
>Mark

Mark,

What BT chipset are you using, have you acccidently disabled it in BIOS? Nothing shows up in google about protocol not 
available but there was a bug in gnome 3.24 and pulseaudio 10 with gnome/GDM where GDM starts its own pulseaudio 
instance. https://wiki.archlinux.org/index.php/Bluetooth_headset#Gnome_with_GDM

I don't run gnome on debian but i do on arch, i didn't find the gnome BT stack particularily stable so i used 
blueman-applet as a backup in the cases gnome BT wouldn't work with my FSL360. see blueman & bluez-utils packages in 
stretch.

Blueman-applet allows you see if the device is trusted & paired and to perform those functions if you wish. It also 
identifies the BT adapter in use which should appear in lsusb.

If that's no further help look up the Arch wiki section on bluetoothctl [from bluez-utils]. 99% of the time the issues 
i had were BT getting confused about adapters.

[toc] | [prev] | [next] | [standalone]

#184607

On Thu, Aug 03, 2017 at 08:25:27PM +0100, dekkzz78@gmail.com wrote:
> 
> Mark,
> 
> What BT chipset are you using, have you acccidently disabled it in BIOS?
> Nothing shows up in google about protocol not available but there was a bug
> in gnome 3.24 and pulseaudio 10 with gnome/GDM where GDM starts its own
> pulseaudio instance.
> https://wiki.archlinux.org/index.php/Bluetooth_headset#Gnome_with_GDM
> 
> I don't run gnome on debian but i do on arch, i didn't find the gnome BT
> stack particularily stable so i used blueman-applet as a backup in the cases
> gnome BT wouldn't work with my FSL360. see blueman & bluez-utils packages in
> stretch.
> 
> Blueman-applet allows you see if the device is trusted & paired and to
> perform those functions if you wish. It also identifies the BT adapter in
> use which should appear in lsusb.
> 
> If that's no further help look up the Arch wiki section on bluetoothctl
> [from bluez-utils]. 99% of the time the issues i had were BT getting
> confused about adapters.

Some more info I just discovered.

First of all, it's not just a2dp-sink protocol that is reported missing. 
I just tried to connect my iPhone which I set up back in the Jessie days 
as an a2dp SOURCE so I could play music from it through my PC speakers, 
and got the same behaviour and an error in the systemd journal saying 
a2dp-source not available. IE same error but source instead of sink. To 
me, this implies the problem is not specific to a2dp-sink protocol.

Now the variable here is that it was way more of a fiddle than I 
expected it to be to get playing music from my iPhone through the 
computer's speakers to work in the first place, years ago, and I haven't 
tried since the upgrade from Jessie->Stretch, so THIS PARTICULAR task 
could have been broken since the upgrade and I wouldn't have known. It's 
far more important to me to get my headphones working again than it is 
to get the iPhone able to play music through the computer's speakers.

To your point about the bluetooth potentially being disabled, I don't 
think so because: A) the bluetooth hardware on this circa-2009 
self-built Core i7-920-based PC with an ASUS P6T motherboard is a USB 
bluetooth dongle about which the BIOS knows nothing, and B) I tried the 
only bluetooth operation I could think of that didn't involve audio, 
trying to connect to my iPhone as a network provider, and while the 
connection failed it did so at the stage of the computer asking it for 
an IP address, NOT at the stage of trying to connect via bluetooth. In 
fact I can clearly see it report success connecting to the phone in the 
log, followed by a series of error messages relating to DHCP, and then 
the connection gets dropped. In terms of visual effect, in this case the 
slider button stays in the ON position for several seconds before going 
back to OFF, in contrast to the audio-based bluetooth attempts which 
fail instantly.

The phone isn't set up to provide a network, so it is no surprise to me 
that that operation failed, but the point is it DIDN'T fail at the 
bluetooth stage.

I guess the next thing to try is your blueman suggestions. It strikes me 
as odd that it would be working fine and then suddenly break though.

I had always thought that blueman IS the Gnome bluetooth applet -- 
guess that was my misunderstanding.

By the way, I failed to mention in my original post, but in case anyone 
is wondering the audio on my PC is basically working fine, if I watch a 
video or something on the computer using the computer speakers, the 
audio is fine. So pulse, audio config on my PC, permissions etc, all are 
demonstrated OK. No problems until I bring the bluetooth devices into it.

Mark

[toc] | [prev] | [next] | [standalone]

#184619

[Multipart message — attachments visible in raw view] — view raw

On 08/04, Mark Fletcher wrote:
>I guess the next thing to try is your blueman suggestions. It strikes me
>as odd that it would be working fine and then suddenly break though.
>

in my 2 years using my FSL headphones BT has broken several times usually on bluez updates and has never been 
particularly stable using the gnome applet. the older chipsets seem more prone to issues wrt a2dp stability which is 
why i disable them and use bt4.0 usb units. i'll set up one on a debian thinkpad over the weekend and see what happens.

[toc] | [prev] | [next] | [standalone]

#184603

Mark Fletcher wrote:

> 
> [Full disclosure -- I previously had a different problem on upgrading to
> Stretch from Jessie -- see this link for that problem and a link to its
> solution --> https://lists.debian.org/debian-user/2017/06/msg01196.html
> I have never been particularly happy with the solution I linked to in
> that thread, precisely because I was worried it would be damaged by
> updates, but it seems to be intact at this point, so I don't think that
> is what the problem is here]
> 
> Thanks in advance if anyone can help me diagnose the sudden loss of the
> a2dp-sink protocol. The headphones work fine with my iPhone, so the
> problem seems to be with the computer, with which they were working fine
> until a bit over a week ago.

I vaguely recall there was a package that needs to be installed for the
audio to work, but it does not show into dependencies, so it is not pulled
with bluez or pulse audio (this is based on jessie storie), while it is
providing the link between them. Perhaps you did autoremove not used
packages and lost it.

Unfortunately I upgraded as well and never had the time to see if audio via
bluetooth works in stretch

[toc] | [prev] | [next] | [standalone]

#184608

On Thu, Aug 03, 2017 at 10:39:03PM +0200, deloptes wrote:
> Mark Fletcher wrote:
> 
> > 
> I vaguely recall there was a package that needs to be installed for the
> audio to work, but it does not show into dependencies, so it is not pulled
> with bluez or pulse audio (this is based on jessie storie), while it is
> providing the link between them. Perhaps you did autoremove not used
> packages and lost it.
> 
> Unfortunately I upgraded as well and never had the time to see if audio via
> bluetooth works in stretch
> 
This has the ring of common sense to it -- it would explain why it 
suddenly stopped working. I didn't do an apt autoremove last Sunday, but 
may have done one the Sunday before -- which would have been reckless 
even for me just before going on a business trip during which I wanted 
to be able to access my machine remotely [albeit not the bluetooth 
parts], but I suspect I did it anyway... I certainly did one recently, 
just can't remember exactly when, and hence can't be sure whether I have 
used bluetooth headphones successfully since...

If anyone can remember which package that is, I can check if it is 
installed... The only thing is I am not sure how it would have got onto 
the system if it isn't depended on and I didn't install it manually. And 
if it IS depended on, or I did install it manually, apt autoremove 
should not have removed it...

To someone's point, Google'S coming up fairly blank on this one...

Mark

[toc] | [prev] | [next] | [standalone]

#184610

Mark Fletcher wrote:

> If anyone can remember which package that is, I can check if it is
> installed... The only thing is I am not sure how it would have got onto
> the system if it isn't depended on and I didn't install it manually. And
> if it IS depended on, or I did install it manually, apt autoremove
> should not have removed it...

to start with

pulseaudio-module-bluetooth - Bluetooth module for PulseAudio sound server

[toc] | [prev] | [next] | [standalone]

#184657

On Fri, Aug 04, 2017 at 01:27:57AM +0200, deloptes wrote:
> Mark Fletcher wrote:
> 
> > If anyone can remember which package that is, I can check if it is
> > installed... The only thing is I am not sure how it would have got onto
> > the system if it isn't depended on and I didn't install it manually. And
> > if it IS depended on, or I did install it manually, apt autoremove
> > should not have removed it...
> 
> to start with
> 
> pulseaudio-module-bluetooth - Bluetooth module for PulseAudio sound server
> 
Right... which I already mentioned is confirmed installed...

Mark

[toc] | [prev] | [next] | [standalone]

#184611

On Fri, 04 Aug 2017, Mark Fletcher wrote:
> suddenly stopped working. I didn't do an apt autoremove last Sunday, but 
> may have done one the Sunday before -- which would have been reckless 

The log files are at:
/var/log/apt*
/var/log/apt/*

Failing that:
/var/log/dpkg*

It will list everything that was updated, installed, removed, or purged.

-- 
  Henrique Holschuh

[toc] | [prev] | [next] | [standalone]

#184660

On Thu, Aug 03, 2017 at 08:35:23PM -0300, Henrique de Moraes Holschuh wrote:
> On Fri, 04 Aug 2017, Mark Fletcher wrote:
> > suddenly stopped working. I didn't do an apt autoremove last Sunday, but 
> > may have done one the Sunday before -- which would have been reckless 
> 
> The log files are at:
> /var/log/apt*
> /var/log/apt/*
> 
> Failing that:
> /var/log/dpkg*
> 
> It will list everything that was updated, installed, removed, or purged.
> 
> -- 

OK I had a look in /var/log/apt/ folders at the history.log files. In 
the one for July I determined that I ran an apt upgrade on July 16th, 
one week before my trip, and the next time I did so was on July 29th, on 
my return from my trip. So I displayed more restraint around updates 
just before travelling than I remembered. In the week between July 16th 
and July 23rd when I left for my trip, I definitely used the headphones, 
so they were working after the July 16th update.

No update on July 23rd, which actually makes sense because I was up at 
5:30am to catch a plane. I might have done the update the day before, 
but it seems i did not.

The upgrade record for July 29th has a long list of packages I will have 
to go through in detail. I have already noticed both pulseaudio and udev 
got updates so those are 2 possible candidates for the culprit. I seem 
to recall there was also a kernel upgrade, meaning I would have rebooted 
after the upgrade.

Next in the apt log is this:

Start-Date: 2017-07-29  23:46:36
Commandline: apt autoremove
Requested-By: mark (1000)
Error: Sub-process /usr/bin/dpkg returned an error code (1)
End-Date: 2017-07-29  23:46:41

[the dpkg error code is a red herring, I have zoneminder installed but 
it requires access to a mysql database, and due to a previous unrelated 
problem with my local mariadb instance, zoneminder's database is in read 
only mode, so zoneminder can't start properly -- that is the cause of 
the error code]

Am I reading that correctly that I ran apt autoremove and it didn't find 
anything to do? Or is it just not telling me what it did?

I also looked in /var/log/dpkg.1 (July's stuff is already partially 
archived) and:

grep 2017-07-29 /var/log/dpkg.1 | awk '{print $3}' | sort -u 

lists the following keywords:

configure
startup
status
trigproc
upgrade


No sign of "remove", but I don't know if there would be or not...

So IF I am interpreting the above correctly, I ran apt autoremove but it 
didn't do anything, I did upgrade a shedload of packages and the next 
thing to do is to sift through that shedload looking for changes 
(somehow) that might have caused the problem. I'm not really sure how I 
am going to tell what changes a package upgrade made, unless the 
changelog happens to mention something useful, but hopefully something 
will turn up... I'll start with packages that look pulseaudio or 
bluetooth-related, and go from there...

Mark

[toc] | [prev] | [next] | [standalone]

#184662

On Sat 05 Aug 2017 at 11:50:45 (+0900), Mark Fletcher wrote:
> On Thu, Aug 03, 2017 at 08:35:23PM -0300, Henrique de Moraes Holschuh wrote:
> > On Fri, 04 Aug 2017, Mark Fletcher wrote:
> > > suddenly stopped working. I didn't do an apt autoremove last Sunday, but 
> > > may have done one the Sunday before -- which would have been reckless 
> > 
> > The log files are at:
> > /var/log/apt*
> > /var/log/apt/*
> > 
> > Failing that:
> > /var/log/dpkg*
> > 
> > It will list everything that was updated, installed, removed, or purged.
> > 
> > -- 
> 
> OK I had a look in /var/log/apt/ folders at the history.log files. In 
> the one for July I determined that I ran an apt upgrade on July 16th, 
> one week before my trip, and the next time I did so was on July 29th, on 
> my return from my trip. So I displayed more restraint around updates 
> just before travelling than I remembered. In the week between July 16th 
> and July 23rd when I left for my trip, I definitely used the headphones, 
> so they were working after the July 16th update.
> 
> No update on July 23rd, which actually makes sense because I was up at 
> 5:30am to catch a plane. I might have done the update the day before, 
> but it seems i did not.
> 
> The upgrade record for July 29th has a long list of packages I will have 
> to go through in detail. I have already noticed both pulseaudio and udev 
> got updates so those are 2 possible candidates for the culprit. I seem 
> to recall there was also a kernel upgrade, meaning I would have rebooted 
> after the upgrade.
> 
> Next in the apt log is this:
> 
> Start-Date: 2017-07-29  23:46:36
> Commandline: apt autoremove
> Requested-By: mark (1000)
> Error: Sub-process /usr/bin/dpkg returned an error code (1)
> End-Date: 2017-07-29  23:46:41
> 
> [the dpkg error code is a red herring, I have zoneminder installed but 
> it requires access to a mysql database, and due to a previous unrelated 
> problem with my local mariadb instance, zoneminder's database is in read 
> only mode, so zoneminder can't start properly -- that is the cause of 
> the error code]
> 
> Am I reading that correctly that I ran apt autoremove and it didn't find 
> anything to do? Or is it just not telling me what it did?
> 
> I also looked in /var/log/dpkg.1 (July's stuff is already partially 
> archived) and:
> 
> grep 2017-07-29 /var/log/dpkg.1 | awk '{print $3}' | sort -u 
> 
> lists the following keywords:
> 
> configure
> startup
> status
> trigproc
> upgrade
> 
> 
> No sign of "remove", but I don't know if there would be or not...
> 
> So IF I am interpreting the above correctly, I ran apt autoremove but it 
> didn't do anything, I did upgrade a shedload of packages and the next 
> thing to do is to sift through that shedload looking for changes 
> (somehow) that might have caused the problem. I'm not really sure how I 
> am going to tell what changes a package upgrade made, unless the 
> changelog happens to mention something useful, but hopefully something 
> will turn up... I'll start with packages that look pulseaudio or 
> bluetooth-related, and go from there...

apt-get autoremove   and   apt-get --purge autoremove
produce lists of packages prefixed with Remove: or Purge:
as appropriate, so it looks as if "Nothing happens" in your
case. (I trust that apt would log the same info as apt-get.)

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#184682

Mark Fletcher wrote:

> 
> 
> No sign of "remove", but I don't know if there would be or not...
> 
> So IF I am interpreting the above correctly, I ran apt autoremove but it
> didn't do anything, I did upgrade a shedload of packages and the next
> thing to do is to sift through that shedload looking for changes
> (somehow) that might have caused the problem. I'm not really sure how I
> am going to tell what changes a package upgrade made, unless the
> changelog happens to mention something useful, but hopefully something
> will turn up... I'll start with packages that look pulseaudio or
> bluetooth-related, and go from there...
> 
> Mark

Can you try bluetoothctl and see if it connects properly.
you can also post the output of "info <bt addr>"

regards

[toc] | [prev] | [next] | [standalone]

#184930

On Sat, Aug 05, 2017 at 05:27:49PM +0200, deloptes wrote:
> 
> Can you try bluetoothctl and see if it connects properly.
> you can also post the output of "info <bt addr>"
> 

bluetoothctl
[NEW] Controller 00:1B:DC:04:DB:FA kazuki [default]
[NEW] Device 8C:8E:F2:C2:BD:93 iPhone
[NEW] Device 00:09:A7:09:BE:22 BeoPlay H8
[NEW] Device F0:CB:A1:89:68:61 Mark's Phone
[NEW] Device 4C:A5:6D:7E:0E:FC Mark's tablet
[NEW] Device A0:E9:DB:09:A0:2D Anker SoundCore
[bluetooth]# connect 00:09:A7:09:BE:22
Attempting to connect to 00:09:A7:09:BE:22
Failed to connect: org.bluez.Error.Failed
[bluetooth]# info 00:09:A7:09:BE:22
Device 00:09:A7:09:BE:22
        Name: BeoPlay H8
        Alias: BeoPlay H8
        Class: 0x240418
        Icon: audio-card
        Paired: yes
        Trusted: yes
        Blocked: no
        Connected: no
        LegacyPairing: no
        UUID: Headset                   (00001108-0000-1000-8000-00805f9b34fb)
        UUID: Audio Sink                (0000110b-0000-1000-8000-00805f9b34fb)
        UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
        UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
        UUID: Handsfree                 (0000111e-0000-1000-8000-00805f9b34fb)
        UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
        Modalias: bluetooth:v0103p4000d0802
[bluetooth]# 

That's what I get when I try to connect -- a less than helpful error 
message. The same error message as quoted before appeared in the systemd 
journal when I make the connection attempt.

And the output of info <addr> is quoted above as well. I am wondering if 
among the UUIDs listed should be a2dp-sink, and since we are not getting 
it it is getting booted. But as we know from the journal entry, 
a2dp-sink protocol is "not available" -- and I think that remains the 
issue to fix to get this working.

Overall I am inclined to think something is misconfigured / broken / 
missing in the _computer_'s bluetooth setup, not the headphones -- as 
the headphones work fine with other devices eg my iPhone, and for anyone 
coming late into the conversation they also worked with this computer 
too until about 2 weeks ago now.

Mark

[toc] | [prev] | [next] | [standalone]

#184949

Mark Fletcher wrote:

> Failed to connect: org.bluez.Error.Failed

Mark Fletcher wrote:

> Failed to connect: org.bluez.Error.Failed

I am not an expert in BT headphones. I had enough experience with phones.
However the process to connect is the same

[bluetooth]# default-agent
No agent is registered
[bluetooth]# agent on
Agent registered
[bluetooth]# default-agent
Default agent request successful
[bluetooth]# pair 40:98:4E:90:56:E3
Attempting to pair with 40:98:4E:90:56:E3
Failed to pair: org.bluez.Error.AlreadyExists
[bluetooth]# trust 40:98:4E:90:56:E3
[CHG] Device 40:98:4E:90:56:E3 Trusted: yes
Changing 40:98:4E:90:56:E3 trust succeeded
[bluetooth]# connect 40:98:4E:90:56:E3
Attempting to connect to 40:98:4E:90:56:E3
[CHG] Device 40:98:4E:90:56:E3 Connected: yes
Connection successful
[CHG] Device 40:98:4E:90:56:E3 ServicesResolved: yes

On my new stretch I also do not see an option to use the audio services on
the phone and in jessie I can in fact connect and use them.

So I found this here
https://unix.stackexchange.com/questions/258074/error-when-trying-to-connect-to-bluetooth-speaker-org-bluez-error-failed

But when I try $ pactl load-module module-bluetooth-discover
Failure: Module initialization failed

is it loaded or fails loading?

pulseaudio -k
pulseaudio --start
pactl load-module module-bluetooth-discover
20
pactl load-module module-bluetooth-discover
Failure: Module initialization failed

So it looks it was loaded anyway.

Now I open the blueman-applet and run bluetooth devices. There I select
audio source and it works. Unfortunately I do not have a BT headphones to
test with

I hope you get there as well

regards

[toc] | [prev] | [next] | [standalone]

#184959

On Wed, Aug 09, 2017 at 08:18:02PM +0200, deloptes wrote:
> But when I try $ pactl load-module module-bluetooth-discover
> Failure: Module initialization failed
> 
> is it loaded or fails loading?
> 
> pulseaudio -k
> pulseaudio --start
> pactl load-module module-bluetooth-discover
> 20
> pactl load-module module-bluetooth-discover
> Failure: Module initialization failed
> 

Ahhhh, you're kidding!!!??

pactl load-module module-bluetooth-discover

returned, in my case, "26".

Then, connecting as normal worked!

So somehow the module, which was previously loading automatically, isn't 
any more. I just have to figure out how to make that automatic and I'm 
off to the races again.

I also noticed that once again I have 2 copies of pulse running, one as 
user "Debian-<something>" (the full name is elided in ps -ef) and one as 
my normal user. That is presumably an artifact of the upgrade from 
Jessie to Stretch -- I had previously removed the system one to fix an 
earlier problem but it seems I can connect and use the headphones 
without doing so now, if I manually load the module.

Thanks a lot for everyone's help with this one. 

Mark

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web