Andy Holmes

It seems like there's probably a new version of `openssl` making the rounds with different output we're failing to parse. Someone with this new version may have to figure out...

These are the two commands we parse output from: 1. Generate fingerprint (sha256sum of DER data): https://github.com/GSConnect/gnome-shell-extension-gsconnect/blob/396ae953f965c5bbbc2a6e354c78b858b623f98c/src/service/__init__.js#L366 2. Extract device ID (CN): https://github.com/GSConnect/gnome-shell-extension-gsconnect/blob/396ae953f965c5bbbc2a6e354c78b858b623f98c/src/service/__init__.js#L387 The certificate and private/public key pair are...

See also: https://github.com/GSConnect/gnome-shell-extension-gsconnect/issues/1395#issuecomment-1159515032

Thanks for reporting. Looks like this would require GSConnect to change the `SessionMode` from `restrictive` to something else or to modify the `restrictive` mode variable `allowScreencast` to `true`. Whether that's...

Okay, glad it's fixed for you :) We can leave this open for awhile, to see if anyone else has the same problem or knows what caused it.

Thanks for reporting with thorough logs! This is probably caused by GNOME Shell locking down external access to its DBus interface. There's probably not a good way to work around...

> Thanks for replying! Can I provide any other useful information? Nope, your report describes the problem perfectly! This is just new change in GNOME Shell that will have to...

There's been no progress. GSConnect is effectively a community-driven project now, so this will probably rely on someone coming forward to contribute a fix.

Not really without peeking through the source code. The available actions are just all the `GAction`s that don't take parameters, if I remember right. If you want to just ignore...

KDE Connect does not expose this state, so you will have to request the protocol addition upstream at https://bugs.kde.org.