Automattic / simplenote-electron

Simplenote for Web, Windows, and Linux
https://app.simplenote.com
GNU General Public License v2.0
4.83k stars 559 forks source link

FATAL:gpu_data_manager_impl_private.cc(415)] GPU process isn't usable. #3044

Closed Jed28 closed 3 months ago

Jed28 commented 3 years ago

Issue

Simplenote-linux-2.21.0-x86_64.rpm

$ /opt/Simplenote/simplenote %U
[93440:1112/150906.643603:FATAL:gpu_data_manager_impl_private.cc(415)] GPU process isn't usable. Goodbye.
[1]    93440 trace trap (core dumped)  /opt/Simplenote/simplenote %U

Simplenote-linux-2.21.0-x86_64.AppImage

$ ./Simplenote-linux-2.21.0-x86_64.AppImage
[144480:1112/160306.085970:FATAL:gpu_data_manager_impl_private.cc(415)] GPU process isn't usable. Goodbye.
[1]    144480 trace trap (core dumped)  ./Simplenote-linux-2.21.0-x86_64.AppImage %U

Expected

I expected the program to start

Observed

I made a fresh VM of Fedora 35 and tested the same rpm/appimage of Simplenote. I got the same results as this bug report. I don't know why mine is different or if it related.

Reproduced

  1. Start simplenote within the terminal

Where did you see the bug

brajevicm commented 3 years ago

I can confirm that this issue also happens on Fedora 35 + Gnome (Both Xorg and Wayland). It happens regardless if you started via terminal or via desktop shortcut.

EDIT: Intel i7-10510U UHD Graphics 620

binary-data commented 3 years ago

Fedora 35 KDE - same issue (5.14.17-301.fc35.x86_64)

brajevicm commented 2 years ago

Temporary workaround would be to edit desktop shortcut, and make the following change: Exec=/opt/Simplenote/simplenote %U -> Exec=/opt/Simplenote/simplenote --no-sandbox %U

On Fedora 35 + Gnome, the shortuct is located at /usr/share/applications/simplenote.desktop

Jed28 commented 2 years ago

The workaround works, thanks.

PinkFrosty commented 2 years ago

Thank you for the workaround. It's now working for me on F35 xfce4 spin.

coderGambit commented 2 years ago

Thanks @brajevicm , this workaround works for ClickUp in F35 KDE

erricgunawan commented 2 years ago

Probably related/similar problem from 4695050-zen:

... at the moment simplenote will not run on the latest version of Fedora 35. It generates a gpu_data_manager_impl_private error. I also have seen this error report in another place that has nothing to do with your great program, so it is likely a Fedora issue. I see the same problem with both the rpm and AppImage versions, and I do not see any problems on my KDE Neon system which is based on an older Ubuntu LTS base. Also the Windows version works fine, but it pains me to have to run Windows! Apple and Android versions are also good.

Simple-linux-2.21.0-x86_64.rpm is installed and produces this output:

al@xvb:/home/al $/opt/Simplenote/simplenote [12257:0124/112406.809083:FATAL:gpu_data_manager_impl_private.cc(415)] GPU process isn't usable. Goodbye. Trace/breakpoint trap (core dumped) al@xvb:/home/al $

I am running Fedora 35, which while it is not completely bleeding edge stuff is one of the more advanced and progressive distributions of Linux:

Linux xvb 5.15.16-200.fc35.x86_64 #1 SMP Thu Jan 20 15:38:18 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

As previously stated, this version runs OK on an Ubuntu LTS based system (KDE Neon, older kernel and libs) and Windows. I also tried the AppImage here, and it fails exactly the same as the rpm version. I found that interesting as I thought an AppImage had all the required libs included as part of the image, thus removing various dependencies.

The same gpu error has been reported for another program on other distributions, so I do not think the error is specific to SimpleNote, but rather a Linux problem, possibly a change (update) in a lib package. See this error report:

https://github.com/LedgerHQ/ledger-live-desktop/issues/4253

xiborg commented 2 years ago

Same issue on Ubuntu Jammy Jellyfish 22.04 Beta 5.15.0-25-generic #25-Ubuntu SMP Gnome 42 System: Intel(R) Core(TM) i9-10900 CPU @ 2.80GHz, CometLake-S GT2 [UHD Graphics 630] Workaroud with --no-sandbox works.

vpn12out commented 2 years ago

Same issue on Kubuntu 22.04 LTS x86_64

libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null) libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null) libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null) [8241:0428/011336.872765:FATAL:gpu_data_manager_impl_private.cc(415)] GPU process isn't usable. Goodbye. Chrome_IOThread[8271] trap int3 ip:5637a021fc68 sp:7f31a0182320 error:0 in simplenote[56379fff0000+626b000] app-simplenote-eb17703a6a8541a199c387521da71481.scope: Consumed 3.188s CPU time.

phodamentals commented 2 years ago

Workaround 'works' on 5.17.5-76051705-generic Pop!_OS 22.04...

ghostry commented 2 years ago

-no-sandbox works on ubuntu 22.04

vpicavet commented 2 years ago

I had the same error with the Linux Zoom client, and launching it with --no-sandbox allows the program to run. No idea why though, but thanks for the workaround ;-)

worldomonation commented 2 years ago

Similar bug but for WordPress.com Desktop app: https://github.com/Automattic/wp-calypso/issues/62088

brennmat commented 2 years ago

Can confirm this issue on Debian bookworm/sid with Gnome 42.2. The workaround described by @brajevicm works for me.

jsvnsk commented 2 years ago

Able to reproduce on the following configuration:

Intel Core i5-4590T (2.00 GHz, quad-core) 8GB RAM Intel HD graphics 4600 (HSW GT2) Ubuntu 22.04.1 LTS + Gnome DE + 5.15.0-46-generic Simplenote: 2.21.0

Also can verify the --no-sandbox workaround resolves the error

ghost commented 2 years ago

Getting the same error on Linux Mint 21.0 (which is based on Ubuntu 22.04); on 20.3 (based on Ubuntu 20.04) I was not having this problem.

akwala commented 2 years ago

+1 Operating System: Ubuntu 22.04.1 LTS
Kernel: Linux 5.15.0-46-generic plasmashell 5.24.6 Qt: 5.15.3 KDE Frameworks: 5.95.0

DocBretti commented 2 years ago

@brajevicm This workaround is still needed and also works on manjaro atm im typing this. Thnx a lot for pointing this out.

trizdev commented 2 years ago

Thanks for the workaround. Same problem using Kubuntu 22.04 but adding --no-sandbox %U helps.

jozsefk9 commented 2 years ago

Still the same issue on Fedora 36 XFCE. Workaround works.

kinton commented 2 years ago

Got the problem today, thanks for the workaround. Manjaro 22.0.0 Sikaris, KDE 5.98.0 / Plasma 5.25.5

irfaanz commented 2 years ago

no sandbox workaround is working fine so far. I am on Simplenote 2.21, and i have added simplenote -no-sandbox as my start up application in linux mint vanessa. However, i want it to get started headless. Any paramaters that i can pass to start it headless.

Flashwalker commented 1 year ago

It is Electron issue, when Electron-libs don't match your system

--in-process-gpu option helps as workaround. Also --disable-gpu-sandbox or --no-sandbox helps too

ghost commented 1 year ago

Disabling sandbox is never a good option because, you know, it disables the sandbox where electron apps are supposed to run. --in-process-gpu is probably a better solution

mbrennwa commented 1 year ago

I can confirm that running Simplenote using /opt/Simplenote/simplenote --in-process-gpu works fine on my Debian SID box. Thanks!

deon-vector commented 1 year ago

Confirming, I have simplenote 2.21.0-25251 installed on Mint 21 (Ubuntu 22.04 based) using apt and it won't launch. I edited the /usr/share/applications/simplenote.desktop file and added "--in-process-gpu" to it, which I agree is better than disabling the sandbox, and simplenote launches now. --no-sandbox works also but since both options work, might-as-well go with the safer one. This is strange that years later this problem still persists.

ralyodio commented 1 year ago

will this ever get fixed on manjaro? I have to use simplenote --no-sandbox icon launcher won't launch it. KDE Plasma

Litos523 commented 1 year ago

Same fail on Debian Trixie Workaround ok

Aleksandr-ru commented 11 months ago

Same on Manjaro 23.1.0, Simplenote: 2.21.0. Using workaround, waiting for solution...

codebykat commented 3 months ago

The latest version (2.22.1) upgraded a ton of dependencies and should have fixed issues such as this one. Please let us know if this is still a problem after updating!