Bluetooth problems with Fedora Workstation 36 and HP Spectre

I have had this regularly following updates to Fedora 36 (and perhaps earlier with 35) then it goes away again after a further update.

HW is an HP Spectre

Just before today’s update I confirmed that that Bluetooth was listed by Gnome as still Off.

Immediately after the update I confirmed that it was now On.

Bellow are my notes from the Gnome Software display of items updated that looked to me as conceivably the update that fixed Bluetooth again (and which will get broken again by a subsequent update as the pattern has been repeated many times).

I am reasonably certain it is fixed by one of the files in the same update that I have extracted below. If given the exact command to get the full log I can do it, but I assume these 3 lines indicate which set of updates is worth checking is likely to contain the fix that repeatedly gets broken.

2023-03-26T2030 BT reappeared routine upgrade

$ uname -a
Linux fedora 6.2.7-100.fc36.x86_64 #1 SMP PREEMPT_DYNAMIC Fri Mar 17 16:53:15 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

elfutils 0.189-1.fc36 Upgrade to upsteam elfutils 0.189.

osinfo-db 20230308-1.fc36 osinfo-db Update to new release (v20230308)

wireplumber 0.4.14-1.fc36 wireplumber 0.4.14

[admin@fedora ~]$ inxi -Fzx
System:
  Kernel: 6.2.7-100.fc36.x86_64 arch: x86_64 bits: 64 compiler: gcc
    v: 2.37-37.fc36 Desktop: GNOME v: 42.6 Distro: Fedora release 36 (Thirty
    Six)
Machine:
  Type: Convertible System: HP product: HP Spectre x360 Convertible 13-aw0xxx
    v: N/A serial: <superuser required>
  Mobo: HP model: 86F9 v: 87.46 serial: <superuser required> UEFI: AMI
    v: F.13 date: 03/02/2020
Battery:
  ID-1: BAT0 charge: 58.6 Wh (100.0%) condition: 58.6/60.8 Wh (96.4%)
    volts: 15.4 min: 15.4 model: HP Primary status: full
  Device-1: hid-0018:04F3:29E0.0001-battery model: ELAN2514:00 04F3:29E0
    charge: N/A status: N/A
CPU:
  Info: quad core model: Intel Core i7-1065G7 bits: 64 type: MT MCP
    arch: Ice Lake rev: 5 cache: L1: 320 KiB L2: 2 MiB L3: 8 MiB
  Speed (MHz): avg: 1334 high: 1500 min/max: 400/3900 cores: 1: 1113 2: 1500
    3: 1500 4: 1500 5: 1500 6: 1166 7: 1197 8: 1200 bogomips: 23961
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel Iris Plus Graphics G7 vendor: Hewlett-Packard driver: i915
    v: kernel arch: Gen-11 bus-ID: 00:02.0
  Device-2: Quanta HP True Vision HD Camera type: USB driver: uvcvideo
    bus-ID: 2-5:3
  Display: wayland server: X.Org v: 1.22.1.8 with: Xwayland v: 22.1.8
    compositor: gnome-shell driver: X: loaded: modesetting unloaded: fbdev,vesa
    dri: iris gpu: i915 resolution: 1920x1080~60Hz
  API: OpenGL v: 4.6 Mesa 22.1.7 renderer: Mesa Intel Iris Plus Graphics
    (ICL GT2) direct-render: Yes
Audio:
  Device-1: Intel Ice Lake-LP Smart Sound Audio vendor: Hewlett-Packard
    driver: sof-audio-pci-intel-icl bus-ID: 00:1f.3
  Sound API: ALSA v: k6.2.7-100.fc36.x86_64 running: yes
  Sound Server-1: PulseAudio v: 15.0 running: no
  Sound Server-2: PipeWire v: 0.3.67 running: yes
Network:
  Device-1: Intel Ice Lake-LP PCH CNVi WiFi driver: iwlwifi v: kernel
    bus-ID: 00:14.3
  IF: wlo1 state: up mac: <filter>
  IF-ID-1: virbr0 state: down mac: <filter>
Bluetooth:
  Device-1: Intel AX201 Bluetooth type: USB driver: btusb v: 0.8
    bus-ID: 2-10:8
  Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends
RAID:
  Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode] driver: ahci
    v: 3.0 bus-ID: 00:17.0
Drives:
  Local Storage: total: 986.1 GiB used: 222.06 GiB (22.5%)
  ID-1: /dev/nvme0n1 vendor: Samsung model: MZVLB512HAJQ-000H1
    size: 476.94 GiB temp: 37.9 C
  ID-2: /dev/sda type: USB vendor: Samsung model: Portable SSD T5
    size: 465.76 GiB
  ID-3: /dev/sdb type: USB vendor: Verbatim model: STORE N GO
    size: 14.55 GiB
  ID-4: /dev/sdc type: USB model: USB DISK 3.0 Pro size: 28.85 GiB
Partition:
  ID-1: / size: 464.09 GiB used: 187.83 GiB (40.5%) fs: btrfs dev: /dev/sda3
  ID-2: /boot size: 1004.8 MiB used: 257.6 MiB (25.6%) fs: ext4
    dev: /dev/sda2
  ID-3: /boot/efi size: 574.8 MiB used: 17.4 MiB (3.0%) fs: vfat
    dev: /dev/sda1
  ID-4: /home size: 464.09 GiB used: 187.83 GiB (40.5%) fs: btrfs
    dev: /dev/sda3
Swap:
  ID-1: swap-1 type: zram size: 8 GiB used: 1.8 MiB (0.0%) dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 53.0 C mobo: N/A
  Fan Speeds (RPM): cpu: 0 fan-2: 0
Info:
  Processes: 523 Uptime: 52m Memory: 15.35 GiB used: 6.29 GiB (41.0%)
  Init: systemd target: graphical (5) Compilers: gcc: 12.2.1 Packages: 42
  note: see --rpm Shell: Bash v: 5.2.15 inxi: 3.3.25

I edited your post above to add the Preformatted text tags </> to the inxi output you provided.

To see the full list of packages that were updated you should be able to run dnf history --reverse to get a list of updates performed, then with the last one performed run dnf history info <idnum> using the id number of the update of interest and it should show the packages that were updated.

Note that I cannot be 100% certain that this works the same when using gnome software to do the updates. I always use dnf from the command line for updates. Doing so gives me much more info and allows control of the updates.

1 Like

Thanks. Below looks the same as the gnome software update that restored BT. I omitted all but the three lines listed above because other packages do not look to me capable of affecting BT.

My suspicion would be on osinfo-db-20230308-1.fc36.noarch - as an OS info database ought to be updated simultaneously with other updates to kernel etc rather than out of sync creating a gap between changes that break things and fixes recorded in the database. But I would not know.

The other two packages I listed were elfutils because it looks very “deep system” that could break or fix anything and wireplumber because it looks like something that could record BT as a “plumbing” connection wire that could be reconnected when broken.

