Open mfurqanliaqat opened 6 months ago
➤ PM Bot commented:
Jira ticket: RSTUDIO-535
Hi, Same for me except I don't get the same message:
Warning: /usr/lib/i386-linux-gnu/libvulkan_virtio.so: mauvaise classe ELF : ELFCLASS32
Warning: loader_icd_scan: Failed loading library associated with ICD JSON /usr/lib/i386-linux-gnu/libvulkan_virtio.so. Ignoring this JSON
Warning: /usr/lib/i386-linux-gnu/libvulkan_intel.so: mauvaise classe ELF : ELFCLASS32
Warning: loader_icd_scan: Failed loading library associated with ICD JSON /usr/lib/i386-linux-gnu/libvulkan_intel.so. Ignoring this JSON
Warning: /usr/lib/i386-linux-gnu/libvulkan_radeon.so: mauvaise classe ELF : ELFCLASS32
Warning: loader_icd_scan: Failed loading library associated with ICD JSON /usr/lib/i386-linux-gnu/libvulkan_radeon.so. Ignoring this JSON
Warning: /usr/lib/i386-linux-gnu/libvulkan_intel_hasvk.so: mauvaise classe ELF : ELFCLASS32
Warning: loader_icd_scan: Failed loading library associated with ICD JSON /usr/lib/i386-linux-gnu/libvulkan_intel_hasvk.so. Ignoring this JSON
Warning: loader_scanned_icd_add: Could not get 'vkCreateInstance' via 'vk_icdGetInstanceProcAddr' for ICD libGLX_nvidia.so.0
Warning: /usr/lib/i386-linux-gnu/libvulkan_lvp.so: mauvaise classe ELF : ELFCLASS32
Warning: loader_icd_scan: Failed loading library associated with ICD JSON /usr/lib/i386-linux-gnu/libvulkan_lvp.so. Ignoring this JSON
Warning: terminator_CreateInstance: Failed to CreateInstance in ICD 2. Skipping ICD
current libvulkan installed:
libvulkan-dev/jammy,now 1.3.204.1-2 amd64 [installé, automatique]
Vulkan loader library -- development files
libvulkan1/jammy,now 1.3.204.1-2 amd64 [installé, automatique]
Vulkan loader library
I've tested under Wayland and Xorg and it doesn't work in both cases.
best regards, Nobur
I have the same issue (Fedora 40). Trying to open Realm studio just hangs forever (terminal)
Same issue for me. Later I tried running it on a fresh Ubuntu 24.04 install and it doesn't work there either, this time with a sandbox error. After working around that issue it hangs indefinitely on launch like before.
I opened a ticket last month at the MongoDB Development Community forum and didn't receive a response yet.
After seeing a variety of issues across multiple releases and OS versions I suspect their release process doesn't include verifying that it opens on all target platforms. I'd be curious if anyone has been successful in running a recent realm-studio in any Linux environment.
@realm-support : I'd be happy to run tests to assist with troubleshooting, as this tool is critical for my work.
Sorry for the late reply.
@mblaughton Your ticket has some similarities with https://issues.chromium.org/issues/41486604 - but it doesn't provide a solution
@mfurqanliaqat @nobur @dannyglover Does this trick work for you?
Sorry for the late reply.
@mblaughton Your ticket has some similarities with https://issues.chromium.org/issues/41486604 - but it doesn't provide a solution
@mfurqanliaqat @nobur @dannyglover Does this trick work for you?
Hi. I had a look through that issue and if I read it correctly, every user there had multiple GPUs (iGPU + dedicated or multiple dedicated).
I only have a single GPU with no iGPU. Specs:
For what it's worth: (ran without sudo):
vulkaninfo --summary
==========
VULKANINFO
==========
Vulkan Instance Version: 1.3.280
Instance Extensions: count = 23
-------------------------------
VK_EXT_acquire_drm_display : extension revision 1
VK_EXT_acquire_xlib_display : extension revision 1
VK_EXT_debug_report : extension revision 10
VK_EXT_debug_utils : extension revision 2
VK_EXT_direct_mode_display : extension revision 1
VK_EXT_display_surface_counter : extension revision 1
VK_EXT_surface_maintenance1 : extension revision 1
VK_EXT_swapchain_colorspace : extension revision 4
VK_KHR_device_group_creation : extension revision 1
VK_KHR_display : extension revision 23
VK_KHR_external_fence_capabilities : extension revision 1
VK_KHR_external_memory_capabilities : extension revision 1
VK_KHR_external_semaphore_capabilities : extension revision 1
VK_KHR_get_display_properties2 : extension revision 1
VK_KHR_get_physical_device_properties2 : extension revision 2
VK_KHR_get_surface_capabilities2 : extension revision 1
VK_KHR_portability_enumeration : extension revision 1
VK_KHR_surface : extension revision 25
VK_KHR_surface_protected_capabilities : extension revision 1
VK_KHR_wayland_surface : extension revision 6
VK_KHR_xcb_surface : extension revision 6
VK_KHR_xlib_surface : extension revision 6
VK_LUNARG_direct_driver_loading : extension revision 1
Instance Layers: count = 11
---------------------------
VK_LAYER_FROG_gamescope_wsi_x86_64 Gamescope WSI (XWayland Bypass) Layer (x86_64) 1.3.221 version 1
VK_LAYER_MANGOAPP_overlay Mangoapp Layer 1.3.0 version 1
VK_LAYER_MANGOAPP_overlay Mangoapp Layer 1.3.0 version 1
VK_LAYER_MANGOHUD_overlay_x86 Vulkan Hud Overlay 1.3.0 version 1
VK_LAYER_MANGOHUD_overlay_x86_64 Vulkan Hud Overlay 1.3.0 version 1
VK_LAYER_MESA_device_select Linux device selection layer 1.3.211 version 1
VK_LAYER_VALVE_steam_fossilize_32 Steam Pipeline Caching Layer 1.3.207 version 1
VK_LAYER_VALVE_steam_fossilize_64 Steam Pipeline Caching Layer 1.3.207 version 1
VK_LAYER_VALVE_steam_overlay_32 Steam Overlay Layer 1.3.207 version 1
VK_LAYER_VALVE_steam_overlay_64 Steam Overlay Layer 1.3.207 version 1
VK_LAYER_VKBASALT_post_processing a post processing layer 1.3.223 version 1
Devices:
========
GPU0:
apiVersion = 1.3.274
driverVersion = 24.0.7
vendorID = 0x1002
deviceID = 0x73a5
deviceType = PHYSICAL_DEVICE_TYPE_DISCRETE_GPU
deviceName = AMD Radeon RX 6950 XT (RADV NAVI21)
driverID = DRIVER_ID_MESA_RADV
driverName = radv
driverInfo = Mesa 24.0.7
conformanceVersion = 1.3.0.0
deviceUUID = 00000000-2d00-0000-0000-000000000000
driverUUID = 414d442d-4d45-5341-2d44-525600000000
GPU1:
apiVersion = 1.3.274
driverVersion = 0.0.1
vendorID = 0x10005
deviceID = 0x0000
deviceType = PHYSICAL_DEVICE_TYPE_CPU
deviceName = llvmpipe (LLVM 18.1.1, 256 bits)
driverID = DRIVER_ID_MESA_LLVMPIPE
driverName = llvmpipe
driverInfo = Mesa 24.0.7 (LLVM 18.1.1)
conformanceVersion = 1.3.1.1
deviceUUID = 6d657361-3234-2e30-2e37-000000000000
driverUUID = 6c6c766d-7069-7065-5555-494400000000
Sorry for the late reply.
@mblaughton Your ticket has some similarities with https://issues.chromium.org/issues/41486604 - but it doesn't provide a solution
@mfurqanliaqat @nobur @dannyglover Does this trick work for you?
I looked at it earlier, but it doesn't seem to work in my case as Vulkan seems to work fine in my case. I tried updating and everything goes smooth. I am using v14 for now not facing any issues with that!
Same issue here. Fedora 39 on Haswell i7-4770S, no external GPU. I don't see any errors specific to this; I get the following:
MESA-INTEL: warning: Haswell Vulkan support is incomplete
libva error: /usr/lib64/dri/iHD_drv_video.so init failed
failed to open /usr/lib64/dri/hybrid_drv_video.so
Not using hybrid_drv_video.so
but this is the same in previous versions, which load fine. Version 15+ just hangs.
Same here, for both 15.0.0 and 15.0.1 versions hangs and it does not start, but 14 versions work fine.
OS: Pop!_OS 22.04 LTS x86_64
Host: 82DJ Lenovo IdeaPad S145-15IIL
Kernel: 6.8.0-76060800daily20240311-generic
Shell: bash 5.1.16
DE: GNOME 42.9
Terminal: gnome-terminal
Similar problem on Manjaro 24.0 KDE Plasma 6 Wayland or X11. the following executions hang with no error, nothing happens.
./realm-studio
./Realm.Studio-15.0.1.AppImage
versions 15 and 14 are the same.
Sorry for the late reply.
@mblaughton Your ticket has some similarities with https://issues.chromium.org/issues/41486604 - but it doesn't provide a solution
@mfurqanliaqat @nobur @dannyglover Does this trick work for you?
Hi, Sorry for the late answer.
nope, it doesn't solve the issue.
in case this is helpful :
nobur@nobur-Laptop:~/Documents$ vulkaninfo --summary
ERROR: [Loader Message] Code 0 : loader_scanned_icd_add: Could not get 'vkCreateInstance' via 'vk_icdGetInstanceProcAddr' for ICD libGLX_nvidia.so.0
WARNING: [Loader Message] Code 0 : terminator_CreateInstance: Failed to CreateInstance in ICD 2. Skipping ICD.
==========
VULKANINFO
==========
Vulkan Instance Version: 1.3.204
Instance Extensions: count = 20
-------------------------------
VK_EXT_acquire_drm_display : extension revision 1
VK_EXT_acquire_xlib_display : extension revision 1
VK_EXT_debug_report : extension revision 10
VK_EXT_debug_utils : extension revision 2
VK_EXT_direct_mode_display : extension revision 1
VK_EXT_display_surface_counter : extension revision 1
VK_EXT_swapchain_colorspace : extension revision 4
VK_KHR_device_group_creation : extension revision 1
VK_KHR_display : extension revision 23
VK_KHR_external_fence_capabilities : extension revision 1
VK_KHR_external_memory_capabilities : extension revision 1
VK_KHR_external_semaphore_capabilities : extension revision 1
VK_KHR_get_display_properties2 : extension revision 1
VK_KHR_get_physical_device_properties2 : extension revision 2
VK_KHR_get_surface_capabilities2 : extension revision 1
VK_KHR_surface : extension revision 25
VK_KHR_surface_protected_capabilities : extension revision 1
VK_KHR_wayland_surface : extension revision 6
VK_KHR_xcb_surface : extension revision 6
VK_KHR_xlib_surface : extension revision 6
Instance Layers: count = 4
--------------------------
VK_LAYER_INTEL_nullhw INTEL NULL HW 1.1.73 version 1
VK_LAYER_MESA_device_select Linux device selection layer 1.3.211 version 1
VK_LAYER_MESA_overlay Mesa Overlay layer 1.3.211 version 1
VK_LAYER_NV_optimus NVIDIA Optimus layer 1.3.242 version 1
Devices:
========
GPU0:
apiVersion = 4206847 (1.3.255)
driverVersion = 96477185 (0x5c02001)
vendorID = 0x8086
deviceID = 0x9bc4
deviceType = PHYSICAL_DEVICE_TYPE_INTEGRATED_GPU
deviceName = Intel(R) UHD Graphics (CML GT2)
driverID = DRIVER_ID_INTEL_OPEN_SOURCE_MESA
driverName = Intel open-source Mesa driver
driverInfo = Mesa 23.2.1-1ubuntu3.1~22.04.2
conformanceVersion = 1.3.6.0
deviceUUID = 8680c49b-0500-0000-0002-000000000000
driverUUID = dc0c24af-21a0-4d95-8772-878c52e18bee
GPU1:
apiVersion = 4206847 (1.3.255)
driverVersion = 1 (0x0001)
vendorID = 0x10005
deviceID = 0x0000
deviceType = PHYSICAL_DEVICE_TYPE_CPU
deviceName = llvmpipe (LLVM 15.0.7, 256 bits)
driverID = DRIVER_ID_MESA_LLVMPIPE
driverName = llvmpipe
driverInfo = Mesa 23.2.1-1ubuntu3.1~22.04.2 (LLVM 15.0.7)
conformanceVersion = 1.3.1.1
deviceUUID = 6d657361-3233-2e32-2e31-2d3175627500
driverUUID = 6c6c766d-7069-7065-5555-494400000000
Any progress on this issue? I have the same problem on Ubuntu 20.04.
Hi, I recently update to 24.04 LTS and the issue is still there.
got also another error ("The SUID sandbox helper binary was found, but is not configured correctly") forcing me to run it with --no-sandbox option but its surely linked to my installation.
regards
Same issue. I am using Ubutun 24.04
Realm Studio 15.2.1 Ubuntu 24.04
Me too!
It's been a while since the last "me too" reply arrived. Did someone find a fix or did we all just switch to using Windows or MacOS for Realm Studio tasks?
It would be a shame to give up hope on the Linux version but if Windows/MacOS "just works" then I might have no choice but to dual boot.
Still a "Me Too!"...
My understanding from reading other threads is that it is an upstream issue w/ Electron and certain video drivers. I can't find the link I used a while back but it involved using a command-line option to disable GPU support. I tried that with Realm Studio but it wasn't a recognized option so I stopped trying. I run Realm Studio on my Mac now. Not super useful when most of my development is on my Ubuntu box.
We can reproduce it on Mint Linux (v14 works, v15 doesn't). We need to investigate it.
Same issue. I'm using Garuda Linux.
Same issue with Pop!_os 22.04.
Having the same issue here on Linux Mint 21.3 (Ubuntu 22.04), but for anyone passing by: the latest version (15.2.1) for Windows works fine under Wine (only tried with 9.16 Staging but Stable and older Wine versions should be fine).
same, void linux
Describe the bug Realm Studio 15.0.0 or 15.0.1, do not display anything, (window doesn't appear) and no error on console as well. v14 works well but it cannot work with database of version 24. I have tried both, AppImage as well as tar.gz file both have same behaviour. Process is stuck without an error.
Expected behavior Display Realm Studio UI Window
Versions:
Additional context After a few seconds this appears on terminal
I have checked my display drivers everything is up to date and working fine without issues. Also, version 14.1.2 is working fine without issues. only problem why i have to use v15 is because v24 database support.