Crash when trying to restore settings

[2stein]

this seems to be new on 037... never had this before.
46940

[linus]

Hello
I have tested the restore settings fonction and do not have this problem, so something specific to your settings.

It'says:
(fd=95): Value too large for defined data type
[eDVBServicePlay] timeshift

Does the value 95 remind you something in the settings related to timeshifting?

[2stein]

no, it doesn't. i have no specific timeshifting settings. permanent timeshift is set to off.

[2stein]

i don't think that this is causing the crash...
it's rather this one:

Skin] processing screen VIXBackupManager:
[Skin] processing screen PluginBrowserSummary:
< 215.390374> [eInputDeviceInit] 0 160 1
[InfoBarGenerics] KEY: 352 OK
Backup Image: 3.2
Current Image: 3.2
[RestoreWizard] Stage 1: Image ver OK
Traceback (most recent call last):
File "/usr/lib/enigma2/python/Tools/BoundFunction.py", line 9, in __call__
File "/usr/lib/enigma2/python/Components/Console.py", line 58, in finishedCB
File "/usr/lib/enigma2/python/Plugins/SystemPlugins/ViX/BackupManager.py", line 319, in settingsRestoreCheck
File "/usr/lib/enigma2/python/Plugins/SystemPlugins/ViX/BackupManager.py", line 326, in keyResstore1
AttributeError: 'VIXBackupManager' object has no attribute 'sel'
< 216.997421> [ePyObject] (CallObject(<Tools.BoundFunction.boundFunction instance at 0x61b55ee0>,(0,)) failed)
]]>

[linus]

You are right.

[abu baniaz]

Is this a beautiful image (one with your edits) or ugly image (Openvix with no alterations)?

[2stein]

ugly one... :D

[abu baniaz]

That crashlog contains details indicating an old file was used. Please double check

[2stein]

which file are you referring to? couldn't find any...

[abu baniaz]

Just invoked a crash

My one has


<crashdate>Wed Feb 24 21:50:06 2016</crashdate>
<compiledate>Feb 22 2016</compiledate>
<contactemail>vixlogs@oe-alliance.com</contactemail>
<!-- Please email this crashlog to above address -->

[2stein]

strange... i just online updated yesterday.... i don't have a setup to compile images.

[2stein]

Just invoked a crash

My one has


<crashdate>Wed Feb 24 21:50:06 2016</crashdate>
<compiledate>Feb 22 2016</compiledate>
<contactemail>vixlogs@oe-alliance.com</contactemail>
<!-- Please email this crashlog to above address -->

well, mine is the same, no?


<crashdate>Di Feb 23 23:05:36 2016</crashdate>
<compiledate>Feb 22 2016</compiledate>
<contactemail>andyblac@icloud.com</contactemail>
<!-- Please email this crashlog to above address -->

[2stein]

ah, you mean the email address...
you are probably using a dev build.

[abu baniaz]

Might be a rogue file causing it then. I'll ask somone to invoke a crash on the Duo2 to confirm the log, although that ios being overhauled anyway.

What you can do:
Transfer your recent backup to your PC and extract it. On STB, you will find the files in /media/hdd/backup/ The files are .tar.gz You can use 7zip to extract them.
All your settings are stored in a file called settigs. File path is /etc/enigma2/

Flash 037.
Note: By default DHCP is on and it should be assigned the same IP address as before
Stop Enigma2 using command

init 4
Transfer the settings file (extracted from most recent desired backup) to /etc/enigma2/
You may also wish to restrore any other config files/autotimers etc at this stage
Restart receiver with following command

init 3

You will find that your personalisations are restored. Plugins will have to be reinsatlled.

[abu baniaz]

ah, you mean the email address...
you are probably using a dev build.
I was using the dev build. After your report, I flashed release 037 to test your issue, I could not reproduce it. Flashed back my image.

Email address is the same on all recent images though.

[2stein]

thanks....

[birdman]

i don't think that this is causing the crash...
it's rather this one:

Skin] processing screen VIXBackupManager:
[Skin] processing screen PluginBrowserSummary:
< 215.390374> [eInputDeviceInit] 0 160 1
[InfoBarGenerics] KEY: 352 OK
Backup Image: 3.2
Current Image: 3.2
[RestoreWizard] Stage 1: Image ver OK
Traceback (most recent call last):
File "/usr/lib/enigma2/python/Tools/BoundFunction.py", line 9, in __call__
File "/usr/lib/enigma2/python/Components/Console.py", line 58, in finishedCB
File "/usr/lib/enigma2/python/Plugins/SystemPlugins/ViX/BackupManager.py", line 319, in settingsRestoreCheck
File "/usr/lib/enigma2/python/Plugins/SystemPlugins/ViX/BackupManager.py", line 326, in keyResstore1
AttributeError: 'VIXBackupManager' object has no attribute 'sel'
< 216.997421> [ePyObject] (CallObject(<Tools.BoundFunction.boundFunction instance at 0x61b55ee0>,(0,)) failed)
]=]=>
settingsRestoreCheck() is only called from keyResstore(), and that starts by setting self.sel. So if the sel attribute isn't there then there must be no current selection on the backup image list - there is no check to cover that possibility.

