GigaBlue UHD 4K - Unable to flash newer image using image manager

[Arcy]

Since graduating to v.6.7.11 on my GigaBlue UHD 4K many months ago, I've been unable to update to any subsequent versions, or even to other images previously loaded into the flash memory. The installation process exits with an error log like the one attached. In v.6.7.11, the receiver works normally without any other signs of distress. Where have I gone wrong?

 

[Huevos]

We are really sorry. Your receiver encountered a software problem, and needs to be restarted.
Please send the logfile /home/root/logs/Enigma2_crash_2025-09-23_10-59-59.log to the OpenViX forum
Your STB restarts in 10 seconds!
Component: Enigma2
< 577.318290> 10:59:54.8001 [MultiPixmap] setPixmapNum(1) failed! defined pixmaps: []
< 577.318616> 10:59:54.8004 [MessageBox] Timeout set to 240 seconds.
< 577.319697> 10:59:54.8015 [Skin] Processing screen 'MessageBoxSummary' from list 'MessageBoxSummary, ScreenSummary', position=(0, 0), size=(400 x 240) for module 'ScreenSummary'
< 577.324533> 10:59:54.8064 [Console] command; unzip -o /media/hdd/imagebackups/openvix-6.7.019.release-gbquad4k_usb.zip -d /media/hdd/imagebackups/imagerestore
< 577.324637> 10:59:54.8065 [eConsoleAppContainer] Starting /bin/sh
< 577.813778> 10:59:55.2956 [Task] job Components. Task.Job name=AutoTimer #tasks=2 completed with [] in None
< 582.037718> 10:59:59.5196 [Console] finished, unzip -o /media/hdd/imagebackups/openvix-6.7.019.release-gbquad4k_usb.zip -d /media/hdd/imagebackups/imagerestore
< 582.040272> 10:59:59.5221 [Skin] Processing screen 'MessageBox', position=(0, 0), size=(1920 x 1080) for module 'MessageBox'.
< 582.048816> 10:59:59.5306 [Screen] Warning: Skin is missing element "icon" in <class 'Screens.MessageBox.MessageBox'>(Flash image unzip successful.).
< 582.050609> 10:59:59.5324 [MultiPixmap] setPixmapNum(1) failed! defined pixmaps: []
< 582.050896> 10:59:59.5327 [MessageBox] Timeout set to 4 seconds.
< 582.051560> 10:59:59.5334 [Skin] Processing screen 'MessageBoxSummary' from list 'MessageBoxSummary, ScreenSummary', position=(0, 0), size=(400 x 240) for module 'ScreenSummary'
< 582.055315> 10:59:59.5371 [ImageManager] MAINDEST=/media/hdd/imagebackups/imagerestore/gigablue/quad4k
< 582.055499> 10:59:59.5373 Traceback (most recent call last);
< 582.055549> 10:59:59.5374 File "/usr/lib/enigma2/python/Components/Console.py", line 49, in finishedCB
< 582.055893> 10:59:59.5377 File "/usr/lib/enigma2/python/Plugins/SystemPlugins/ViX/ImageManager.py", line 581, in keyRestore4
< 582.056208> 10:59:59.5380 File "/usr/lib/enigma2/python/Plugins/SystemPlugins/ViX/ImageManager.py", line 598, in keyRestore6
< 582.056517> 10:59:59.5383 KeyError: 'rootsubdir'
< 582.056586> 10:59:59.5384 [ePyObject] (CallObject(<bound method Screen.close of <class 'Screens.MessageBox.MessageBox'>(Please wait while the flash prepares.)>,(0,)) failed)

 

[twol]

Since graduating to v.6.7.11 on my GigaBlue UHD 4K many months ago, I've been unable to update to any subsequent versions, or even to other images previously loaded into the flash memory. The installation process exits with an error log like the one attached. In v.6.7.11, the receiver works normally without any other signs of distress. Where have I gone wrong?

Since graduating to v.6.7.11 on my GigaBlue UHD 4K many months ago, I've been unable to update to any subsequent versions, or even to other images previously loaded into the flash memory. The installation process exits with an error log like the one attached. In v.6.7.11, the receiver works normally without any other signs of distress. Where have I gone wrong?

OK this issue was fixed some time ago.....
Preferably stop the box e.g. with putty type init 4 (space between)
can you copy over attachment to /usr/lib/enigma2/python/Plugins/SystemPlugins/ViX and restart the box. (init 3 in putty - better to rename existing ImageManager.pyc before you do this)

Please confirm that this fixes your issue.

 

[Arcy]

Thank you for replying so quickly, but it looks as if I haven't got this right yet :-(

Having stopped the box, I renamed the existing ImageManager.pyc as ImageManager-old.pyc and copied your attachment in as ImageManager.py -- and then did an init 3. But the box still crashes and restarts. I notice that Vix no longer appears at the bottom of the box's main Setup menu, and that ImageManager.py is a much smaller file than ImageManager.pyc.

 

[abu baniaz]

Stop receiver with "init 4"
Rename existing file, I normally add a .original at end, but what you have done is fine
Transfer the new file
Restart with "init 3"

