Event JSON
{
"id": "4cbbc8ed72aa09673a589c155dd2d6657b75894cff675f0c17908069f1bec355",
"pubkey": "f5cb277ce6066db9e0b11aa66fef222f1ec7b53a6960c0f964c3174fc569eaf9",
"created_at": 1759410695,
"kind": 1,
"tags": [
[
"t",
"bluetooth"
],
[
"imeta",
"url https://files.mastodon.social/media_attachments/files/115/304/735/813/413/765/original/dc8f3ac76c9df011.png",
"m image/png"
],
[
"t",
"bluez"
],
[
"proxy",
"https://mastodon.social/@nekohayo/115304739317377070",
"web"
],
[
"emoji",
"blobpats",
"https://files.mastodon.social/custom_emojis/images/000/003/679/original/80d1ba80bf06950e.png"
],
[
"t",
"gnome"
],
[
"proxy",
"https://mastodon.social/users/nekohayo/statuses/115304739317377070",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://mastodon.social/users/nekohayo/statuses/115304739317377070",
"pink.momostr"
],
[
"-"
]
],
"content": "Found why the #Bluetooth behavior in #GNOME was so confusing to me over the years: while my computer (and the gnome-bluetooth backend) supports connecting \u0026 pairing multiple devices at once, it turns out that #BlueZ sometimes reports some devices as disconnected when reactivating Bluetooth… so I end up accidentally disconnecting a device when I think it is not already connected :blobpats:\n\n…as discovered in https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/8692, it turns out to be a BlueZ issue… but BlueZ has no bug tracker 🫠\nhttps://files.mastodon.social/media_attachments/files/115/304/735/813/413/765/original/dc8f3ac76c9df011.png\n",
"sig": "df5708001fc96ec4dfbd012b159b61864006aa3aebded99b7090a7a819a9a53bce48e647565eff70ea331cc2744e4f44c7f88db36c54f5684f80bcddb11f6057"
}