Pi Config not working after December update

After update, i cant`t open Pi Config at My OSMC (RPi2)


1 Like

Same here! Ah, that comforting feeling of not being the only one with a problem! :slight_smile:

Yes, I have got the same problem. I have just tried another update (to 2015.12-1) and it’s not working.

Curiously I am also unable to drill into the ‘Audio’ sub-menu, although that may be entirely unrelated.

I have only just built my OSMC (on a new Pi 2 for Xmas) but everything else seems to be working ok.

Me too, RPi2 as well.

Same here.
Pi Config not opening on RPi 2 after December Upate.

We are aware of this issue and will post here again when it is resolved.


Good to hear, if it’s any help…

20:42:46 1039.669556 T:1692398624 DEBUG: OSMC PI scriptmoduleosmcsettingpi.run received: pos0: <OSMCSettingClass(Thread-31, started daemon 1692398624)>
20:42:46 1039.669922 T:1692398624 DEBUG: OSMC PI scriptmoduleosmcsettingpi.populate_pi_settings_dict received: pos0: <OSMCSettingClass(Thread-31, started daemon 1692398624)>
20:42:46 1039.674805 T:1692398624 DEBUG: OSMC PI Config settings received from the parser: {‘disable_overscan’: ‘1’, ‘disable_splash’: ‘1’, ‘sdtv_mode’: ‘2’, ‘force_turbo’: ‘0’, ‘over_voltage_sdram’: ‘0’, ‘core_freq’: ‘450’, ‘initial_turbo’: ‘0’, ‘start_x’: ‘1’, ‘max_usb_current’: ‘0’, ‘gpu_mem_1024’: ‘256’, ‘sdtv_aspect’: ‘3’, ‘arm_freq’: ‘900’, ‘sdram_freq’: ‘450’, ‘hdmi_ignore_cec_init’: ‘1’, ‘over_voltage’: ‘0’}
20:42:47 1039.774414 T:1692398624 DEBUG: OSMC PI scriptmoduleosmcsettingpi.translate_device_tree received: pos0: <OSMCSettingClass(Thread-31, started daemon 1692398624)>, pos1:
20:42:47 1039.786499 T:1692398624 DEBUG: OSMC PI scriptmoduleosmcsettingpi.translate_device_tree [0.0116748809814] returns: None
20:42:47 1039.797974 T:1692398624 ERROR: Exception in thread Thread-31:
Traceback (most recent call last):
File “/usr/lib/python2.7/threading.py”, line 810, in bootstrap_inner
File “/usr/share/kodi/addons/service.osmc.settings/resources/lib/CompLogger.py”, line 61, in wrapper
func(*args, **kwargs)
File “/usr/share/kodi/addons/script.module.osmcsetting.pi/resources/osmc/OSMCSetting.py”, line 376, in run
File “/usr/share/kodi/addons/service.osmc.settings/resources/lib/CompLogger.py”, line 71, in wrapper
result = func(*args, **kwargs)
File “/usr/share/kodi/addons/script.module.osmcsetting.pi/resources/osmc/OSMCSetting.py”, line 355, in populate_pi_settings_dict
setting_value = translate_method(setting_value)
File “/usr/share/kodi/addons/script.module.osmcsetting.pi/resources/osmc/OSMCSetting.py”, line 919, in translate_orphanedparams
k, v = param.split(’|
ValueError: need more than 1 value to unpack

On it.

Fix out shortly.

1 Like

OK, go into MyOSMC - Updates - down to manual controls - Enter HotFix and provide this code:


This will download the corrected file and allow the Pi Config to open. The fix will be in the next update.

This is a short-lived HotFix, so anyone with this problem and reading this thread from more than a couple of weeks in the future, you should update normally to get the proper fix.

Thanks for the fix @Karnage

Just a heads up that performing a manual update via My OSMC -> Updater will now fix this issue.

Apologies for the inconvenience caused.

1 Like

Thanks very much!

Closing this thread. Please re-open if the issue persists.