Details
Description
When installed from the Installer with nightly builds from June 13, the Climate app fails to launch with the following messages on the console:
[WARN | am.deployment | qml-launcher] Absolute import path in the runtime configuration can lead to problems inside containers (e.g. "/home/vladimir/Qt/5.13.0/gcc_64/neptune3/imports_shared") [launcher-qml.cpp:216] [WARN | qt.qpa.wayland.backingstore | c.t.cluster] Delivering update request through fallback timer, may not be in sync with display [WARN | default | c.p.climate] QQmlApplicationEngine failed to load component [WARN | default | c.p.climate] file:///home/vladimir/development/builds/neptune/apps/com.pelagicore.climate/Main.qml:50 Type ClimateView unavailable file:///home/vladimir/development/builds/neptune/apps/com.pelagicore.climate/views/ClimateView.qml:49 Type ClimateStore unavailable file:///home/vladimir/development/builds/neptune/apps/com.pelagicore.climate/stores/ClimateStore.qml:34 module "QtIvi.VehicleFunctions" is not installed [CRIT | am.system | c.p.climate] could not load "/home/vladimir/development/builds/neptune/apps/com.pelagicore.climate/Main.qml" : no root object
The strange thing is that the paths are pointing to components which located in my local build which I've tested before. Is there a problem with the new persistency ?
Attachments
Issue Links
- relates to
-
AUTOSUITE-1027 VehicleData server does not start on MacOS
-
- Closed
-