[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]
** Changed in: bluez (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
** Changed in: bluez (Ubuntu)
Assignee: Mathieu Trudel-Lapierre (cyphermox) => (unassigned)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1413363
Title:
bluetooth speaker and
Reduced priority for Ubuntu Touch bugs.
** Changed in: bluez (Ubuntu)
Importance: High => Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1413363
Title:
bluetooth speaker and
** Tags added: bluez-touch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1413363
Title:
bluetooth speaker and suspension issue
Status in bluez package in Ubuntu:
Incomplete
Bug
No, it's not widely broken. Some things are broken on some hardware, and
it's not all broken in the same way, that's why I asked for logs -- so
we can know what the actual issue is.
I don't have all the hardware in the world, so I can't reproduce these
issues myself.
Dave, if you're still having
I can reproduce this on krillin-rc274 with following steps:
1.Pair a bluetooth speaker
2.Open the music app and play music
3.Turn off the bluetooth speaker (the playback pauses)
4.Wait a few seconds, then turn on the bluetooth speaker
5.Wait until the speaker reconnects
6.Tap on play button to
This bug affects uses on x64 platforms also.
---
Mathieu: rather than require the bug reporter to provide you with log
data so that you can sidestep the fix, you could just try to replicate
the issue?
A cursory google search shows that bluetooth support on Ubuntu is widely
broken.
--
You
In that case we'll need the logs from ubuntu-system-settings; on re-
connection there should be a message, something like Host down or
Connection refused. Perhaps there is something extra we need to do in
this particular case for the headset to be happy with re-connecting.
--
You received this
Mathieu I have pressed the connect button on the phone in setting
bluetooth (s10 the device) nothing happens, I have pressed buttons on
the speaker and nothing happens, the speakers ready to pair is done
automatically on power on so unless it finds a thing it has previously
connected to it will
Could you also try to re-pair the speaker by pressing a button after the
system is resumed?
** Package changed: bluez-utils (Ubuntu) = bluez (Ubuntu)
** Changed in: bluez (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Kernel
Packages,
10 matches
Mail list logo
