Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Users can no longer write after changing their display names #2508

Closed
mpldr opened this issue Jun 1, 2022 · 7 comments · Fixed by #3231
Closed

Users can no longer write after changing their display names #2508

mpldr opened this issue Jun 1, 2022 · 7 comments · Fixed by #3231
Labels
F-State-Res T-Defect Bugs, crashes, hangs, security vulnerabilities, or other reported issues. X-Needs-Info This issue is blocked awaiting information from the reporter

Comments

@mpldr
Copy link

mpldr commented Jun 1, 2022

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
@neilalexander
Copy link
Contributor

Please try the latest main commit, since this should be fixed by #2507.

@mpldr
Copy link
Author

mpldr commented Jun 2, 2022

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)

@mpldr
Copy link
Author

mpldr commented Jun 2, 2022

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\"

@neilalexander
Copy link
Contributor

If you try to re-/join the room first, does it let you leave after?

@mpldr
Copy link
Author

mpldr commented Jun 3, 2022 via email

@S7evinK
Copy link
Contributor

S7evinK commented Oct 20, 2022

Possibly related: #1662
But also, does this still happen? There have been some fixes to membership events/state resolution, which may have fixed issues like this.

@kegsay kegsay added T-Defect Bugs, crashes, hangs, security vulnerabilities, or other reported issues. X-Needs-Info This issue is blocked awaiting information from the reporter F-State-Res and removed bug labels Dec 5, 2022
@dkopecek
Copy link

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.

S7evinK added a commit that referenced this issue Oct 23, 2023
danpe pushed a commit to globekeeper/dendrite that referenced this issue Oct 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
F-State-Res T-Defect Bugs, crashes, hangs, security vulnerabilities, or other reported issues. X-Needs-Info This issue is blocked awaiting information from the reporter
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants