AnotherRedisDesktopManager icon indicating copy to clipboard operation
AnotherRedisDesktopManager copied to clipboard

Unable to start AppImage on Linux Mint 22

Open lemassykoi opened this issue 8 months ago β€’ 4 comments

after downloading latest version 1.7.1 and making it executable:

chmod +x Another-Redis-Desktop-Manager-linux-1.7.1-x86_64.AppImage

then trying to run:

user@PC:~/Downloads$ ./Another-Redis-Desktop-Manager-linux-1.7.1-x86_64.AppImage 
[11992:0414/214928.476490:FATAL:gpu_data_manager_impl_private.cc(415)] GPU process isn't usable. Goodbye.
Trappe pour point d'arrΓͺt et de trace (core dumped)

I have to add --in-process-gpu for it to start

user@PC:~/Downloads$ ./Another-Redis-Desktop-Manager-linux-1.7.1-x86_64.AppImage --in-process-gpu

lemassykoi avatar Apr 14 '25 20:04 lemassykoi

try this https://github.com/qishibo/AnotherRedisDesktopManager/issues/1161#issuecomment-1955767670

qishibo avatar Apr 15 '25 00:04 qishibo

try this #1161 (comment)

this : sudo sysctl kernel.unprivileged_userns_clone=1 is not working on my system

this: ./Another-Redis-Desktop-Manager.1.5.2.AppImage --no-sandbox is working, as well as --in-process-gpu

lemassykoi avatar Apr 16 '25 11:04 lemassykoi

I'm on Pop!_OS 22.04, and also not able to open Another-Redis-Desktop-Manager.1.6.4.AppImage (nor the latest version as of today). I get this:

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) [54037:0913/114059.961542:FATAL:gpu_data_manager_impl_private.cc(415)] GPU process isn't usable. Goodbye. [appimagelauncher-binfmt-bypass/lib] ERROR: child exited with code 5

I have to include the following flags top make it open:

--disable-gpu \
--disable-software-rasterizer \
--no-sandbox

My system: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz 32GB DDR4 RAM GeForce GTX 1070 8GB GPU

kristjem avatar Sep 13 '25 09:09 kristjem

@kristjem actually you need only --no-sandbox option, or you can write a desktop file(or bash file) to include this option

qishibo avatar Oct 28 '25 02:10 qishibo