Hello,
After upgrading to Fedora 40 (Lenovo Thinkpad T480 with NVIDIA MX150) I encountered some issues that weren’t there before.
When I wake up my laptop from suspend, Bluetooth is often turned off, which is quite annoying as I usually work with an external Bluetooth mouse and keyboard. UI still doesn’t allow you to turn the Bluetooth on, but I found out that when I see it woke up with the Bluetooth turned off, I have to put it to sleep again and wake it up once more.
I often change the audio output device to Bluetooth headphones, Bluetooth speakers or speakers of an external monitor. However, when I unplug my laptop from the external screen often everything is muted and what I think happens is the system still thinks it’s connected to external speakers while it cannot access it. You cannot change the output device on your own at this point. The workaround for this issue is to connect the laptop again to some external audio device, then change the audio output to internal speakers, then unplug the laptop from the external screen, and it should be fine, it will have access to internal speakers once more.
I don’t know if there are some commands I could use to help you diagnose what’s the issue about. I would appreciate help in solving this.
with sudo the output of dmesg | grep bluetooth is:
sudo dmesg | grep bluetooth
[ 9.207559] thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is unblocked
[21964.012916] bluetoothd[1065]: segfault at 2b ip 00007f6fc2212d75 sp 00007ffdc5e69cb0 error 4 in libc.so.6[7f6fc2194000+169000] likely on CPU 2 (core 2, socket 0)
For journalctl | grep bluetooth the output is very long and it doesn’t allow me to post it here.
Should I provide something specific found there, maybe around some keywords?
Can you please boot into kernel 6.8.8 and test your issues?
If you do not know how to set a different kernel for boot you can
My apologies, You can modofy the command to view events many different ways. From the time of boot, or other time intervals. Let’s just try kernel first, then if possible try to recreate then run a more focused command.
On the other hand I remember that sometimes when computer gets stuck during reboot forced by update and I force it to turn off and turn it back on I see the screen of choosing the kernel.
So I did hold the power while seeing lenovo boot screen and then it showed me the screen with kernel to choose, I did open 6.8.8 but it was still buggy with all the same issues.
Every second waking up from suspend would be with a bluetooth turned off without ability to turn it on. Even through Setting app. The toggle doesn’t react. Then when you suspend the laptop and wake it up again bluetooth works.
Nevertheless the grubby command, when I booted and checked, I was on 6.8.8 the issue persisted as I described it. After another reboot I see I’m back to 6.8.9.
The issue still seems to be related to the recent update to Fedora 40, but the change between 6.8.8 and 6.8.9 is not it.
It came to my mind that maybe these were some lenovo drivers that got update in recent weeks?
That’s my bad, the paste I had, had the top index cut off. I was trying to get you to boot into kernel 6.8.7 which is the oldest. Restarting should get you back since that is a one-shot reboot.
It didn’t allow me to log into X11, after inputting password it didn’t go through and the password prompt field showed up again and again. Only after switching to Wayland it allowed me to go further.
Still the same issue. Every second wake up is with the Bluetooth turned off and blocked from turning it on again. Putting the laptop to sleep and waking it up again, resolves the issue. Another suspend, another blocked Bluetooth
I guess through testing, you can check the logs and look for bluetooth errors or power issues in regards to bluetooth. Give me a second to get some commands.
systemctl status bluetooth - you can start / stop from this command too
sudo journalctl -xe | grep -i blue - will bring up anything related to bluetooth
bluetoothctl - this is to go into the bluetooth interface with various commands.
Also would be good to know what power mode you are on ? Performance, Balanced, Power Saver,
I would consider filing a bug as well maybe even reference this thread if you want :