This code hasn't changed in the last 5+ months (so no-one has got rid of that double-s yet...)

[2stein]

well, let's see... i'm sure i selected a backup to be restored. however, I think the crash happened on the second trial to do a restore.
the first one didn't crash but didn't work either. it started, but the progress bar didn't move (stayed at 0) and ended after a while with the error message "timeout occurred" or something.
again: it never happened to me before. on the other hand, i never do a restore after an image update. this time i thought i needed one due to the "ugly" boot logo. :-)
i went back now to 036 and will be skipping 037.
let's see how things are in oe3.3 :-)

[2stein]

Email address is the same on all recent images though.
i will investigate this further... the only reason i could think of is the backup settings. maybe something gets backed up and restored which shouldn't.

[birdman]

i will investigate this further... the only reason i could think of is the backup settings. maybe something gets backed up and restored which shouldn't.The Image backup code changed for 037 - to add a settings backup (IIRC). But the Backup code didn't..

[2stein]

The Image backup code changed for 037 - to add a settings backup (IIRC). But the Backup code didn't..
no, i'm talking about my backup settings... maybe i checked something which i shouln't have checked.
it worries me that the email address was changed long time ago and i still have ancient code that still has the old address. wonder what else might be old???

[birdman]

no, i'm talking about my backup settings... maybe i checked something which i shouln't have checked.
it worries me that the email address was changed long time ago and i still have ancient code that still has the old address. wonder what else might be old???What email address?

[2stein]

this one:

<contactemail>andyblac@icloud.com</contactemail>
in the crashlog implies an old bsod.cpp... and with that an old enigma2 (bsod.cpp is compiled into enigma2, right?)

[2stein]

i checked the backup settings: /usr/bin/enigma2 is not checked.
i unpacked a backup file: /usr/bin/enigma2 is not in there.
so, i claim, that the image must contain an enigma2 binary with an old bsod.cpp...

[2stein]

this is the enigma2 binary:

-rwxr-xr-x 1 root root 2652392 Jan 28 15:14 enigma2
it's build 036.

[abu baniaz]

First sentence in post 14 has the following:


Might be a rogue file causing it then. I'll ask somone to invoke a crash on the Duo2 to confirm the log, although that is being overhauled anyway.

[2stein]

if there is one... there might be more ;-)

[abu baniaz]

Not a case of "the more the merrier"?

[birdman]

i checked the backup settings: /usr/bin/enigma2 is not checked.
i unpacked a backup file: /usr/bin/enigma2 is not in there.
so, i claim, that the image must contain an enigma2 binary with an old bsod.cpp...Have you looked at the bsod.cpp source code? What mail address does that contain?

[2stein]

if there is one... there might be more ;-)
not at all :-)

[2stein]

Have you looked at the bsod.cpp source code? What mail address does that contain?
vixlogs@something.com

[birdman]

OK. I now see what the mail address discussion is about.


this is the enigma2 binary:

-rwxr-xr-x 1 root root 2652392 Jan 28 15:14 enigma2
it's build 036.Well, that enigma2 binary matches the one for 036 (assuming you are on the Western European mainland - as my time-stamp shows 14:14.)
BUT the debug log in post #1 says it is build 037.
I've just downloaded the flash images for a Vu+ Duo2 and looked at the enigma2 binaries. The mail address contained in each is vixlogs@oe-alliance.com.

I can't see how you ended up with the email address, or version 037 being reported.

[TeflonDon]

I had the same issue: could not restore settings (was trying to restore 032 settings) after 037 update.

When back to 027 backup and that restored fine. Had to rescan which was a long winded process but all fine now: I hope.

[2stein]

I can't see how you ended up with the email address, or version 037 being reported.
well, the log was created with 037, however i did not do a fresh flash but an update. so, this could make a difference.
the 036 enigma2 binary was just to check if there was an old enigma2 binary on 036 before the update. which you confirmed was not.
so, the question is still, where this old address comes from.

[2stein]

looks like andy fixed the crash...
https://github.com/OpenViX/vix-core/commit/2959d88cee0a02fbbbdd2867a26f3aa124208920

still curious to find out what caused the wrong email address.

[twol]

Thats a change to imagemanager, not backupsmanager

[2stein]

ooops........