PDA

View Full Version : [ViX_Misc] [034] <> history button causes crash



maxben
19-01-16, 19:21
pressing <> history menu causes E2 crash

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


[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(_ZN26eListboxPythonMultiContent5paintER8gP ainterR12eWindowStyleRK6ePointi) [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_object 9ePyObject) [0x73EE4]
< 7768.858560> /usr/bin/enigma2(_ZN9eMainloop7iterateEjPP7_object9ePyObjec t) [0x73FDC]
< 7768.858690> /usr/bin/enigma2(_ZN9eMainloop4pollE9ePyObjectS0_) [0x740E4]
< 7768.858857> /usr/bin/enigma2(n/a) [0x110D60]
< 7768.858879> -------FATAL SIGNAL (11)

khan888
19-01-16, 19:27
Yep same here using 1080 confluence skin on a TM Nano SE


Sent from my iPhone using Tapatalk

gibbletts
19-01-16, 19:48
Also bello on duo2

judge
19-01-16, 20:22
It's not a box or skin issue.
Thanks for reporting it though, bug report opened.

abu baniaz
20-01-16, 00:04
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.

khan888
20-01-16, 00:19
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

abu baniaz
20-01-16, 00:21
Have you spotted the difference?

khan888
20-01-16, 00:52
Have you spotted the difference?

Works both on my TM Nano and Miraclebox premium ultra :thumbsup:

Thanks

judge
20-01-16, 01:07
Works both on my TM Nano and Miraclebox premium ultra :thumbsup:

With a well needed new feature for multiple Sats or different tuner types...

Ashley69
20-01-16, 10:10
Thank for the fix. Much needed for us channel hoppers.:thumbsup:

Willmoore
20-01-16, 10:10
Have you spotted the difference?

The progress panel no longer covers the screen :thumbsup::thumbsup:

abu baniaz
20-01-16, 14:39
Well spotted, but that was a different one during image backup.

Try again.

Bazzer
20-01-16, 17:48
Well spotted, but that was a different one during image backup.

Try again.

Found it .Clue 1 Sats > zap.

Willmoore
20-01-16, 20:55
Found it .Clue 1 Sats > zap.

I'm no wiser :confused:

Bazzer
20-01-16, 21:47
Have a look at History zap that is the only difference I have noticed :D

Willmoore
20-01-16, 22:03
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

Bazzer
20-01-16, 22:10
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:

abu baniaz
21-01-16, 00:21
You can now see which satellite you are zapping back to.

judge
21-01-16, 02:42
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.