This bug was fixed in the package bluez - 5.53-0ubuntu3.1
---
bluez (5.53-0ubuntu3.1) focal; urgency=medium
* Add support for the pi 400 (LP: #1903048)
-- William 'jawn-smith' Wilson Mon, 15
Mar 2021 19:25:22 +
** Changed in: bluez (Ubuntu Focal)
Status: Fix
The verification passed for focal.
* On Pi 400 **
ubuntu@ubuntu:~$ apt-cache policy bluez pi-bluetooth linux-firmware-raspi2
bluez:
Installed: 5.53-0ubuntu3
Candidate: 5.53-0ubuntu3.1
Version table:
5.53-0ubuntu3.1 500
500 http://ports.ubuntu.com/ubuntu-ports
Hello Dave, or anyone else affected,
Accepted bluez into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/bluez/5.53-0ubuntu3.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Thanks, uploaded to the focal queue now!
** Changed in: bluez (Ubuntu Focal)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
** Changed in: bluez (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: bluez (Ubuntu Groovy)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
@seb128 it turns out Dave had already forwarded the patches, so I
included the URLs in this new debdiff
@vanvugt I set the version to ubuntu3.1 rather than ubuntu4
** Patch added: "Focal SRU"
Also is the correct version 5.53-0ubuntu3.1 ?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1903048
Title:
[SRU] Bluetooth won't activate on the pi 400
Status in bluez
@William, thanks for the work. Some of those patches are 'forwarded:
no', anything blocking upstreaming the fixes? That would be preferable
to do before upload because experience from the previous SRU round
showed it's likely to not happen otherwise
--
You received this bug notification because
** Also affects: bluez (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: bluez (Ubuntu Focal)
Status: New => In Progress
** Changed in: bluez (Ubuntu Focal)
Assignee: (unassigned) => William Wilson (jawn-smith)
--
You received this bug notification because
Attached is a patch to SRU for focal.
** Patch added: "Focal SRU"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903048/+attachment/5477287/+files/lp1903048_focal.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Changed in: bluez (Ubuntu Hirsute)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1903048
Title:
[SRU] Bluetooth won't activate on
Thanks Dave, the updated patches have been uploaded now, removing the
block-proposed
** Tags removed: block-proposed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1903048
There's a version of bluez with the patches that I've submitted upstream
built in the following PPA against the hirsute branch (the patch changes
are pretty minimal; basically amounts to removal of the arbitrary
sleep(1) as during December's tests I couldn't find a single platform
that actually
Or maybe use bug 1905627 from now on :)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1903048
Title:
[SRU] Bluetooth won't activate on the pi 400
Status in bluez package
yonailo, that must be a different issue. :(
Please open a new bug by running:
ubuntu-bug bluez
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1903048
Title:
[SRU]
Bluetooth does not work any more on my Raspberry Pi 400 :
system : Ubuntu 20.10 (groovy)
kernel : 5.8.0-1011-raspi
bluez : 5.55-0ubuntu1.1
It used to work when I installed the Ubuntu 20.10 image, the groovy-
updates has done something wrong :(
--
You received this bug notification because you
I installed version 5.55-0ubuntu2
did not make a difference.
in journalctl is this :
bluetoothd[40120]: src/main.c:parse_controller_config() Key file does not have
group “Controller”
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
I opened a new bug #1905627. And I didn't change anything regarding
Bluetooth from Ubuntu 20.10 default configuration. There is no miniuart-
bt in /boot/firmware/config.txt.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
@hujq is there anything unusual about your bluetooth setup? miniuart-bt
overlay or anything like that? I'm unable to replicate the failure here
on a Pi 4 8GB
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
Could you open a new report about the regression using 'ubuntu-bug
bluez'?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1903048
Title:
[SRU] Bluetooth won't activate on
Hi,
This update seems to break Bluetooth on the Pi 4 8GB. /usr/bin/btuart returns
"bcm43xx_init Initialization timed out". It's working again after reverting to
version 5.55-0ubuntu1.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
This bug was fixed in the package bluez - 5.55-0ubuntu1.1
---
bluez (5.55-0ubuntu1.1) groovy; urgency=medium
* Added patches from the Raspberry Pi Foundation
- d/p/raspi-bcm43xx-load-firmware.patch
- d/p/raspi-bcm43xx-3wire.patch
- d/p/raspi-cypress-305-bdaddr.patch
*
Releasing this a day earlier to get the update shipped to users ASAP.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1903048
Title:
[SRU] Bluetooth won't activate on the pi
I also tried this on my pi400 and confirmed I can see and connect to
bluetooth devices after updating to bluez 5.55-0ubuntu1.1 from groovy-
proposed
** Tags removed: verification-needed verification-needed-groovy
** Tags added: verification-done verification-done-groovy
--
You received this bug
I've just used a fresh image of Mate 20.10 and used -proposed and done a
full update and reboot. My bluetooth mouse, headphones and external
keyboard are working fine now with this build so this bug has been fixed
for me.
Thank you all for your efforts in getting it sorted
Kind regards
Tony
--
Hello Dave, or anyone else affected,
Accepted bluez into groovy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/bluez/5.55-0ubuntu1.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
On Fri, Nov 13, 2020 at 09:37:34AM -, Sebastien Bacher wrote:
>@Matthieu, @Dave, thanks for the comments and details.
>
>I'm not blocking work to land, the 20.10 SRU could be accepted now and I
>didn't revert in that serie.
>The SRU team tries to ensure the fix is in the new serie so it
The point for me is that we should be trying to avoid taking on
indefinite technical debt (patches that have to be rebased forever).
It's "fine" to include them ahead of any upstream schedule if we need to
for hardware enablement, but we do need to have plans to make this be a
non permanent
@tmolloy, thank you for circling back around. I'm glad the patches worked for
you :-)
Note that there are other (unrelated) packages in @waveform's PPA that may get
installed with an apt upgrade. I don't know what the state of those packages
are. I disabled the PPA after installing bluez, just
There is no intend here to block any fix for stable serie but in case
that was not clear enough or if the SRU team didn't feel comfortable
with hirsute lacking behind and I uploaded back the patches but I'm
tagging the bug as 'block-proposed' instead which should be enough
incensitive to sort out
@Matthieu, @Dave, thanks for the comments and details.
I'm not blocking work to land, the 20.10 SRU could be accepted now and I didn't
revert in that serie.
The SRU team tries to ensure the fix is in the new serie so it doesn't get
forgotten/regress when next version is out but I think it's
On Thu, Nov 12, 2020 at 11:11:23AM -, Sebastien Bacher wrote:
>Sorry but I'm reverting that upload for now until the patches are
>properly upstreamed. We have been bitten too often by unforwarded
>changes that create issues or create maintainance burden over the years
>and we currently don't
@seb128: Do you think you can re-revert this change? we are going
to work with upstream and give them access to the patch. I don't think
we should should prevent the device to work until this is done.
As Chris said in #20, there's a lot of hype on the pi400 and
bluetooth not working is
What's the status of this? We desperately need this fix in Groovy, as
we're making lots of noise about the pi400 and this is a pretty glaring
hole in functionality.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in
On Ubuntu 20.10 MATE on a pi400, I ran through the following steps:
* Boot the Ubuntu 20.10 MATE for Pi image on a Pi 400 (Was not a fresh
installation)
* Start the Settings application and switch to the Bluetooth tab
* Verify that Bluetooth is not enabled and attempting to activate it fails
*
> Was the revert discussed somewhere before being performed?
I pinged you guys on IRC some days ago but didn't get any comment back
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
> in the meantime maintain the patches ourselves as many others related
to the Pi (as in various other projects)
I'm not asking for the patches to be merged upstream but at least to be
sent there for review and have the appropriate tagging, it's easy to
unblock from your side. Also I would like
I personally think the revert is a bit extreme. Even though we are not
maintainers of bluez, this being a critical feature for the Pi400 we
would of course make sure that the changes get upstreamed as much as
possible and in the meantime maintain the patches ourselves as many
others related to the
I understand the logic of the of doing this and don't disagree.
However, as this is an entry level device and I believe the only true
64bit O/S advertised for this device, the fact that it does not not
work out of the box may impact on the perception of potential new
Ubuntu users?
Reading Tony's
> I'm not convinced it's worth investing the time required to figure out
the minimum.
The value of the sleep is not really the issue but it feels like there
should be a better way to tell when the system is ready, what are we
waiting for? Is there any api call we could do to check if the thing we
Sorry but I'm reverting that upload for now until the patches are
properly upstreamed. We have been bitten too often by unforwarded
changes that create issues or create maintainance burden over the years
and we currently don't have the team capacity to deal with extra cost.
If foundations would
On Tue, Nov 10, 2020 at 03:12:30PM -, Sebastien Bacher wrote:
>Thanks for the work but it there any work to upstream those changes? I'm
>not happy to carry a sleep(1) hack in our package unless there is a
>strong reason and we are working on a way to replace it by a better
>solution
The
Hi,
I implemented the fix detailed in the test case yesterday and the bug
still existed. I've double checked again this morning and done a
full-upgrade just to check nothing new was waiting and the bug still
exists on this Mate 20.10 install. Yesterday after applying the fix I
started getting
Łukasz and Dave, thanks for the fix.
I have renamed 'ubuntu' to 'hirsute' to keep with the existing naming
scheme: https://git.launchpad.net/~bluetooth/bluez
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
This bug was fixed in the package bluez - 5.55-0ubuntu2
---
bluez (5.55-0ubuntu2) hirsute; urgency=medium
* Added patches from the Raspberry Pi Foundation
- d/p/raspi-bcm43xx-load-firmware.patch
- d/p/raspi-bcm43xx-3wire.patch
- d/p/raspi-cypress-305-bdaddr.patch
*
** Also affects: bluez (Ubuntu Hirsute)
Importance: High
Assignee: Dave Jones (waveform)
Status: Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
Thanks guys for all the work.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1903048
Title:
[SRU] Bluetooth won't activate on the pi 400
Status in bluez package in Ubuntu:
Test case works perfectly on the Pi400.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1903048
Title:
[SRU] Bluetooth won't activate on the pi 400
Status in bluez package
Thanks for the work but it there any work to upstream those changes? I'm
not happy to carry a sleep(1) hack in our package unless there is a
strong reason and we are working on a way to replace it by a better
solution
--
You received this bug notification because you are a member of Ubuntu
Touch
** Changed in: bluez (Ubuntu)
Importance: Undecided => High
** Changed in: bluez (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
** Description changed:
+ [Impact]
+
+ Without these patches, Bluetooth is inoperable on the recently released
+ Raspberry Pi 400.
+
+ [Test Case]
+
+ * Boot the Ubuntu Desktop for Pi image on a Pi 400.
+ * Start the Settings application and switch to the Bluetooth tab
+ * Verify that
** Summary changed:
- Bluetooth won't activate on the pi 400
+ [SRU] Bluetooth won't activate on the pi 400
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1903048
Title:
52 matches
Mail list logo
