Er zijn 55 reacties in dit onderwerp

[doglover]

When using Fastscan on the server receiver for TélésatBelgium an userbouquet with the name:  userbouquet.TéléSATBelgium.tv

is written.

 

This is all fine.

 

However when now on the fallback receiver the bouquet are automatically transferred, there is an error as the userbouquet.TéléSATBelgium.tv cannot be transferred.

An error is displayed.

 

Changing the name to:

 

userbouquet.TeleSATBelgium.tv

 

by replacing the é by e and everything is correct.

 

Could this be looked at?

 

Systems:

Server receiver OpenPLi 7.3 - HD2400

Fallbackreceiver:  OpenPLI develop - Zgemma Star S  (2021-03-24-develop)

[littlesat]

Do you have another file with invalid characters in the /etc/enigma2 directory? Or the file was rewritten back to the box via a windows pc and a settings editor? Here I cannot verify your issue...
Maybe we should simply remove the accents to this bouquet... as when files are transfered through different systems it can lead to issues.?

Veranderd door littlesat, 6 april 2021 - 15:05

[WanWizard]

This is from box to box, so that shouldn't be an issue. Sounds more like some code isn't utf-8 compliant.

 

Please note that one of the boxes runs 7.3, so it could be related to an issue already adressed.

[doglover]

Do you have another file with invalid characters in the /etc/enigma2 directory? Or the file was rewritten back to the box via a windows pc and a settings editor? Here I cannot verify your issue...
Maybe we should simply remove the accents to this bouquet... as when files are transfered through different systems it can lead to issues.?

No: file is created by the fast scan on the OpenPLi 7.3 box.

Did not touch it by anything.

 

Just tried on the OpenPLI develop to transfer the bouquetfiles with the option supplied in the menu.

The error occured on the develop image. 

Something in there does not like utf-8 characters.

Veranderd door doglover, 6 april 2021 - 15:35

[littlesat]

I have the bouquet here without issues????

[doglover]

The bouquet itself is no problem.

It opens on both OpenPLi 7.3 as on the develop.

 

The transfer from one box to the other with build in copy command goes wrong!!!!!

(also during the automatic transfer when you start the box)

 

Copying it with an external program is also no problem.

Veranderd door doglover, 6 april 2021 - 18:53

[littlesat]

I’m not able to verify that.... I’m also working with that import!!!! No issue with the transfer here!!!!! But here I’m working with develop and release 8.0.... with 7.3 I do not know.... but I’m afraid we will not fix it for 7.3. As far I remember owif had an issue that time. Please try 8.0 or develop on the server box.

Veranderd door littlesat, 6 april 2021 - 19:37

[doglover]

OK.  Fair enough you will not fix it in 7.3

 

At the moment OpenPLi 8.0 on the server box is a problem.  (Exteplayer has problems on that image)

Develop seems to work (exteplayer I mean) on my other player, but I hesitate to install develop on this receiver, as it is the main player. (and I am afraid my wife will complain if something is not working)

 

On the other hand the error is just the é characters in the name.  It is easy to get around it.

[littlesat]

Develop should not be any issue.... when you do not upgrade/update daily.... (before checking when there are big changes and nothing is reported on the forum). Please test first if you have the issue you experienced is solved on 8.0 or develop.

Veranderd door littlesat, 7 april 2021 - 08:03

[doglover]

So it is my own fault.

This reminds when I noticed that exteplayer in 8.0 and develop did not work anymore..  (some months ago)

Reaction:  it works fine here. 

 

Yes, on ARM boxes with plenty of memory.

 

A month later:  sorry we had problems with small memories and removed some files for these boxes.

Now develop works again. But I was intrinsically accused of causing the problem myself, because developers could not reproduce it.

[WanWizard]

Please remember:

• Not everyone has all hardware available to test with
• Not everyone has the skills to understand each and every commit made
• To avoid chasing ghosts, the latest develop needs to be tested first to make sure you're not experiencing an issue already fixed

Sometimes "I can't fix it because I can't reproduce it" means just that, we're not saying (or implying) you're an idiot, we are just saying we can't reproduct it so we don't know where to start looking...

[littlesat]

I just read later that you had the issue with 7.3 on a server box.... so I recommend to try 8.0 and then you are arguing about extreplayer on 8.0 an issue that should also be solved in between (I’m not aware in develop only)

Veranderd door littlesat, 7 april 2021 - 12:40

[WanWizard]

an issue that should also be solved in between (I’m not aware in develop only)

 

Only in develop.
 

[littlesat]

Then the solution for doglover is simple.... upgrade to develop... but do not upgrade from that moment daily on a box that should be stable

[doglover]

enigma in de bug mode:

loaded 316 channels/transponders and 6178 services
[Skin] Processing screen 'MessageBoxSimple', position=(340, 355), size=(600 x 10) for module 'MessageBox'.
[Screen] Warning: Skin is missing element 'WarningPixmap' in <class 'Screens.MessageBox.MessageBox'>(Import vanaf de Fallback tuner mislukt, Fout tijdens het downloaden van bestand /etc/enigma2/userbouquet.TéléSATBelgium.tv).
[Skin] Parsing embedded skin '<embedded-in-SimpleSummary>'.
[Skin] Processing screen '<embedded-in-SimpleSummary>' from list 'MessageBoxSimple_summary, SimpleSummary', position=(0, 0), size=(132 x 64) for module 'SimpleSummary'.
[Screen] Showing screen '['MessageBoxSimple_summary', 'SimpleSummary']'.
[Screen] Showing screen 'MessageBoxSimple'.
[Screen] Showing screen 'InfoBarSummary'.

And after renaming it to TeleSATBelgium

[eDVBDB] loaded 316 channels/transponders and 6178 services
[Skin] Processing screen 'MessageBoxSimple', position=(340, 355), size=(600 x 10) for module 'MessageBox'.
[Screen] Warning: Skin is missing element 'WarningPixmap' in <class 'Screens.MessageBox.MessageBox'>(Zenders geïmporteerd vanaf de Fallback tuner).
[Skin] Parsing embedded skin '<embedded-in-SimpleSummary>'.
[Skin] Processing screen '<embedded-in-SimpleSummary>' from list 'MessageBoxSimple_summary, SimpleSummary', position=(0, 0), size=(132 x 64) for module 'SimpleSummary'.
[Screen] Showing screen '['MessageBoxSimple_summary', 'SimpleSummary']'.
[Screen] Showing screen 'MessageBoxSimple'.
[Screen] Showing screen 'InfoBarSummary'.

 

[WanWizard]

What I notice: even the correct success message is displayed in the wrong characterset, aren't those strings from a po file?

 

Does is show like this on the box, or is this some copy/paste error somewhere, or perhaps a Windows terminal programme not it in utf-8?

Veranderd door WanWizard, 8 april 2021 - 00:05
changed post to English

[doglover]

This is just a copy/paste from the log.
Opened the log with PSpad.

Will post the complete log tommorow. (receiver is switched off now)

[doglover]

Sorry.

Opened the log with Geany and got this:

loaded 316 channels/transponders and 6178 services
[Skin] Processing screen 'MessageBoxSimple', position=(340, 355), size=(600 x 10) for module 'MessageBox'.
[Screen] Warning: Skin is missing element 'WarningPixmap' in <class 'Screens.MessageBox.MessageBox'>(Import vanaf de Fallback tuner mislukt, Fout tijdens het downloaden van bestand /etc/enigma2/userbouquet.TéléSATBelgium.tv).
[Skin] Parsing embedded skin '<embedded-in-SimpleSummary>'.
[Skin] Processing screen '<embedded-in-SimpleSummary>' from list 'MessageBoxSimple_summary, SimpleSummary', position=(0, 0), size=(132 x 64) for module 'SimpleSummary'.
[Screen] Showing screen '['MessageBoxSimple_summary', 'SimpleSummary']'.
[Screen] Showing screen 'MessageBoxSimple'.

[Skin] Processing screen 'MessageBoxSimple', position=(340, 355), size=(600 x 10) for module 'MessageBox'.
[Screen] Warning: Skin is missing element 'WarningPixmap' in <class 'Screens.MessageBox.MessageBox'>(Zenders geïmporteerd vanaf de Fallback tuner).
[Skin] Parsing embedded skin '<embedded-in-SimpleSummary>'.
[Skin] Processing screen '<embedded-in-SimpleSummary>' from list 'MessageBoxSimple_summary, SimpleSummary', position=(0, 0), size=(132 x 64) for module 'SimpleSummary'.
[Screen] Showing screen '['MessageBoxSimple_summary', 'SimpleSummary']'.
[Screen] Showing screen 'MessageBoxSimple'.

Notepad++ gives the same result.

 

Conclusion:  PSPad is crap..... (does not recognize the file correctly)

Checked and indeed opens it in Windows 1252.

 

Although I did not use a terminal window in this case.  I checked my terminal windows and they all are set to utf-8.

It should be surprised if it was not, because I am in general very well aware of this. 

Just PSPad caugth me by surprise.  Escpecially since PSPad normally does this correct.

 

 

PS: After I checked the fallback import Yesterday, I have updated the receiver with the debug still on.

So that info is also in the log

Bijgevoegde Bestanden

•  enigma.20210407.zip   11,28K   0 Aantal bijlagen

Veranderd door doglover, 8 april 2021 - 07:57

[WanWizard]

As I understand it, PSPad uses only a small section from the beginning of the file to autodetect the encoding.
If no UTF-8 characters are present in that section, it assumes the default encoding, which might be wrong.

 

Good you found the culprit.

 

I've setup a box with develop, with this:

bash-5.0# cat bouquets.tv 
#NAME User - bouquets (TV)
#SERVICE 1:7:1:0:0:0:0:0:0:0:FROM BOUQUET "userbouquet.Dutch.tv" ORDER BY bouquet
#SERVICE 1:7:1:0:0:0:0:0:0:0:FROM BOUQUET "userbouquet.English.tv" ORDER BY bouquet
#SERVICE 1:7:1:0:0:0:0:0:0:0:FROM BOUQUET "userbouquet.Movies.tv" ORDER BY bouquet
#SERVICE 1:7:1:0:0:0:0:0:0:0:FROM BOUQUET "userbouquet.HDChannels.tv" ORDER BY bouquet
#SERVICE 1:7:1:0:0:0:0:0:0:0:FROM BOUQUET "userbouquet.Freeview.tv" ORDER BY bouquet
#SERVICE 1:7:1:0:0:0:0:0:0:0:FROM BOUQUET "userbouquet.LastScanned.tv" ORDER BY bouquet
#SERVICE 1:7:1:0:0:0:0:0:0:0:FROM BOUQUET "userbouquet.TéléSATBelgium.tv" ORDER BY bouquet

and setup fallback with import on a second box, and got the same error. So the problem is still present in the current develop.

 

Bijgevoegde Bestanden

•  1_0_19_1B1C_802_2_11A0000_0_0_0_20210408122805.jpg   108,1K   2 Aantal bijlagen

[littlesat]

Mmmmm here it is my 3rd bouquet... wtf