[admin@fedora ~]$ dnf history info 314
Transaction ID : 314
Begin time     : Sun 26 Mar 2023 08:22:49 PM AEDT
Begin rpmdb    : e00b862fe4482551745838f0ae9ac5b31e56a31aaab69ca7da5feca68b33b2f4
End time       : Sun 26 Mar 2023 08:22:55 PM AEDT (6 seconds)
End rpmdb      : adfec7feb995ba2df762a471d2173e8040809ce557c7beaff77712ba7b1b8834
User           : root <root>
Return-Code    : Success
Releasever     : 
Command Line   : 
Comment        : 
Packages Altered:
    Upgrade  elfutils-0.189-1.fc36.x86_64                         @updates
    Upgrade  elfutils-debuginfod-client-0.189-1.fc36.x86_64       @updates
    Upgrade  elfutils-debuginfod-client-devel-0.189-1.fc36.x86_64 @updates
    Upgrade  elfutils-default-yama-scope-0.189-1.fc36.noarch      @updates
    Upgrade  elfutils-devel-0.189-1.fc36.x86_64                   @updates
    Upgrade  elfutils-libelf-0.189-1.fc36.x86_64                  @updates
    Upgrade  elfutils-libelf-devel-0.189-1.fc36.x86_64            @updates
    Upgrade  elfutils-libs-0.189-1.fc36.x86_64                    @updates
    Upgrade  httpd-2.4.56-1.fc36.x86_64                           @updates
    Upgrade  httpd-core-2.4.56-1.fc36.x86_64                      @updates
    Upgrade  httpd-filesystem-2.4.56-1.fc36.noarch                @updates
    Upgrade  httpd-manual-2.4.56-1.fc36.noarch                    @updates
    Upgrade  httpd-tools-2.4.56-1.fc36.x86_64                     @updates
    Upgrade  mod_lua-2.4.56-1.fc36.x86_64                         @updates
    Upgrade  mod_ssl-1:2.4.56-1.fc36.x86_64                       @updates
    Upgrade  openldap-2.6.4-1.fc36.x86_64                         @updates
    Upgrade  openldap-compat-2.6.4-1.fc36.x86_64                  @updates
    Upgrade  osinfo-db-20230308-1.fc36.noarch                     @updates
    Upgrade  php-8.1.17-1.fc36.x86_64                             @updates
    Upgrade  php-cli-8.1.17-1.fc36.x86_64                         @updates
    Upgrade  php-common-8.1.17-1.fc36.x86_64                      @updates
    Upgrade  php-fpm-8.1.17-1.fc36.x86_64                         @updates
    Upgrade  php-gd-8.1.17-1.fc36.x86_64                          @updates
    Upgrade  php-intl-8.1.17-1.fc36.x86_64                        @updates
    Upgrade  php-ldap-8.1.17-1.fc36.x86_64                        @updates
    Upgrade  php-mbstring-8.1.17-1.fc36.x86_64                    @updates
    Upgrade  php-mysqlnd-8.1.17-1.fc36.x86_64                     @updates
    Upgrade  php-opcache-8.1.17-1.fc36.x86_64                     @updates
    Upgrade  php-pdo-8.1.17-1.fc36.x86_64                         @updates
    Upgrade  php-sodium-8.1.17-1.fc36.x86_64                      @updates
    Upgrade  php-xml-8.1.17-1.fc36.x86_64                         @updates
    Upgrade  wireplumber-0.4.14-1.fc36.x86_64                     @updates
    Upgrade  wireplumber-libs-0.4.14-1.fc36.x86_64                @updates
    Upgraded elfutils-0.188-3.fc36.x86_64                         @@System
    Upgraded elfutils-debuginfod-client-0.188-3.fc36.x86_64       @@System
    Upgraded elfutils-debuginfod-client-devel-0.188-3.fc36.x86_64 @@System
    Upgraded elfutils-default-yama-scope-0.188-3.fc36.noarch      @@System
    Upgraded elfutils-devel-0.188-3.fc36.x86_64                   @@System
    Upgraded elfutils-libelf-0.188-3.fc36.x86_64                  @@System
    Upgraded elfutils-libelf-devel-0.188-3.fc36.x86_64            @@System
    Upgraded elfutils-libs-0.188-3.fc36.x86_64                    @@System
    Upgraded httpd-2.4.55-1.fc36.x86_64                           @@System
    Upgraded httpd-core-2.4.55-1.fc36.x86_64                      @@System
    Upgraded httpd-filesystem-2.4.55-1.fc36.noarch                @@System
    Upgraded httpd-manual-2.4.55-1.fc36.noarch                    @@System
    Upgraded httpd-tools-2.4.55-1.fc36.x86_64                     @@System
    Upgraded mod_lua-2.4.55-1.fc36.x86_64                         @@System
    Upgraded mod_ssl-1:2.4.55-1.fc36.x86_64                       @@System
    Upgraded openldap-2.6.3-1.fc36.x86_64                         @@System
    Upgraded openldap-compat-2.6.3-1.fc36.x86_64                  @@System
    Upgraded osinfo-db-20221130-1.fc36.noarch                     @@System
    Upgraded php-8.1.16-1.fc36.x86_64                             @@System
    Upgraded php-cli-8.1.16-1.fc36.x86_64                         @@System
    Upgraded php-common-8.1.16-1.fc36.x86_64                      @@System
    Upgraded php-fpm-8.1.16-1.fc36.x86_64                         @@System
    Upgraded php-gd-8.1.16-1.fc36.x86_64                          @@System
    Upgraded php-intl-8.1.16-1.fc36.x86_64                        @@System
    Upgraded php-ldap-8.1.16-1.fc36.x86_64                        @@System
    Upgraded php-mbstring-8.1.16-1.fc36.x86_64                    @@System
    Upgraded php-mysqlnd-8.1.16-1.fc36.x86_64                     @@System
    Upgraded php-opcache-8.1.16-1.fc36.x86_64                     @@System
    Upgraded php-pdo-8.1.16-1.fc36.x86_64                         @@System
    Upgraded php-sodium-8.1.16-1.fc36.x86_64                      @@System
    Upgraded php-xml-8.1.16-1.fc36.x86_64                         @@System
    Upgraded wireplumber-0.4.13-1.fc36.x86_64                     @@System
    Upgraded wireplumber-libs-0.4.13-1.fc36.x86_64                @@System
[admin@fedora ~]$

Note, last item was 315 - me installing inxi to produce above report:


[admin@fedora ~]$ dnf history info 315
Transaction ID : 315
Begin time     : Sun 26 Mar 2023 09:15:45 PM AEDT
Begin rpmdb    : adfec7feb995ba2df762a471d2173e8040809ce557c7beaff77712ba7b1b8834
End time       : Sun 26 Mar 2023 09:15:47 PM AEDT (2 seconds)
End rpmdb      : a162f2f3c2284f9d9d8fd7ee2500637c8e0292998ca5964ca43ba0e806f11799
User           : Admin <admin>
Return-Code    : Success
Releasever     : 
Command Line   : 
Comment        : 
Packages Altered:
    Install freeipmi-1.6.10-1.fc36.x86_64            @updates
    Install inxi-3.3.25-1.fc36.noarch                @updates
    Install hddtemp-0.3-0.50.beta15.fc36.x86_64      @fedora
    Install ipmitool-1.8.18-25.fc36.x86_64           @fedora
    Install lm_sensors-3.6.0-11.fc36.x86_64          @fedora
    Install lm_sensors-libs-3.6.0-11.fc36.x86_64     @fedora
    Install perl-Cpanel-JSON-XS-4.27-2.fc36.x86_64   @fedora
    Install perl-JSON-XS-1:4.03-6.fc36.x86_64        @fedora
    Install perl-Types-Serialiser-1.01-5.fc36.noarch @fedora
    Install perl-XML-Dumper-0.81-43.fc36.noarch      @fedora
    Install perl-common-sense-3.7.5-8.fc36.x86_64    @fedora
    Install wmctrl-1.07-32.fc36.x86_64               @fedora
    Install xrandr-1.5.1-4.fc36.x86_64               @fedora
[admin@fedora ~]$

But not relevant as BT was fixed by 314.

PS now solved problem of using preformatted icon to avoid error message that new users cannot mention more than one user. Can delete hidden drafts.

As expected a subsequent update has again broken BT (turned Off in Gnome) after confirming it remained turned On following each update performed since my previous report of update that turned it On.

Very short list so my guess is that the two (!?) upgrades to python3-pytz are somehow turning it off.

Hopefully these 2 confirmed reports of exact updates that toggle regular repeated BT breakage should enable tracking it down.

Please confirm this info is sufficient for somebody competent to enter it into issue tracker.

[admin@fedora ~]$ dnf history info 320
Transaction ID : 320
Begin time     : Sat 08 Apr 2023 09:42:15 PM AEST
Begin rpmdb    : b80d0a5cfc84c7d606d4bd47a8471f769cebc54d7b093e489b61e9502a5c342b
End time       : Sat 08 Apr 2023 09:42:18 PM AEST (3 seconds)
End rpmdb      : 9d7d9ec358fc5367f817e4572bae29c2eb3d9287c0910a63f7230b07ad327f5a
User           : root <root>
Return-Code    : Success
Releasever     : 
Command Line   : 
Comment        : 
Packages Altered:
    Upgrade  mtools-4.0.43-1.fc36.x86_64         @updates
    Upgrade  python3-pytz-2023.3-1.fc36.noarch   @updates
    Upgraded mtools-4.0.42-1.fc36.x86_64         @@System
    Upgraded python3-pytz-2022.7.1-1.fc36.noarch @@System
[admin@fedora ~]$ 

[admin@fedora ~]$ inxi -Fzx
System:
  Kernel: 6.2.8-100.fc36.x86_64 arch: x86_64 bits: 64 compiler: gcc
    v: 2.37-37.fc36 Desktop: GNOME v: 42.6 Distro: Fedora release 36 (Thirty
    Six)
Machine:
  Type: Convertible System: HP product: HP Spectre x360 Convertible 13-aw0xxx
    v: N/A serial: <superuser required>
  Mobo: HP model: 86F9 v: 87.46 serial: <superuser required> UEFI: AMI
    v: F.13 date: 03/02/2020
Battery:
  ID-1: BAT0 charge: 58.6 Wh (100.0%) condition: 58.6/60.8 Wh (96.4%)
    volts: 15.3 min: 15.4 model: HP Primary status: full
  Device-1: hid-0018:04F3:29E0.0001-battery model: ELAN2514:00 04F3:29E0
    charge: N/A status: N/A
