I want to start by saying, Bluetooth works at the login screen if you sign out. Meaning signing back in is not a problem. Bluetooth also works at the lock screen if you are away from the computer for a while. Meaning, unlocking your computer is also not a problem.
The problem is, if you reboot your computer and attempt to sign in, you cannot, because it does not appear Bluetooth is available. This requires you to use either a wired keyboard (or 2.4Ghz wireless) keyboard to sign in. As a result, I now keep a 2nd keyboard (wired) plugged in all the time, just for those moments when I reboot (or power off and on).
I suspect this is a bug, but I would not want to report this bug before confirming with other people. I am also not 100% sure what information you would want (please be very specific) if it were a bug. I have encountered this issue on both Fedora (Ultramarine Linux, KDE Plasma edition) and Kubuntu (Ubuntu’s KDE edition). I believe I also encountered this issue on an immutable distro (Universal Blue Aurora, based on Fedora KDE Spin).
Bluetooth is operable only after the operating system is loaded
I am confused by your reply. The operating system is loaded and, furthermore, this is a semi-recent development. That is to say, this issue first appeared sometime during Fedora 39 (and with Kubuntu around the same time). If I am not clear, you could previous log-in with a Bluetooth keyboard.
This is a low priority issue since I do have a wired keyboard to circumvent this annoyance and I assumed, incorrectly, that it would eventually be reported and resolved. Clearly, that has not happened, but now that I am brining this up, I would like to see it addressed (please).
Furthermore, the last time I was using Gnome / Gdm (I am not a fan of Gnome), it worked. I do not currently have a system running Gnome / Gdm at this time, but I would assume that is still the case.
But I digress. Your reply is confusing.
1 Like
I think “Bluetooth is operable only after the operating system is loaded” is a pretty clear statement.
If you believe bluetooth is failing after this then it seems to a fault in either loading the bluetooth components, or in their operation which is a bug and should be reported as such.
Just BTW I have as much power to “see it addressed” as you do, but reporting the problem as a bug seems to be a reasonable first step
I am unsure how you’re not understanding, as I previously stated, the operating system is already loaded. I can see the log-in screen and using that login screen after a reboot, with a Bluetooth keyboard, used to work (with KDE / SDDM). To my knowledge, it works just fine with Gnome / GDM, for example (last I checked).
That said, do you know where I would best report this in bugs ?
I suppose, since this could also be a “ssdm” issue, I should forward this to that community as well. And that is what I worry, that I’ll be playing “whack a mole” between developments.
Edit: I switched to KDE’s LightDM just to be sure and can confirm the issue remains.
It sounds like Bluetooth isn’t operational when the system turns on, but then becomes operational after you log in. I know for a fact that we do have a thing in Plasma that enables bluetooth after login, but what happens before login is unfortunately beyond our control at the moment. For this reason, many distros have an “automatically enable Bluetooth on boot” package.
This is one of many reasons why I prefer wired input devices, FWIW.