Testers required for OpenViX Python 3 images

[abu baniaz]

Or you can list updates then force an update of the packages

[Joe_90]

Yes. I assume every version has had updates.

However latterly (while I was still using 5.5.015.003) if I went to Menu / Information / About / Software Update
it always said there were updates available and if I installed them, rebooted and looked again it said the same updates are still available.

That was confusing me Brian. When I got update announcements for the py3 branch they always updated ok for me. I think you had additional software which broke the update process.

[twol]

I have a NAS on the network which the box has a mount to. Can I flash an image from this across the network? I think I’ve tried doing image backups from the box to NAS previously which didn’t work.

I have a couple of Synology NAS boxes. If I automount a folder and then go to ImageManager, press Menu button and select the automount then Save, I can both store backups and download an image to flash using this mount

[carpcat]

I have a couple of Synology NAS boxes. If I automount a folder and then go to ImageManager, press Menu button and select the automount then Save, I can both store backups and download an image to flash using this mount

Thanks for confirming. Just tried myself and I can create a settings backup that’s sent to the Synology NAS, and also an image backup, that hasn’t worked for me before, but did this time. So that’s great. However when I try to flash this image back to the box from the NAS, it crashes with ‘error flashing kernel’ and reboots. I’ve attached the debug log which shows the start of the image flash at the end of the log before it rebooted, and the crash log to see if this helps understand what’s going on. It states the image file is not found but it’s definitely there as the box created and put it there!

[twol]

Thanks for confirming. Just tried myself and I can create a settings backup that’s sent to the Synology NAS, and also an image backup, that hasn’t worked for me before, but did this time. So that’s great. However when I try to flash this image back to the box from the NAS, it crashes with ‘error flashing kernel’ and reboots. I’ve attached the debug log which shows the start of the image flash at the end of the log before it rebooted, and the crash log to see if this helps understand what’s going on. It states the image file is not found but it’s definitely there as the box created and put it there!

Interesting! I will check tomorrow but I think its a Vu+ issue.
So ofgwrite completed. (Or you get loads of debug)
With Vu+ ofgwrite doesn‘t return gracefully to ImageManager but kills the system, so probably the network is disconnected by the time this check is made.
I will check on a multiboot boxes tomorrow, but if OK maybe I can do something for Vu+

[twol]

Thanks for confirming. Just tried myself and I can create a settings backup that’s sent to the Synology NAS, and also an image backup, that hasn’t worked for me before, but did this time. So that’s great. However when I try to flash this image back to the box from the NAS, it crashes with ‘error flashing kernel’ and reboots. I’ve attached the debug log which shows the start of the image flash at the end of the log before it rebooted, and the crash log to see if this helps understand what’s going on. It states the image file is not found but it’s definitely there as the box created and put it there!

So Yes, Vu+ issue.
Try copying the attachment to /usr/lib/enigma2/python/Plugins/SystemPlugins/ViX and reboot.

[carpcat]

So Yes, Vu+ issue.
Try copying the attachment to /usr/lib/enigma2/python/Plugins/SystemPlugins/ViX and reboot.

Tried the new file but still the same ‘error flashing kernel’ and then a reboot, although no crash logs created this time. Extract from debug log below