Try process again. If it still has the same issue, enable debug logs and attach them.

 

[Arcy]

Stop receiver with "init 4"
Rename existing file, I normally add a .original at end, but what you have done is fine
Transfer the new file
Restart with "init 3"

Try process again. If it still has the same issue, enable debug logs and attach them.

But should the new file be renamed as .pyc -- or copied just as .py ?

 

[twol]

But should the new file be renamed as .pyc -- or copied just as .py ?

Copied as .py.
If it crashes then enable logs menu/setup/system/logs/settings ——-> enable, save to other than flash, local time
logs will be saved in destination entered plus logs
that file is from a day after your image was created, plus fix so should be OK….. but if not we need to see debug logs to fix your situation

 

[Arcy]

Copied as .py.
If it crashes then enable logs menu/setup/system/logs/settings ——-> enable, save to other than flash, local time
logs will be saved in destination entered plus logs
that file is from a day after your image was created, plus fix so should be OK….. but if not we need to see debug logs to fix your situation

I tried once again, but with the same result. I've attached three log files which were created then.

 

[twol]

I tried once again, but with the same result. I've attached three log files which were created then.

error is [PluginComponent] Plugin SystemPlugins/ViX failed to load: No module named 'Plugins.SystemPlugins.ViX.ImageManager'
So its not finding the ImageManager.py in /usr/lib/enigma2/python/Plugins/SystemPlugins/ViX

can you check that you have copied it to /usr/lib/enigma2/python/Plugins/SystemPlugins/ViX and its correctly named ( it should be copied as .py and will be converted to a .pyc)

 

[twol]

as an aside why do you need this plugin as it also crashes and is not in use??
< 397.405966> InfoBarTunerState start
< 397.407363> [Skin] Parsing embedded skin '<embedded-in-TunerStateBase>'.
< 397.408410> [Skin] Processing screen '<embedded-in-TunerStateBase>', position=(0, 75), size=(1500 x 48) for module 'TunerStateBase'.
< 397.412333> [ePNG] couldn't open /usr/lib/enigma2/python/Plugins/Extensions/InfoBarTunerState/InfoBarTunerState/progress.png
< 397.412446> [Skin] Error: [Skin] {Simple_Ten_Eighty/skin.xml}: Pixmap file '/usr/lib/enigma2/python/Plugins/Extensions/InfoBarTunerState/InfoBarTunerState/progress.png' not found! Please contact the skin's author!
< 397.418685> [StartEnigma] Plugin raised exception at WHERE_SESSIONSTART
< 397.421289> Traceback (most recent call last):
< 397.422761> File "/usr/lib/enigma2/python/StartEnigma.py", line 58, in __init__
p(reason=0, session=self)
< 397.422831> File "/usr/lib/enigma2/python/Plugins/Plugin.py", line 110, in __call__
< 397.422877> File "/usr/lib/enigma2/python/Plugins/Extensions/StreamInterface/plugin.py", line 229, in autostart
startServer(kwargs["session"])
< 397.422922> File "/usr/lib/enigma2/python/Plugins/Extensions/StreamInterface/plugin.py", line 208, in startServer
res.putChild("", list)
< 397.422961> File "/usr/lib/python3.12/site-packages/twisted/web/resource.py", line 236, in putChild
< 397.423070> TypeError: Path segment must be bytes, but '' is <class 'str'>

 

[Arcy]

I'm wondering whether my new Windows 11 peecee may be to blame. When I download the .py file to my desktop, it gets filetyped automatically as a Web document (with the same icon as a saved web page). Then, when it arrives in /usr/lib/enigma2/python/Plugins/SystemPlugins/ViX
it shows up as ImageManager.py.url -- which I imagine might be enough to stop it being processed as intended.

I can't see any easy way of changing it to something more neutral. But perhaps I should try it again in the morning, using a different computer.

 

[twol]

I'm wondering whether my new Windows 11 peecee may be to blame. When I download the .py file to my desktop, it gets filetyped automatically as a Web document (with the same icon as a saved web page). Then, when it arrives in /usr/lib/enigma2/python/Plugins/SystemPlugins/ViX
it shows up as ImageManager.py.url -- which I imagine might be enough to stop it being processed as intended.

I can't see any easy way of changing it to something more neutral. But perhaps I should try it again in the morning, using a different computer.

So when you copy over, just rename using filezilla to ImageManager.py

 

[abu baniaz]

Have you tried to perform a software update instead of flashing a newer image?

 

[Joe_90]

