** Tags added: patch
--
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/1922792
Title:
Bluez should notify users when they need to reboot to apply changes on
Raspberry Pi
Status in bluez
** Changed in: bluez (Ubuntu)
Status: In Progress => Triaged
--
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/1922792
Title:
Bluez should notify users when they need to reboot to
** Tags removed: hirsute
--
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/1922792
Title:
Bluez should notify users when they need to reboot to apply changes on
Raspberry Pi
Status in
> Thanks for the details. You did address the part about upstreaming the
change to Debian. How important is that notification in practice? If
feels like we should have bluez preinstall on the raspi images if that's
not the case, and if it's pre-install is that really worth the packaging
overhead
Maybe unsubscribe Ubuntu Sponsors for the moment? Seb dropped this fix
from the latest update:
https://launchpad.net/ubuntu/+source/bluez/5.56-0ubuntu4
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
** Changed in: bluez (Debian)
Status: Unknown => New
--
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/1922792
Title:
Bluez should notify users when they need to reboot to apply
** Also affects: bluez (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986836
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
Thanks!
--
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/1922792
Title:
Bluez should notify users when they need to reboot to apply changes on
Raspberry Pi
Status in bluez package in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986836
Apparently I had not created the bug report correctly the first time.
** Bug watch added: Debian Bug tracker #986836
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986836
--
You received this bug notification because you are a
@William, thanks, could you share the Debian bug url? I browsed
https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=yes=bluez
but I'm not finding it...
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
** Changed in: bluez (Ubuntu)
Status: Incomplete => In Progress
--
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/1922792
Title:
Bluez should notify users when they need to reboot
I have submitted a Debian bug report with the patch suggested, and
updated the bug description.
bluez is pre-installed on the desktop images, but not the server images.
This warning would be very useful for server users that want to install
bluez for the first time.
--
You received this bug
** Description changed:
- In the case of upgrading bluez on certain raspberry pi devices, a reboot
- may be required to apply the changes. We should add a check for this
- scenario in the postinst script.
+ In the case of upgrading or installing bluez for the first time on
+ certain raspberry pi
Thanks for the details. You did address the part about upstreaming the
change to Debian. How important is that notification in practice? If
feels like we should have bluez preinstall on the raspi images if that's
not the case, and if it's pre-install is that really worth the packaging
overhead to
Seb,
A reboot is needed in this case because the bluetooth device on the
raspberry pi has to be initialized at boot time. Restarting the service
will not cause the device to be brought up.
The hardcoded addresses are the approach used in the pi-bluetooth
package, and recommended by waveform.
As
Thank you for the work, could give a bit more context why a reboot is
needed in those cases? Isn't restarting the service enough?
Having hardcoded addresses in the script seems a bit fragile. And is
that the sort of change we could try to upstream to Debian to not
increase our delta?
Also the
** Summary changed:
- Bluez should notify users when they need to reboot to apply changes on arm64
+ Bluez should notify users when they need to reboot to apply changes on
Raspberry Pi
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
17 matches
Mail list logo
