Unable to turn on bluetooth after update to linux kernel 6.0.5

I am new to using Fedora (and Linux in general) and am observing some strange behavior that I do not understand. It appears to me that the Linux kernel is sometimes updated without me knowing it and this results in functionality being broken. Whether Fedora is automatically updating the kernel behind the scenes or I did something that accidentally updated the kernel, I do not know. If anyone knows whether or not Fedora just automatically updates the kernel every so often without user input, let me know. This is something I would like to disable if possible.

A few days ago, I booted my computer in the morning to find that the nvidia drivers no longer worked. I did a fresh re-install of Fedora using my USB that I originally used to install it and this seemed to solve the issue. This morning I booted my computer to find that bluetooth is no longer working. I click on the button that says “turn on bluetooth” but nothing happens. It worked perfectly fine yesterday when I turned it off, but the moment I turn it back on, I am unable to turn bluetooth on. The kernel version is now 6.0.5. I don’t know what it was when I turned it off, but fedora having the major version of “6” and not “5” is not something I remember seeing previously.

Any insight as to how I can fix bluetooth and avoid this kernel updating without me knowing would be greatly appreciated. I tried using grub to boot into a previous linux kernel, but when I do this, the wifi no longer works, so this would just be trading one problem for an even bigger problem.

This is the output of running systemctl status bluetooth:

● bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
     Active: active (running) since Tue 2022-11-01 11:30:46 EDT; 7h ago
       Docs: man:bluetoothd(8)
   Main PID: 1177 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 76058)
     Memory: 2.0M
        CPU: 15ms
     CGroup: /system.slice/bluetooth.service
             └─ 1177 /usr/libexec/bluetooth/bluetoothd

Nov 01 11:30:45 joelsdesktop systemd[1]: Starting bluetooth.service - Bluetooth service...
Nov 01 11:30:45 joelsdesktop systemd[1177]: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555)
Nov 01 11:30:45 joelsdesktop bluetoothd[1177]: Bluetooth daemon 5.65
Nov 01 11:30:46 joelsdesktop bluetoothd[1177]: Starting SDP server
Nov 01 11:30:46 joelsdesktop systemd[1]: Started bluetooth.service - Bluetooth service.
Nov 01 11:30:46 joelsdesktop bluetoothd[1177]: Bluetooth management interface 1.22 initialized
~

There is an option to apply updates before shutting down. You can uncheck that box if you want that not to happen.

You should be able to press ‘shift’ right at the beginning of the boot in order to select from several previous kernels — that way you can verify if that’s what is causing the problem.

Then, we can take the next steps to figure out how to get it fixed.

I am currently in the process of trying older kernels. When I go to the grub menu and select 5.19.16-200.fc36.x86-64, and run systemctl status bluetooth, this is the message I get (still cannot turn on bluetooth):

bluetooth.service - Bluetooth service
        Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; vendor preset: enabled)
        Active: inactive (dead)
            Docs: man:bluetoothhd(8)

Nov 02 09:32:39 joelsdesktop systems[1]: bluetooth.service - Bluetooth service was skipped because of a failed condition check (ConditionPathIsDirectory=/sys/class/bluetooth).

When I go to the grub menu and select 5.17.5-300.fc36.x86-64, this is the message I get after running systemctl status bluetooth:

● bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
     Active: active (running) since Wed 2022-11-02 09:44:23 EDT; 1min 0s ago
       Docs: man:bluetoothd(8)
   Main PID: 1041 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 76078)
     Memory: 2.0M
        CPU: 11ms
     CGroup: /system.slice/bluetooth.service
             └─ 1041 /usr/libexec/bluetooth/bluetoothd

Nov 02 09:44:22 joelsdesktop systemd[1]: Starting bluetooth.service - Bluetooth service...
Nov 02 09:44:22 joelsdesktop systemd[1041]: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555)
Nov 02 09:44:22 joelsdesktop bluetoothd[1041]: Bluetooth daemon 5.65
Nov 02 09:44:22 joelsdesktop bluetoothd[1041]: Starting SDP server
Nov 02 09:44:22 joelsdesktop bluetoothd[1041]: Bluetooth management interface 1.21 initialized
Nov 02 09:44:23 joelsdesktop systemd[1]: Started bluetooth.service - Bluetooth service.

1 Like

Can you please make us a inxi -Fzx in your terminal and post the output as </> pre formatted text here to se your hardware setup?

1 Like

Here is the requested output:

System:
  Kernel: 6.0.5-200.fc36.x86_64 arch: x86_64 bits: 64 compiler: gcc
    v: 2.37-36.fc36 Desktop: GNOME v: 42.5 Distro: Fedora release 36 (Thirty
    Six)
Machine:
  Type: Desktop System: Gigabyte product: X670E AORUS MASTER v: -CF
    serial: <superuser required>
  Mobo: Gigabyte model: X670E AORUS MASTER v: x.x
    serial: <superuser required> UEFI: American Megatrends LLC. v: F6
    date: 08/24/2022
Battery:
  Device-1: hid-F0T013700NQHTCYAF-battery model: Apple Inc. Magic Keyboard
    with Numeric Keypad charge: N/A status: discharging
  Device-2: hidpp_battery_0 model: Logitech Wireless Mouse charge: 55%
    (should be ignored) status: discharging
CPU:
  Info: 16-core model: AMD Ryzen 9 7950X bits: 64 type: MT MCP arch: Zen 4
    rev: 2 cache: L1: 1024 KiB L2: 16 MiB L3: 64 MiB
  Speed (MHz): avg: 537 high: 2600 min/max: 400/5881 boost: enabled cores:
    1: 400 2: 400 3: 400 4: 400 5: 400 6: 2599 7: 400 8: 400 9: 400 10: 400
    11: 400 12: 400 13: 400 14: 400 15: 400 16: 400 17: 400 18: 2600 19: 400
    20: 400 21: 400 22: 400 23: 400 24: 400 25: 400 26: 400 27: 400 28: 400
    29: 400 30: 400 31: 400 32: 400 bogomips: 287990
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
  Device-1: NVIDIA GA104 [GeForce RTX 3060 Ti] driver: nvidia v: 520.56.06
    arch: Ampere bus-ID: 01:00.0
  Device-2: AMD Raphael vendor: Gigabyte driver: amdgpu v: kernel
    arch: RDNA-2 bus-ID: 37:00.0
  Display: wayland server: X.Org v: 1.22.1.3 with: Xwayland v: 22.1.3
    compositor: gnome-shell driver: X: loaded: modesetting,nouveau,nvidia
    unloaded: fbdev,vesa gpu: nvidia,nvidia-nvswitch
    resolution: 3840x2160~60Hz
  OpenGL: renderer: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA
    520.56.06 direct render: Yes
Audio:
  Device-1: NVIDIA GA104 High Definition Audio driver: snd_hda_intel
    v: kernel bus-ID: 01:00.1
  Device-2: AMD Rembrandt Radeon High Definition Audio
    driver: snd_hda_intel v: kernel bus-ID: 37:00.1
  Device-3: AMD Family 17h/19h HD Audio vendor: Gigabyte
    driver: snd_hda_intel v: kernel bus-ID: 37:00.6
  Sound Server-1: ALSA v: k6.0.5-200.fc36.x86_64 running: yes
  Sound Server-2: PulseAudio v: 15.0 running: no
  Sound Server-3: PipeWire v: 0.3.59 running: yes
Network:
  Device-1: Intel Ethernet I225-V vendor: Gigabyte driver: igc v: kernel
    port: N/A bus-ID: 0c:00.0
  IF: enp12s0 state: down mac: <filter>
  Device-2: Intel Wi-Fi 6 AX210/AX211/AX411 160MHz driver: iwlwifi
    v: kernel bus-ID: 0d:00.0
  IF: wlp13s0 state: up mac: <filter>
Bluetooth:
  Device-1: Intel AX210 Bluetooth type: USB driver: btusb v: 0.8
    bus-ID: 1-9:3
  Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends
Drives:
  Local Storage: total: 1.82 TiB used: 18.93 GiB (1.0%)
  ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 980 PRO 2TB size: 1.82 TiB
    temp: 34.9 C
Partition:
  ID-1: / size: 1.82 TiB used: 18.65 GiB (1.0%) fs: btrfs dev: /dev/nvme0n1p3
  ID-2: /boot size: 973.4 MiB used: 271.3 MiB (27.9%) fs: ext4
    dev: /dev/nvme0n1p2
  ID-3: /boot/efi size: 598.8 MiB used: 13.9 MiB (2.3%) fs: vfat
    dev: /dev/nvme0n1p1
  ID-4: /home size: 1.82 TiB used: 18.65 GiB (1.0%) fs: btrfs
    dev: /dev/nvme0n1p3
Swap:
  ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 41.0 C mobo: N/A gpu: amdgpu temp: 29.0 C
  Fan Speeds (RPM): N/A
Info:
  Processes: 853 Uptime: 49m Memory: 61.95 GiB used: 2.18 GiB (3.5%)
  Init: systemd target: graphical (5) Compilers: gcc: 12.2.1 Packages: 5
  note: see --rpm Shell: Bash v: 5.2.2 inxi: 3.3.21

Note that the bluetooth devices listed here are different that what I would normally use since what I usually use (Logitech MX Master Keys and MX Master 3 mouse) do not allow for non-bluetooth connection (The logitech wireless mouse listed here is a cheap one I got that has a USB receiver-type wireless connection that seems to work fine). Although I doubt this matters because the issue seems to be that I can’t turn on bluetooth in the first place.

What about the output of rfkill
That should show both wifi and bluetooth.

Output of rfkill using kernel 6.0.5:

ID TYPE      DEVICE      SOFT      HARD
 0 bluetooth hci0   unblocked unblocked
 1 wlan      phy0   unblocked unblocked

Hello,
when I search the internet for
“systemd, File system: 755 ConfigurationDirectoryMode: 555”
the recommended solution is to restart systemd.
So:

sudo systemctl daemon-reload
sudo systemctl restart bluetooth

Maybe you want to try this once. Maybe it also helps to log out and log in again.
Although it should work immediately.

I hope it works.

1 Like

Thank you for the suggestion, however the problem persists after running these commands. I also tried logging out and back in as well as a full reboot.

So I rebooted my computer again and now bluetooth seems to be working again. I am not sure what solved it. Maybe there were automatic updates that fixed it or the suggestion by mustermann required multiple reboots for some reason.

1 Like

The main thing is that the problem is solved.
I just believe in an interaction of developers and your bug report here in the forum and an update.
Most developers and software developers know each other and talk to each other. They do that across all distributions.
If the problem is solved for them just click on solved. Although I would not like to be called because I have not actually done anything.