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

Segmentation fault when attempting to launch #2180

Closed
poperigby opened this issue Mar 2, 2025 · 2 comments
Closed

Segmentation fault when attempting to launch #2180

poperigby opened this issue Mar 2, 2025 · 2 comments
Labels
A-Electron 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

Comments

@poperigby
Copy link

poperigby commented Mar 2, 2025

Steps to reproduce

  1. Launch Element Desktop

Outcome

What did you expect?

The app to launch.

What happened instead?

The app crashes with a segmentation fault.

Coredump: https://drive.google.com/file/d/1kDhgW3Hhdi0a4Gl6tXqs4yJtZXlJiyKf/view?usp=sharing

Operating system

NixOS

Application version

1.11.91

How did you install the app?

nixpkgs

Homeserver

matrix.org

@dosubot dosubot bot added A-Electron 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 Mar 2, 2025
@HeroBrine1st
Copy link

HeroBrine1st commented Mar 2, 2025

Downstream issue NixOS/nixpkgs#384743
Can't reproduce on ba78e710534796deb1b09ba271115a8c5317b56e (nixpkgs). I used nix run github:NixOS/nixpkgs#element-desktop and got this commit hash from URL (rev=... can be used for exact reproduce). On 0196c0175e9191c474c26ab5548db27ef5d34b05 it is easily reproduced, but that was some time ago.

As said in downstream issue, it is fixed. I failed to find exactly which commit fixed that though. Also, according to (almost) instant launch after downloading, fix is already on cachix.

@t3chguy
Copy link
Member

t3chguy commented Mar 3, 2025

The nixpkg isn't maintained by us but the issue is likely due to nodejs/node#57233 and the house of cards that is the Node ecosystem

@t3chguy t3chguy closed this as not planned Won't fix, can't repro, duplicate, stale Mar 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Electron 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
Projects
None yet
Development

No branches or pull requests

3 participants