matrix-org
Users can no longer write after changing their display names
Background information
- Dendrite version or git SHA: 0.8.5
- Monolith or Polylith?: Monolith
- SQLite3 or Postgres?: Postgres
- Running in Docker?: yes
go version: /shrug- Client used (if applicable): Element/Schildichat
Description
- What is the problem: Users can't write in their encrypted rooms anymore after changing their displaynames
- Who is affected: Everyone who has tried so far
- How is this bug manifesting: Messages can't be sent ("Some of your messages have not been sent. You can select all or individual messages to retry or delete")
- When did this first appear: after setting the server up some days ago
The logs are too long to just "find" related events… anything I should look out for?
Steps to reproduce
- Create user
- Invite user to encrypted room
- User logs in for the first time
- User joins Room
- User sends "Hello" which is successfully received
- User changes displayname
- User cannot send messages to the room anymore
Please try the latest main commit, since this should be fixed by #2507.
Updated to 0.8.7 and still no message sent. Only log message generated:
level=info msg=PerformPusherCreation display_name="FluffyChat ios" localpart=user pushkey="cuohufdMj0UMrcSAjVptnC:APA91bHCV70RATc4b2RZLRj5F6xvBQ9PMph-duZNGmjzdQqCn9g5pWLNMxhB0fKNjK1F_y3PcaEcQjI7u0GoxEIX7_lEE59ToHj4pgkxNGsc6ZzYVDQnbme0ZtTXKrBXTb3JxJeKq0nc" req.id=Ok1Y7UjL9rzQ req.method=POST req.path=/_matrix/client/r0/pushers/set user_id="@user:server.com"
(This happened in a private chat)
Leaving said private chat is also not possible:
level=info msg="User requested to leave join" room_id="!RooMIdeNTIfIEr:server.com" user_id="@user:server.com"
level=error msg="Failed to leave room" error="user \"@user:server.com\" is not a member of room \"!RooMIdeNTIfIEr:server.com\"" room_id="!RooMIdeNTIfIEr:server.com" user_id="@user:server.com\"
Possibly related: https://github.com/matrix-org/dendrite/issues/1662 But also, does this still happen? There have been some fixes to membership events/state resolution, which may have fixed issues like this.
Still happens. I got the same problem with v0.12.0 now, triggered by changing display name in an encrypted room. The user cannot be removed from room as the server replies that kicked or left users cannot be removed, although the user is still a room member.
