-
-
Notifications
You must be signed in to change notification settings - Fork 297
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bluetooth dropping connection almost instant on every device connected. #1559
Comments
@YeGop0218 can you elaborate more on what this zip does? |
This is malware, ignore it. Github is getting spammed. |
@KyleGospo is there any info i can provide that can help you dive deeper into it? |
Hi, @levi2m. I'm Dosu, and I'm helping the bazzite team manage their backlog. I'm marking this issue as stale. Issue Summary:
Next Steps:
Thank you for your understanding and contribution! |
hey @dosubot yes, definitely still happening my way of using the DS4s even with this issue is every time I boot up the machine, I need to go into remote console and pair again the DS4 im currently using I can't say how much this issue is bugging me, and also happens on another machine I have that is a ryzen laptop |
Hi, My Wife approval factor of Bazzite is now quit low 1/10 😄 |
Describe the bug
When trying to connect, any device that is already paired (for example a couple of DualShock 4's i've), they instantly drop connection as you can see in the screenshot bellow:
Note that when this does happen, the controllers doesn't show a specific color as when they show when forced-connected or via USB. They just keep blinking white as waiting for the host to accept connection.
But, the controllers can connect and work with bluetooth if they got forced to connect through bluetoothctl or Steam's system > bluetooth > device > connect.
What did you expect to happen?
Power on machine with the PS button on the DS4's is a feature at this point, but would love to see it connecting and keeping that way when the system is full powered on and idle.
Output of
rpm-ostree status
l2m@bazzy:~$ rpm-ostree status State: idle Deployments: ostree-unverified-registry:ghcr.io/ublue-os/bazzite-deck:stable Digest: sha256:f23de493b70d8900546a7f485a9110c75df9c8d7529626ce4580d557b7349587 Version: 40.20240826.0 (2024-08-27T06:59:55Z) LayeredPackages: ncdu ● ostree-unverified-registry:ghcr.io/ublue-os/bazzite-deck:stable Digest: sha256:f23de493b70d8900546a7f485a9110c75df9c8d7529626ce4580d557b7349587 Version: 40.20240826.0 (2024-08-27T06:59:55Z) LayeredPackages: ncdu ostree-unverified-registry:ghcr.io/ublue-os/bazzite-deck:40-testing Digest: sha256:6161ea5dfb03263283552b128f31b3d23f4c3ebaeb36a8b44ea5dee1d1dc4321 Version: testing-40.20240822.3 (2024-08-23T20:45:29Z) LayeredPackages: ncdu
Hardware
neofetch:
Extra information or context
No response
The text was updated successfully, but these errors were encountered: