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] - Application won't launch on Debian Bookworm without passing '--no-sandbox' or '--in-process-gpu' arguments #1258

Open
Jimmajones opened this issue Mar 10, 2024 · 2 comments
Labels
bug Minor issue

Comments

@Jimmajones
Copy link

Describe the bug
r2modman will immediately crash when starting on Debian Bookworm. Seems to start fine if either --no-sandbox or --in-process-gpu are passed as arguments.

To Reproduce
Steps to reproduce the behavior:

  1. Attempt to start r2modman. Empty window will briefly show up, then disappear.

Expected behavior
Expected r2modman to start.

Additional context
Output:

$ ./r2modman-3.1.47.AppImage
xdg-settings: default-url-scheme-handler not implemented for xfce
starting server on  /tmp/app.r2mm 
starting TLS server false
starting server as Unix || Windows Socket
[26290:0310/115649.567725:FATAL:gpu_data_manager_impl_private.cc(445)] GPU process isn't usable. Goodbye.
Trace/breakpoint trap

Seems to be some sort of Electron issue. See Automattic/simplenote-electron#3096

@Jimmajones Jimmajones added the bug Minor issue label Mar 10, 2024
@Reonu
Copy link

Reonu commented Apr 12, 2024

Launching it with the --no-sandbox launch argument works as a workaround. I just edited the shortcut.

@doonv
Copy link

doonv commented May 10, 2024

This happened to me on Kubuntu, and it continues to happen to me after installing Arch Linux.

Thankfully --no-sandbox does fix it on both OSes.

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

3 participants