Repository: ublue-os/bazzite

Issue #950: [Regression][SteamDeckOLED][bazzite-deck-gnome:latest] Bluetooth stopped working completely and is root cause for issue of auto-resume from suspend
Created: 2024-04-06T14:01:01Z
Describe the bug
Description
Bluetooth is broken on Steam Deck OLED on bazzite-deck-gnome:latest after version 39.20240328.0 (this is the last version when it worked correctly).
It doesn't work at all - cannot connect to paired devices (fails immediately upon selection), doesn't detect new/unpaired devices. I'm not sure if Bluetooth on/off switch even works at all.
This issue also is most probably (from my superficial log analysis) root cause of device's "'auto-resume' after suspend" issue. When device is suspended (either via power button or via menu option), it 'auto-resumes' after a few seconds pass. It happens every time, regardless of whether Bluetooth switch is ON or OFF. Relevant logs can be found in journalctl_after-suspend.txt file.
Both of those issues occur in both gamescope and desktop mode.
Last version of bazzite-deck-gnome where neither of these issues occured was 39.20240328.0. After updating from it, both of those issues started occurring.
Captured logs
dmesg_after-suspend.txt
dmesg_before-suspend.txt
journalctl_after-suspend.txt
journalctl_before-suspend.txt
journalctl-bluetooth_after-suspend.txt
journalctl-bluetooth_before-suspend.txt
lshw_after-suspend.txt
lshw_before-suspend.txt
lspci_after-suspend.txt
lspci_before-suspend.txt
lsusb_after-suspend.txt
lsusb_before-suspend.txt
What did you expect to happen?
I expected Bluetooth to continue to work properly (and not cause suspend issue) like in 39.20240328.0.
Output of rpm-ostree status
No response
Hardware
No response
Extra information or context
No response

Duplicate issue #960: every other boot boots with usb and bluetooth broken and cant shut down
Created: 2024-04-08T17:31:14Z
Describe the bug
Every other time I boot into bazzite my wireless usb mouse\keyboard doesnt work, bluetooth doesnt work, and if i use kdeconnect to control the mouse and click shutdown the screen goes black with the bazzite logo on the bottom and stays frozen forever. I can't press esc to check boot messages because the mouse\keyboard dont work and kdeconnect disconnects at this point.
What did you expect to happen?
This only happens every other time i boot into bazzite. When this happens I forcefully shut off my pc and then it boots like normal and everything works.
Output of rpm-ostree status
State: idle
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-gnome-nvidia:stable
                   Digest: sha256:2afc445458e106aab2db13cfea78afa908c0599516b5b9207d3c44b796a09859
                  Version: 39.20240116.0 (2024-04-07T01:32:51Z)
          LayeredPackages: nemo ulauncher
                Initramfs: '"-I /etc/crypttab /usr/lib/modprobe.d/nvidia.conf" ' 

  ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-gnome-nvidia:stable
                   Digest: sha256:2afc445458e106aab2db13cfea78afa908c0599516b5b9207d3c44b796a09859
                  Version: 39.20240116.0 (2024-04-07T01:32:51Z)
                Initramfs: '"-I /etc/crypttab /usr/lib/modprobe.d/nvidia.conf" '
Hardware
No response
Extra information or context
heres some screenshots from the Logs application (not sure if theyre relevant) and ill copy paste the sudo dmesg too



https://pastebin.com/rja07gwF

Closing comment (2024-04-18T14:20:48Z): On an OLED Deck.
Rebased from gnome:39-20240328 to gnome:stable (39-20240415) after seeing #950 closed. Bluetooth and sleep worked after the first reboot. I was excited, so I tried connecting my Steam Controller via BT. After everything seemed like it was working, I turned the controller off.
That's when the problems started. The built-in controller started going haywire: the Steam button was erratic, Dpad was intermittent, and when I went into the Settings to do a button test, all the inputs except the trackpads and sticks were detected. So I did a reboot again to try to fix it.
This time, navigating the menus was even harder. All the inputs except B, Option, Start, and the Dpad were detected (with B eventually stopping, too). Additionally, I could not get it to shutdown, restart, or boot into Desktop Mode, and there was no sound. The system menu showed no locale, no timezone, Bluetooth had no profiles, and the built-in controller was no longer detected. I forced a shutdown via long-press, and after reboot, BT is no longer working and sleep is still broken (possibly still related to #950 ).
A simple workaround for the Sleep issue seems to be:

Turn off Bluetooth
Reboot

This should re-enable Sleep mode until BT is turned on again.
Edit: Rolled back to gnome:39-20240328, and everything is working again. Sleep mode is now unaffected by BT, and connecting and disconnecting my BT controller does not adversely affect the built-in controller. Additionally, I can connect a BT controller, put the device to sleep or reboot it, and BT dis/reconnects as expected.