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] - Not working on Ubuntu 22.04 - GPU process isn't usable #735

Open
pkkid opened this issue Mar 2, 2022 · 11 comments
Open

[BUG] - Not working on Ubuntu 22.04 - GPU process isn't usable #735

pkkid opened this issue Mar 2, 2022 · 11 comments
Labels
bug Minor issue

Comments

@pkkid
Copy link

pkkid commented Mar 2, 2022

App is not working on Ubuntu 22.04. We get the error message displayed below. I get the same error trying the AppImage or the deb install. After searching around to see what this means, it sounds like the app needs to be rebuilt with an updated version of Electron.

> r2modman 
(node:5095) electron: The default of contextIsolation is deprecated and will be changing from false to true
in a future release of Electron.  See https://github.com/electron/electron/issues/23506 for more information
starting server on  /tmp/app.r2mm 
starting TLS server false
starting server as Unix || Windows Socket
[5095:0301/193628.615200:FATAL:gpu_data_manager_impl_private.cc(445)] GPU process isn't usable. Goodbye.
Trace/breakpoint trap

UPDATE: In Discord it was mentioned that using the --no-sandbox option on the AppImage gets the app up and running if you are OK running it that way.

@pkkid pkkid added the bug Minor issue label Mar 2, 2022
@Alfenstein8
Copy link

I have exactly the same error message on fedora 35. The --no-sandbox flag also works with the .rpm version.

@MagmaiKH
Copy link

Same on Gentoo and running with --no-sandbox also works around the issue.

@wdw781
Copy link

wdw781 commented Jul 30, 2022

where to use --no-sandbox??

@Alfenstein8
Copy link

where to use --no-sandbox??

In the terminal after the filepath/filename.

@Oman395
Copy link

Oman395 commented Oct 8, 2022

Same issue on arch 5.19.13 and plasma 5.25.5, installed through AUR. Fixed by running r2modman --no-sandbox. To make the app work without terminal, find the .desktop file (usually in /usr/share/applications, usually named r2modman.desktop) and change Exec=env DESKTOPINTEGRATION=false /usr/bin/r2modman to Exec=env DESKTOPINTEGRATION=false /usr/bin/r2modman --no-sandbox.

@jpw1991
Copy link

jpw1991 commented Nov 12, 2023

I use r2modman --in-process-gpu rather than --no-sandbox.

@IsaiahBjornlie
Copy link

how do i use the terminal to launch r2modman? when i try it says command not found

@al12gamer
Copy link

is it working fine in wayland for amd users? My friend saw this in wayland in KDE with an NVIDIA card

@DreamyK9
Copy link

DreamyK9 commented Sep 1, 2024

@IsaiahBjornlie If you're using the AppImage of r2modman, it will likely not be in your path.

You'll either want to open the directory of the AppImage in your terminal and then run it like ./r2modman.AppImage (e.g. by using cd path/to/the/folder).
Or if you're using KDE Plasma, you can also add it to the application launcher, where you can set the argument once and then just start it with one click whenever you want.

I'm not familiar with other desktop envs, but there should be lots of resources on the internet about that kind of stuff.

@DreamyK9
Copy link

DreamyK9 commented Sep 1, 2024

@al12gamer It's working fine in wayland with KDE and NVIDIA Card for me, using --in-process-gpu. If it doesn't work with AMD, then I guess there's a different issue between r2modman and the AMD driver.
Not a pro tho, just guessing.

@al12gamer
Copy link

@DreamyK9 it's worked fine for me on AMD

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

9 participants