CPU:
  Info: quad core model: Intel Core i7-1065G7 bits: 64 type: MT MCP
    arch: Ice Lake rev: 5 cache: L1: 320 KiB L2: 2 MiB L3: 8 MiB
  Speed (MHz): avg: 1195 high: 1500 min/max: 400/3900 cores: 1: 830 2: 1500
    3: 1062 4: 1067 5: 1005 6: 1500 7: 1100 8: 1500 bogomips: 23961
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel Iris Plus Graphics G7 vendor: Hewlett-Packard driver: i915
    v: kernel arch: Gen-11 bus-ID: 00:02.0
  Device-2: Quanta HP True Vision HD Camera type: USB driver: uvcvideo
    bus-ID: 3-5:3
  Display: wayland server: X.Org v: 1.22.1.8 with: Xwayland v: 22.1.8
    compositor: gnome-shell driver: X: loaded: modesetting unloaded: fbdev,vesa
    dri: iris gpu: i915 resolution: 1920x1080~60Hz
  API: OpenGL v: 4.6 Mesa 22.1.7 renderer: Mesa Intel Iris Plus Graphics
    (ICL GT2) direct-render: Yes
Audio:
  Device-1: Intel Ice Lake-LP Smart Sound Audio vendor: Hewlett-Packard
    driver: sof-audio-pci-intel-icl bus-ID: 00:1f.3
  Sound API: ALSA v: k6.2.8-100.fc36.x86_64 running: yes
  Sound Server-1: PulseAudio v: 15.0 running: no
  Sound Server-2: PipeWire v: 0.3.67 running: yes
Network:
  Device-1: Intel Ice Lake-LP PCH CNVi WiFi driver: iwlwifi v: kernel
    bus-ID: 00:14.3
  IF: wlo1 state: up mac: <filter>
  IF-ID-1: virbr0 state: down mac: <filter>
Bluetooth:
  Device-1: Intel AX201 Bluetooth type: USB driver: btusb v: 0.8
    bus-ID: 3-10:7
  Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends
RAID:
  Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode] driver: ahci
    v: 3.0 bus-ID: 00:17.0
Drives:
  Local Storage: total: 986.1 GiB used: 223.68 GiB (22.7%)
  ID-1: /dev/nvme0n1 vendor: Samsung model: MZVLB512HAJQ-000H1
    size: 476.94 GiB temp: 28.9 C
  ID-2: /dev/sda type: USB vendor: Samsung model: Portable SSD T5
    size: 465.76 GiB
  ID-3: /dev/sdb type: USB vendor: Verbatim model: STORE N GO
    size: 14.55 GiB
  ID-4: /dev/sdc type: USB model: USB DISK 3.0 Pro size: 28.85 GiB
Partition:
  ID-1: / size: 464.09 GiB used: 189.44 GiB (40.8%) fs: btrfs dev: /dev/sda3
  ID-2: /boot size: 1004.8 MiB used: 261.9 MiB (26.1%) fs: ext4
    dev: /dev/sda2
  ID-3: /boot/efi size: 574.8 MiB used: 17.4 MiB (3.0%) fs: vfat
    dev: /dev/sda1
  ID-4: /home size: 464.09 GiB used: 189.44 GiB (40.8%) fs: btrfs
    dev: /dev/sda3
Swap:
  ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 35.0 C mobo: N/A
  Fan Speeds (RPM): cpu: 0 fan-2: 0
Info:
  Processes: 375 Uptime: 15m Memory: 15.35 GiB used: 7.25 GiB (47.2%)
  Init: systemd target: graphical (5) Compilers: gcc: 12.2.1 Packages: 43
  note: see --rpm Shell: Bash v: 5.2.15 inxi: 3.3.25
[admin@fedora ~]$ 

Following up on above. As expected from previous pattern another update turned off BlueTooth after checking that it was On immediately before. No other updates broke BlueTooth by turning Off since previous report that update 314 fixed it On.

[admin@fedora ~]$ dnf history info 328
Transaction ID : 328
Begin time     : Fri 28 Apr 2023 02:45:59 AM AEST
Begin rpmdb    : 775bfce2e1e74d972c5e470ca3c32d14d22b0bd9a538385bf3e7ffa4cdb1c7a8
End time       : Fri 28 Apr 2023 02:47:40 AM AEST (101 seconds)
End rpmdb      : 8ac4fe91986720495a761d06ef45a470a06cc975fdfa53f41dd07347d96e1176
User           : root <root>
Return-Code    : Success
Releasever     : 
Command Line   : 
Comment        : 
Packages Altered:
    Install  kernel-6.2.12-100.fc36.x86_64               @updates
    Install  kernel-core-6.2.12-100.fc36.x86_64          @updates
    Install  kernel-devel-6.2.12-100.fc36.x86_64         @updates
    Install  kernel-modules-6.2.12-100.fc36.x86_64       @updates
    Install  kernel-modules-core-6.2.12-100.fc36.x86_64  @updates
    Install  kernel-modules-extra-6.2.12-100.fc36.x86_64 @updates
    Upgrade  firefox-112.0.1-1.fc36.x86_64               @updates
    Upgrade  ghc-srpm-macros-1.6.1-1.fc36.noarch         @updates
    Upgrade  transmission-common-4.0.3-1.fc36.x86_64     @updates
    Upgrade  transmission-gtk-4.0.3-1.fc36.x86_64        @updates
    Upgraded kernel-6.2.9-100.fc36.x86_64                @@System
    Upgraded kernel-core-6.2.9-100.fc36.x86_64           @@System
    Upgraded kernel-devel-6.2.9-100.fc36.x86_64          @@System
    Upgraded kernel-modules-6.2.9-100.fc36.x86_64        @@System
    Upgraded kernel-modules-core-6.2.9-100.fc36.x86_64   @@System
    Upgraded kernel-modules-extra-6.2.9-100.fc36.x86_64  @@System
    Upgraded firefox-112.0-3.fc36.x86_64                 @@System
    Upgraded ghc-srpm-macros-1.5.0-6.fc36.noarch         @@System
    Upgraded transmission-common-4.0.2-1.fc36.x86_64     @@System
    Upgraded transmission-gtk-4.0.2-1.fc36.x86_64        @@System
[admin@fedora ~]$ 

[admin@fedora ~]$ inxi -Fzx
System:
  Kernel: 6.2.12-100.fc36.x86_64 arch: x86_64 bits: 64 compiler: gcc
    v: 2.37-37.fc36 Desktop: GNOME v: 42.9 Distro: Fedora release 36 (Thirty
    Six)
Machine:
  Type: Convertible System: HP product: HP Spectre x360 Convertible 13-aw0xxx
    v: N/A serial: <superuser required>
  Mobo: HP model: 86F9 v: 87.46 serial: <superuser required> UEFI: AMI
    v: F.13 date: 03/02/2020
Battery:
  ID-1: BAT0 charge: 58.6 Wh (100.0%) condition: 58.6/60.8 Wh (96.4%)
    volts: 15.2 min: 15.4 model: HP Primary status: full
  Device-1: hid-0018:04F3:29E0.0001-battery model: ELAN2514:00 04F3:29E0
    charge: N/A status: N/A
CPU:
  Info: quad core model: Intel Core i7-1065G7 bits: 64 type: MT MCP
    arch: Ice Lake rev: 5 cache: L1: 320 KiB L2: 2 MiB L3: 8 MiB
  Speed (MHz): avg: 1254 high: 1500 min/max: 400/3900 cores: 1: 1291 2: 464
    3: 1172 4: 1500 5: 1500 6: 1303 7: 1500 8: 1302 bogomips: 23961
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel Iris Plus Graphics G7 vendor: Hewlett-Packard driver: i915
    v: kernel arch: Gen-11 bus-ID: 00:02.0
  Device-2: Quanta HP True Vision HD Camera type: USB driver: uvcvideo
    bus-ID: 3-5:3
  Display: wayland server: X.Org v: 1.22.1.9 with: Xwayland v: 22.1.9
    compositor: gnome-shell driver: X: loaded: modesetting unloaded: fbdev,vesa
    dri: iris gpu: i915 resolution: 1920x1080~60Hz
  API: OpenGL v: 4.6 Mesa 22.1.7 renderer: Mesa Intel Iris Plus Graphics
    (ICL GT2) direct-render: Yes
Audio:
  Device-1: Intel Ice Lake-LP Smart Sound Audio vendor: Hewlett-Packard
    driver: sof-audio-pci-intel-icl bus-ID: 00:1f.3
  API: ALSA v: k6.2.12-100.fc36.x86_64 status: kernel-api
  Server-1: PipeWire v: 0.3.67 status: active
Network:
  Device-1: Intel Ice Lake-LP PCH CNVi WiFi driver: iwlwifi v: kernel
    bus-ID: 00:14.3
  IF: wlo1 state: up mac: <filter>
  IF-ID-1: virbr0 state: down mac: <filter>
