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.
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.
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.
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.