pnnl / GLIMPSE

GLIMPSE is a graph-based web application to visualize and update distribution power grid models.
Other
15 stars 2 forks source link

Error running on WSL Ubuntu 24.04.1 #2

Open nathantgray opened 1 month ago

nathantgray commented 1 month ago

After following the installation instructions using WSL Ubuntu 24.04.1. I receive the following error in the terminal. Additionally a GUI window pops up notifying that there was an uncaught exception. The splash screen remains open until the process is canceled with ctr-c.

~/git/GLIMPSE/glimpse$ npm run start

> glimpse@0.4.0 start
> electron-forge start

✔ Checking your system
✔ Locating application
✔ Loading configuration
✔ Preparing native dependencies [1s]
✔ Running generateAssets hook

WARNING: dzn is not a conformant Vulkan implementation, testing use only.
WARNING: dzn is not a conformant Vulkan implementation, testing use only.
WARNING: Some incorrect rendering might occur because the selected Vulkan device (Microsoft Direct3D12 (Intel(R) Iris(R) Xe Graphics)) doesn't support base Zink requirements: feats.features.logicOp have_EXT_custom_border_color have_EXT_line_rasterization
[1039760:1024/124200.080372:ERROR:object_proxy.cc(590)] Failed to call method: org.freedesktop.DBus.StartServiceByName: object_path= /org/freedesktop/DBus: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
[1039760:1024/124225.086556:ERROR:object_proxy.cc(590)] Failed to call method: org.freedesktop.portal.Settings.Read: object_path= /org/freedesktop/portal/desktop: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
itsMando commented 1 month ago

Hi @nathantgray thanks for bringing this issue up. Before doing npm run start did you have the python environment created and activated ?