Open BlackHole Online Update

Alexwilmac said:
Yes, I posted about it in all possible testing scenarios but nobody wanted to admit it...
https://www.vuplus-community.net/bo...ossible-in-rec-play-timeshift-submenus.42230/

What is for sure is that it affects in a different way different VU+ models (for instance, no problem in Duo2) and it counts if the image is running from OMB or in flash.
Just for this bug (I insist it's a bug, not my faulty image) I had to abandon my wish of running OBH from OMB (in order to preserve flash) and I was forced to run it from flash.

What VU+ do you have? Where is OBH installed?
Click to expand...

No problem in OBH 4.4.018 on Duo 4K (image on flash)... later I see in other models.
 
Alexwilmac said:
Yes, I posted about it in all possible testing scenarios but nobody wanted to admit it...
https://www.vuplus-community.net/bo...ossible-in-rec-play-timeshift-submenus.42230/

What is for sure is that it affects in a different way different VU+ models (for instance, no problem in Duo2) and it counts if the image is running from OMB or in flash.
Just for this bug (I insist it's a bug, not my faulty image) I had to abandon my wish of running OBH from OMB (in order to preserve flash) and I was forced to run it from flash.

What VU+ do you have? Where is OBH installed?
Click to expand...

i have vu+ zero4k
i am using neoboot plugins
 
p.rodrigues said:
No problem in OBH 4.4.018 on Duo 4K (image on flash)... later I see in other models.
Click to expand...
As explained many times, the problem is mainly if the image is installed in OMB. As I wrote in the linked post...

To sum up my tries, I tested all my 3 boxes, both from flash and from OMB. This is what happens (I repeat: clean images both in flash or in OMB):
1) Duo2 and Solo4K both perfectly work from flash and not from OMB in both submenus.
2) Zero4K behaves differently (and should tell something by itself): either from flash or from OMB, it works only the Recording submenu whilst the Timeshift one doesn't.

This clearly means this is a model-related bug.
It is caused by ViX image, the one whom OBH shares a lot of code with.
 
It seems to me that some of you have had a bad upgrade,
or something else.

I tested OBH on Ultimo 4K in multiboot on USB stick
My advice.
Reinstall the OBH 4.4.013 file on the forum.
Make an upgrade to the current OBH version immediately after installation.
Currently 4.4.019
Attention doe not use old skins and old bakups.
Doe not use modified skins ,we changed the coding for some panels.
Use skins from OBH image server.
For those who use the Common Interface put
Show CI messages on No
because in some cases it can block the CI menu or image
 
Last edited:
In my case, wasn't a bad update: I clarified and detailed in my original post: it happened (of course) after an update. But then I tried everything, every possible scenario, above all a totally clean install without anything and subsequent update.
But I'm here only talking about the submenu Recording and Timeshift and its issue.
 
Alexwilmac said:
In my case, wasn't a bad update: I clarified and detailed in my original post: it happened (of course) after an update. But then I tried everything, every possible scenario, above all a totally clean install without anything and subsequent update.
But I'm here only talking about the submenu Recording and Timeshift and its issue.
Click to expand...

There is everything mixed up.
Some use modified skins or another old backup,the third something else or failed to upgrade completely.
In such cases, it is best to start from scratch.
Install the image and upgrade.
To make sure the real bug exists.

Sometimes it is easier and better to install the whole OS (image)
rather than looking for the cause of the problem.
For this purpose, I install the image in about ten minutes
because I have a backup of everything I need directly on my PC.
The rest can be installed after skin or plug-in.
 
Exactly what I wrote I did: everything from scratch. Clean images in flash and then clean images in OMB with the results I reported.
 
mosad said:
Crash 4.4.018

View attachment 50710
Click to expand...
In your log
< 82762.4839> 17:53:48.7785 ImportError: cannot import name VIXImageManager

but VIXImageManager no longer exists in the upgraded image
it is now OBHImageManager
and this applies to all old VIX panels that are now OBH panels.
What it means.
Either the image is not upgraded correctly or you have use some backup or there is a bug in your modified skin.
I guess the image is a bug because something is not upgraded properly and still searching for VIXImageManager
 
4.4.019 released.
Again, like last update, quite a slow process (I updated by command line, fortunately).

I had a strange conclusion of the update:

