-
Notifications
You must be signed in to change notification settings - Fork 2k
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
GPU process isn't usable. Goodbye. #3639
Comments
It is one of tumbleweed's problem with nvidia. To run most of electron apps you should add flag --disable-gpu-sandbox |
As @NikitinGs said. Closing |
I have no problem with Nvidia on Tumbleweed, environment and driver are used intensively every day with CUDA, and many intensive 3D applications etc. I believe it is not an issue experienced exclusively with openSUSE, this seems to be an issue with electron. But anyway, thanks for the recipe. |
how do I add flags and wdym add a flag? (Sorry, I'm new to linux) |
launch it from console and add flags after space (example: |
Create a file called etcher.desktop with the contents below: [Desktop Entry]
Name=Etcher
Comment=Flash OS images to SD cards & USB drives, safely and easily
Exec=sh -c "/home/username/Applications/balenaEtcher.AppImage --disable-gpu-sandbox"
Icon=/home/username/Applications/Icons/etcher.png
Type=Application
StartupNotify=false
Terminal=false
Categories=DiskTools;Utility Copy etcher.desktop to /usr/share/applications You can get the icon from here |
The In addition, I don't think that GPU acceleration is really needed for etcher in general. Of course this should be removed again, when NVIDIA got everything working. |
Failing on Ubuntu 22.04 too. I agree, if it's not working on NVidia generally, that's 50% of users. Balena should deploy with the flag until this is resolved. |
This is still a problem on Arch (installed with yay) |
Its verry Unweildy to not have --disable-gpu-sandbox as the default and enable-gpu-sandbox as a flagg |
@NicTanghe I do not think this is stupid in general, as using the GPU could increase performance for other applications. In this case though, "--disable-gpu-sandbox" should obviously be the default, as not having it set by default causes problems and is not really necessary for this kind of application. |
right but isn`t sandboxing the gpu something that is a part of this application ? |
[mcraa] This has attached https://jel.ly.fish/2feff0f1-bf45-4506-a11f-ef6cc0fe1065 |
Are there any security risks when --disable-gpu-sandbox ? |
I'm wondering why is the situation. If that is the truth, then electron/chromium team will probably make it as the default best practice 🤔 |
./balenaEtcher-1.7.0-x64.AppImage
libva error: /usr/lib64/dri/i965_drv_video.so init failed
libva error: /usr/lib64/dri/i965_drv_video.so init failed
libva error: /usr/lib64/dri/i965_drv_video.so init failed
[Axios v1.7.0] Transitional option 'clarifyTimeoutError' has been deprecated since v1.0.0 and will be removed in the near future
[Axios v1.7.0] Transitional option 'forcedJSONParsing' has been deprecated since v1.0.0 and will be removed in the near future
[Axios v1.7.0] Transitional option 'silentJSONParsing' has been deprecated since v1.0.0 and will be removed in the near future
[19146:1123/180729.228900:FATAL:gpu_data_manager_impl_private.cc(415)] GPU process isn't usable. Goodbye.
/tmp/.mount_balenanM6ZuF/balena-etcher-electron: line 10: 19146 Trace/breakpoint trap (core dumped) "${script_dir}"/balena-etcher-electron.bin "$@"
PC has Nvidia video card and NVIDIA Driver Version 470.74 installed.
The text was updated successfully, but these errors were encountered: