Version 0.15.2 and 0.15.3 of riot-web: Encryption not working any longer, earlier encrypted rooms become undecryptable

[chrissi55]

Description

After Upgrading my Version of riot-web: to 0.15.2 all e2e encrypted chats are undecryptable.
Program says - enforce resending keys again but when key pulling is enforced nothing happened.

Exporting and Importing Keys of another (Android) Client will re-enable all posts till point of export.

But newly send messages are again encrypted for the Linux Client.

All my devices where accepted by riot.

Steps to reproduce

• For bugs, list the steps
• that reproduce the bug
• using hyphens as bullet points

Describe how what happens differs from what you expected.

@dbkr Log: How to extract the errorlogfile? I can't find the log under /var/log/... nor /opt/riot/.... please give me a hint

Version information

• Platform: desktop!

For the web app:

• Browser: no webapp -> desktop
• OS: Linux
• URL: riot.im/develop / riot.im/app / somewhere else? If a private server, what version of riot-web?

For the desktop app:

• OS: Linux, Zorin OS (ubuntu)?
• Version: riot 0.15.2, Zorin 12.3

Update:
I cleared the Cache and reboot ... no difference, chat stays encrypted

[dbkr]

Can you fill in the rest of the fields in the bug report please? Most importantly, sent log files from both the sender and receiver.

[akontsevich]

I have same issue: now can't access messages at all on any device with 0.14 or 0.15.2 versions, both: desktop and web version in any browser. Terrible: now I can't read the room where I'm an administrator. I suggested people to use Riot now will be forced to close this room and create new one. Need to test better before release to public! Now it is totally unusable!

OS: Linux openSUSE
Browser: FF, Chrome

[chrissi55]

I did some more tests ....

Created a new Room with linux desktop app 0.15.2
Started e2e encryption and invited someone

Invite has been accepted and messages sent were signed with a green lock.
On side of the receiver every message is marked as

"** Unable to decrypt: The sender's device has not sent us the keys for this message. **
Verschlüsselungs-Schlüssel von deinen anderen Geräten erneut anfragen.?"

So the problem exists not only for earlier created e2e encrypted rooms but also for newly created ones.
Something must be broken by e2e encryption.

Opening the details of the encrypted room and clicking on the device list of a member offers "all deveices are accepted"

Rooms with no e2e are working as expected.

[chrissi55]

Somebody should tag this problem as bug or maybe critical before other users upgrade their desktop app and run into same desaster!

[ara4n]

we have only heard about this from two people, and haven’t seen any logs to debug (please submit them via the Submit Logs button in User Settings), so we’re still trying to assess how bad the situation is.

Have you been trying to switch back and forth between 0.14 and 0.15 desktop apps?

[ara4n]

(i'm going to delete the "why don't we completely change Matrix's encryption model" comments, as they're irrelevant and distracting to this bug - feel free to open a separate spec bug over at matrix-org/matrix-doc if you like)