Collected errors:
* check_data_file_clashes: Package rtmpdump wants to install file /usr/lib/librtmp.so.1
But that file is already provided by package * librtmp1
* check_data_file_clashes: Package python-core wants to install file /usr/lib/python2.7/ntpath.pyo
But that file is already provided by package * python-misc
* check_data_file_clashes: Package python-core wants to install file /usr/lib/python2.7/ntpath.pyo
But that file is already provided by package * python-misc
* check_data_file_clashes: Package python-core wants to install file /usr/lib/python2.7/ntpath.pyo
But that file is already provided by package * python-misc
* check_data_file_clashes: Package python-core wants to install file /usr/lib/python2.7/ntpath.pyo
But that file is already provided by package * python-misc
* check_data_file_clashes: Package python-core wants to install file /usr/lib/python2.7/ntpath.pyo
But that file is already provided by package * python-misc
* check_data_file_clashes: Package python-core wants to install file /usr/lib/python2.7/ntpath.pyo
But that file is already provided by package * python-misc
* check_data_file_clashes: Package python-core wants to install file /usr/lib/python2.7/ntpath.pyo
But that file is already provided by package * python-misc
* check_data_file_clashes: Package python-core wants to install file /usr/lib/python2.7/ntpath.pyo
But that file is already provided by package * python-misc
* check_data_file_clashes: Package python-core wants to install file /usr/lib/python2.7/ntpath.pyo
But that file is already provided by package * python-misc
* check_data_file_clashes: Package python-core wants to install file /usr/lib/python2.7/ntpath.pyo
But that file is already provided by package * python-misc
* check_data_file_clashes: Package python-core wants to install file /usr/lib/python2.7/ntpath.pyo
But that file is already provided by package * python-misc
* check_data_file_clashes: Package python-core wants to install file /usr/lib/python2.7/ntpath.pyo
But that file is already provided by package * python-misc
* check_data_file_clashes: Package python-core wants to install file /usr/lib/python2.7/ntpath.pyo
But that file is already provided by package * python-misc
* check_data_file_clashes: Package python-core wants to install file /usr/lib/python2.7/ntpath.pyo
But that file is already provided by package * python-misc
* check_data_file_clashes: Package python-core wants to install file /usr/lib/python2.7/ntpath.pyo
But that file is already provided by package * python-misc
* check_data_file_clashes: Package python-core wants to install file /usr/lib/python2.7/ntpath.pyo
But that file is already provided by package * python-misc
* check_data_file_clashes: Package python-core wants to install file /usr/lib/python2.7/ntpath.pyo
But that file is already provided by package * python-misc
 
Last edited:
Hi , i have vu+ zero OBH installed on flash , i did the new update but its stuck on upgrade in progress for an hour now , is it normal and what should i do now , wait or manualy reboot my box .. i had version 4.4.018
 
Elouardi said:
Hi , i have vu+ zero OBH installed on flash , i did the new update but its stuck on upgrade in progress for an hour now , is it normal and what should i do now , wait or manualy reboot my box .. i had version 4.4.018
Click to expand...
Now it reboot by itself .. took more than 1 hour
 
Of course it reboots by itself: it is always so for every updates if you launch the update by the GUI. Only, as the server was slow, it took all this time.
In my case, as I always update not by the GUI but by the command line, I left it running, but it took "only" 10 minutes.
Obviously, it also depends on the Internet connection.
 
I wrote how to make a clean upgrade.

Reinstall the OBH 4.4.013 file on the forum.
Make an upgrade to the current OBH version immediately after installation.
Currently 4.4.019
Attention doe not use old skins and old bakups.
Doe not use modified skins ,we changed the coding for some panels.
Use skins from OBH image server.
For those who use the Common Interface put
Show CI messages on No
because in some cases it can block the CI menu or image

The upgrade may be slow if the server is loaded.
So wait
 
Alexwilmac said:
As explained many times, the problem is mainly if the image is installed in OMB. As I wrote in the linked post...

To sum up my tries, I tested all my 3 boxes, both from flash and from OMB. This is what happens (I repeat: clean images both in flash or in OMB):
1) Duo2 and Solo4K both perfectly work from flash and not from OMB in both submenus.
2) Zero4K behaves differently (and should tell something by itself): either from flash or from OMB, it works only the Recording submenu whilst the Timeshift one doesn't.

This clearly means this is a model-related bug.
It is caused by ViX image, the one whom OBH shares a lot of code with.
Click to expand...

Where us the bug?
 
Alexwilmac said:
As explained many times, the problem is mainly if the image is installed in OMB. As I wrote in the linked post...

To sum up my tries, I tested all my 3 boxes, both from flash and from OMB. This is what happens (I repeat: clean images both in flash or in OMB):
1) Duo2 and Solo4K both perfectly work from flash and not from OMB in both submenus.
2) Zero4K behaves differently (and should tell something by itself): either from flash or from OMB, it works only the Recording submenu whilst the Timeshift one doesn't.

This clearly means this is a model-related bug.
It is caused by ViX image, the one whom OBH shares a lot of code with.
Click to expand...

But you are quoting @p.rodrigues post!
 
Yes, because he said there is no problem in 4.0.018, but it's not so. Maybe the quote was not appropriate? ;)
But the problem was still there, at least until 4.0.018. I haven't tried the 019, yet, in OMB.
 
You must log in or register to reply here.
Back
Top