[VU+ Duo2] Crash when trying to restore settings

[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>[email protected]</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?

[email protected]

 

[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 [email protected].

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........