Whether the code will be closed or open is not for you to decide =) ..
If it started out as GPL code it's not for you to decide, no matter how much you've added to it. That's the relevant part here.
Whether the code will be closed or open is not for you to decide =) ..
If it started out as GPL code it's not for you to decide, no matter how much you've added to it. That's the relevant part here.
The crashlog is attached.
The crashlog is attached.
There is no line or letter of crash of my plugin in this log
< 754.144393> 01:16:30.9133 Traceback (most recent call last):
< 754.144450> 01:16:30.9134 File "/usr/lib/enigma2/python/Components/ActionMap.py", line 58, in action
< 754.144832> 01:16:30.9138 File "/usr/lib/enigma2/python/Screens/InfoBarGenerics.py", line 1894, in showDefaultINFO
< 754.145204> 01:16:30.9141 File "/usr/lib/enigma2/python/Screens/InfoBarGenerics.py", line 1920, in openEventView
< 754.145482> 01:16:30.9144 File "/usr/lib/enigma2/python/StartEnigma.py", line 150, in openWithCallback
< 754.147128> 01:16:30.9161 dialog = self.open(screen, *arguments, **kwargs)
< 754.147627> 01:16:30.9165 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
< 754.147749> 01:16:30.9167 File "/usr/lib/enigma2/python/StartEnigma.py", line 158, in open
< 754.148335> 01:16:30.9173 dialog = self.current_dialog = self.instantiateDialog(screen, *arguments, **kwargs)
< 754.148854> 01:16:30.9178 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
< 754.148895> 01:16:30.9178 File "/usr/lib/enigma2/python/StartEnigma.py", line 100, in instantiateDialog
< 754.149341> 01:16:30.9183 return self.doInstantiateDialog(screen, arguments, kwargs, self.desktop)
< 754.149809> 01:16:30.9187 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
< 754.149847> 01:16:30.9188 File "/usr/lib/enigma2/python/StartEnigma.py", line 127, in doInstantiateDialog
< 754.150239> 01:16:30.9192 dialog.applySkin()
< 754.150360> 01:16:30.9193 File "/usr/lib/enigma2/python/Screens/Screen.py", line 272, in applySkin
< 754.150694> 01:16:30.9196 File "/usr/lib/enigma2/python/Screens/Screen.py", line 304, in createGUIScreen
< 754.150970> 01:16:30.9199 File "/usr/lib/enigma2/python/Screens/EventView.py", line 100, in onCreate
< 754.151330> 01:16:30.9203 File "/usr/lib/enigma2/python/Plugins/Extensions/EPGTranslator/plugin.py", line 1096, in My_setEvent
< 754.151962> 01:16:30.9209 AttributeError: 'EventViewEPGSelect' object has no attribute 'EPGTr_translating'
Display More
In the log you provided, the EPGTranslator plugin crashes, which neither I nor my plugin has anything to do with. Please contact the author of the EPGTranslator plugin with this log, not me.
That plugin does not crash unless your plugin is installed.
This is an ongoing conflict between Epgtranslator and hzs that was reported a long time ago. You need to choose one of them to use. Once you install hzs, you will not be able to use Epgtranslator. I believe both plugins attempt to perform the same action, which is why the crashes occur.
This is an ongoing conflict between Epgtranslator and hzs that was reported a long time ago. You need to choose one of them to use. Once you install hzs, you will not be able to use Epgtranslator. I believe both plugins attempt to perform the same action, which is why the crashes occur.
No. The crash occurs because HZS doesn't run the intercepted call (EventViewBase.__init__())correctly.
If it did there would be no crash.
The result might not be exactly what is wanted, but there doesn't need to be a crash.
Of course, since the HZS code is not available we're not able to check this and fix it.
That plugin does not crash unless your plugin is installed.
You cannot use both together. If you wish to use this EPG Translator needs to be removed. It was on my todo list to look at the reasons why this is happening.
No. The crash occurs because HZS doesn't run the intercepted call (EventViewBase.__init__())correctly.
![]()
Let's start with the fact that the crash does not occur in my code ... it's this part of the crash log
Traceback (most recent call last):
File "/usr/lib/enigma2/python/Screens/Hotkey.py", line 580, in action
File "/usr/lib/enigma2/python/Screens/Hotkey.py", line 627, in hotkeyGlobal
File "/usr/lib/enigma2/python/Screens/Hotkey.py", line 671, in execHotkey
File "<string>", line 1, in <module>
File "/usr/lib/enigma2/python/Screens/InfoBarGenerics.py", line 1435, in openEventView
File "/usr/lib/enigma2/python/StartEnigma.py", line 296, in openWithCallback
dlg = self.open(screen, *arguments, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/enigma2/python/StartEnigma.py", line 306, in open
dlg = self.current_dialog = self.instantiateDialog(screen, *arguments, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/enigma2/python/StartEnigma.py", line 249, in instantiateDialog
return self.doInstantiateDialog(screen, arguments, kwargs, self.desktop)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/enigma2/python/StartEnigma.py", line 273, in doInstantiateDialog
dlg.applySkin()
File "/usr/lib/enigma2/python/Screens/Screen.py", line 261, in applySkin
File "/usr/lib/enigma2/python/Screens/Screen.py", line 293, in createGUIScreen
File "/usr/lib/enigma2/python/Screens/EventView.py", line 74, in onCreate
File "/usr/lib/enigma2/python/Plugins/Extensions/EPGTranslator/plugin.py", line 862, in My_setEvent
if not self.EPGTr_translating: return
Display More
After a little “digging” on the Internet I found some code ---> https://github.com/original-bi…Translator/plugin.py#L859
Having briefly analyzed the code, it became clear at once who is incorrectly and in the wrong place overriding classes =) .... But it's such a ... matter of taste, syntax and semantics ... In order to prevent your plugin from crashing, just add a check for the presence of an attribute of a class ... If you get bored, then analyze which class in which case you pass to My_setEvent ... And then wonder if the class ‘Screens.EventView.EventViewEPGSelect' has the attribute 'EPGTr_translating’ ... and what does this have to do with the above fantasies about EventViewBase.__init__() in the code of which you haven't seen .....
For a quick solution, just change the code like this
# If we aren't translating then we have nothing more to do...
#
if hasattr(self, 'EPGTr_translating') and not self.EPGTr_translating:
return
And your plugin will work in any variations with any plugins without any conflicts whatsoever
Снимок экрана 2025-07-19 в 13.10.40.pngСнимок экрана 2025-07-19 в 13.11.03.png
First pressing the EPG button on the RC - No crashes.
Снимок экрана 2025-07-19 в 13.12.33.png
Repeatedly pressing the EPG button on the RC
Снимок экрана 2025-07-19 в 13.13.41.png
Good luck !
Let's start with the fact that the crash does not occur in my code .
But it is a caused by your code as you've done something that means you've gone through the set-up code for EPGTranslator, but then wiped out part of the result of doing so and hence end up in part of my code without going through the associated initializing code despite these two thing being set-up at the same time.
As I've noted, were your code available I might be able to fix it, but since it isn't I'll have to let you stay with your bugged code. I see no reason to add unnecessary code to EPGTranslator to handle someone else's undisclosed oddities.
But it is a caused by your code
Somewhere above in any of the crash logs is there even a line or letter mentioning my code? Personally, I couldn't find one. Everything else is just idle chatter. I told you what to analyze. Open a thread discussing YOURS plugin, and I will write there what and where to fix. Quick solution for YOUR plugin - above. Everything works without any crashes.... No crashes at all!!
Good luck! ![]()
I see no reason to add unnecessary code to EPGTranslator to handle someone else's undisclosed oddities.
The code is yours. It's up to you. Those who need it to work can fix one line as I wrote above, and.... it will work.
The code is yours. It's up to you. Those who need it to work can fix one line as I wrote above, and.... it will work.
Pity I can't do that to yours and fix the real problem, rather then the symptom.
Somewhere above in any of the crash logs is there even a line or letter mentioning my code?
If you think that is relevant then you clearly have no idea about how enigma2 works. Or can't be bothered to think.
If you think that is relevant then you clearly have no idea about how enigma2 works. Or can't be bothered to think.
That's why HZS works on any images (including DreamOS-based) with any skins and translates descriptions directly into them
. Have you opened a topic on your plugin yet?
Good luck! ...
If the mountain won't come to Muhammad, Muhammad must go to the mountain ( (С)Hodja Nasreldin ).... I made a change to my plugin (2 lines) to play around with the nonsense of overriding the EventViewBase class in the EPG-Translator plugin code. Now my plugin will work without any problems together with EPG-Translator... The EPG-Translator will not crash when called, and its “proud” author doesn't need to make any changes to his code.
An update will be coming soon ...
UPDATE
1.0.45
1) Corrected installation package scripts to clean “tails” in opkg-list-files to avoid the error “unlink(”/tmp“) = 0” when uninstalling the plugin.
2) Made changes to the code to make the plugin compatible for simultaneous use with different versions of EPG-Translate plugin from different authors.
You need to give users the option to be able to turn off the country flag in their infobars. Its incredily annoying and distracting when it overwrites the picon every few seconds. Or just get rid of it entirely, its overkill, you have a notification pop up that can be turned on or off but not this.
Thanks for the new update
my gigablue goes nuts when I press the info button, yes epg trans. on bord, now they can live in peace
what is the best / optimum setup to use your plug? your plug feels its isolated from the system vs epg trans which easier access via info button.
You need to give users the option to be able to turn off the country flag in their infobars. Its incredily annoying and distracting when it overwrites the picon every few seconds. Or just get rid of it entirely, its overkill, you have a notification pop up that can be turned on or off but not this.
Ok, I will add this option to the settings
what is the best / optimum setup to use your plug? your plug feels its isolated from the system vs epg trans which easier access via info button.
I'm a little unclear about your question..... If we are talking about the translation of program descriptions, it is all done automatically when you call the standard EPG description window. There are two options - automatic translation and on demand. This is all configurable in the plugin settings
For example, I press the EPG button on the remote while watching a movie
Снимок экрана 2025-07-20 в 13.35.02.png
We see the description in Russian and a message that you can get a translation of the description into Ukrainian by pressing the “audio” button on the remote ... Press “audio.”
Снимок экрана 2025-07-20 в 13.35.23.png
In the same window (this is the window of the skin you use in the system), you will see a description in Ukrainian. Pressing the “Audio” button again will return the original description
Also available is an option to automatically translate to a given language ... for example, I have set the program descriptions to be automatically translated into English. When you press the “EPG” button on the RC, the description of the broadcast will be immediately displayed in the specified default language
Снимок экрана 2025-07-20 в 13.41.38.png
Also, automatic translation is available for SecondInfobar
Снимок экрана 2025-07-20 в 13.42.01.png
It works the same way if you stand on the channel list and press the “EPG” button. So you don't have to switch to a channel to get a translation of the program description (unlike any version of any EPG-Translate author).
Снимок экрана 2025-07-20 в 14.07.56.png
Press the "EPG" ('Info'") button
Снимок экрана 2025-07-20 в 14.08.44.png
What could be simpler and more convenient?
p.s. The way you set the combination of settings - so it will work ... The settings are “to the taste” and “at the will” of the users. Who likes it .. EPG-Translate plugin is not needed
. This plugin does everything by itself
I made a change to my plugin (2 lines) to play around with the nonsense of overriding the EventViewBase class in the EPG-Translator plugin code.
It's not an override (very specifically not an override). It intercepts it, calls the original (whatever was there at initialization time) then adds what EPGTranslator needs. You should have been doing the same from the start.
Glad you've finally found your bug that was affecting other code even without yours being mentioned in the crash log.
Don’t have an account yet? Register yourself now and be a part of our community!