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

Leaving and re-joining a Libera.Chat room inside a space results in a "Something went wrong!" message. #23250

Closed
ArrayBolt3 opened this issue Sep 9, 2022 · 3 comments
Labels

Comments

@ArrayBolt3
Copy link

Steps to reproduce

  1. Join the space #ubuntu-workshop:matrix.org.
  2. Join one of the rooms (#ubuntu-devel works).
  3. Leave the room (run the "/part" command in the text box)
  4. Attempt to join the same room again.

Outcome

What did you expect?

The room should be joined without error, and all messages will go through the Libera.Chat IRC bridge properly, both incoming and outgoing.

What happened instead?

The following screen appears:
image
Clicking off of it and onto the newly joined room seems to work, though I have not yet tested whether messages go through or not.

Operating system

Ubuntu 22.04.1

Application version

Element version: 1.11.4, Olm version: 3.2.12

How did you install the app?

From the element.io apt repository

Homeserver

matrix.org

Will you send logs?

Yes

@ArrayBolt3
Copy link
Author

Additionally, I've noticed that messages I send through Matrix show up in IRC, but messages from IRC aren't showing up in Matrix.

Quick notice, I may have messed up the IRC bridge, or it might be Libera.Chat's fault, so this might not be a bug, but rather an issue on my end.

@ArrayBolt3
Copy link
Author

New updates - multiple bridged IRC rooms are still working for me. I have attempted entirely leaving the Ubuntu Workshop space and another space I was joined to, logging out, closing Element, opening it, logging back in, joining the space, and attempting to join a room, and I still get the error message.

@SimonBrandner
Copy link
Contributor

Duplicate of #22752

@SimonBrandner SimonBrandner marked this as a duplicate of #22752 Sep 10, 2022
@SimonBrandner SimonBrandner closed this as not planned Won't fix, can't repro, duplicate, stale Sep 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants