View Full Version : [VU+ Duo2] Box crashes when I access EPG
Upgraded to version 6 a few weeks ago and keep getting box crashes. Today I took my time and box crashed when I tried to access EPG. I have zipped the crash log as its vast but can cut and paste if required.
Help
<337251.1752> 15:20:59.4899 [Skin] Attribute 'EntryFontWrap' (with value of 'no') in object of type 'eListbox' is not implemented!
<337251.4537> 15:20:59.7685 [Skin] Processing screen 'GraphicalEPGPIG_summary' from list 'GridEPGPIGSummary, GraphicalEPGPIGSummary, ScreenSummary, GridEPGPIG_summary, GraphicalEPGPIG_summary, SimpleSummary', position=(0, 0), size=(140 x 32) for module 'ScreenSummary'.
<337251.5412> 15:20:59.8560 UnicodeDecodeError: 'utf-8' codec can't decode byte 0xc9 in position 9: unexpected end of data
<337251.5414> 15:20:59.8561
The above exception was the direct cause of the following exception:
<337251.5416> 15:20:59.8563 SystemError: <class 'UnicodeDecodeError'> returned a result with an error set
<337251.5416> 15:20:59.8564
The above exception was the direct cause of the following exception:
<337251.5418> 15:20:59.8565 Traceback (most recent call last):
<337251.5419> 15:20:59.8566 File "/usr/lib/enigma2/python/Screens/EpgSelectionGrid.py", line 136, in loadEPGData
<337251.5474> 15:20:59.8621 self["list"].fillEPGNoRefresh(self.services)
<337251.5475> 15:20:59.8623 File "/usr/lib/enigma2/python/Components/EpgListGrid.py", line 791, in fillEPGNoRefresh
<337251.5562> 15:20:59.8710 epgData = self.queryEPG(test)
<337251.5564> 15:20:59.8711 File "/usr/lib/enigma2/python/Components/EpgListBase.py", line 158, in queryEPG
<337251.5593> 15:20:59.8741 return self.epgcache.lookupEvent(list)
<337251.5595> 15:20:59.8743 SystemError: <built-in function eEPGCache_lookupEvent> returned a result with an error set
<337251.5597> 15:20:59.8744 [ePyObject] (CallObject(<bound method EPGSelectionGrid.loadEPGData of <class 'Screens.EpgSelectionGrid.EPGSelectionGrid'>>,()) failed)
Upgraded to version 6 a few weeks ago and keep getting box crashes. Today I took my time and box crashed when I tried to access EPG. I have zipped the crash log as its vast but can cut and paste if required.
Help
can you do this:
Putty type init 4 (space between)
copy attachment to /usr/lib/enigma2/python/Components
Putty init 6 (space between)
post next crash log.
I have done that now and will report back.
Hi, box crashed again last night but was not able to post back.
Trying to read the data on the crash and mentions skin issues and wonder if this is a new edition added and causing the crash and maybe try another skin??
... it looks like it's just got extra debugging details.
Run the attached file for a while and then get the debug log.
This just looks like another EPG data de(en?)coding error.
Related to this thread?
https://www.world-of-satellite.com/showthread.php?64907-Crash-in-InfoBarGenerics&p=521220
This just looks like another EPG data de(en?)coding error.
Related to this thread?
https://www.world-of-satellite.com/showthread.php?64907-Crash-in-InfoBarGenerics&p=521220No, that is junk in the epg. This is junk in the user's bouquet files. Most likely using Latin1 instead of UTF8.
got another crash today but this time I was trying to set a recording. Here is the log.
got another crash today but this time I was trying to set a recording. Here is the log.How old is that image? This was fixed weeks ago.
https://github.com/OpenViX/enigma2/commit/699acac8140a60fac1cd9dbc3301bb69dc0a2c96#diff-4d8ed2d3906a32145ab9f879a5e6a7b37cca47fc2d7d8c5240 52ae95f43606e4
abu baniaz
12-01-22, 22:20
Please update your image to 6.0 006 to include fixes since 6.0 004
P.S
There is no need to zip your crash logs.
well I updated to latest vix and restored settings and plugins ... and it still crashes. here is the log. It happened when I pressed the text key and it happened when I pressed EPG key.
I may try a clean install as a last resort or I might go back to ver 5.
< 1522.4397> 18:18:12.9675 [Skin] Processing screen 'GraphicalEPGPIG_summary' from list 'GridEPGPIGSummary, GraphicalEPGPIGSummary, ScreenSummary, GridEPGPIG_summary, GraphicalEPGPIG_summary, SimpleSummary', position=(0, 0), size=(140 x 32) for module 'ScreenSummary'.
< 1522.5589> 18:18:13.0867 UnicodeDecodeError: 'utf-8' codec can't decode byte 0xc9 in position 2: invalid continuation byte
< 1522.5590> 18:18:13.0868
The above exception was the direct cause of the following exception:
< 1522.5593> 18:18:13.0871 SystemError: <class 'UnicodeDecodeError'> returned a result with an error set
< 1522.5594> 18:18:13.0872
The above exception was the direct cause of the following exception:
< 1522.5595> 18:18:13.0873 Traceback (most recent call last):
< 1522.5596> 18:18:13.0874 File "/usr/lib/enigma2/python/Screens/EpgSelectionGrid.py", line 136, in loadEPGData
< 1522.5619> 18:18:13.0897 self["list"].fillEPGNoRefresh(self.services)
< 1522.5622> 18:18:13.0900 File "/usr/lib/enigma2/python/Components/EpgListGrid.py", line 791, in fillEPGNoRefresh
< 1522.5685> 18:18:13.0963 epgData = self.queryEPG(test)
< 1522.5687> 18:18:13.0965 File "/usr/lib/enigma2/python/Components/EpgListBase.py", line 158, in queryEPG
< 1522.5707> 18:18:13.0985 return self.epgcache.lookupEvent(list)
< 1522.5709> 18:18:13.0987 SystemError: <built-in function eEPGCache_lookupEvent> returned a result with an error set
< 1522.5713> 18:18:13.0991 [ePyObject] (CallObject(<bound method EPGSelectionGrid.loadEPGData of <class 'Screens.EpgSelectionGrid.EPGSelectionGrid'>>,()) failed)
abu baniaz
13-01-22, 19:36
If you perform a software update, there is no need to restore settings and plugins. You would only do that after flashing an image.
Anyway, can you delete the EPG cache. Then flash the latest image, (6.0 006), but not restore settings and plugins this time? Please also re-add the file by Huevos, this will get debug of issue.
abu baniaz
13-01-22, 19:44
Which channel list do you have installed on your box?
If you don't have softcams, please upload the settings backup for someone to try. Once again, only if you are not using softcams.
As Abu has said you need to get the debug by installing the Huevos change.
In the meantime how do you create your IPTV bouquets (which are the cause of the problem)- which app??
I could not do a software update online it hung on ...waiting. I just flashed 0006 without restoring anything i.e set up from scratch, and then added the usual bits, like crossepg, epg refresh. softcams, and a motorised channel list. This time when I clicked on AUTOBOUQUETMAKER box crashed. I'll run that file now but don't know how to clear epg cache.
I have not messed with this box in years and I'm getting rusty.
Maybe box has got a fault.
Thanks for help.
< 8070.9054> 22:06:35.3985 [Skin] Processing screen 'AutoBouquetsMaker_MenuSummary' from list 'AutoBouquetsMaker_MenuSummary, SetupSummary', position=(0, 0), size=(140 x 32) for module 'AutoBouquetsMaker_MenuSummary'.
< 8070.9279> 22:06:35.4210 [Skin] Processing screen 'AutoBouquetsMaker_Setup', position=(0, 0), size=(1920 x 1080) for module 'AutoBouquetsMaker_Setup'.
< 8070.9663> 22:06:35.4594 [Screen] Warning: Skin is missing element 'HelpWindow' in <class 'Plugins.SystemPlugins.AutoBouquetsMaker.setup.Aut oBouquetsMaker_Setup'>.
< 8071.0072> 22:06:35.5003 [Skin] Processing screen 'SetupSummary', position=(0, 0), size=(140 x 32) for module 'SetupSummary'.
< 8071.0177> 22:06:35.5107 [eInputDeviceInit] 0 160 (352) 1
< 8071.0177> 22:06:35.5108 [eRCDeviceInputDev] emit: 0
< 8071.0196> 22:06:35.5127 [InfoBarGenerics] Key: 352 (Break) KeyID='KEY_OK' Binding='('OK',)'.
< 8071.0437> 22:06:35.5368 Traceback (most recent call last):
< 8071.0440> 22:06:35.5371 File "/usr/lib/enigma2/python/Plugins/SystemPlugins/AutoBouquetsMaker/setup.py", line 478, in prepare
< 8071.0468> 22:06:35.5399 bouquets = Manager().getBouquetsList()
< 8071.0471> 22:06:35.5402 File "/usr/lib/enigma2/python/Plugins/SystemPlugins/AutoBouquetsMaker/scanner/manager.py", line 299, in getBouquetsList
< 8071.0498> 22:06:35.5429 return BouquetsReader().getBouquetsList(self.path)
< 8071.0499> 22:06:35.5430 File "/usr/lib/enigma2/python/Plugins/SystemPlugins/AutoBouquetsMaker/scanner/bouquetsreader.py", line 46, in getBouquetsList
< 8071.0512> 22:06:35.5442 ret[bouquet_type] = self.parseBouquetIndex(path, content)
< 8071.0514> 22:06:35.5444 File "/usr/lib/enigma2/python/Plugins/SystemPlugins/AutoBouquetsMaker/scanner/bouquetsreader.py", line 23, in parseBouquetIndex
< 8071.0523> 22:06:35.5454 firstline = bouquet.read().split("\n")[0]
< 8071.0524> 22:06:35.5455 File "/usr/lib/python3.9/codecs.py", line 322, in decode
< 8071.0543> 22:06:35.5474 (result, consumed) = self._buffer_decode(data, self.errors, final)
< 8071.0545> 22:06:35.5476 UnicodeDecodeError: 'utf-8' codec can't decode byte 0xb0 in position 137: invalid start byte
< 8071.0547> 22:06:35.5478 [ePyObject] (CallObject(<bound method AutoBouquetsMaker_Setup.prepare of <class 'Plugins.SystemPlugins.AutoBouquetsMaker.setup.Aut oBouquetsMaker_Setup'>>,()) failed)
I only tried iptv bouquets last week and in truth I was just messing ie do not know what I am doing. And I can do without them.
From memory, menu/setup/Epg/load, save and delete epg cache
abu baniaz
13-01-22, 23:45
Forget the EPG, it is one of the bouquets as mentioned by Huevos in post 9.
Which channel list have you installed?
well I updated to latest vix and restored settings and plugins ... and it still crashes. here is the log. It happened when I pressed the text key and it happened when I pressed EPG key.
I may try a clean install as a last resort or I might go back to ver 5.
< 1522.4397> 18:18:12.9675 [Skin] Processing screen 'GraphicalEPGPIG_summary' from list 'GridEPGPIGSummary, GraphicalEPGPIGSummary, ScreenSummary, GridEPGPIG_summary, GraphicalEPGPIG_summary, SimpleSummary', position=(0, 0), size=(140 x 32) for module 'ScreenSummary'.
< 1522.5589> 18:18:13.0867 UnicodeDecodeError: 'utf-8' codec can't decode byte 0xc9 in position 2: invalid continuation byte
< 1522.5590> 18:18:13.0868
The above exception was the direct cause of the following exception:
< 1522.5593> 18:18:13.0871 SystemError: <class 'UnicodeDecodeError'> returned a result with an error set
< 1522.5594> 18:18:13.0872
The above exception was the direct cause of the following exception:
< 1522.5595> 18:18:13.0873 Traceback (most recent call last):
< 1522.5596> 18:18:13.0874 File "/usr/lib/enigma2/python/Screens/EpgSelectionGrid.py", line 136, in loadEPGData
< 1522.5619> 18:18:13.0897 self["list"].fillEPGNoRefresh(self.services)
< 1522.5622> 18:18:13.0900 File "/usr/lib/enigma2/python/Components/EpgListGrid.py", line 791, in fillEPGNoRefresh
< 1522.5685> 18:18:13.0963 epgData = self.queryEPG(test)
< 1522.5687> 18:18:13.0965 File "/usr/lib/enigma2/python/Components/EpgListBase.py", line 158, in queryEPG
< 1522.5707> 18:18:13.0985 return self.epgcache.lookupEvent(list)
< 1522.5709> 18:18:13.0987 SystemError: <built-in function eEPGCache_lookupEvent> returned a result with an error set
< 1522.5713> 18:18:13.0991 [ePyObject] (CallObject(<bound method EPGSelectionGrid.loadEPGData of <class 'Screens.EpgSelectionGrid.EPGSelectionGrid'>>,()) failed)
This is because you are not using the EpgList file I posted a few days ago in this topic.
I could not do a software update online it hung on ...waiting. I just flashed 0006 without restoring anything i.e set up from scratch, and then added the usual bits, like crossepg, epg refresh. softcams, and a motorised channel list. This time when I clicked on AUTOBOUQUETMAKER box crashed. I'll run that file now but don't know how to clear epg cache.
I have not messed with this box in years and I'm getting rusty.
Maybe box has got a fault.
Thanks for help.
< 8070.9054> 22:06:35.3985 [Skin] Processing screen 'AutoBouquetsMaker_MenuSummary' from list 'AutoBouquetsMaker_MenuSummary, SetupSummary', position=(0, 0), size=(140 x 32) for module 'AutoBouquetsMaker_MenuSummary'.
< 8070.9279> 22:06:35.4210 [Skin] Processing screen 'AutoBouquetsMaker_Setup', position=(0, 0), size=(1920 x 1080) for module 'AutoBouquetsMaker_Setup'.
< 8070.9663> 22:06:35.4594 [Screen] Warning: Skin is missing element 'HelpWindow' in <class 'Plugins.SystemPlugins.AutoBouquetsMaker.setup.Aut oBouquetsMaker_Setup'>.
< 8071.0072> 22:06:35.5003 [Skin] Processing screen 'SetupSummary', position=(0, 0), size=(140 x 32) for module 'SetupSummary'.
< 8071.0177> 22:06:35.5107 [eInputDeviceInit] 0 160 (352) 1
< 8071.0177> 22:06:35.5108 [eRCDeviceInputDev] emit: 0
< 8071.0196> 22:06:35.5127 [InfoBarGenerics] Key: 352 (Break) KeyID='KEY_OK' Binding='('OK',)'.
< 8071.0437> 22:06:35.5368 Traceback (most recent call last):
< 8071.0440> 22:06:35.5371 File "/usr/lib/enigma2/python/Plugins/SystemPlugins/AutoBouquetsMaker/setup.py", line 478, in prepare
< 8071.0468> 22:06:35.5399 bouquets = Manager().getBouquetsList()
< 8071.0471> 22:06:35.5402 File "/usr/lib/enigma2/python/Plugins/SystemPlugins/AutoBouquetsMaker/scanner/manager.py", line 299, in getBouquetsList
< 8071.0498> 22:06:35.5429 return BouquetsReader().getBouquetsList(self.path)
< 8071.0499> 22:06:35.5430 File "/usr/lib/enigma2/python/Plugins/SystemPlugins/AutoBouquetsMaker/scanner/bouquetsreader.py", line 46, in getBouquetsList
< 8071.0512> 22:06:35.5442 ret[bouquet_type] = self.parseBouquetIndex(path, content)
< 8071.0514> 22:06:35.5444 File "/usr/lib/enigma2/python/Plugins/SystemPlugins/AutoBouquetsMaker/scanner/bouquetsreader.py", line 23, in parseBouquetIndex
< 8071.0523> 22:06:35.5454 firstline = bouquet.read().split("\n")[0]
< 8071.0524> 22:06:35.5455 File "/usr/lib/python3.9/codecs.py", line 322, in decode
< 8071.0543> 22:06:35.5474 (result, consumed) = self._buffer_decode(data, self.errors, final)
< 8071.0545> 22:06:35.5476 UnicodeDecodeError: 'utf-8' codec can't decode byte 0xb0 in position 137: invalid start byte
< 8071.0547> 22:06:35.5478 [ePyObject] (CallObject(<bound method AutoBouquetsMaker_Setup.prepare of <class 'Plugins.SystemPlugins.AutoBouquetsMaker.setup.Aut oBouquetsMaker_Setup'>>,()) failed)
This is because you have junk in one of your bouquet files (not proper UTF8). What settings files have you loaded? Have you used DBE?
Ok I have time today to sort it. Here is the latest crash log but this time I think its the settings file, I used malimali. motor settings and these have a bouquet layout. I normally use catseyes but too lazy this time. I will load cats and hope that sorts it. I'll report back.
Let's see if we can get ABM to ignore the junk in your bouquet files.
Add the attached file. It goes in:
/usr/lib/enigma2/python/Plugins/SystemPlugins/AutoBouquetsMaker/scanner
Restart enigma and do an ABM scan.
Good news. I loaded catseyes channel settings and everything now works again and faster. I assumed a channel listing in plugins would work. I have had it going for the last few hours and did the usual run autobouquets, add a few channels and so on.
I have not touched epg yet but all I do is get a full listing for cnn hd and c4hd.
I use the text button quite a bit and wonder does that have a secondary function ie if I press it and not on the channel with text? Which I can do? I only downloaded xcplugin and thats even better.
I think I'm but will be a bit more careful.
Thanks for help.
abu baniaz
14-01-22, 17:03
Let's see if we can get ABM to ignore the junk in your bouquet files.
Add the attached file. It goes in:
/usr/lib/enigma2/python/Plugins/SystemPlugins/AutoBouquetsMaker/scanner
Restart enigma and do an ABM scan.
Tested that file with Malimali motorised channel list. It works and does not crash on UTF error.
I have the same problem.
box: Mut@nt HD2400
image: OpenViX 6.2.010 (2022-09-19)
I have the same problem.
box: Mut@nt HD2400
image: OpenViX 6.2.010 (2022-09-19)Which channel are you opening the EPG on?
It crashes at any (DVB-C, DVB-T, DVB-S) channel in any bouquet.
Bouquets were created in openvix-5.4.016.
In Satellites EPG works properly. (epg1, epg2, epg3)
I tried to create a new bouquet, but "add service to bouquet" also crashes. (crash log)
If I make a new scan for the channel selected in Satellites (epg4) the EPG from the Last Scanned bouquet also crashes.
It seems, that the problem is with bouqets as described in the discussion before, but the attachments (EpgListBase.py, bouquetsreader.py) do not solve the problem.
It crashes at any (DVB-C, DVB-T, DVB-S) channel in any bouquet.
Bouquets were created in openvix-5.4.016.
In Satellites EPG works properly. (epg1, epg2, epg3)
I tried to create a new bouquet, but "add service to bouquet" also crashes. (crash log)
If I make a new scan for the channel selected in Satellites (epg4) the EPG from the Last Scanned bouquet also crashes.
It seems, that the problem is with bouqets as described in the discussion before, but the attachments (EpgListBase.py, bouquetsreader.py) do not solve the problem.How are you creating the bouquets?
What provider?
What country/language?
How are you creating the bouquets?
I created the bouquets "completely regularly" in openvix-5.4: create bouquet, add service to bouquet.
Openvix-6.2 install brought them back from the vix-mutant2400-rel-5.4.016-20221014-0900.tar.gz backup.
I am not able to create a new bouquet, as the "Add service to bouquet" crashes in the new system (see the previous crash log).
But I deleted the "Last Scanned bouquet" and started a scan, so the "Last Scanned bouquet" is created by the new (openvix-6.2.010) system.
The EPG crashes in this, also.
What provider?
It doesn't depend on that!
EPG crashes at all channels in the bouquet, meanwhile everything is working in "Satellites" (see jpg-s attached in the previous post)
What country/language?
System language is English.
The language of the EPG-s tested are most different: Hungarian, English, German, Greek, ...
Summarized:
If starting from "Satellites" (see epg1.jpg) all EPG-s are working, starting from bouquet (old or newly created as well) causes a crash at each trial.
It would seem there is bad encoding in the channels you are trying to add.
5.4.016 was python 2. That would ignore bad encoding.
First put the bouquets in a zip and post on here.
Then create an empty bouquet and try adding to that.
Report the result.
I got it !
#NAME SAT - 9°E - Eutelsat 9B / Ka-Sat @ 9° E
The symbol ° interferes.
There were a few bouquets with that, but most of the bouquetnames did not contain it.
After deleting ° symbols from #NAME, everything works.
It's interesting, that in rows 2-3 it does not make any problem:
#SERVICE 1:64:9:0:0:0:0:0:0:0::=== Eutelsat 9B / Ka-Sat @ 9° E ===
#DESCRIPTION === Eutelsat 9B / Ka-Sat @ 9° E ===
The more interesting, that despite of that, the bouquet is visible, the channel selection works,
and it is even editable (rename, move),
only the EPG asked from all bouquets crashes (started from bouquets not containing the ° symbol as well)
and the "add service to bouquet" function also crashes, while it is not known to which bouquet I want to add the channel.
By the way, e.g. the ° symbol is acceptable in the Slovak code table of VIX.
64350
This is a sw failure, isn't it ?
I got it !
#NAME SAT - 9°E - Eutelsat 9B / Ka-Sat @ 9° E
The symbol ° interferes.
There were a few bouquets with that, but most of the bouquetnames did not contain it.
After deleting ° symbols from #NAME, everything works.
It's interesting, that in rows 2-3 it does not make any problem:
#SERVICE 1:64:9:0:0:0:0:0:0:0::=== Eutelsat 9B / Ka-Sat @ 9° E ===
#DESCRIPTION === Eutelsat 9B / Ka-Sat @ 9° E ===
The more interesting, that despite of that, the bouquet is visible, the channel selection works,
and it is even editable (rename, move),
only the EPG asked from all bouquets crashes (started from bouquets not containing the ° symbol as well)
and the "add service to bouquet" function also crashes, while it is not known to which bouquet I want to add the channel.
By the way, e.g. the ° symbol is acceptable in the Slovak code table of VIX.
64350
This is a sw failure, isn't it ?
The issue is how the symbol was originally encoded, and if the encoding is not utf-8 then there is likely to be an íssue
The issue is how the symbol was originally encoded, and if the encoding is not utf-8 then there is likely to be an íssueAlthough I'd argue that shouldn't make Vix crash (i.e. make it unusable). It should just display the offending part using 'backslashreplace' (or 'surrogateescape').
Although I'd argue that shouldn't make Vix crash (i.e. make it unusable). It should just display the offending part using 'backslashreplace' (or 'surrogateescape').??? This is a c++ crash. Those files are read and written by c++.
If you know the best way to fix please send a pull request.
??? This is a c++ crash. Those files are read and written by c++.
<337251.5412> 15:20:59.8560 UnicodeDecodeError: 'utf-8' codec can't decode byte 0xc9 in position 9: unexpected end of dataA UnicodeDecodeError looks like Python to me...
A UnicodeDecodeError looks like Python to me...
1) That is a c++ exception. It happens before the result is returned to python (SWIG).
<337251.5416> 15:20:59.8563 SystemError: <class 'UnicodeDecodeError'> returned a result with an error set
2) That is not the crash we are talking about anyway but if you know how to fix it that would be helpful. Or are you talking about the crash in ABM that was fixed last January? https://github.com/oe-alliance/AutoBouquetsMaker/commit/30765e68640906faaaae2b3bf3da2010d0306725
3) Currently that c++ exception is protected by a try/except but that leaves a hole in EPG data.
4) The following is the crash we are talking about.
< 37259.6921> [eRCDeviceInputDev] emit: 1
< 37259.6927> [InfoBarGenerics] Key: 352 (Make) KeyID='KEY_OK' Binding='('OK',)'.
< 37259.6929> [ActionMap] Keymap 'OkCancelActions' -> Action = 'ok'.
< 37259.7005> [Skin] Processing screen 'BouquetSelector', position=(0, 0), size=(1920 x 1080) for module 'BouquetSelector'.
< 37259.7344> [Skin] Processing screen 'SimpleSummary' from list 'BouquetSelectorSummary, ScreenSummary, BouquetSelector_summary, SimpleSummary', position=(0, 0), size=(255 x 64) for module 'ScreenSummary'.
< 37259.8462> PC: 75c14bd4
< 37259.8462> 00000000 00000001 00000000 7705a020
< 37259.8462> 0000762f 0000762f 00000006 00000000
< 37259.8462> 00000007 00000001 75d40000 75d80000
< 37259.8463> 75d400f4 75d78c24 75d78c3c 75ebf3c8
< 37259.8463> 0000762f 75d30000 75d30000 00000006
< 37259.8463> 00000001 00000000 04b3c4a8 01231bcc
< 37259.8463> 00000018 75c51b90 00000000 00000000
< 37259.8463> 75d34580 7fb84910 00000000 75c14bc0
< 37259.8466> Backtrace:
< 37259.8471> /usr/bin/enigma2(_Z17handleFatalSignaliP9siginfo_tPv) [0x46F058]
< 37259.8472> linux-vdso.so.1(n/a) [0x77099540]
< 37259.8474> /lib/libc.so.6(n/a) [0x75C14BD4]
< 37259.8476> /lib/libc.so.6(gsignal) [0x75BCDC3C]
< 37259.8478> /lib/libc.so.6(abort) [0x75BB86B8]
< 37259.8478> -------FATAL SIGNAL (6)
1) That is a c++ exception. It happens before the result is returned to python (SWIG).Agreed, but I think it happens after python passes in a "string" that isn't utf-8?
4) The following is the crash we are talking about.
.....
No idea about that one
4) The following is the crash we are talking about.
< 37259.6921> [eRCDeviceInputDev] emit: 1
< 37259.6927> [InfoBarGenerics] Key: 352 (Make) KeyID='KEY_OK' Binding='('OK',)'.
< 37259.6929> [ActionMap] Keymap 'OkCancelActions' -> Action = 'ok'.
< 37259.7005> [Skin] Processing screen 'BouquetSelector', position=(0, 0), size=(1920 x 1080) for module 'BouquetSelector'.
< 37259.7344> [Skin] Processing screen 'SimpleSummary' from list 'BouquetSelectorSummary, ScreenSummary, BouquetSelector_summary, SimpleSummary', position=(0, 0), size=(255 x 64) for module 'ScreenSummary'.
< 37259.8462> PC: 75c14bd4
< 37259.8462> 00000000 00000001 00000000 7705a020
< 37259.8462> 0000762f 0000762f 00000006 00000000
< 37259.8462> 00000007 00000001 75d40000 75d80000
< 37259.8463> 75d400f4 75d78c24 75d78c3c 75ebf3c8
< 37259.8463> 0000762f 75d30000 75d30000 00000006
< 37259.8463> 00000001 00000000 04b3c4a8 01231bcc
< 37259.8463> 00000018 75c51b90 00000000 00000000
< 37259.8463> 75d34580 7fb84910 00000000 75c14bc0
< 37259.8466> Backtrace:
< 37259.8471> /usr/bin/enigma2(_Z17handleFatalSignaliP9siginfo_tPv) [0x46F058]
< 37259.8472> linux-vdso.so.1(n/a) [0x77099540]
< 37259.8474> /lib/libc.so.6(n/a) [0x75C14BD4]
< 37259.8476> /lib/libc.so.6(gsignal) [0x75BCDC3C]
< 37259.8478> /lib/libc.so.6(abort) [0x75BB86B8]
< 37259.8478> -------FATAL SIGNAL (6)
Most likely it crashes when trying to display character. To fix it you would need to find out where it uses that string.
Fix could then be similar as in movielist.py, chardet.detect()
Ofcourse C++ code should also be fixed so that it does not crash. I did mention this before here:
https://www.world-of-satellite.com/showthread.php?65365-Crash-when-folder-contains-filenames-with-Windows-encoding/page9
Most likely it crashes when trying to display character. To fix it you would need to find out where it uses that string.
Fix could then be similar as in movielist.py, chardet.detect()
Ofcourse C++ code should also be fixed so that it does not crash. I did mention this before here:
https://www.world-of-satellite.com/showthread.php?65365-Crash-when-folder-contains-filenames-with-Windows-encoding/page9
It is a "º" in a bouquet file causes the crash when trying to add an additional channel to the bouquet... but the bouquet is from Py2 version. So first test he need to do is create the bouquet file using the current version.
Agreed, but I think it happens after python passes in a "string" that isn't utf-8?No. The service ref is passed to EPGCache. The junk is in the EPG data. The return value from EPGCache to python is returned with the exception set. There is a workaround in python to avoid the crash. https://github.com/OpenViX/enigma2/commit/bb349e0c259b3ac20084d2e54421e2f8facb78cc but we need to workout how the junk data is getting in. Maybe the wrong encoding flag is being sent in the SI table, or none at all.
No. The service ref is passed to EPGCache. The junk is in the EPG data.That was certainly the case several years ago.
Anything using externally-supplied data should be able to get by without crashing regardless of what is sent, since in practice you have no control over it.
There is nothing wrong with the query. You can even play with the duration and find out exactly which program is responsible, but not part (title, description, etc).
The exception is return from this function: https://github.com/OpenViX/enigma2/blob/Developer/lib/dvb/epgcache.h#L221
I would be interested in feedback from @ocean.
There is nothing wrong with the query. You can even play with the duration and find out exactly which program is responsible, but not part (title, description, etc).So your saying that the error is in the EPG data itself?
So that should be validated before it gets put into place.
So your saying that the error is in the EPG data itself?
So that should be validated before it gets put into place.Yes the junk is in the EPG data already in the cache. If you know how to validate that on entry please be my guest.
Yes the junk is in the EPG data already in the cache. If you know how to validate that on entry please be my guest.If it's being downloaded and inserted than that program can (and should) do it.
EIT data might be more of a problem, but I suspect there's just one location...
If it's being downloaded and inserted than that program can (and should) do it.
EIT data might be more of a problem, but I suspect there's just one location...Pretty sure it is junk in eit, or no encoding specified in eit. I tested here locally and it was crashing for me on one channel. Right now I can't remember the channel. :(
Powered by vBulletin® Version 4.2.5 Copyright © 2024 vBulletin Solutions Inc. All rights reserved.