RAID:
  Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode] driver: ahci
    v: 3.0 bus-ID: 00:17.0
Drives:
  Local Storage: total: 986.1 GiB used: 226.95 GiB (23.0%)
  ID-1: /dev/nvme0n1 vendor: Samsung model: MZVLB512HAJQ-000H1
    size: 476.94 GiB temp: 39.9 C
  ID-2: /dev/sda type: USB vendor: Samsung model: Portable SSD T5
    size: 465.76 GiB
  ID-3: /dev/sdb type: USB vendor: Verbatim model: STORE N GO
    size: 14.55 GiB
  ID-4: /dev/sdc type: USB model: USB DISK 3.0 Pro size: 28.85 GiB
Partition:
  ID-1: / size: 464.09 GiB used: 192.71 GiB (41.5%) fs: btrfs dev: /dev/sda3
  ID-2: /boot size: 1004.8 MiB used: 266.2 MiB (26.5%) fs: ext4
    dev: /dev/sda2
  ID-3: /boot/efi size: 574.8 MiB used: 17.4 MiB (3.0%) fs: vfat
    dev: /dev/sda1
  ID-4: /home size: 464.09 GiB used: 192.71 GiB (41.5%) fs: btrfs
    dev: /dev/sda3
Swap:
  ID-1: swap-1 type: zram size: 8 GiB used: 1.41 GiB (17.6%) dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 47.0 C mobo: N/A
  Fan Speeds (RPM): cpu: 0 fan-2: 0
Info:
  Processes: 462 Uptime: 23h 9m Memory: 15.35 GiB used: 10.21 GiB (66.5%)
  Init: systemd target: graphical (5) Compilers: gcc: 12.2.1 Packages: 43
  note: see --rpm Shell: Bash v: 5.2.15 inxi: 3.3.26
[admin@fedora ~]$ 

So presumably whatever fixed it in update 314 above broke it again in this update 328.

Hopefully it should now be possible to isolate the problem.

There were several kernel updates between 314 and 328. I still suspect it was fixed by osinfo-db when that was eventually updated. (But I would not know).

Please confirm this info has been properly entered into appropriate issue or point me to where to do it.

It’s possible that kernel updates introduce regressions in the Bluetooth driver, but it’s quite unlikely that a bug is fixed and unfixed repeatedly in such a short time.

Note that there was no kernel update in transaction 314 which you said fixed Bluetooth—in fact, there are no common packages between any of the transactions shown.

Regardless, to test if the latest kernel update is related to your Bluetooth not working again, you can use a previous kernel by holding the Shift key when booting (right after you see the manufacturer’s logo or BIOS/UEFI information). You will see a GRUB menu with several options; the top one should be your newest kernel 6.2.12-100.fc36. Choose the next highest version and see if Bluetooth works.

If it’s still broken, please post the output of the following commands:

dmesg | grep -i 'blue\|btusb'
rfkill

It’s also worth ruling out other causes. Do you dual boot with Windows? Fast Startup may cause issues. Even if you don’t dual boot, look for “fast boot” in your BIOS/UEFI settings and try disabling it if it was enabled.

Is there a Bluetooth or “Airplane mode” button on your keyboard? Have you tried pressing it (might require holding the Fn key)?

Do you see in “dmesg” the lines:

Bluetooth: hci0: Reading Intel version command failed (-110)
Bluetooth: hci0: command 0xfc05 tx timeout

There are kernel issues with Intel AX20x Bluetooth adapters.

Thanks!

Also included dmesg Bluetooth for @hmmsjan - displays no lines.

I installed Fedora on external SSD with no Windows and boot only from that directly via the Grub on that external SSD.

Am not aware of a Bluetooth or “Airplane mode” function key.

Gnome Help does not describe an icon for a Bluetooth function key. It does imply that the Gnome system menu at top right performs the same function.

The usual Bluetooth icon is not on my keyboard.

All icons on my HP Spectre keyboard function keys are as illustrated except:

Fn 5 has a different icon that better represents turning the (non-existant) keyboard backlight on

Fn 12 has an airplane icon at the above link but a microphone button and stop icon on my keyboard.

Pressing it toggles display of “Headphones Stereo Microphone” bar. Verified no effect on Bluetooth.
(BTW thanks for that - it may solve a separate problem I have had with video calls).

Current kernel after update 328 below.

I am certain Gnome displayed “Bluetooth Off” immediately before update 314 and “Bluetooth On” immediately after update 314 (with no kernel update). I did not actually select Gnome “Bluetooth settings” as the consistent pattern has been that when Off it displays:

No Bluetooth Found
Plug in a dongle to use Bluetooth.

Have confirmed that now.

Will also confirm it when I repeat requested tests using previous kernel.

[admin@fedora ~]$ uname -a
Linux fedora 6.2.12-100.fc36.x86_64 #1 SMP PREEMPT_DYNAMIC Fri Apr 21 00:10:57 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
[admin@fedora ~]$ 
[admin@fedora ~]$ dmesg | grep -i 'blue\|btusb'
rfkill
ID TYPE DEVICE      SOFT      HARD
 0 wlan phy0   unblocked unblocked
[admin@fedora ~]$ 
[admin@fedora ~]$ dmesg | grep -i 'Bluetooth'
[admin@fedora ~]$ 

PS

I just checked whether the non-existant backlight function key Fn 5 might affect Bluetooth and confirmed that it does not. (Also discovered that the backlight DOES exist - so again, thanks for that!)

I powered down and entered BIOS Setup.

Confirmed Boot Sequence gets to Fedora before Windows with nothing about “Fast Boot”

When restarted I did not hold down shift key but saw Grub menu as usual and selected previous kernel.

Boot proceeded with blank screen until I power cycled.

Then allowed Grub to use current Kernel instead and now Bluetooth works!

Gnome displays Bluetooth On, confirmed by Bluetooth Settings.

Don’t know if it ever got to previous kernel or not and no idea how that would fix it for current kernel.

Entering BIOS may have been what fixed it?

Can try again later but not now and more inclined to wait for it to break again unless further suggestions. No idea why it would not boot the previous kernel.

Anyway, here’s the test results with Bluetooth On

Note that it is the SAME kernel as before, but with lots more info now that Bluetooth is On.

[admin@fedora ~]$ uname -a
Linux fedora 6.2.12-100.fc36.x86_64 #1 SMP PREEMPT_DYNAMIC Fri Apr 21 00:10:57 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
[admin@fedora ~]$ dmesg | grep -i 'blue\|btusb'
rfkill
[    4.186703] Bluetooth: Core ver 2.22
[    4.186721] NET: Registered PF_BLUETOOTH protocol family
[    4.186722] Bluetooth: HCI device and connection manager initialized
[    4.186725] Bluetooth: HCI socket layer initialized
[    4.186727] Bluetooth: L2CAP socket layer initialized
[    4.186730] Bluetooth: SCO socket layer initialized
[    4.244265] usbcore: registered new interface driver btusb
[    4.246744] Bluetooth: hci0: Bootloader revision 0.4 build 0 week 11 2017
[    4.247751] Bluetooth: hci0: Device revision is 2
[    4.247754] Bluetooth: hci0: Secure boot is enabled
[    4.247755] Bluetooth: hci0: OTP lock is enabled
[    4.247756] Bluetooth: hci0: API lock is enabled
[    4.247757] Bluetooth: hci0: Debug lock is disabled
[    4.247758] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[    4.320857] Bluetooth: hci0: Found device firmware: intel/ibt-19-32-4.sfi
[    4.320970] Bluetooth: hci0: Boot Address: 0x24800
[    4.320973] Bluetooth: hci0: Firmware Version: 15-45.22
[    5.231587] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    5.231591] Bluetooth: BNEP filters: protocol multicast
[    5.231594] Bluetooth: BNEP socket layer initialized
[    6.131130] Bluetooth: hci0: Waiting for firmware download to complete
[    6.131780] Bluetooth: hci0: Firmware loaded in 1768500 usecs
[    6.131825] Bluetooth: hci0: Waiting for device to boot
[    6.146795] Bluetooth: hci0: Malformed MSFT vendor event: 0x02
[    6.146796] Bluetooth: hci0: Device booted in 14646 usecs
[    6.147117] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-19-32-4.ddc
[    6.148831] Bluetooth: hci0: Applying Intel DDC parameters completed
[    6.149752] Bluetooth: hci0: Firmware revision 0.4 build 15 week 45 2022
[    6.214940] Bluetooth: MGMT ver 1.22
[    7.996112] Bluetooth: hci0: Bad flag given (0x1) vs supported (0x0)
[   14.128333] Bluetooth: RFCOMM TTY layer initialized
[   14.128341] Bluetooth: RFCOMM socket layer initialized
[   14.128348] Bluetooth: RFCOMM ver 1.11
ID TYPE      DEVICE      SOFT      HARD
 0 bluetooth hci0   unblocked unblocked
 1 wlan      phy0   unblocked unblocked