< 180.0816> [Console] command: unzip -o /media/autofs/videoDISKSTATION/imagebackups/openvix-vuzero4k-Py3-5.5.016.001-20211007_164423.zip -d /media/autofs/videoDISKSTATION/imagebackups/imagerestore
< 180.0817> [eConsoleAppContainer] Starting /bin/sh
< 223.6662> [AutoTimer] current auto poll 2021-10-08 20:20:42
< 223.6664> [AutoTimer] Auto Poll Started
< 223.6694> [Task] job Components.Task.Job name=AutoTimer #tasks=0 completed with [] in None
< 223.6700> [AutoTimer] next auto poll at 2021-10-08 20:50:42
< 314.8326> [Console] finished: unzip -o /media/autofs/videoDISKSTATION/imagebackups/openvix-vuzero4k-Py3-5.5.016.001-20211007_164423.zip -d /media/autofs/videoDISKSTATION/imagebackups/imagerestore
< 314.8371> [Skin] Processing screen 'MessageBox', position=(0, 0), size=(1920 x 1080) for module 'MessageBox'.
< 314.8540> [Screen] Warning: Skin is missing element 'icon' in <class 'Screens.MessageBox.MessageBox'>(Flash image unzip successful.).
< 314.8554> [Skin] Attribute 'scrollbarMode' (with value of 'showOnDemand') in object of type 'eLabel' is not implemented!
< 314.8674> [Pixmap] setPixmapNum(1) failed! defined pixmaps: []
< 314.8684> [MessageBox] Timeout set to 4 seconds.
< 314.8692> [Skin] Parsing embedded skin '<embedded-in-ScreenSummary>'.
< 314.8700> [Skin] Processing screen '<embedded-in-ScreenSummary>' from list 'MessageBoxSummary, ScreenSummary, MessageBox_summary, SimpleSummary', position=(0, 0), size=(132 x 64) for module 'ScreenSummary'.
< 314.8717> [eWindowStyleManager] getStyle(style_id=1): NOT FOUND
< 314.9182> [ImageManager] running commnd: /usr/bin/ofgwrite -r -k '/media/autofs/videoDISKSTATION/imagebackups/imagerestore/vuplus/zero4k'
< 314.9189> [Console] command: /usr/bin/ofgwrite -r -k '/media/autofs/videoDISKSTATION/imagebackups/imagerestore/vuplus/zero4k'
< 314.9194> [eConsoleAppContainer] Starting /bin/sh
< 318.1536> [InputHotplug] connectionLost? [Failure instance: Traceback (failure with no frames): <class 'twisted.internet.error.ConnectionLost'>: Connection to the other side was lost in a non-clean fashion: Connection lost.
]< 318.1537>

[twol]

Tried the new file but still the same ‘error flashing kernel’ and then a reboot, although no crash logs created this time. Extract from debug log below

Be interesting to see whats in this folder imagebackups/imagerestore/vuplus/zero4k'

[carpcat]

Be interesting to see whats in this folder imagebackups/imagerestore/vuplus/zero4k'

The image file ‘ openvix-vuzero4k-Py3-5.5.016.001-20211007_164423.zip ’ is located directly in the imagebackups folder. There is no other folders as per stated in the log

[birdman]

Tried the new file but still the same ‘error flashing kernel’ and then a reboot, although no crash logs created this time. Extract from debug log below

< 314.9189> [Console] command: /usr/bin/ofgwrite -r -k '/media/autofs/videoDISKSTATION/imagebackups/imagerestore/vuplus/zero4k'

That's interesting.

On my system (an MBTwin) an in-memory /newroot file-system is set-up, ofgwrite is copied to there then that is used. Why is this different?

[birdman]

With Vu+ ofgwrite doesn‘t return gracefully to ImageManager but kills the system, so probably the network is disconnected by the time this check is made.

ofgwrite has just flashed the system. There is no "ImageManager" to return to (which is why enigma2 is shutdown as ofgwrite starts).
Unless a Vu+ is somehow wildly different.

[twol]

ofgwrite has just flashed the system. There is no "ImageManager" to return to (which is why enigma2 is shutdown as ofgwrite starts).
Unless a Vu+ is somehow wildly different.

