[VU+ Duo2] Spinning Vix

[Alanp]

from the last crashlog
its a C++ error somewhere.

added some stuff a while back to catch c++ errors

< 11370.871587> Backtrace:
< 11370.873208> /usr/bin/enigma2(_Z17handleFatalSignaliP9siginfo_tPv) [0x45D7D0]
< 11370.874591> -------FATAL SIGNAL

will need time to debug etc.

Would you recommend reverting back to Hades 010 in the meantime Thanks for your help its appreciated

 

[rossi2000]

if this issue is causing you grief, then ye
if not, stay on 11

so hades 10 is ok?

i havent seen this crash at all on a few different boxes.

 

[bellejt]

would it be possible to set the coach flash/updating to hades 10 instead of 11 ? Awaiting to find the bug.

 

[rossi2000]

you can couch flash back to build10 np

 

[pembo]

I need to look back through my posts... I'm pretty sure I've had this in previous versions of hades so isn't limited to build 011 only... let me check!

Updated - similar issue but slightly different address:

http://www.world-of-satellite.com/showthread.php?46023-Spinner-then-log-manager-crash

By the way - to add - after updating to 011, I've not had the problem since, but I suspect that's just coincidence, but I did do major surgery on my EPG since then to try and stop these issues.

 

[jtrus]

Just happened again this evening. Recording one programme while watching another recording. about 10-15mins into the I pressed OK on the remote to see the programme details, a little later noticed the spinning VIX. When the recording reached the end it just stopped and did not return to list of recordings. I used a telnet session to restart enigma2.
Hope this helps.

 

[pembo]

do you have a lot of 'dead' timers?

There's no spinner showing at the end of the log - and there was action after the previous spinner in the log with remote key presses.
There's quite a few timer/epg cache lookup events in the log at the end - hence the quesion

 

[jtrus]

Most timers are enabled, mainly to pick up new series. EG my wife is a fan of most of the cooking programmes such as Masterchef, so I leave the timer enabled ready for the next series. I got Brownie points when she realises the next series has started and she has missed the first episode
I copied the timers over from my ultimo about 2 weeks ago and they have been expanded over the years!
I could re-enable the ones on the ultimo and start again, but is is a real pain when I have filters set up. eg exclude SL in description so as to skip programmes with sign language.
I'm happy to try anything to help.
I'm out today but back this evening.

 

[tappari]

Let me take an example of this spinning ViX. When I move a movie from my Duo2 to my Synology Diskstation both connected with Gigabit switch ethernet having cat6 cables, I see spinning Vix if I return back watching tv. Shouldn`t the speed of Duo2 and Synology processors be fast ehough for ViX?

 

[pembo]

Let me take an example of this spinning ViX. When I move a movie from my Duo2 to my Synology Diskstation both connected with Gigabit switch ethernet having cat6 cables, I see spinning Vix if I return back watching tv. Shouldn`t the speed of Duo2 and Synology processors be fast ehough for ViX?

recreate it and post your debug log.

 

[gilvey]

Vix spinning every time I try to set up an auto timer in hades 11 on my technomate tm twin oe.
Also when I was using Hades 10 when zap was set up it crashed the box every time. Zap ok in hades 11
Though. Just need this auto timer bug sorting.

 

[rimas]

I deleted etc/enigma2/autotimer.xml, restarted enigma2 and the problem was gone. After that I was able to recreate all my autotimers without spinners. Now my box is running more then 24 hours without any problems

 

[bbbuk]

Can anyone else having problems try removing all their timers as mentioned in post above and adding each timer yourself to see if this solves problem.

 

[lincsat]

I don't think it's all the timers. I just deleted the autotimer event above and below the crash and it cured it. I suspect there is something in the .xml from certain timer entries that doesn't like.

 

[rimas]

I think something is changed in autoimer.xml format. Just deleting single event is not enough.
It's not that bad. I didn't lose all my timers entirely. They were still visible in EPG list (marked as autotimers). It helped a lot.

 

[bbbuk]

I don't think it's all the timers. I just deleted the autotimer event above and below the crash and it cured it. I suspect there is something in the .xml from certain timer entries that doesn't like.

I manually copied over the autotimer.xml file from hades 10 to 11 and, as yet, not noticed this issue. I never copy timer.xml file as I let the autotimer re-populate (all my timers are based on autotimers).

Mods/admin - was there any change in code to (auto)timer or something related to (auto)timer maybe?

 

[gilvey]

ok just done the above method of deleting autotimers.xml, started to go fine until i input e4 thurs 20.30 new big bang theory - ok
then try to set up e4 thurs 21.00 new brooklyn nine nine - continuous vix spinner

back to the drawing board.....................

 

[Alanp]

Can anyone else having problems try removing all their timers as mentioned in post above and adding each timer yourself to see if this solves problem.

Tried this problem still present

 

[pembo]

if you're having the problem and it's easy to recreate please post a debug log!
People could be having different problems, it could be the same problem, without debug logs and some investigation, everyone is just jumping to conclusions...

 

[bbbuk]

ok just done the above method of deleting autotimers.xml, started to go fine until i input e4 thurs 20.30 new big bang theory - ok
then try to set up e4 thurs 21.00 new brooklyn nine nine - continuous vix spinner

Ok, I added your two autotimers and immediately got the spinning vix.

Up until I added these two autotimers I never had this problem.

I will do further testing and enable debut logs for re-creating this spinning vix......