Thank you for reporting this bug to Ubuntu.
Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
The Groovy Gorilla has reached end of life, so this bug will not be
fixed for that release
** Changed in: pi-bluetooth (Ubuntu Groovy)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The Groovy Gorilla has reached end of life, so this bug will not be
fixed for that release
** Changed in: linux-raspi (Ubuntu Groovy)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The Groovy Gorilla has reached end of life, so this bug will not be
fixed for that release
** Changed in: bluez (Ubuntu Groovy)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Further potentially useful information about the behavior after PPA
install: If you remove a device via the ui, it leaves a ghosted version
that may or may not be able to reconnect if the device tries to. You
must remove this ghosted device (two removes in total) and then it
appears to allow a
Additionally, I've noted that I really need to disable/re-enable
bluetooth to re-associate with the same device that I've unpaired, even
with PPA. My BT mouse is usable, but significantly more laggy than the
same mouse used via it's 2.4ghz usb, and I use this same model mouse in
BT with win10 and
I also just installed on a pi 4 and had the same issue -- devices worked but
would not persist across reboots, and then successive re-adds were... strange,
unreliable, etc. Lots of "it appears to work but doesn't." Tried the PPA
packages and it worked at first, but was seriously inconsistent
I face a similar issue that I posted on ubuntu forum:
https://ubuntuforums.org/showthread.php?t=2452881
PPA solves my issue and interestingly changes the Bluetooth controller
address
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
First of all, this bug is so unpredictable, it's hard to replicate "on demand".
It was happening when I power off device and back on and after restart it
works, so it's not only what I said in description.
@Dave yes I installed your ppa and after that no device associated before were
present in
@Daniel could you try out the bluez package from the following PPA:
https://launchpad.net/~waveform/+archive/ubuntu/pi-bluetooth/+packages ?
Should be as simple as doing:
sudo add-apt-repository ppa:waveform/pi-bluetooth
sudo apt update
sudo apt upgrade
The version in that PPA contains
Is there any work needed on bluez or linux there?
** Tags removed: rls-gg-incoming
** Changed in: bluez (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: bluez (Ubuntu Groovy)
Status: New => Incomplete
** Changed in: linux-raspi (Ubuntu)
Status: Confirmed =>
** Changed in: pi-bluetooth (Ubuntu)
Assignee: (unassigned) => Dave Jones (waveform)
** Changed in: pi-bluetooth (Ubuntu Groovy)
Assignee: (unassigned) => Dave Jones (waveform)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Package changed: linux-raspi2 (Ubuntu) => linux-raspi (Ubuntu)
** Also affects: bluez (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: pi-bluetooth (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: linux-raspi (Ubuntu Groovy)
** Tags added: rls-gg-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901272
Title:
Can't connect Bluetooth devices after reboot - Ubuntu 20.10 on
Raspberry Pi 4
To manage notifications
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: pi-bluetooth (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901272
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-raspi2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901272
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: bluez (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901272
Title:
** Tags added: groovy
** Also affects: linux-raspi2 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: bluez (Ubuntu)
Importance: Undecided
Status: New
** Tags added: raspi
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Package changed: bluez (Ubuntu) => pi-bluetooth (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901272
Title:
Can't connect Bluetooth devices after reboot - Ubuntu 20.10 on
Raspberry
** Summary changed:
- Inconsistent Bluetooth behavior on reboot 20.10 on rpi4
+ Can't connect Bluetooth devices after reboot - Ubuntu 20.10 on Raspberry Pi 4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
20 matches
Mail list logo
