Hm, that is wired. The "Emit abort..." is a message which is caused by aborting all image list downloads, which is triggered when an image installation starts. So it seems that Tezi actually starts to autoinstall an image, which triggers the abort of all other image (list) downloads. I wonder why that autoinstall does not make progress. So Tezi is at this point stuck in the main window?
If feels like a race... sometimes if i start manually after it failed with tezi -autoinstall it seems to work (though very rare at this point i cannot get it to work). But if i start without -autoinstall i can select the image and install it and it works.
Full log is this:
Failed to load client buffer integration: wayland-egl
USB Gadget: RNDIS enabled
Trying to read configblock from "mmcblk0boot0" at -512
Running Command: "/usr/bin/avahi-set-host-name" ("colibri-imx6-10615279")
Finished with exit code: 0
avahi-set-host-name:
""
USB Gadget: RNDIS enabled
"AVAHI_CLIENT_S_REGISTERING"
Using the 'xdg-shell' shell integration
Scanning media initially...
Network up in 0.096 seconds
Tezi Server lookup successfully
Downloading image list from "http://tezi.toradex.com/image_list.json"
Downloading image list from "http://tezi.toradex.com/image_list_3rdparty.json"
RNDIS up in 0.594 seconds
"AVAHI_CLIENT_S_RUNNING"
libpng warning: iCCP: known incorrect sRGB profile
"AVAHI_BROWSER_CACHE_EXHAUSTED"
"New service 'Custom Toradex Easy Installer Feed' of type _tezi._tcp in domain local on protocol IPv4."
Adding zeroconf feed "Custom Toradex Easy Installer Feed"
Downloading image list from "http://alap19.local:80/~asac/tezi/image_list.json"
Emit abort...
Emit abort...
Emit abort...
Hm, that is wired. The "Emit abort..." is a message which is caused by aborting all image list downloads, which is triggered when an image installation starts. So it seems that Tezi actually starts to autoinstall an image, which triggers the abort of all other image (list) downloads. I wonder why that autoinstall does not make progress. So Tezi is at this point stuck in the main window?
Yeah see the screenshot. thats how tezi looks like when its in that state...
dev-to-uploads.s3.amazonaws.com/i/...
If feels like a race... sometimes if i start manually after it failed with tezi -autoinstall it seems to work (though very rare at this point i cannot get it to work). But if i start without -autoinstall i can select the image and install it and it works.
Full log is this:
Here the tezi UI when i start it without -autoinstall...
dev-to-uploads.s3.amazonaws.com/i/...