On multiboot boxes, ofgwrite returns to ImageManager, where the return code is checked and the STARTUP files are manipulated before rebooting. In ATV they actually allow the user to decide what to do after flashing, continue running or reboot etc).
On Vu+ boxes, ofgwrite does not return, but kills the system - which is why I was surprised that some ImageManager code still ran (see #814). I put in a Try/Except to gracefully handle the crash in ImageManager - and I am guessing it happens because of an ofgwrite error(kernel error) - and the /newroot mount is retained (which can lead to other issues)
I forgot that ImageManager on a restart cleans up the Imagerestore folder (so its no longer there to see whats in the folder - my ImageManager doesn‘t cleanup) - as I would really like to understand why we get a kernel error with Vu+. I will have to power up my Xtrend and see what I can do, as its not an issue with multiboot boxes running from a NAS.

[dsayers]

I'm not sure what plugin these depend on but I'm getting stuck on software update

root@vuuno4k:~# opkg list-upgradable
Not selecting libgstrtsp-1.0-0 1.18.5+git20610+57fb883 as installing it would break existing dependencies.
Not selecting libgsturidownloader-1.0-0 1.18.5+git26379+d3af58d as installing it would break existing dependencies.
Not selecting libgstsdp-1.0-0 1.18.5+git20610+57fb883 as installing it would break existing dependencies.
Not selecting libgsttag-1.0-0 1.18.5+git20610+57fb883 as installing it would break existing dependencies.
Not selecting gstreamer1.0 1.18.5+git19084+71c213f as installing it would break existing dependencies.
Not selecting libgstadaptivedemux-1.0-0 1.18.5+git26379+d3af58d as installing it would break existing dependencies.
Not selecting libgstcodecparsers-1.0-0 1.18.5+git26379+d3af58d as installing it would break existing dependencies.
Not selecting libgstisoff-1.0-0 1.18.5+git26379+d3af58d as installing it would break existing dependencies.
Not selecting libgstriff-1.0-0 1.18.5+git20610+57fb883 as installing it would break existing dependencies.
Not selecting libgstvideo-1.0-0 1.18.5+git20610+57fb883 as installing it would break existing dependencies.
Not selecting libgstpbutils-1.0-0 1.18.5+git20610+57fb883 as installing it would break existing dependencies.
Not selecting libgstrtp-1.0-0 1.18.5+git20610+57fb883 as installing it would break existing dependencies.
Not selecting libgstaudio-1.0-0 1.18.5+git20610+57fb883 as installing it would break existing dependencies.
Not selecting libgstmpegts-1.0-0 1.18.5+git26379+d3af58d as installing it would break existing dependencies.
Not selecting libgstapp-1.0-0 1.18.5+git20610+57fb883 as installing it would break existing dependencies.
Not selecting libx264-164 r2970+git0+66a5bc1bd1 as installing it would break existing dependencies.
root@vuuno4k:~#

[Huevos]

I'm not sure what plugin these depend on but I'm getting stuck on software update

root@vuuno4k:~# opkg list-upgradable
Not selecting libgstrtsp-1.0-0 1.18.5+git20610+57fb883 as installing it would break existing dependencies.
Not selecting libgsturidownloader-1.0-0 1.18.5+git26379+d3af58d as installing it would break existing dependencies.
Not selecting libgstsdp-1.0-0 1.18.5+git20610+57fb883 as installing it would break existing dependencies.
Not selecting libgsttag-1.0-0 1.18.5+git20610+57fb883 as installing it would break existing dependencies.
Not selecting gstreamer1.0 1.18.5+git19084+71c213f as installing it would break existing dependencies.
Not selecting libgstadaptivedemux-1.0-0 1.18.5+git26379+d3af58d as installing it would break existing dependencies.
Not selecting libgstcodecparsers-1.0-0 1.18.5+git26379+d3af58d as installing it would break existing dependencies.
Not selecting libgstisoff-1.0-0 1.18.5+git26379+d3af58d as installing it would break existing dependencies.
Not selecting libgstriff-1.0-0 1.18.5+git20610+57fb883 as installing it would break existing dependencies.
Not selecting libgstvideo-1.0-0 1.18.5+git20610+57fb883 as installing it would break existing dependencies.
Not selecting libgstpbutils-1.0-0 1.18.5+git20610+57fb883 as installing it would break existing dependencies.
Not selecting libgstrtp-1.0-0 1.18.5+git20610+57fb883 as installing it would break existing dependencies.
Not selecting libgstaudio-1.0-0 1.18.5+git20610+57fb883 as installing it would break existing dependencies.
Not selecting libgstmpegts-1.0-0 1.18.5+git26379+d3af58d as installing it would break existing dependencies.
Not selecting libgstapp-1.0-0 1.18.5+git20610+57fb883 as installing it would break existing dependencies.
Not selecting libx264-164 r2970+git0+66a5bc1bd1 as installing it would break existing dependencies.
root@vuuno4k:~#

Reflash .

[BrokenUnusableAccount]

SAMBA seems to be messed up again in 5.5.016.001 on my Zgemma H7.

I noticed nmbd wasn't running (I could only access by IP address not by name) so I tried to remove and re-install samba to fix it but once it was removed the option to re-install it just wasn't even there to try it.


I think there's probably nothing useful int he log files but here they are anyway:
Attachment 62684
Attachment 62685
Attachment 62686