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

Element Desktop crashed upon attempting to accept an incoming 1:1 call #19104

Closed
anoadragon453 opened this issue Sep 20, 2021 · 4 comments
Closed
Labels
A-VoIP O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Critical Prevents work, causes data loss and/or has no workaround T-Defect X-Cannot-Reproduce Z-Platform-Specific

Comments

@anoadragon453
Copy link
Member

Steps to reproduce

  1. Have an incoming 1:1 call.
  2. Click pickup from the cell in the timeline.
  3. Element desktop closes.

What happened?

What did you expect?

The call to start.

What happened?

Element desktop closed.

Operating system

Arch Linux

Application version

Element Nightly version: 2021091901; Olm version: 3.2.3

How did you install the app?

The AUR

Homeserver

No response

Have you submitted a rageshake?

Yes

@SimonBrandner SimonBrandner added A-VoIP O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Critical Prevents work, causes data loss and/or has no workaround labels Sep 20, 2021
@germain-gg
Copy link
Contributor

I was not able to unveil any useful information from the rageshake report unfortunately
Looking at the recent changelog, I can only see element-hq/element-desktop#256 that could possibly impact you in this case.

We currently do not have a way to rageshake the IPC logs unfortunately, will open an issue for it

@SimonBrandner
Copy link
Contributor

@anoadragon453, are you using Wayland?

@anoadragon453
Copy link
Member Author

@SimonBrandner I am not, but I am using Pipewire. It's also worth mentioning that Element desktop did not crash after starting it up again, changing my media sources and sinks in Element's settings and then making a call to the same participant.

@novocaine
Copy link
Contributor

novocaine commented Sep 23, 2021

If we don't have any other process-level logs or a core dump, we can't take action, so will close for now - we can reopen if we receive subsequent reports.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-VoIP O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Critical Prevents work, causes data loss and/or has no workaround T-Defect X-Cannot-Reproduce Z-Platform-Specific
Projects
None yet
Development

No branches or pull requests

4 participants