Could not prepare runtime resources

[JMattChiam]

Hi LVGL team,
This is for version LVGL Pro Editor version 1.1.2, continuing from #307, apologies for not following up on it earlier before it was closed.

I am still encountering the same issue where LVGL could not load the preview. I am running the 1_hello_world tutorial.

Console:

Failed to read binary file.
Failed to prefetch WASM: Error: Error invoking remote method 'read-binary-file': Error: ENOENT: no such file or directory, open 'C:\Users\xxx \Documents\LVGL Editor\lvgl_editor\tutorials\1_hello_world\preview-bin\lved-runtime.wasm'
Failed to read file C:\Users\xxx \Documents\LVGL Editor\lvgl_editor\tutorials\1_hello_world\preview-bin\lved-runtime.js.
Failed to read runtime script: Error: Error invoking remote method 'read-file': Error: ENOENT: no such file or directory, open 'C:\Users\xxx \Documents\LVGL Editor\lvgl_editor\tutorials\1_hello_world\preview-bin\lved-runtime.js'
Could not load Preview: Could not prepare runtime resources. Perhaps the runtime is not currently available?

Nothing happens when I select "Clean and Build UI Project" - nothing on the console. Additionally, the hammer build icon on the preview panel is greyed out.

Thank you for your help in advance!

[laszlobalint]

@JMattChiam, please, download and install the latest release, and try again. If the issue is still persisted, please, share your environment and some screen shots, so we can investigate.

[JMattChiam]

Hi @laszlobalint
Thanks for the reply
I'm trying now on the latest nightly build of 1.1.2

I am running on Windows 11 Enterprise 23H2, with WSL Ubuntu installed

wsl --version
  WSL version: 2.6.3.0
  Kernel version: 6.6.87.2-1
  WSLg version: 1.0.71
  MSRDC version: 1.2.6353
  Direct3D version: 1.611.1-81528511
  DXCore version: 10.0.26100.1-240331-1435.ge-release
  Windows version: 10.0.22631.6783

wsl --status
  Default Distribution: Ubuntu
  Default Version: 2

I had some issues installing WSL on my device, probably due to security permissions.

I tried running LVGL Editor as admin, and it is able to start the virtual machine and begin the build process which is an improvement from before. However, it still fails and the runtime preview still does not work.

lvgl_editor_admin_build_log_1.txt - Tail end of the console after "clean user data cache" then "clean and build UI project"

lvgl_editor_admin_build_log.txt - Output on console after building, but without cleaning data cache

[JMattChiam]

I've managed to try the editor out on my personal Linux and Windows 11 machines and it works on both.
I believe this would have to do with some inherent security permissions with WSL on the enterprise machine.

When running LVGL Editor as admin, the build process seems to work but fails with emscripten. I'm wondering if this may be an issue with the container image.

I have noticed that uninstalling and reinstalling LVGL Editor, the message "Pulling Container image for LVGL, this may take a few minutes..." never displays. Even after deregistering and reinstalling Ubuntu from WSL, then reinstalling LVGL Editor as admin.

Would there be a way to verify/ check if the container was pulled and is functional? Or alternatively, a way to remove it and reinstall?

[mrhubbs]

@JMattChiam I'm sorry for the difficulties. Yes, you can check on the container using standard Podman CLI. You aren't getting the message again because the container is not cleared / reset on uninstall (which isn't great).

We are actually about to release a new version which lets you install and use Emscripten locally. We've found it to be very stable and it solves a ton of issues by not requiring Podman at all. I hope you'll give it a try. We'll keep you posted!

[JMattChiam]

Hi @mrhubbs
Great to hear on the newer version.

Regarding the podman container. I'd never installed podman on my machine - following the official Windows LVGL editor instructions, I only installed WSL.

Looking at the console logs, it says that Podman is indeed running the virtual machine. How is the editor running the podman container without it being installed by the user? And how would I check on the container in that case?

[mrhubbs]

Ah, right. The Podman executables are bundled with the Editor, only for Windows (not on Mac or Linux).

You should find the Podman executables in your user's home directory under AppData\Roaming\lvgl-editor\internal-bin. You can run podman.exe from there. For example:

podman.exe container list
podman.exe container rm ID
etc.

[JMattChiam]

Hi @mrhubbs
I think I've figured it out. I've managed to get the preview running locally so things are working now.

• My Podman virtual machine provider was defaulting to Hyper-V (visible via podman machine info)
• Hyper-V requires admin permissions, which is why running LVGL Editor as a normal user failed to start the VM
• Running LVGL Editor as admin fixes the VM startup, but the container then mounts file paths under the admin user profile instead of the logged-in user's so it can't find some of the resources

The fix was to manually switch the podman virtualization provider to WSL, which doesn't require the admin rights to run:

1. In a normal (non-admin) PowerShell, set the provider:

$env:CONTAINERS_MACHINE_PROVIDER="wsl"

2. Restart PowerShell in admin mode, then remove any existing Hyper-V machine using

.\podman.exe machine rm 

3. Re-initialize from a normal user PowerShell:

.\podman.exe machine init
.\podman.exe machine start

4. Subsequently, launching the Editor as a normal user pulls the container image and things build/ preview correctly.

[mrhubbs]

Thanks so much for sharing this!

The Editor is able to set environment variables when it invokes Podman. Probably it would be best for it to specify CONTAINERS_MACHINE_PROVIDER="wsl"?

[JMattChiam]

That sounds like reasonable fix, though I'm not sure why I didn't encounter the error on my other machines. I'm not very familiar with Podman.

What about having users install Podman themselves? Why only bundle podman for the Windows version and not the Linux and Mac versions?