Comment 56 for bug 2051720

Created attachment 306340
dmesg log

(In reply to Paul Menzel from comment #26)
> @nickolas, from your bug description it’s unclear, if this is a regression,
> or if Bluetooth never worked for you. Could you please clarify?
>
> Please attach the output of `dmesg`.
>
> Also, please run `bluetoothctl` and share all the output.

The issue is still presenting the same as originally reported, bluetooth does not work on boot and requires the reset script I provided before it will start working. The only difference between then and now is that one log is missing.

Here are the extra logs you've asked for, the dmesg log was quite long so I attached it as a file:

# dmesg
(see attached file)

(before running the reset script)
$ bluetoothctl
Waiting to connect to bluetoothd...

(after running the reset script)
$ bluetoothctl
Waiting to connect to bluetoothd...[bluetooth]# Agent registered
[bluetooth]# hci0 new_settings: powered bondable ssp br/edr le secure-conn wide-band-speech
[bluetooth]# [CHG] Controller A4:B1:C1:D5:F5:24 Pairable: yes
[bluetooth]# AdvertisementMonitor path registered
[bluetooth]#

(In reply to Dustin from comment #27)
> This is a regression. It has been broken since 6.5. It worked fine in prior
> kernel versions.

I believe your issue is different than this one, this issue has been reported starting in 5.16 on the original bug linked that they closed and asked for someone to make a new issue if it was still present.