Manual update doesn't work - 8.95.2 -> 8.95.3

Help & Support Installation & Booting
1

Hi,

I keep getting notification about the latest update for CE, but when I go to update it via the CE addon, it shows blank update channels and versions.

There’s not much debug information in the logfile from the CE addon update functions. The only error I get, is when I exit the blank versions window.

Excerpt from the debug log (I’m not allowed to attach the full log):

18:59:40.784 T:4090426976   DEBUG: ------ Window Init (DialogSelect.xml) ------
18:59:40.784 T:4090426976    INFO: Loading skin file: DialogSelect.xml, load type: KEEP_IN_MEMORY
18:59:44.978 T:4080006000   DEBUG: CLibInputKeyboard::ProcessKey - using delay: 500ms repeat: 33ms
18:59:44.978 T:3700556656   DEBUG: Thread Timer start, auto delete: false
18:59:45.009 T:4090426976   DEBUG: Keyboard: scancode: 0x01, sym: 0x001b, unicode: 0x001b, modifier: 0x0
18:59:45.069 T:3700556656   DEBUG: Thread Timer 3700556656 terminating
18:59:45.108 T:4090426976   DEBUG: Keyboard: scancode: 0x01, sym: 0x001b, unicode: 0x001b, modifier: 0x0
18:59:45.108 T:4090426976   DEBUG: HandleKey: escape (0xf01b) pressed, action is Back
18:59:45.286 T:4090426976   DEBUG: ------ Window Deinit (DialogSelect.xml) ------
18:59:45.303 T:3677164400   ERROR: ## CoreELEC Addon ## system::do_manual_update ## ERROR: (KeyError('',))
18:59:45.304 T:3677164400   ERROR: Traceback (most recent call last):
					  File "/home/adamg/CoreELEC/build.CoreELEC-Odroid_C2.arm-8.95.2/CoreELEC-settings-61dc05b32cc6a033cc1d7f37d8ec4da55f46aed4/.install_pkg/usr/share/kodi/addons/service.coreelec.settings/resources/lib/modules/system.py", line 734, in do_manual_update
					KeyError: ''
19:00:05.393 T:3716445040   DEBUG: Thread JobWorker 3716445040 terminating (autodelete)
19:00:05.394 T:3947881328   DEBUG: Thread JobWorker 3947881328 terminating (autodelete)
19:00:05.394 T:3985822576   DEBUG: Thread JobWorker 3985822576 terminating (autodelete)
19:00:05.394 T:3939488624   DEBUG: Thread JobWorker 3939488624 terminating (autodelete)
19:00:08.753 T:4090426976   ERROR: Control 1200 in window 13001 has been asked to focus, but it can't

Also see attached screenshot.

Can this be confirmed, and perhaps fixed?

Thanks :slight_smile:
/Miwer

screenshot005
screenshot0051920×1080 280 KB

2

Not a solution, download the update tar file from github, copy to the update folder on your device & reboot

3

The blank channel and version number is the expected behavior.
The problem is, that you changed your update config from “auto” to “manual”.
This way you only get the update notification.
I would suggest to activate “auto” update to always have the newest version installed automatically.

4

How is this expected behavior?
In LibreElec, I could select update channel (major version) and the available versions would show the versions of that major version, allowing for manual up-/downgrading from within kodi.

That should be the expected behavior also in CoreElec. Otherwise I don’t see any reason even having the entries in the menu. If they just show blanks, then they should just as well be removed.

Is the Custom Channel update feature not implemented either? (not that I use it anyway)
How about the “Submit Statistics” - any point in keeping that enabled, or is this working as expected?

Thanks for the suggestion about the “auto” update feature, which is also the default in new setups. However there’s a reason I choose to do manual updates only (also on addons). You see, that way I can decide when to install any updates, and maybe hold off updates for some time, instead of being caught off-guard with an update that could potentially break something.

Please let me know if this can be accepted as a valid bug report. In the mean time, I will use the tar file to update.

Thanks :slight_smile:

5

Why should it be? CoreELEC != LibreELEC

6

The custom update channel is implemented, and both the “update channel” and “versions” fields are used for that. Therefore it’s not useless and can’t be removed.
If you keep choosing “manual” as your update strategy, then the manual way indeed would be to copy the tar file to your .update folder.
But again: It’s not a bug, but the expected behavior.