[admin@fedora ~]$ 

Seems like your Bluetooth issue was never related to any Fedora update then.

If you use Windows, try disabling Fast Startup. It is a setting in Windows,
not the same as Fast Boot.

Fast Boot is a UEFI setting, sometimes called “Quick Boot” or similar. It might
not be in the same place as the boot sequence/order; check other pages of the
UEFI settings.

I’ve seen one case where a UEFI update from the manufacturer removed the Fast
Boot setting (making it always enabled), so the user had to always shut down
fully instead of rebooting to avoid a similar issue with hardware not
initialising.

The regular pattern has been that it gets turned Off and subsequently gets turned back On after some update that requires a restart.

I hardly ever do restarts for any other reason and just leave the laptop to hibernate when not in use. (Don’t even shut the lid).

So perhaps it is a restart issue rather than an update issue. But there is no Windows involvement so I think it is still a Fedora issue.

I do not use Windows at all. Boot only from external SSD to avoid accidentally booting it.

Entered BIOS via HP ESC, not via Windows.

Perhaps this oddity should be mentioned.

On restart for frequent Fedora updates I get a light blue screen for selecting boot device from BEFORE grub menu that mentions something like.

“Boot restored”

There is a short delay with a choice of 3 options. I think they are something like:

  1. Restart
  2. Continue booting
  3. Always continue booting

I use the down arrow key to select Continue booting and it goes to Grub menu for choosing kernels.

If I don’t do that it restarts again and would loop continuously if left like that.

It doesn’t have any Windows branding and I assume it is from HP but do not recall whether it has HP branding.

I vaguely recall having had to do something via Windows (a long time ago) to avoid having to make sure I pressed the right buttons in time to stop Windows from booting despite boot order in BIOS.

Perhaps that does something like swapping out a Windows boot sector?

It hasn’t bothered me.

I will make a note here of the exact sequence next time I restart.

Will also check whether merely going into BIOS fixes Bluetooth next time it stops working, and if not, will again try to boot previous kernel.

Will then also consider going in to Windows to look for Fast Start but I would rather wait until it stops working again and have tried other stuff above first.

I expect what you have is window uefi booting from the internal drive and fedora uefi booting from the usb device. Thus the system automatically wants to use the internal drive.

It seems probable that had you done the install and allowed the installer to share the efi partition on the internal drive then grub would boot from the usb device automatically as grub would be installed on the internal drive and you would not need to select the usb device every time for booting. As it is, it seems the efi partition on the internal device only knows about windows so you have to select the fedora device every time.

BlueTooth still working after latest update to kernel 6.2.13 so I’m not planning to do anything about it right now.

Thanks for info that it is booting via the Blue screen because I did not allow installer to share the uefi partition on the internal drive. I confirm that the Blue screen immediately before Grub is almost exactly as described above with no branding at all. The full title centered at the top of large thin white frame is “Boot Option Restored”. The first and default option of the three inside the small thin white frame at the center of the Blue screen is “Restart system”. Next two are “Continue boot” (which I always choose) and “Always continue boot”.

But are you suggesting that gives Windows a chance to screw up Fedora use of Bluetooth?

I’m assuming not, as it is just part of UEFI, not part of Windows, unless you say it might.

I assume from what you said that it is part of the HP UEFI prior to Windows itself.

The UEFI Boot Order displayed in BIOS is:

USB Flash Drive/USB Hard Disk
OS Boot Manager [submenu opens as shown below]

    Fedora [External SSD Samsung T5)
    Windows Boot Manager [Internal nvme]

I’m not bothered by it but I do need to do backups.

Original intention was to leave laptop internal drive as untouched as possible by Fedora to unplug external SSD if using Windows so that Windows cannot attack it.

Also hoping that there might be some way to just mount external SSD on a different PC with minimal installation, but never got around to investigating that and don’t have time. I do still assume that I will be able to easily mount /home from external SSD after installing a new Fedora on a new PC.

Am assuming that to fix things I would need to at least read GRUB2 manual and learn a lot of stuff about booting and Linux that I have either forgotton or never knew.

Was planning to write a script that copies everything exactly (including permissions, links, devices, owners and timestamps) from the current external 500 GB Samsung T5 to a new Samsung 1TB as fast as possible while also preparing logs with md5 and sha hashes.

When that works as complete replacement for current external SSD that would enable me to risk playing around and provide enough space for regular incremental backups using normal Fedora backup tools eg Borg with Pika or Vorta.

Currently I would need to spend many hours looking things up just to rescue from a failure to boot so I don’t want to fiddle with anything that might prevent booting.

Was thinking DCP from NSA might be suitable but I am not skilled and the Issues mentions buildsystem/INSTALL out of date.

  1. Is there something suitable for that initial fast file copy with hashes in Fedora?

  2. Would it be simpler to just dd and find out how to add the extra space to btrfs? (I want to avoid this because only 208GB of 499GB is actually used and I assume the copying will take a long time and DCP is optimized to do file copying while simultaneously hashing as quickly as possible).

  3. Would it be simpler to “defrag” and reduce size of Btrfs partitions to minimum first and then use dd? I am reluctant to do that before having done a complete working backup on a separate external SSD and verified that it works. But I assume less time would be required to become confident that the steps required could not possibly result in failure to boot.

  4. If I get something working on another external SSD one way or another is there a simple way to just modify the internal UEFI so it does what the installer would have done if I allowed it to? eg running an installer to a certain point and stopping or just copying certain /boot/efi files from external to internal drive perhaps with small modifications in advance that are reasonably certain to work and certain to be undoable by booting from the other SSD?

  5. Below are details of external and internal partitions.

[root@fedora fedora]# df -H
Filesystem      Size  Used Avail Use% Mounted on
devtmpfs        4.2M     0  4.2M   0% /dev
tmpfs           8.3G   78M  8.2G   1% /dev/shm
tmpfs           3.3G  2.4M  3.3G   1% /run
/dev/sda3       499G  208G  290G  42% /
tmpfs           8.3G   17k  8.3G   1% /tmp
/dev/sda3       499G  208G  290G  42% /home
/dev/sda2       1.1G  280M  703M  29% /boot
/dev/sda1       603M   19M  585M   4% /boot/efi
tmpfs           1.7G  3.3M  1.7G   1% /run/user/1000
/dev/sdb1        16G   13G  3.4G  79% /run/media/admin/STORE N GO
/dev/sdc1        31G   25G  6.8G  79% /run/media/admin/PUBLIC
[root@fedora fedora]# 

---

[root@fedora fedora]# lsblk
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda           8:0    0 465.8G  0 disk 
├─sda1        8:1    0   576M  0 part /boot/efi
├─sda2        8:2    0     1G  0 part /boot
└─sda3        8:3    0 464.1G  0 part /home
                                      /
sdb           8:16   1  14.6G  0 disk 
└─sdb1        8:17   1  14.6G  0 part /run/media/admin/STORE N GO
sdc           8:32   1  28.9G  0 disk 
└─sdc1        8:33   1  28.8G  0 part /run/media/admin/PUBLIC
zram0       252:0    0     8G  0 disk [SWAP]
nvme0n1     259:0    0 476.9G  0 disk 
├─nvme0n1p1 259:1    0   260M  0 part 
├─nvme0n1p2 259:2    0    16M  0 part 
├─nvme0n1p3 259:3    0 476.2G  0 part 
└─nvme0n1p4 259:4    0   489M  0 part 
[root@fedora fedora]# 

---

[root@fedora fedora]# sfdisk -d /dev/sda
label: gpt
label-id: 8B2258DF-AB3F-4E4A-82E1-2EDC35BA5AE8
device: /dev/sda
unit: sectors
first-lba: 34
last-lba: 976773134
sector-size: 512

/dev/sda1 : start=       65535, size=     1179630, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=C3E244F5-5BE9-4E52-A24C-E2007903CC8C, name="EFI System Partition"
/dev/sda2 : start=     1245165, size=     2162655, type=0FC63DAF-8483-4772-8E79-3D69D8477DE4, uuid=62C8B6A1-BAFB-4FCF-8158-5DA525302878
/dev/sda3 : start=     3407820, size=   973260285, type=0FC63DAF-8483-4772-8E79-3D69D8477DE4, uuid=4B90ED51-FDB1-4E9C-AD1C-06B441AB3B0B

---

[root@fedora fedora]# sfdisk -d /dev/nvme0n1
label: gpt
label-id: 6B5C557D-8418-497F-BB27-BF804DBAB936
device: /dev/nvme0n1
unit: sectors
first-lba: 34
last-lba: 1000215182
sector-size: 512

/dev/nvme0n1p1 : start=        2048, size=      532480, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=C08AAA28-100E-4AD3-80B4-128C2C010A89, name="EFI system partition", attrs="GUID:63"
/dev/nvme0n1p2 : start=      534528, size=       32768, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=7EAAC110-17A7-4D66-9944-FFFBA5D198C6, name="Microsoft reserved partition", attrs="GUID:63"
/dev/nvme0n1p3 : start=      567296, size=   998633472, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=941E265F-DBEB-4416-BAF9-E278D3F6BEFE, name="Basic data partition"
/dev/nvme0n1p4 : start=   999200768, size=     1001472, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=CDC09809-F739-4133-A27A-34B27453E765, name="Basic data partition", attrs="RequiredPartition GUID:63"

I can also provide ls -alR of /boot or /boot/efi but I don’t know how to mount the corresponding internal partition to a directory to do the same for that.

Fact that I could figure out above, but needed to look stuff up first, and could not immediately see what to look up for the last bit gives a rough idea of my level for comprehending pointers.

Thanks for any pointers.

Have confirmed that /dev/sda1 from external SSD is mounted as /boot/efi and have mounted the internal (HP/Microsoft) EFI at /dev/nvme0n1p1 to ~admin/nvme0n1p1

[root@fedora admin]# mount -r /dev/nvme0n1p1 ./nvme0n1p1

So can provide ls -alR of both. No idea where to look for the blue screen code or what should be copied to internal version to boot straight into external version.

I assume nothing from HP/Microsoft internal drive remains visible to Fedora after booting since it is not mounted anywhere until I manually mount the EFI partition read only at the end of the mount table below.

