It seems that 6.8.0-49 has not been installed previously or is not
visible:

```
rc  linux-image-6.8.0-47-generic                  6.8.0-47.47                   
           amd64        Signed kernel image generic
rc  linux-image-6.8.0-48-generic                  6.8.0-48.48                   
           amd64        Signed kernel image generic
ii  linux-image-6.8.0-50-generic                  6.8.0-50.51                   
           amd64        Signed kernel image generic
ii  linux-image-6.8.0-51-generic                  6.8.0-51.52                   
           amd64        Signed kernel image generic
ii  linux-image-generic                           6.8.0-51.52
```

However, I can confirm that this issue is not new. I experienced it
around 8 months ago but never reported it. I wonder if the VPN
connection might be causing something unusual (though that would
potentially suggest a lower-level bug or some headless config issue
which reflects on the bluetooth controller status). Will try without a
VPN and see if the issue persists.

In any case, the issue isn’t particularly strenuous. If it happens and I
need Bluetooth again to connect my earbuds, I simply restart the laptop.
It’s mildly annoying at worst.

Have a great Christmas.


Sent with Proton Mail secure email.

On Tuesday, December 24th, 2024 at 3:49 PM, Jeremy
<[email protected]> wrote:

> Can you try booting into kernel 6.8.0-49 and see if the problem exists
> 
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/2092413
> 
> Title:
> Bluetooth can't be turned on, after turning it off manually
> 
> Status in bluez package in Ubuntu:
> New
> 
> Bug description:
> Hello my most principally distinguished developers and representatives of the 
> Ubuntu(Linux) and Human interface,
> My bluetooth does not turn back on after manually turning off from the UI or 
> from the terminal.
> "qd91@daniel-Latitude-5420:~$ bluetoothctl
> Waiting to connect to bluetoothd...[bluetooth]# Agent registered
> [bluetooth]# power on
> No default controller available
> [bluetooth]# exit"
> Thank you for your kind consideration.
> 
> ProblemType: Bug
> DistroRelease: Ubuntu 24.04
> Package: bluez 5.72-0ubuntu5
> ProcVersionSignature: Ubuntu 6.8.0-51.52-generic 6.8.12
> Uname: Linux 6.8.0-51-generic x86_64
> ApportVersion: 2.28.1-0ubuntu3.3
> Architecture: amd64
> CasperMD5CheckResult: pass
> CurrentDesktop: ubuntu:GNOME
> Date: Mon Dec 23 18:13:28 2024
> InstallationDate: Installed on 2024-02-08 (319 days ago)
> InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
> (20230807.2)
> InterestingModules: rfcomm bnep btusb bluetooth
> MachineType: Dell Inc. Latitude 5420
> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-51-generic 
> root=UUID=02738a08-52ac-4d19-88c9-cacd3b303bbb ro quiet splash vt.handoff=7
> SourcePackage: bluez
> UpgradeStatus: Upgraded to noble on 2024-05-22 (215 days ago)
> dmi.bios.date: 11/10/2023
> dmi.bios.release: 1.33
> dmi.bios.vendor: Dell Inc.
> dmi.bios.version: 1.33.0
> dmi.board.name: 0772C9
> dmi.board.vendor: Dell Inc.
> dmi.board.version: A00
> dmi.chassis.type: 10
> dmi.chassis.vendor: Dell Inc.
> dmi.modalias: 
> dmi:bvnDellInc.:bvr1.33.0:bd11/10/2023:br1.33:svnDellInc.:pnLatitude5420:pvr:rvnDellInc.:rn0772C9:rvrA00:cvnDellInc.:ct10:cvr:sku0A20:
> dmi.product.family: Latitude
> dmi.product.name: Latitude 5420
> dmi.product.sku: 0A20
> dmi.sys.vendor: Dell Inc.
> hciconfig:
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2092413/+subscriptions

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2092413

Title:
  Bluetooth can't be turned on, after turning it off manually

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2092413/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to