Update 720

[duoduo]

Hi guys updated to version 720 this morning and now when the box restarts I an getting starting on front screen and the box is unresponsive for about half an hour before being able to work it again. I only did a full restart because on each occasion the picon wouldn't load. There is no debug logs because nothing has crashed. Please help/advise. Picons are on mounted usb ext4. Updated from version 714 previously.

[judge]

debug logs are different from crash logs.
enable them at Menu -> Setup -> System -> Logs -> Settings -> Enable debug log = yes
Then reboot & upload one after this happens.

[duoduo]

I have enabled them judge as soon as this blasted box starts I will look at what's showing. Its been 40 minutes and waiting, thank god the footys on itv .. Cheers

[duoduo]

Hi, please find all the debug logs on my reciever.

[judge]

what plugins have you installed?
might be worth reflashing as no issues with 720 here.

[duoduo]

tsmedia, cacheflush, sportsmax and iptv updater

[duoduo]

Sorry couldnt remove the previous ones, there are 2 new ones now which is the first 2.

[judge]

I don't use any of those, but no way should it take any box that long to become responsive to the remote.
Make a new back-up, fresh flash & restore settings/plugins in FIW.
If you then have the same issue, fresh flash without restore & try each plugin one by one.

[judge]

something funky happening with your picons, lots of:

[Trashcan] Failed to stat 1_0_19_3C_20D0_6B2_5A0000_0_0_0.png: [Errno 2] No such file or directory: '/media/hdd/.Trash/picon/1_0_19_3C_20D0_6B2_5A0000_0_0_0.png'
[Trashcan] Failed to stat 1_0_1_38E1_2648_FBFF_820000_0_0_0.png: [Errno 2] No such file or directory: '/media/hdd/.Trash/picon/1_0_1_38E1_2648_FBFF_820000_0_0_0.png'
[Trashcan] Failed to stat 1_0_19_71_271B_85_EB0000_0_0_0.png: [Errno 2] No such file or directory: '/media/hdd/.Trash/picon/1_0_19_71_271B_85_EB0000_0_0_0.png'

and

[eDVBRecordFileThread] cancelling
[eDVBRecordStreamThread] failed to cancel, killing all waiting IO
[eDVBRecordFileThread] poll: aio_return returned failure: Interrupted system call
[eDVBRecordFileThread] poll: aio_return returned failure: Interrupted system call
[eDVBRecordFileThread] poll: aio_return returned failure: Interrupted system call
[eDVBRecordFileThread] Waiting for I/O to complete
[eFilePushThreadRecorder] Warning: All write buffers busy
[eDVBRecordFileThread] cancelling

To be honest, I'd just fresh flash.

[duoduo]

I thought it may have something to do with the picons, keep having issues with them recently and not sure why. I have saved to USB, HDD, internal flash but in each location still having issues (obviously deleted from each location each time). Right now they show on EPG no problem but not on info bar, dont know how that can be?? Thank you for looking at this for me.

[judge]

ftp into the box & delete them all including any that might be in the trash can.
depending on how many you need/how many sats you have, if it's just 28.2 I'd put them on flash, root directory called picon.

[duoduo]

Problem is when I download the oscram shd transparent Picons from feeds it's not just 28.2 and these are the only ones I require.

[judge]

Downloading picons from the feeds can massively slow down any online updates if any changes have been made since last update.
So, during your update to build 720, something could have gone wrong.
I'm sure he has is own server or GIT where they can be downloaded manually, might be worth using that method rather than from the feeds if you want a faster online update.

[judge]

Also, I think but could easily be wrong here, but think those picons also come with a simlink to the picon with channel name, so not only have you to overwrite every picon, but also have to overwrite every simlink, so online update mightn't be the best for your box/network.
Personally, I never use picons from the feeds, but lots do without issues.
I just prefer to FTP them to the box so online updates take no more than a few minutes.

[Rob van der Does]

Seeing

[Skin] SKIN ERROR in SecondInfoBar: No module named VtiInfo
suggests you have something funky installed.

Really: you should reflash.