[VU+ Ultimo4K] 5.3.030 crashing. Fixed in 5.3 032

[ccs]

Nasty looking crash after couch flashing 5.3.030 and restoring settings from 5.3.029

The box boots up ok until the programme info bar appears and then crashes before live tv is shown.

The GUI restarts and the box is ok, but if I reboot it crashes again with the same sequence. Same crash starting from deep standby.

ET10K couch flashed ok.

Tried re-flashing, no better.

<    30.6001> 15:08:41.5856 [Avahi] timeout elapsed
<    30.6003> 15:08:41.5858 [Avahi] client state: 2
<    30.6005> 15:08:41.5859 [Avahi] avahi_timeout_new
<    30.6022> 15:08:41.5877 [Avahi] avahi_timeout_free
<    30.6025> 15:08:41.5880 [Avahi] avahi_timeout_new
<    30.6040> 15:08:41.5895 [Avahi] avahi_timeout_free
<    30.6043> 15:08:41.5898 [Avahi] avahi_timeout_new
<    30.6056> 15:08:41.5910 [Avahi] avahi_timeout_free
<    30.6062> 15:08:41.5917 [Avahi] avahi_timeout_new
<    30.6079> 15:08:41.5934 [Avahi] avahi_timeout_free
<    30.6081> 15:08:41.5935 [Avahi] avahi_timeout_new
<    30.6088> 15:08:41.5943 [Avahi] avahi_timeout_free
<    30.6089> 15:08:41.5943 [Avahi] avahi_timeout_update
<    30.6089> 15:08:41.5944 [Avahi] Registered vuultimo4k (_e2stream._tcp) on vuultimo4k:8001
<    30.6090> 15:08:41.5945 [Avahi] avahi_timeout_new
<    30.6114> 15:08:41.5969 [Avahi] avahi_timeout_free
<    30.6116> 15:08:41.5971 [Avahi] avahi_timeout_new
<    30.6127> 15:08:41.5982 [Avahi] avahi_timeout_free
<    30.6135> 15:08:41.5990 Backtrace:
<    30.6137> 15:08:41.5992 /usr/bin/enigma2(_Z17handleFatalSignaliP9siginfo_tPv) [0x1853A4]
<    30.6138> 15:08:41.5993 /lib/libc.so.6(__default_rt_sa_restorer) [0xB6CACE20]
<    30.6139> 15:08:41.5993 /lib/libc.so.6(gsignal) [0xB6CABFB4]
<    30.6139> 15:08:41.5994 /lib/libc.so.6(abort) [0xB6C9A200]
<    30.6139> 15:08:41.5994 -------FATAL SIGNAL (6)

 

[ccs]

Same problem with no settings restored.

Exits the wizard ok, but a reboot crashes.

Need to repeat to get hold of the crash log, not stored on hdd by default.

 

[twol]

Kind of indicates hardware error, its really early in initialisation - but maybe if the settings backup was from 029, re- flash and don't restore settings as 029 had some incorrect information in SystemInfo.

.... you beat me to it!

 

[twol]

Go back to 028/029 and see what happens ....... there are only 3 changes between 029 & 030

 

[ccs]

Post #2, continued.

Couch flashed 5.3.029 + settings restore, all fine.

Crash and debug logs now attached.... maybe a clue?

dbus[1703]: arguments to dbus_message_iter_append_basic() were incorrect, assertion "_dbus_check_is_valid_utf8 (*string_p)" failed in file ../../dbus-1.12.10/dbus/dbus-message.c line 2754.
This is normally a bug in some application using the D-Bus library.

  D-Bus not built with -rdynamic so unable to print a backtrace

 

[twol]

Post #2, continued.

Couch flashed 5.3.029 + settings restore, all fine.

Crash and debug logs now attached.... maybe a clue?

dbus[1703]: arguments to dbus_message_iter_append_basic() were incorrect, assertion "_dbus_check_is_valid_utf8 (*string_p)" failed in file ../../dbus-1.12.10/dbus/dbus-message.c line 2754.
This is normally a bug in some application using the D-Bus library.

  D-Bus not built with -rdynamic so unable to print a backtrace

