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

[BUG] - Linux Appimage and pacman package crash on startup. "GPU process isn't usable. Goodbye." #1395

Open
Cknight70 opened this issue Jul 8, 2024 · 10 comments
Labels
bug Minor issue

Comments

@Cknight70
Copy link

Describe the bug
When starting r2modmanPlus with both the appimage version and the pacman package, the program will start and show a blank r2modmanPlus window for a few seconds, then close.

To Reproduce
Steps to reproduce the behavior:

  1. Install the pacman package, or simply run the appimage provided in releases or on the thunderstore page
  2. Run program

Additional context
I have a Nvidia graphics card, I'm using the proprietary driver on Xorg, I am Running Arch linux.

I ran the app image in bash and got the following log

$   /ebkr-r2modman-3.1.49/r2modman-3.1.49.AppImage 
xdg-mime: application argument missing
Try 'xdg-mime --help' for more information.
starting server on  /tmp/app.r2mm 
starting TLS server false
starting server as Unix || Windows Socket
[7373:0707/182304.968192:FATAL:gpu_data_manager_impl_private.cc(445)] GPU process isn't usable. Goodbye.
Trace/breakpoint trap (core dumped)
@Cknight70 Cknight70 added the bug Minor issue label Jul 8, 2024
@Cknight70
Copy link
Author

Hi, I've seemed to have fixed the issue myself by appending --no-sandbox at the end of the run command for this.
so for example I can type r2modman --no-sandbox in bash, or add the argument to the desktop startup file like this screenshot

image

@Jaskowicz1
Copy link

Same issue with the deb installation, just seems like it's every single package that is broken.

@TupalupaGit
Copy link

Your solution worked for me, thanks!

@al12gamer
Copy link

Are the people here experiencing this using NVIDIA cards? Honestly wondering if this is a recurring theme as it was in #1383

@Jaskowicz1
Copy link

@al12gamer yeah I'm on Nvidia getting the issue 😅 the no-sandbox flag does fix this though.

@al12gamer
Copy link

My friend experiencing the issue has NVIDIA as well. I haven't experienced this on the Intel test bench nor AMD gaming desktop so I'm wondering if there's something to that.

@swapmasterx
Copy link

I'm getting this issue with my deb install. This did fix it

@sageworksstudio
Copy link

Same .deb install issue (with Nvidia graphics), @Cknight70 's suggestion to use the --no-sandbox option worked to get it started.

@candroid-man
Copy link

How do I add the --no-sandbox flag on Fedora on GNOME? I'd like it to run that flag any time I launch the RPM package

@Cknight70
Copy link
Author

@candroid-man

Find your .desktop file in

/usr/share/applications/ or /usr/local/share/applications/ for applications installed system-wide, or ~/.local/share/applications/

Find the "exec" line, and add the --no-sandbox parameter on the same line. So it may look like Exec=r2modman --no-sandbox

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Minor issue
Projects
None yet
Development

No branches or pull requests

7 participants