[BUG] BlueZ timed out while connecting to device - Debian 13

[abulusky]

Describe the bug
On my debian system, when trying to connect to earbuds, it shows Bluez timed out error. Can't connect.

To Reproduce
Steps to reproduce the behavior:

1. Launch the app (flatpak run me.timschneeberger.GalaxyBudsClient or from app menu)
2. Try to connect to Galaxy Buds
   • Automatic connection fails
   • Manual connection fails via both system Bluetooth manager and the app

Expected behavior
Buds should connect automatically, or at least when clicked connect.

Screenshots

Desktop (please complete the following information):

• OS: Debian GNU/Linux 13 (trixie) x86_64
• Kernel: Linux 6.12.35+deb13-amd64
• DE: KDE Plasma 6.3.5
• Application version: 5.1.0.2

Additional context
On a second Debian testing laptop, the same app version works.

However, even on that device, system Bluetooth manager couldn't connect — only along with the app it works

Log files
In most cases if you have a bug, log file will be required - it is located at %localappdata%\GalaxyBudsClient\application.log

• Captured through flatpak run me.timschneeberger.GalaxyBudsClient | tee debug.log debug.log
• System stored app log application.log

[GBlackfog]

I am also getting "BlueZ timed out while connecting to device" when connecting my Galaxy Buds 3 Pro.

I am running it on SteamOS on Steam Deck Oled.

[abulusky]

Extra Info:

On first pairing, it works. But after reboots (earbuds is paired to system) it fails