Cannot see anything in OE-A that could cause this - (its a pity you don't have a multiboot box!)
Try this: save these 3 modules: /usr/lib/enigma2/python/Screens/InfobarGenerics.pyo and separately /usr/lib/enigma2/python/RecordTimer.pyo and /usr/lib/enigma2/python/Components/EpgListGrid.pyo

Then reflash and see if problem re -occurs. If it does 1st copy over teh InforbarGenerics.pyo (rename the existing one) and reboot. ANy difference??
If not copy over the other 2(having renamed the old ones) and reboot .

 

[ccs]

OK - I'll have to restore settings to get networking up quickly, but it shouldn't affect the outcome.

 

[BrianTheTechieSnail]

Same here.

Upgrade from 5.3.029 to 5.3.030 and after reboot device crashes and recovers (automatically restarts GUI maybe, not sure).

Reboot again - same crash and recover after boot.

restore image of 5.3.029 - back to normal.

I didn't investigate yet whether anything wasn't working after crash and recover.

 

[ccs]

Cannot see anything in OE-A that could cause this - (its a pity you don't have a multiboot box!)
Try this: save these 3 modules: /usr/lib/enigma2/python/Screens/InfobarGenerics.pyo and separately /usr/lib/enigma2/python/RecordTimer.pyo and /usr/lib/enigma2/python/Components/EpgListGrid.pyo

Then reflash and see if problem re -occurs. If it does 1st copy over teh InforbarGenerics.pyo (rename the existing one) and reboot. ANy difference??
If not copy over the other 2(having renamed the old ones) and reboot .

Changing all 3 has made no difference, still crashes the same.

 

[twol]

Have to say I am bemused - so few changes between the 2 releases 029/030

 

[ccs]

Have to say I am bemused - so few changes between the 2 releases 029/030

Fortunately, I'm not the only one (with the same problem).

 

[dsayers]

I use openmultiboot plugin on my uno4k when testing images.

Added vix 5.3.030 to openmultiboot with no restore no crash then restored settings and still fine.

So switched to my flash image that had vix 5.2.029 and did a software update to 5.3.030 and no issues with crashes.

Possibly box issues? Any specific driver updates between images?

 

[ccs]

Possibly box issues? Any specific driver updates between images?

Very unlikely, drivers are over a year old, and I'm assuming @BrianTheTechHead's box is a zgemma, so no.

 

[bbbuk]

Solo2 did online update from 29 to 30 and no issues noticed yet.

I've had a Fatal signal before but it's been a very, very long time (touch wood) and wasn't, at least for me, easily creatable again (so more of a one-off).

 

[ccs]

Solo2 did online update from 29 to 30 and no issues noticed yet.

My ET10K was ok as well, couch flashed like the Ultimo4K, which crashes (just the once, the GUI restart doesn't see it again, which might be a clue?)

This crash happens ever time.

 

[ccs]

Just did an online update from 5.3.029 to 5.3.030 and..........

It still crashes.

Also the tried and tested "switch off at the mains for 5 minutes" didn't help.

 

[simonc]

On the offchance this is something to do with me, can you try replacing /usr/lib/enigma2/python/RecordTimer.py with this

https://raw.githubusercontent.com/S...d765b0edb9182ffecbe16e255d16dd/RecordTimer.py

 

[ccs]

On the offchance this is something to do with me, can you try replacing /usr/lib/enigma2/python/RecordTimer.py with this

https://raw.githubusercontent.com/S...d765b0edb9182ffecbe16e255d16dd/RecordTimer.py

OK will take 5 minutes or so.

 

[ccs]

On the offchance this is something to do with me, can you try replacing /usr/lib/enigma2/python/RecordTimer.py with this

https://raw.githubusercontent.com/S...d765b0edb9182ffecbe16e255d16dd/RecordTimer.py

I wish I could say it was, but it still crashes.

 

[ccs]

Is this commit a pure coincidence, or......

https://github.com/OpenPLi/enigma2/commit/e1923b7c0d0304fe76218a13bf2d968fc2960bcd