Andy Holmes

I've just pushed a release candidate here: https://github.com/andyholmes/gnome-shell-extension-gsconnect/releases/tag/v40-rc1 You can start using that (and testing :wink:) by following the instructions [in the Wiki](https://github.com/andyholmes/gnome-shell-extension-gsconnect/wiki/Installation#install-from-zip).

Well, this issue I'm going to leave open to track the "keyboardstate" protocol problem. Those particular key issues, I'll have to poke around a bit when I have time. They...

Good news is @nicolasfella submitted an [MR yesterday](https://invent.kde.org/network/kdeconnect-android/-/merge_requests/183/diffs), so I'll give that a test later tonight and maybe we can revert the workaround in `v40-rc1`. For things like focusing the...

Just to avoid confusion, this use of bluetooth is orthogonal to the bluetooth *connection* backend. Both could operate at the same time, though. I'd guess that the way to control...

As far as I know, there is no GObject-based library for real bluetooth stuff. The `gnome-bluetooth` library only offers very high-level list/connect/disconnect functionality. The bluez DBus service is probably the...

Normally I'd recommend you'd pop onto the kdeconnect development channel, but since you've posted some research here I'm going to go ahead and CC @albertvaka and @nicolasfella. They may have...

> Due to this, even if you installed the v53 tag or release, you would end up with v50 in the GUI. This could have already caused a packaging issue...

> I am sorry. I checked the release again, the versioning is alright for v53. Before, when I tried, there was an issue with the GUI version. No problem. There's...

That's probably not a bad idea, assuming someone wants to keep rolling backported releases. There's really no reason why the e.g.o version has to match our tags anyways, and really...

Closing since v54 was ultimately released for GNOME 43.