UTD(unable to decrypt) errors even though verification with another device happened successfully

[albertotirla]

Steps to reproduce

1. Go sign into an account, preferably one which was active before the switch to matrix rust sdk
2. When you're asked for verification, select verify with another device
3. Complete verification, in this case, this person used element desktop on windows to verify linux. Nothing else out of the ordinary has to happen here, click they match, obviously only if the emojis match

Outcome

What did you expect?

I expected the e2ee rooms to be decryptable, everything should read as normal

What happened instead?

all my previous messages to this person are showing as UTD errors on their side. However, as is to be expected, any messages after the new device is signed in work and decrypt normally

Note: I think the issue is backup related, it's possible that key backup might be malformed on the account. This person never used anything else other than element and element X, so behaviour of other clients can be ruled out

Operating system

linux is the device which is being verified, the verification comes from windows

Application version

latest(flatpak)

How did you install the app?

flathub, using the application store of kde, aka discover

Homeserver

Synapse 1.116.0

Will you send logs?

Yes

[t3chguy]

The flatpak is supported in https://github.com/flathub/im.riot.Riot/

[albertotirla]

I don't think the packaging method is specifically related to this issue, it's possibly a bug with element desktop. If everything went well, you should have recieved two rageshakes, one from each device

So, should I make an issue there, then?