Superb quality and spec AB-Com PULSe 4K SE. Crazy offer! Only £129! FREE UK DELIVERY! 4K UHD, Enigma 2, Multiboot 4 images & more!...
Superb quality and spec AB-Com PULSe 4K Rev II Twin Satellite tuner only £179! FREE UK DELIVERY! 4K UHD, Enigma 2, SATA HDD facility, Multiboot 4 images & more!...

[ViX_Misc] [034] <> history button causes crash

maxben

Forum Supporter
Donated Member
Joined
Nov 10, 2014
Messages
352
Reaction score
0
Points
16
pressing <> history menu causes E2 crash

After today's update with fresh install of skin from feed.

Code:
[InfoBarGenerics] KEY: 412 ARROWLEFT
[ActionMap] InfobarChannelSelection historyBack
<  7768.696665> [gAccel] alloc failed

<  7768.696759> [gSurface] ERROR: accelAlloc failed
<  7768.714358> [gAccel] alloc failed

<  7768.714454> [gSurface] ERROR: accelAlloc failed
<  7768.732605> [gAccel] alloc failed

<  7768.732703> [gSurface] ERROR: accelAlloc failed
<  7768.754496> [gAccel] alloc failed

<  7768.754593> [gSurface] ERROR: accelAlloc failed
<  7768.775381> [gAccel] alloc failed

<  7768.775479> [gSurface] ERROR: accelAlloc failed
<  7768.793559> [gAccel] alloc failed

<  7768.793661> [gSurface] ERROR: accelAlloc failed
<  7768.809945> [gAccel] alloc failed

<  7768.810205> [gSurface] ERROR: accelAlloc failed
[Skin] processing screen HistoryZapSelector:
<  7768.832675> [ePNG] couldn't open /usr/share/enigma2/skin_default/selectionbars/SelectionBar_H150x1160.png
[Skin] Error: [Skin] {YouViX-Blue/skin.xml}: [Skin] pixmap file /usr/share/enigma2/skin_default/selectionbars/SelectionBar_H150x1160.png not found!. Please contact the skin's author!
[Skin] processing screen SimpleSummary:
<  7768.839658> [gAccel] alloc failed

<  7768.839723> [gSurface] ERROR: accelAlloc failed
<  7768.856385> Backtrace:
<  7768.856798> /usr/bin/enigma2(_Z17handleFatalSignaliP9siginfo_tPv) [0x6F0FC]
<  7768.856932> /lib/libc.so.6(__default_rt_sa_restorer) [0xB63CE6C0]
<  7768.857157> /usr/bin/enigma2(_ZN26eListboxPythonMultiContent5paintER8gPainterR12eWindowStyleRK6ePointi) [0xF6460]
<  7768.857352> /usr/bin/enigma2(_ZN8eListbox5eventEiPvS0_) [0xF3028]
<  7768.857518> /usr/bin/enigma2(_ZN7eWidget7doPaintER8gPainterRK7gRegioni) [0xFB834]
<  7768.857686> /usr/bin/enigma2(_ZN7eWidget7doPaintER8gPainterRK7gRegioni) [0xFB880]
<  7768.857848> /usr/bin/enigma2(_ZN7eWidget7doPaintER8gPainterRK7gRegioni) [0xFB880]
<  7768.858008> /usr/bin/enigma2(_ZN14eWidgetDesktop10paintLayerEP7eWidgeti) [0xFD7D8]
<  7768.858176> /usr/bin/enigma2(_ZN14eWidgetDesktop5paintEv) [0xFD848]
<  7768.858309> /usr/bin/enigma2(_ZN6eTimer8activateEv) [0x7372C]
<  7768.858438> /usr/bin/enigma2(_ZN9eMainloop15processOneEventEjPP7_object9ePyObject) [0x73EE4]
<  7768.858560> /usr/bin/enigma2(_ZN9eMainloop7iterateEjPP7_object9ePyObject) [0x73FDC]
<  7768.858690> /usr/bin/enigma2(_ZN9eMainloop4pollE9ePyObjectS0_) [0x740E4]
<  7768.858857> /usr/bin/enigma2(n/a) [0x110D60]
<  7768.858879> -------FATAL SIGNAL (11)
 
Yep same here using 1080 confluence skin on a TM Nano SE


Sent from my iPhone using Tapatalk
 
It's not a box or skin issue.
Thanks for reporting it though, bug report opened.
 
035 is being built to take in a change which was still in the Developer image.

If you can't wait, you can transfer this .pyo file to /usr/lib/enigma2/python/Screens/ and restart.
 

Attachments

035 is being built to take in a change which was still in the Developer image.

If you can't wait, you can transfer this .pyo file to /usr/lib/enigma2/python/Screens/ and restart.

Cheers for the speedy fix


Sent from my iPhone using Tapatalk
 
Thank for the fix. Much needed for us channel hoppers.:thumbsup:
 
[034] &lt;&gt; history button causes crash

Well spotted, but that was a different one during image backup.

Try again.
 
Have a look at History zap that is the only difference I have noticed :D
 
I was always shite at spot the difference :)- is it because it says 28.2 - if so, not much use to me as that's the only sat i use
 
I am the same m8 only one I use , Sat all day trying to find something different but that is the only one different thing I noticed :thumbsup:
 
You can now see which satellite you are zapping back to.
 

Attachments

  • orbital position.webp
    orbital position.webp
    39.6 KB · Views: 12
  • orbital position 2.webp
    orbital position 2.webp
    13.9 KB · Views: 11
You can now see which satellite you are zapping back to.

If we can include that in EPG search & EPG timers, we're doing good...
Great addition for multiple tuners & multiple sat use.
 

OpenViX Feeds Status

Back
Top