-
-
Notifications
You must be signed in to change notification settings - Fork 14.1k
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
Electron apps don't launch: Cannot find target for triple amdgcn #340196
Comments
I get the same problem with some electron-based apps from nixos-unstable and rarely find hints to similar problems (like this). I have encountered the same problem with: morgen, obsidian and todoist-electron about a week ago. Switched back to stable for them and they keep working. In common or maybe relevant:
Common error message:
Followed by (depending on your shell)
I'm not sure where to report this cause I'm not sure if it's related to an upstream electron issue (chrome had related issues recently) or one of the circumstances, or all of them and I am waiting for an electron update in unstable to see if it is fixed by then. Edit: might be gpu- and libva-related. Github issue search finds chrome, signal, visual studio code startup-, and jellyfin encoding issues. But not a lot. |
Same problem with mpv.
The system is 24.05 stable |
Same here with Brave version 1.69.162 from unstable
Edit: According to this post over at Signal Desktop signalapp/Signal-Desktop#6855 (comment) Someone fixed the error by removing old Mesa drivers. Mentioned here: https://dev1galaxy.org/viewtopic.php?pid=46495#p46495 I wonder if there is something similar going on for us 🤔 Edit2: There is also this post on a Debian bug tracker, which seems to confirm the direction this being an issue with Mesa https://lists.debian.org/debian-x/2024/05/msg00010.html Assuming all this is the same issue of course. |
I see my issue was mentioned. This happens to me with But it's a bit annoying I have this happen randomly. |
Having the same issue with cage:
Followed by a seg fault |
Does also happen with onlyoffice desktopeditors
|
This theory may be of interest to those experiencing this bug. |
Following the link above and then to another forum, I found that this works for me:
Would love an explanation of what this env var does in comparison to above thread. Interestingly, latest chromium build worked fine in Ubuntu 24.04 for instance (w/ amdgpu) but Chrome official Google release did not. VS Code broken. Basically any electron junk broken and I guess anything using Blink ? But Slack worked - which is also electron. Maybe they disable GPU acceleration in their build? |
I can confirm the LIBVA_DRIVER_NAME="vdpau" fixed this for google-chrome and signal-desktop for me. For me this problem was caused on an ubuntu 24.04 system with a 7800XT. All was fine until I installed AMD's ROCm. |
Describe the bug
When launching (unstable) anytype (from terminal or gnome) the GUI is not appearing/ no window is spawned. I updated my system and the next day it stopped working. It seems as some (probably the usual) background processes are started. When running the anytype AppImage, from their website, with appimage-run, the problem does not occure. I have an AMD GPU, if that is important. I also removed the
~/.config/anytype/
directory to reduce the likely hood of an configuration error.Steps To Reproduce
I am not sure, but the steps to reproduce the behavior on my system are:
Expected behavior
A GUI/Window appearing.
Screenshots
Additional context
None
Notify maintainers
@running-grass
Metadata
Please run
nix-shell -p nix-info --run "nix-info -m"
and paste the result.Add a 👍 reaction to issues you find important.
The text was updated successfully, but these errors were encountered: