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

GPU process isn't usable. Goodbye. #38

Open
arfar opened this issue Aug 15, 2022 · 4 comments
Open

GPU process isn't usable. Goodbye. #38

arfar opened this issue Aug 15, 2022 · 4 comments
Labels
workaround There's a workaround available

Comments

@arfar
Copy link

arfar commented Aug 15, 2022

Hi there

When trying to start the mtgatool-desktop-6.1.39.AppImage from the terminal I get the following message:

Checking for update
[7517:0815/234553.579214:FATAL:gpu_data_manager_impl_private.cc(415)] GPU process isn't usable. Goodbye.
Trace/breakpoint trap (core dumped)

I've tried to use some flags like --debug or --help to see if anything would change, but I can't seem to get any other output that what is provided above.

It also doesn't work when double clicking on the icon in a file viewer. I suspect the same error occurs, but no error window is provided or anything like that.

Any help would be greatly appreciated.
Thank in advance

@arfar
Copy link
Author

arfar commented Aug 22, 2022

I've completely reinstalled Pop_OS on my computer (for reasons unrelated to this) and now I get the following error. I note the application did actually launch once. But upon re-launching I get this error.

Checking for update
Update for version 6.1.41 is not available (latest version: 6.1.41, downgrade is disallowed).
Update not available
{
  version: '6.1.41',
  files: [
    {
      url: 'mtgatool-desktop-6.1.41.AppImage',
      sha512: 'TuVc5hhzT8pfFmZF4dgFV19I5E+YEMX7oFpyFyQCRlz0l1pjfWFnA0o8T1o8iVIOxYlR4dX56gV6rfzAL2qyLg==',
      size: 161871525,
      blockMapSize: 169657
    }
  ],
  path: 'mtgatool-desktop-6.1.41.AppImage',
  sha512: 'TuVc5hhzT8pfFmZF4dgFV19I5E+YEMX7oFpyFyQCRlz0l1pjfWFnA0o8T1o8iVIOxYlR4dX56gV6rfzAL2qyLg==',
  releaseDate: '2022-08-20T21:05:29.617Z',
  releaseName: '6.1.41',
  releaseNotes: ''
}
\>> createWindow()
checkForUpdatesAndNotify called, downloadPromise is null
[51920:0822/223254.321491:FATAL:gpu_data_manager_impl_private.cc(415)] GPU process isn't usable. Goodbye.
Trace/breakpoint trap (core dumped)

It may or may not be relevant, but when trying to run the daemon, I get the following error:

~/bin/mtgatool$ /usr/share/mtga-tracker-daemon/mtga-tracker-daemon
Current version = 1.0.5.0
No usable version of libssl was found
Aborted (core dumped)

@clagiordano
Copy link

@arfar it seems related to the electron sandbox security options, trying to run it with --no-sandbox it starts, if i remember correctly i had the same issue with rambox back then.

  • we can:
    • run it using the CLI and the parameter --no-sandbox
    • add the flag --no-sandbox to the .desktop file entry

i've also tested changing the sticky bits with chmod but it doesn't seems a working solutions.

I hope that it could be helpful.

@multimeric
Copy link

Thanks @clagiordano that seems to work! I updated the start.sh script since that seems to be run by the .desktop file, so changing it there fixes it everywhere:

--- start.sh	2022-12-17 17:04:17.343472641 +1100
+++ /usr/share/mtgatool/start.sh	2022-12-17 17:02:23.953367412 +1100
@@ -1,4 +1,4 @@
 #!/usr/bin/env bash
 LAST_VERSION=$(ls mtgatool-desktop-* | sort -t. -k 1,1n -k 2,2n -k 3,3n -k 4,4n | tail --lines=1)
-./$LAST_VERSION
+./$LAST_VERSION --no-sandbox

@riQQ
Copy link
Contributor

riQQ commented May 27, 2023

There is also --disable-gpu-sandbox, which should be better than disabling the whole sandbox.
Maybe there are more relevant switches here: https://chromium.googlesource.com/chromium/chromium/+/master/content/public/common/content_switches.cc

@riQQ riQQ added the workaround There's a workaround available label Apr 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
workaround There's a workaround available
Projects
None yet
Development

No branches or pull requests

4 participants