[root@fedora en-US]# mount
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime,seclabel)
devtmpfs on /dev type devtmpfs (rw,nosuid,seclabel,size=4096k,nr_inodes=1048576,mode=755,inode64)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,seclabel,inode64)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,seclabel,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,nodev,seclabel,size=3219724k,nr_inodes=819200,mode=755,inode64)
cgroup2 on /sys/fs/cgroup type cgroup2 (rw,nosuid,nodev,noexec,relatime,seclabel,nsdelegate,memory_recursiveprot)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime,seclabel)
efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
bpf on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)
/dev/sda3 on / type btrfs (rw,relatime,seclabel,compress=zstd:1,ssd,space_cache,subvolid=257,subvol=/root)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,nosuid,noexec,relatime)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=31,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=17944)
mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime,seclabel)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,seclabel,pagesize=2M)
debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime,seclabel)
tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime,seclabel)
fusectl on /sys/fs/fuse/connections type fusectl (rw,nosuid,nodev,noexec,relatime)
configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,seclabel,nr_inodes=1048576,inode64)
/dev/sda3 on /home type btrfs (rw,relatime,seclabel,compress=zstd:1,ssd,space_cache,subvolid=256,subvol=/home)
/dev/sda2 on /boot type ext4 (rw,relatime,seclabel,stripe=8191)
/dev/sda1 on /boot/efi type vfat (rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=winnt,errors=remount-ro)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,nosuid,nodev,noexec,relatime)
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatime)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,seclabel,size=1609860k,nr_inodes=402465,mode=700,uid=1000,gid=1000,inode64)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
/dev/sdc1 on /run/media/admin/PUBLIC type vfat (rw,nosuid,nodev,relatime,uid=1000,gid=1000,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,showexec,utf8,flush,errors=remount-ro,uhelper=udisks2)
/dev/sdb1 on /run/media/admin/STORE N GO type vfat (rw,nosuid,nodev,relatime,uid=1000,gid=1000,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,showexec,utf8,flush,errors=remount-ro,uhelper=udisks2)
portal on /run/user/1000/doc type fuse.portal (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
/dev/nvme0n1p1 on /home/admin/nvme0n1p1 type vfat (ro,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro)
[root@fedora en-US]# 

As expected BT eventually got broken again following another update.

It survived several updates including full upgrade at end of life for Fedora 37 so now on Fedora 38 before breaking on this particular large update.

I will check whether just going into BIOS clears it again without actually doing anything, next time I reboot.

Meanwhile here’s all the info below.

PS I am currently repeated getting a message:

“Application Stopped
Device memory is nearly full. An application that was using a lot of memory and was forced to stop.”

This only started just now so I assume unrelated to BT breakage that was earlier.

[admin@fedora ~]$ dnf history info 345
Transaction ID : 345
Begin time     : Tue 30 May 2023 09:43:22 PM AEST
Begin rpmdb    : b5382a13cd7fbb29cec71e26a226ce14e38055d9c664e339b8addd418bab71a6
End time       : Tue 30 May 2023 09:43:49 PM AEST (27 seconds)
End rpmdb      : 87dc92ccd36fd0b20647704ebfc07c90d3d35720415f9ac937d47419f0425769
User           : root <root>
Return-Code    : Success
Releasever     : 
Command Line   : 
Comment        : 
Packages Altered:
    Upgrade  container-selinux-2:2.215.0-2.fc38.noarch                   @updates
    Upgrade  edk2-ovmf-20230301gitf80f052277c8-26.fc38.noarch            @updates
    Upgrade  evolution-3.48.2-1.fc38.x86_64                              @updates
    Upgrade  evolution-bogofilter-3.48.2-1.fc38.x86_64                   @updates
    Upgrade  evolution-data-server-3.48.2-1.fc38.x86_64                  @updates
    Upgrade  evolution-data-server-langpacks-3.48.2-1.fc38.noarch        @updates
    Upgrade  evolution-ews-3.48.2-1.fc38.x86_64                          @updates
    Upgrade  evolution-ews-langpacks-3.48.2-1.fc38.noarch                @updates
    Upgrade  evolution-langpacks-3.48.2-1.fc38.noarch                    @updates
    Upgrade  evolution-mapi-3.48.1-1.fc38.x86_64                         @updates
    Upgrade  evolution-mapi-langpacks-3.48.1-1.fc38.noarch               @updates
    Upgrade  evolution-pst-3.48.2-1.fc38.x86_64                          @updates
    Upgrade  evolution-spamassassin-3.48.2-1.fc38.x86_64                 @updates
    Upgrade  exfatprogs-1.2.1-1.fc38.x86_64                              @updates
    Upgrade  fuse-overlayfs-1.12-1.fc38.x86_64                           @updates
    Upgrade  gnome-software-44.2-1.fc38.x86_64                           @updates
    Upgrade  gst-editing-services-1.22.3-1.fc38.x86_64                   @updates
    Upgrade  gstreamer1-1.22.3-1.fc38.x86_64                             @updates
    Upgrade  gstreamer1-plugin-libav-1.22.3-1.fc38.x86_64                @updates
    Upgrade  gstreamer1-plugins-bad-free-1.22.3-1.fc38.x86_64            @updates
    Upgrade  gstreamer1-plugins-bad-free-extras-1.22.3-1.fc38.x86_64     @updates
    Upgrade  gstreamer1-plugins-bad-free-fluidsynth-1.22.3-1.fc38.x86_64 @updates
    Upgrade  gstreamer1-plugins-bad-free-wildmidi-1.22.3-1.fc38.x86_64   @updates
    Upgrade  gstreamer1-plugins-bad-free-zbar-1.22.3-1.fc38.x86_64       @updates
    Upgrade  gstreamer1-plugins-base-1.22.3-1.fc38.x86_64                @updates
    Upgrade  gstreamer1-plugins-good-1.22.3-1.fc38.x86_64                @updates
    Upgrade  gstreamer1-plugins-good-extras-1.22.3-1.fc38.x86_64         @updates
    Upgrade  gstreamer1-plugins-good-gtk-1.22.3-1.fc38.x86_64            @updates
    Upgrade  gstreamer1-plugins-good-qt-1.22.3-1.fc38.x86_64             @updates
    Upgrade  gstreamer1-plugins-ugly-free-1.22.3-1.fc38.x86_64           @updates
    Upgrade  ibus-1.5.28-5.fc38.x86_64                                   @updates
    Upgrade  ibus-gtk2-1.5.28-5.fc38.x86_64                              @updates
    Upgrade  ibus-gtk3-1.5.28-5.fc38.x86_64                              @updates
    Upgrade  ibus-libs-1.5.28-5.fc38.x86_64                              @updates
    Upgrade  ibus-setup-1.5.28-5.fc38.noarch                             @updates
    Upgrade  iptables-compat-1.8.9-4.fc38.x86_64                         @updates
    Upgrade  iptables-legacy-1.8.9-4.fc38.x86_64                         @updates
    Upgrade  iptables-legacy-libs-1.8.9-4.fc38.x86_64                    @updates
    Upgrade  iptables-libs-1.8.9-4.fc38.x86_64                           @updates
    Upgrade  iptables-nft-1.8.9-4.fc38.x86_64                            @updates
    Upgrade  iptables-utils-1.8.9-4.fc38.x86_64                          @updates
    Upgrade  kubernetes-1.26.4-2.fc38.x86_64                             @updates
    Upgrade  kubernetes-client-1.26.4-2.fc38.x86_64                      @updates
    Upgrade  kubernetes-master-1.26.4-2.fc38.x86_64                      @updates
    Upgrade  kubernetes-node-1.26.4-2.fc38.x86_64                        @updates
    Upgrade  librados2-2:17.2.6-3.fc38.x86_64                            @updates
    Upgrade  librbd1-2:17.2.6-3.fc38.x86_64                              @updates
    Upgrade  mariadb-connector-c-3.3.5-1.fc38.x86_64                     @updates
    Upgrade  mariadb-connector-c-config-3.3.5-1.fc38.noarch              @updates
    Upgrade  mesa-dri-drivers-23.0.3-5.fc38.x86_64                       @updates
    Upgrade  mesa-filesystem-23.0.3-5.fc38.x86_64                        @updates
    Upgrade  mesa-libEGL-23.0.3-5.fc38.x86_64                            @updates
    Upgrade  mesa-libGL-23.0.3-5.fc38.x86_64                             @updates
    Upgrade  mesa-libgbm-23.0.3-5.fc38.x86_64                            @updates
    Upgrade  mesa-libglapi-23.0.3-5.fc38.x86_64                          @updates
    Upgrade  mesa-libxatracker-23.0.3-5.fc38.x86_64                      @updates
    Upgrade  mesa-va-drivers-23.0.3-5.fc38.x86_64                        @updates
    Upgrade  mesa-vulkan-drivers-23.0.3-5.fc38.x86_64                    @updates
    Upgrade  microcode_ctl-2:2.1-55.fc38.x86_64                          @updates
    Upgrade  python-pyqt6-rpm-macros-6.5.0-1.fc38.noarch                 @updates
    Upgrade  python2.7-2.7.18-31.fc38.x86_64                             @updates
    Upgrade  python3-pyqt6-base-6.5.0-1.fc38.x86_64                      @updates
    Upgrade  qpdf-libs-11.4.0-1.fc38.x86_64                              @updates
    Upgrade  xapian-core-libs-1.4.22-1.fc38.x86_64                       @updates
    Upgrade  xen-libs-4.17.1-2.fc38.x86_64                               @updates
    Upgrade  xen-licenses-4.17.1-2.fc38.x86_64                           @updates
    Upgraded container-selinux-2:2.213.0-1.fc38.noarch                   @@System
    Upgraded edk2-ovmf-20230301gitf80f052277c8-4.fc38.noarch             @@System
    Upgraded evolution-3.48.1-1.fc38.x86_64                              @@System
    Upgraded evolution-bogofilter-3.48.1-1.fc38.x86_64                   @@System
    Upgraded evolution-data-server-3.48.1-1.fc38.x86_64                  @@System
    Upgraded evolution-data-server-langpacks-3.48.1-1.fc38.noarch        @@System
    Upgraded evolution-ews-3.48.1-1.fc38.x86_64                          @@System
    Upgraded evolution-ews-langpacks-3.48.1-1.fc38.noarch                @@System
    Upgraded evolution-langpacks-3.48.1-1.fc38.noarch                    @@System
    Upgraded evolution-mapi-3.48.0-1.fc38.x86_64                         @@System
    Upgraded evolution-mapi-langpacks-3.48.0-1.fc38.noarch               @@System
    Upgraded evolution-pst-3.48.1-1.fc38.x86_64                          @@System
    Upgraded evolution-spamassassin-3.48.1-1.fc38.x86_64                 @@System
    Upgraded exfatprogs-1.2.0-2.fc38.x86_64                              @@System
    Upgraded fuse-overlayfs-1.10-3.fc38.x86_64                           @@System
    Upgraded gnome-software-44.1-1.fc38.x86_64                           @@System
    Upgraded gst-editing-services-1.22.2-1.fc38.x86_64                   @@System
    Upgraded gstreamer1-1.22.2-1.fc38.x86_64                             @@System
    Upgraded gstreamer1-plugin-libav-1.22.2-1.fc38.x86_64                @@System
    Upgraded gstreamer1-plugins-bad-free-1.22.2-3.fc38.x86_64            @@System
    Upgraded gstreamer1-plugins-bad-free-extras-1.22.2-3.fc38.x86_64     @@System
    Upgraded gstreamer1-plugins-bad-free-fluidsynth-1.22.2-3.fc38.x86_64 @@System
    Upgraded gstreamer1-plugins-bad-free-wildmidi-1.22.2-3.fc38.x86_64   @@System
    Upgraded gstreamer1-plugins-bad-free-zbar-1.22.2-3.fc38.x86_64       @@System
    Upgraded gstreamer1-plugins-base-1.22.2-1.fc38.x86_64                @@System
    Upgraded gstreamer1-plugins-good-1.22.2-1.fc38.x86_64                @@System
    Upgraded gstreamer1-plugins-good-extras-1.22.2-1.fc38.x86_64         @@System
    Upgraded gstreamer1-plugins-good-gtk-1.22.2-1.fc38.x86_64            @@System
    Upgraded gstreamer1-plugins-good-qt-1.22.2-1.fc38.x86_64             @@System
    Upgraded gstreamer1-plugins-ugly-free-1.22.2-1.fc38.x86_64           @@System
    Upgraded ibus-1.5.28-4.fc38.x86_64                                   @@System
    Upgraded ibus-gtk2-1.5.28-4.fc38.x86_64                              @@System
    Upgraded ibus-gtk3-1.5.28-4.fc38.x86_64                              @@System
    Upgraded ibus-libs-1.5.28-4.fc38.x86_64                              @@System
    Upgraded ibus-setup-1.5.28-4.fc38.noarch                             @@System
    Upgraded iptables-compat-1.8.9-2.fc38.x86_64                         @@System
    Upgraded iptables-legacy-1.8.9-2.fc38.x86_64                         @@System
    Upgraded iptables-legacy-libs-1.8.9-2.fc38.x86_64                    @@System
    Upgraded iptables-libs-1.8.9-2.fc38.x86_64                           @@System
    Upgraded iptables-nft-1.8.9-2.fc38.x86_64                            @@System
    Upgraded iptables-utils-1.8.9-2.fc38.x86_64                          @@System
    Upgraded kubernetes-1.26.4-1.fc38.x86_64                             @@System
    Upgraded kubernetes-client-1.26.4-1.fc38.x86_64                      @@System
    Upgraded kubernetes-master-1.26.4-1.fc38.x86_64                      @@System
    Upgraded kubernetes-node-1.26.4-1.fc38.x86_64                        @@System
    Upgraded librados2-2:17.2.6-2.fc38.x86_64                            @@System
    Upgraded librbd1-2:17.2.6-2.fc38.x86_64                              @@System
    Upgraded mariadb-connector-c-3.3.4-2.fc38.x86_64                     @@System
    Upgraded mariadb-connector-c-config-3.3.4-2.fc38.noarch              @@System
    Upgraded mesa-dri-drivers-23.0.3-3.fc38.x86_64                       @@System
    Upgraded mesa-filesystem-23.0.3-3.fc38.x86_64                        @@System
    Upgraded mesa-libEGL-23.0.3-3.fc38.x86_64                            @@System
    Upgraded mesa-libGL-23.0.3-3.fc38.x86_64                             @@System
    Upgraded mesa-libgbm-23.0.3-3.fc38.x86_64                            @@System
    Upgraded mesa-libglapi-23.0.3-3.fc38.x86_64                          @@System
    Upgraded mesa-libxatracker-23.0.3-3.fc38.x86_64                      @@System
    Upgraded mesa-va-drivers-23.0.3-3.fc38.x86_64                        @@System
    Upgraded mesa-vulkan-drivers-23.0.3-3.fc38.x86_64                    @@System
    Upgraded microcode_ctl-2:2.1-54.fc38.x86_64                          @@System
    Upgraded python-pyqt6-rpm-macros-6.4.0-7.fc38.noarch                 @@System
    Upgraded python2.7-2.7.18-30.fc38.x86_64                             @@System
    Upgraded python3-pyqt6-base-6.4.0-7.fc38.x86_64                      @@System
    Upgraded qpdf-libs-11.3.0-2.fc38.x86_64                              @@System
    Upgraded xapian-core-libs-1.4.20-2.fc38.x86_64                       @@System
    Upgraded xen-libs-4.17.1-1.fc38.x86_64                               @@System
    Upgraded xen-licenses-4.17.1-1.fc38.x86_64                           @@System
[admin@fedora ~]$ dmesg | grep -i 'blue\|btusb'
[admin@fedora ~]$ rfkill
ID TYPE DEVICE      SOFT      HARD
 0 wlan phy0   unblocked unblocked
[admin@fedora ~]$ uname -a
Linux fedora 6.2.15-300.fc38.x86_64 #1 SMP PREEMPT_DYNAMIC Thu May 11 17:37:39 UTC 2023 x86_64 GNU/Linux
[admin@fedora ~]$ inxi -Fzx
System:
  Kernel: 6.2.15-300.fc38.x86_64 arch: x86_64 bits: 64 compiler: gcc
    v: 2.39-9.fc38 Desktop: GNOME v: 44.1 Distro: Fedora release 38 (Thirty
    Eight)
Machine:
  Type: Convertible System: HP product: HP Spectre x360 Convertible 13-aw0xxx
    v: N/A serial: <superuser required>
  Mobo: HP model: 86F9 v: 87.46 serial: <superuser required> UEFI: AMI
    v: F.13 date: 03/02/2020
Battery:
  ID-1: BAT0 charge: 58.6 Wh (100.0%) condition: 58.6/60.8 Wh (96.4%)
    volts: 15.1 min: 15.4 model: HP Primary status: full
  Device-1: hid-0018:04F3:29E0.0002-battery model: ELAN2514:00 04F3:29E0
    charge: N/A status: N/A
CPU:
  Info: quad core model: Intel Core i7-1065G7 bits: 64 type: MT MCP
    arch: Ice Lake rev: 5 cache: L1: 320 KiB L2: 2 MiB L3: 8 MiB
  Speed (MHz): avg: 1360 high: 2612 min/max: 400/3900 cores: 1: 866 2: 2612
    3: 963 4: 896 5: 1347 6: 400 7: 2300 8: 1500 bogomips: 23961
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel Iris Plus Graphics G7 vendor: Hewlett-Packard driver: i915
    v: kernel arch: Gen-11 bus-ID: 00:02.0
  Device-2: Quanta HP True Vision HD Camera type: USB driver: uvcvideo
    bus-ID: 3-5:3
  Display: wayland server: X.Org v: 22.1.9 with: Xwayland v: 22.1.9
    compositor: gnome-shell driver: X: loaded: modesetting unloaded: fbdev,vesa
    dri: iris gpu: i915 resolution: 1920x1080~60Hz
  API: OpenGL v: 4.6 Mesa 23.0.3 renderer: Mesa Intel Iris Plus Graphics
    (ICL GT2) direct-render: Yes
Audio:
  Device-1: Intel Ice Lake-LP Smart Sound Audio vendor: Hewlett-Packard
    driver: sof-audio-pci-intel-icl bus-ID: 00:1f.3
  API: ALSA v: k6.2.15-300.fc38.x86_64 status: kernel-api
  Server-1: PipeWire v: 0.3.71 status: active
Network:
  Device-1: Intel Ice Lake-LP PCH CNVi WiFi driver: iwlwifi v: kernel
    bus-ID: 00:14.3
  IF: wlo1 state: up mac: <filter>
  IF-ID-1: virbr0 state: down mac: <filter>
RAID:
  Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode] driver: ahci
    v: 3.0 bus-ID: 00:17.0
