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

At startup, the Riot web rings unexpectedly. #4607

Open
lampholder opened this issue Jul 17, 2017 · 11 comments
Open

At startup, the Riot web rings unexpectedly. #4607

lampholder opened this issue Jul 17, 2017 · 11 comments
Labels
A-Notifications A-VoIP O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Minor Impairs non-critical functionality or suitable workarounds exist T-Defect

Comments

@lampholder
Copy link
Member

At startup, the Riot web rings unexpectedly.

To reproduce:

  • close riot web
  • be called by another peer
  • answer the call on a phone (or possibly from another browser from another machine but I have not tested it)
  • open riot Web. Riot web rings like if the call was not answered.

Note that, when resuming like this, mobiles have some code to ignore m.call.invite if they are followed by m.call.answer or reject in the rest of first /sync responses.

@lampholder lampholder added T-Defect S-Major Severely degrades major functionality or product features, with no satisfactory workaround S-Minor Impairs non-critical functionality or suitable workarounds exist P2 A-VoIP and removed S-Major Severely degrades major functionality or product features, with no satisfactory workaround labels Jul 17, 2017
@rain-1
Copy link

rain-1 commented May 18, 2018

I also witness this bug, the phone rings for a fraction of a second when I open up riot. The reason is because there is a phonecall in my chat history.

@lofidevops
Copy link

Is this the same as/duplicate of #3572 (as suggested by #3699)?

@lofidevops
Copy link

(I'm experiencing this on the Flathub build of riot-web 0.17.3)

@rain-1
Copy link

rain-1 commented Aug 21, 2019

This is still a problem

@pacien
Copy link
Contributor

pacien commented Dec 6, 2019

Still here in 1.5.5…

@jryans
Copy link
Collaborator

jryans commented Dec 6, 2019

It's possible this is fixed by matrix-org/matrix-js-sdk#1082, which first reach release in 1.5.6 next week.

@SimonBrandner
Copy link
Contributor

@lampholder, is this still a problem?

@SimonBrandner
Copy link
Contributor

I've seen this a few times, so it seems to be an issue :(

@SimonBrandner SimonBrandner added O-Uncommon Most users are unlikely to come across this or unexpected workflow and removed P2 labels Aug 30, 2021
@HarHarLinks
Copy link
Contributor

This is the closest I could find to what is happening to me: I started a session that I have not used in a month or so and had several calls in the meantime. I scrolled and jumped to that room's history a bunch, including by search. It has happend 2 times that element rang unexpectedly for half a second or so.

Since it's both about loading history, it seems to be that it might even be the same issue.

@akoyaxd
Copy link

akoyaxd commented Sep 22, 2022

I do have this for a few Chats as well.

For me, it only happens on federated DMs..
The call also doesn't stop for me. I have to decline it to make it stop ringing.

@zhao-nan
Copy link

zhao-nan commented Nov 8, 2023

I seem to have a similar problem. Whenever I open Element Desktop, it appears that one of my contacts (always the same) is calling me, although they aren't. Unlike actual calls, this spurious call does not appear in the chat history.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Notifications A-VoIP O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Minor Impairs non-critical functionality or suitable workarounds exist T-Defect
Projects
None yet
Development

No branches or pull requests

9 participants