I’m afraid the number button fix did not work…
Edited by littlesat, 16 April 2024 - 22:28.
Posted 17 April 2024 - 07:56
Vu+DUO4KSE, DM920UHD, Vu+Uno4KSE, SF8008Mini, 2xPulse4K, Vu+Solo2, Dreambox DM500HD, Triax 78 (7E,9E,13E,19.2E,23.5E) & 2xTriax 78 (39E)
Posted 17 April 2024 - 09:36
So i was right the problem is the sorting of the menu which was not supported by the MainMenu addon.
Fixed with that: https://github.com/O...igma2/pull/3955
Vu+DUO4KSE, DM920UHD, Vu+Uno4KSE, SF8008Mini, 2xPulse4K, Vu+Solo2, Dreambox DM500HD, Triax 78 (7E,9E,13E,19.2E,23.5E) & 2xTriax 78 (39E)
Posted 17 April 2024 - 09:38
Also a build from 30 minutes ago doesn't have this issue.
It does however have another issue:
Traceback (most recent call last): File "/usr/lib/enigma2/python/Components/Addons/ColorButtonsSequence.py", line 52, in buildEntry if len(sequence) == 0: SystemError: <built-in function len> returned a result with an exception set Traceback (most recent call last): File "/usr/lib/enigma2/python/Screens/ChannelSelection.py", line 806, in updateEventInfo cur = self.getCurrentSelection() TypeError: 'float' object cannot be interpreted as an integer [ePyObject] (CallObject(<bound method SelectionEventInfo.updateEventInfo of <class 'Screens.ChannelSelection.ChannelSelection'>>,()) failed)so somewhere a division is introduced that should be an integer divison.
Is that on Kirkstone build? I dont get that here on normal nightly...
Vu+DUO4KSE, DM920UHD, Vu+Uno4KSE, SF8008Mini, 2xPulse4K, Vu+Solo2, Dreambox DM500HD, Triax 78 (7E,9E,13E,19.2E,23.5E) & 2xTriax 78 (39E)
Posted 17 April 2024 - 09:39
I did just update on a box.. and then it is working fine...
I checked it on that specific box and I indeed had some menu sort stuff inside that other box...
Without menu sort stuff...
[ActionMap] Keymap 'InfobarMenuActions' -> Action = 'mainMenu'. loading mainmenu XML... [ePNG] loadSVG /usr/share/enigma2/E2-DarkOS/menu/timer_edit.svg 48x48 from 192x192 [ePNG] loadSVG /usr/share/enigma2/E2-DarkOS/menu/info_screen.svg 48x48 from 192x192 [ePNG] loadSVG /usr/share/enigma2/E2-DarkOS/menu/plugin_selection.svg 48x48 from 192x192 [ePNG] loadSVG /usr/share/enigma2/E2-DarkOS/menu/setup_selection.svg 48x48 from 192x192 [ePNG] loadSVG /usr/share/enigma2/E2-DarkOS/menu/standby_restart_list.svg 48x48 from 192x192 [Skin] Processing screen 'menu_mainmenu' from list 'menu_mainmenu, Menu', position=(0, 0), size=(1920 x 1080) for module 'MainMenu'. [ePNG] loadSVG /usr/share/enigma2/logos/distrologo.svg 610x64 from 533x96 [Skin] No skin to read or screen to display. [Skin] Processing screen '<embedded-in-MenuSummary>', position=(0, 0), size=(0 x 0) for module 'MenuSummary'. [Screen] Showing screen 'MenuSummary'. [Screen] Showing screen '['menu_mainmenu', 'Menu']'.
WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W
Posted 17 April 2024 - 09:40
With menu sort stuff
[ActionMap] Keymap 'InfobarMenuActions' -> Action = 'mainMenu'. loading mainmenu XML... [ePNG] loadSVG /usr/share/enigma2/E2-DarkOS/menu/timer_edit.svg 48x48 from 192x192 [ePNG] loadSVG /usr/share/enigma2/E2-DarkOS/menu/info_screen.svg 48x48 from 192x192 [ePNG] loadSVG /usr/share/enigma2/E2-DarkOS/menu/plugin_selection.svg 48x48 from 192x192 [ePNG] loadSVG /usr/share/enigma2/E2-DarkOS/menu/setup_selection.svg 48x48 from 192x192 [ePNG] loadSVG /usr/share/enigma2/E2-DarkOS/menu/standby_restart_list.svg 48x48 from 192x192 [Skin] Processing screen 'menu_mainmenu' from list 'menu_mainmenu, Menu', position=(0, 0), size=(1920 x 1080) for module 'MainMenu'. [ePNG] loadSVG /usr/share/enigma2/logos/distrologo.svg 610x64 from 533x96 [Skin] Processing screen 'MenuSummary', position=(0, 0), size=(-1 x -1) for module 'MenuSummary'. [Screen] Showing screen 'MenuSummary'. [Screen] Showing screen '['menu_mainmenu', 'Menu']'. TypeError: buildEntry() takes 7 positional arguments but 8 were given [eListboxPythonMultiContent] error getting item 0 TypeError: buildEntry() takes 7 positional arguments but 8 were given [eListboxPythonMultiContent] error getting item 1 TypeError: buildEntry() takes 7 positional arguments but 8 were given [eListboxPythonMultiContent] error getting item 2 TypeError: buildEntry() takes 7 positional arguments but 8 were given [eListboxPythonMultiContent] error getting item 3 TypeError: buildEntry() takes 7 positional arguments but 8 were given [eListboxPythonMultiContent] error getting item 4
WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W
Posted 17 April 2024 - 09:42
Thanks merged....
That it only occurred when you reposition menu items also clarified why WanWizard and me initially could not verify the issue....
Edited by littlesat, 17 April 2024 - 09:43.
WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W
Posted 17 April 2024 - 14:13
Is that on Kirkstone build? I dont get that here on normal nightly...
Yes.
But Kirkstone is running the develop Enigma2, we haven't branched that yet. So if that is related, it may be caused by a different Python version?
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
Posted 17 April 2024 - 14:18
I also noticed that on screens that cause this crash, not all (or none at all) colour buttons are displayed at the bottom of the screen.
I'll see if I can do some tests...
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
Posted 17 April 2024 - 14:53
I can't really find the issue, this is the difference between develop (left) and kirkstone (right), with identical enigma2. Not only the buttons are not displayed, also the "multi-page" dots don't show.
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
Posted 17 April 2024 - 14:55
As to the crash, it can be reproduced (on kirkstone, not on develop) by pressing "right" in the troubleshoot section (menu - info - about - yellow - right ).
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
Posted 17 April 2024 - 15:06
As to the buttons, the debug log shows:
[Screen] Showing screen 'About'. LOGO PosX: 1724 [ePNG] loadSVG /usr/share/enigma2/logos/brandlogo.svg 84x34 from 192x126 TypeError: 'float' object cannot be interpreted as an integer The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/lib/enigma2/python/Components/Addons/ColorButtonsSequence.py", line 52, in buildEntry if len(sequence) == 0: SystemError: <built-in function len> returned a result with an exception set [eListboxPythonMultiContent] error getting item 0
which I assume is captured somewhere as it is not visable in the GUI.
I tried to add a print, but that results in
Traceback (most recent call last): File "/usr/lib/enigma2/python/Components/Addons/ColorButtonsSequence.py", line 52, in buildEntry print (sequence) TypeError: 'float' object cannot be interpreted as an integer
which I don't understand either.
And this time it already crashes when I press Yellow:
[ActionMap] Keymap 'ColorActions' -> Action = 'yellow'. [Skin] Processing screen 'Troubleshoot', position=(0, 0), size=(1920 x 1080) for module 'Troubleshoot'. [Skin] Attribute 'connection' (with value of 'key_red,key_green,key_yellow,key_blue') in object of type 'eListbox' is not implemented! [Skin] Attribute 'connection' (with value of 'Title,ScreenPath') in object of type 'eListbox' is not implemented! [Skin] Attribute 'titleFont' (with value of 'Bold; 28') in object of type 'eListbox' is not implemented! [Skin] Attribute 'connection' (with value of 'key_info,key_help,key_pvr,key_next,key_menu,key_previous,key_text,VKeyIcon') in object of type 'eListbox' is not implemented! [Skin] Attribute 'connection' (with value of 'AboutScrollLabel') in object of type 'eListbox' is not implemented! [eConsoleAppContainer] Starting /bin/sh [Skin] Processing screen 'SimpleSummary' from list 'Troubleshoot_summary, SimpleSummary', position=(0, 0), size=(480 x 320) for module 'SimpleSummary'. [Screen] Showing screen '['Troubleshoot_summary', 'SimpleSummary']'. [Screen] Showing screen 'Troubleshoot'. LOGO PosX: 1724 [ePNG] loadSVG /usr/share/enigma2/logos/brandlogo.svg 84x34 from 192x126 Traceback (most recent call last): File "/usr/lib/enigma2/python/Components/Addons/ServiceInfoBar.py", line 114, in checkCrypto_update service = NavigationInstance.instance.getCurrentService() TypeError: 'float' object cannot be interpreted as an integer [ePyObject] (CallObject(<bound method ServiceInfoBar.checkCrypto_update of <Components.Addons.ServiceInfoBar.ServiceInfoBar object at 0xaf182d48>>,()) failed) [gRC] Warning: Main thread is busy, displaying spinner! Killed
Edited by WanWizard, 17 April 2024 - 15:13.
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
Posted 17 April 2024 - 17:13
No. Its not number keys the problem.
Are you using custom menu sorting?
That might be the issue. But that can be confirmed with a log.
Yes, I had a custom menu sorting. After your correction Addon MainMenu.py today everything is ok.
1_0_1_20D_1_0_208AFC2_0_0_0_20240417181038.jpg 115.35KB 3 downloads
Octagon SF8008 4K Twin, Formuler F3, Vu+ Duo² Toroidal T-90 14°W -- 42°E
Posted 19 April 2024 - 19:48
The issue with the single left-aligned dot mentioned in https://forums.openp...dpost&p=1618465 still exists.
Any tips on how I can debug this? It suggests some calculations go wrong somewhere, possibly float vs int problems?
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
Posted 20 April 2024 - 07:36
As to the crash, it can be reproduced (on kirkstone, not on develop) by pressing "right" in the troubleshoot section (menu - info - about - yellow - right ).
Looks like it only happens on Kirkstone.......
Aan de rand van de afgrond is een stap voorwaarts niet altijd vooruitgang....
On the edge of the abyss, a step forward is not always progress....
Hardware: 2x Daily used Vu+ Ultimo 4K - Vu+ Duo 4K SE and a lot more.... - VisioSat BiBigsat - Jultec Unicable Multiswitch 4 positions: 19.2/23.5/28.2 East - Diseqc motorized flatdish antenna
Software : HomeBuild OpenPLi Develop and Scarthgap builds, local cards driven by OsCam
Press the button on the buttom right of this message
Have you tried our wiki yet? Many answers can be found in our OpenPLi wiki
Posted 20 April 2024 - 12:15
Indeed. It seems to be caused by a difference between Python 3.9.9 and 3.10.13, and it is specific to this skin, the standard skin doesn't have any issue.
Digging a bit in the release notes, I found:
Builtin and extension functions that take integer arguments no longer accept Decimals, Fractions and other objects that can be converted to integers only with a loss (e.g. that have the __int__() method but do not have the __index__() method). (Contributed by Serhiy Storchaka in bpo-37999.)
which may be the cause?
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
0 members, 4 guests, 0 anonymous users