@Arcy - make sure that FileZilla (if that is what you're using to FTP files from PC to receiver) is set to use binary transfer and not text. Microsoft PC and linux use different line endings and if FileZilla "helpfully" converts the file during transfer it can mess up the line endings and cause problems when it is run on linux. I learned the hard way some years ago when transferring scripts between systems using FileZilla. It can default certain file types to text format and try to use a best guess to convert them. Using binary mode will always transfer exactly what is in the file. For the same reason don't use ordinary MS Windows notepad to edit scripts or linux text files. Notepad++ will allow you to edit files while retaining linux line endings.

 

[Arcy]

@Arcy - make sure that FileZilla (if that is what you're using to FTP files from PC to receiver) is set to use binary transfer and not text. Microsoft PC and linux use different line endings and if FileZilla "helpfully" converts the file during transfer it can mess up the line endings and cause problems when it is run on linux. I learned the hard way some years ago when transferring scripts between systems using FileZilla. It can default certain file types to text format and try to use a best guess to convert them. Using binary mode will always transfer exactly what is in the file. For the same reason don't use ordinary MS Windows notepad to edit scripts or linux text files. Notepad++ will allow you to edit files while retaining linux line endings.

Thank you, all, for your help. Unfortunately I've now got myself into a real mess. Having failed to get round the Windows PC's manipulation of the upload, I tried again with an Ububtu Linux laptop, and it worked. The box started correctly, the Vix entry reappeared at the bottom of the main Setup menu, and the box received broadcasts normally.

Thrilled by this success, I then went to the image manager and launched the upgrade to version 019. I pressed the Power button to start it off, but very soon the box became stuck on the GigaBlue splash screen (on both the LCD and the HDMI output) and progressed no further. I've since tried installing 019 from a USB stick, but that did not progress either. So I'm at a loss to know what to do.

Thanks, twol, for pointing out another plugin that is crashing, but I'm afraid I don't understand which one it is :-( Is it something from the plugins menu (which, alas, I can't access at present) or is it hidden? Perhaps that's just an academic question at the moment.

 

[twol]

Thank you, all, for your help. Unfortunately I've now got myself into a real mess. Having failed to get round the Windows PC's manipulation of the upload, I tried again with an Ububtu Linux laptop, and it worked. The box started correctly, the Vix entry reappeared at the bottom of the main Setup menu, and the box received broadcasts normally.

Thrilled by this success, I then went to the image manager and launched the upgrade to version 019. I pressed the Power button to start it off, but very soon the box became stuck on the GigaBlue splash screen (on both the LCD and the HDMI output) and progressed no further. I've since tried installing 019 from a USB stick, but that did not progress either. So I'm at a loss to know what to do.

Thanks, twol, for pointing out another plugin that is crashing, but I'm afraid I don't understand which one it is :-( Is it something from the plugins menu (which, alas, I can't access at present) or is it hidden? Perhaps that's just an academic question at the moment.

OK I am confused as to what you have done here.
“ I then went to the image manager and launched the upgrade to version 019. I pressed the Power button to start it off“
Can you explain….did you download the 019 image in ImageManager (yellow button) and then flash an image slot (blue button) or ?
When did you press the Power button? Not something I expected to be done

if you can do that before we start looking at gigablue,s Recovery system

 

[Arcy]

OK I am confused as to what you have done here.
“ I then went to the image manager and launched the upgrade to version 019. I pressed the Power button to start it off“
Can you explain….did you download the 019 image in ImageManager (yellow button) and then flash an image slot (blue button) or ?
When did you press the Power button? Not something I expected to be done

if you can do that before we start looking at gigablue,s Recovery system

Sorry for confusion :-( First I tried in ImageManager, to flash into Slot 1 an 019 image which I had downloaded some days ago. When after >10 minutes this had not passed beyond the GigaBlue splash screen, I decided instead to try installing from a USB stick newly loaded with 019 -- and it asked me to press the Power button within ten seconds to start the upgrade.

 

[Arcy]

Sorry for confusion :-( First I tried in ImageManager, to flash into Slot 1 an 019 image which I had downloaded some days ago. When after >10 minutes this had not passed beyond the GigaBlue splash screen, I decided instead to try installing from a USB stick newly loaded with 019 -- and it asked me to press the Power button within ten seconds to start the upgrade.

I don't know whether this is any kind of clue to what's going on, but when the GigaBlue screen appears after switch-on, the number 1846 is superimposed on it for about 20 seconds and then vanishes.

 

[twol]

Sorry for confusion :-( First I tried in ImageManager, to flash into Slot 1 an 019 image which I had downloaded some days ago. When after >10 minutes this had not passed beyond the GigaBlue splash screen, I decided instead to try installing from a USB stick newly loaded with 019 -- and it asked me to press the Power button within ten seconds to start the upgrade.

So in ImageManager did you flash an image using the Blue button and did it say successful??
If you try usb , then you need to unzip to the usb so that it contains just the gigablue folder and contents.

https://www.openvix.co.uk/openvix-builds/Guides%20and%20Tutorials/Flashing%20Guides/GiGaBlue%20USB%20Flashing%20Guides/How%20to%20flash%20a%20Gigablue%20UHD%20Quad%204K.pdf

Unfortunately you are on the old bootloader so recovery not as simple.

 

[Joe_90]

Also, if you are flashing from a USB stick, then you must press the power button on the receiver - not the remote (if your Gigablue is similar to my old GB Quad Plus). Also front USB, if fitted, is preferred. The number on the screen is normal at initial boot for my GB Quad also.