Drives:
  Local Storage: total: 986.1 GiB used: 272.95 GiB (27.7%)
  ID-1: /dev/nvme0n1 vendor: Samsung model: MZVLB512HAJQ-000H1
    size: 476.94 GiB temp: 36.9 C
  ID-2: /dev/sda type: USB vendor: Samsung model: Portable SSD T5
    size: 465.76 GiB
  ID-3: /dev/sdb type: USB vendor: Verbatim model: STORE N GO
    size: 14.55 GiB
  ID-4: /dev/sdc type: USB model: USB DISK 3.0 Pro size: 28.85 GiB
Partition:
  ID-1: / size: 464.09 GiB used: 238.65 GiB (51.4%) fs: btrfs dev: /dev/sda3
  ID-2: /boot size: 1004.8 MiB used: 324.6 MiB (32.3%) fs: ext4
    dev: /dev/sda2
  ID-3: /boot/efi size: 574.8 MiB used: 17.4 MiB (3.0%) fs: vfat
    dev: /dev/sda1
  ID-4: /home size: 464.09 GiB used: 238.65 GiB (51.4%) fs: btrfs
    dev: /dev/sda3
Swap:
  ID-1: swap-1 type: zram size: 8 GiB used: 8 GiB (100.0%) dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 66.0 C mobo: N/A
  Fan Speeds (RPM): cpu: 0 fan-2: 0
Info:
  Processes: 528 Uptime: 1d 13h 56m Memory: 15.35 GiB used: 14.32 GiB (93.3%)
  Init: systemd target: graphical (5) Compilers: gcc: 13.1.1 Packages: 40
  note: see --rpm Shell: Bash v: 5.2.15 inxi: 3.3.26
[admin@fedora ~]$ 

Had frozen screen/cursor so did powercycle.
Went into BIOS before reboot and immediately exited without looking at anything.
BT now working.

I believe the following additional update was done AFTER I confirmed BT was working but just in case I am confused:

admin@fedora ~]$ dnf history info 346
Transaction ID : 346
Begin time     : Thu 01 Jun 2023 12:40:18 PM AEST
Begin rpmdb    : 87dc92ccd36fd0b20647704ebfc07c90d3d35720415f9ac937d47419f0425769
End time       : Thu 01 Jun 2023 12:40:31 PM AEST (13 seconds)
End rpmdb      : 56dcd6d3db7ca981a0160f95b70d0d0287b57b0acff9eef4d73c2659715b19d2
User           : root <root>
Return-Code    : Success
Releasever     : 
Command Line   : 
Comment        : 
Packages Altered:
    Upgrade  brave-browser-1.52.117-1.x86_64       @brave-browser-rpm-release.s3.brave.com_x86_64_
    Upgrade  blosc-1.21.4-1.fc38.x86_64            @updates
    Upgrade  cmake-filesystem-3.26.4-3.fc38.x86_64 @updates
    Upgrade  python3-PyDrive2-1.15.4-1.fc38.noarch @updates
    Upgraded brave-browser-1.51.118-1.x86_64       @@System
    Upgraded blosc-1.21.2-2.fc38.x86_64            @@System
    Upgraded cmake-filesystem-3.26.4-2.fc38.x86_64 @@System
    Upgraded python3-PyDrive2-1.15.3-1.fc38.noarch @@System
[admin@fedora ~]$ 
[admin@fedora ~]$ dmesg | grep -i 'blue\|btusb'
[    5.819049] Bluetooth: Core ver 2.22
[    5.819071] NET: Registered PF_BLUETOOTH protocol family
[    5.819073] Bluetooth: HCI device and connection manager initialized
[    5.819078] Bluetooth: HCI socket layer initialized
[    5.819081] Bluetooth: L2CAP socket layer initialized
[    5.819086] Bluetooth: SCO socket layer initialized
[    5.971015] usbcore: registered new interface driver btusb
[    6.037565] Bluetooth: hci0: Found device firmware: intel/ibt-19-32-4.sfi
[    6.037651] Bluetooth: hci0: Boot Address: 0x24800
[    6.037653] Bluetooth: hci0: Firmware Version: 144-11.23
[    6.037655] Bluetooth: hci0: Firmware already loaded
[    6.642989] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    6.642991] Bluetooth: BNEP filters: protocol multicast
[    6.642995] Bluetooth: BNEP socket layer initialized
[    6.644032] Bluetooth: MGMT ver 1.22
[    6.955412] Bluetooth: hci0: Bad flag given (0x1) vs supported (0x0)
[   11.169821] Bluetooth: RFCOMM TTY layer initialized
[   11.169829] Bluetooth: RFCOMM socket layer initialized
[   11.169838] Bluetooth: RFCOMM ver 1.11
[admin@fedora ~]$ rfkill
ID TYPE      DEVICE      SOFT      HARD
 0 bluetooth hci0   unblocked unblocked
 1 wlan      phy0   unblocked unblocked
[admin@fedora ~]$ 

We already established through your own testing that it’s not caused by updates.

To save you time, you can stop checking and posting dnf transactions (in the context of troubleshooting this problem). None of the packages changed in transactions 345 or 346 are related to Bluetooth. I promise, it wasn’t osinfo-db, elfutils, wireplumber, python3-pytz, or any other package you suspected in previous transactions either.

The next time Bluetooth doesn’t work, post the entire output of dmesg. Maybe (unlikely) we can see where it fails.

I still suspect Fast Boot (not Window’s Fast Startup). You said your BIOS doesn’t have a Fast Boot option, but as previously mentioned: