[SOLVED] XBian menu in System, Settings not working

[A.T.E.]

I have recently installed Xbian from scratch, and since the beginning the XBian menu in System/Settings did not work.

Terminal

Software
XBian version: 20160124-0
XBMC/Kodi version: 16.0-1456188746
Overclock settings: no overclock

Hardware
Device type and model (e.g. Raspberry Pi Model A/B 256/512 MB, CuBox-i i4Pro, ...): RPi2
Power supply rating: 5V 2A
SD card size and make/type: 4GB Sandisk
Network (Ethernet or wireless): Ethernet
Connected devices (TV, USB, network storage, ...): TV

Log tail output when attempting to enter the Xbian menu in System, Settings
12:16:29 86616.812500 T:1702015920 NOTICE: XBian : XBian-config started
12:16:29 86617.117188 T:1702015920 WARNING: CSkinInfo: failed to load skin settings
12:16:30 86618.460938 T:1702015920 ERROR: Traceback (most recent call last):
12:16:30 86618.460938 T:1702015920 ERROR: File "/usr/local/share/kodi/addons/plugin.xbianconfig/default.py", line 222, in <module>
12:16:30 86618.460938 T:1702015920 ERROR: win.show()
12:16:30 86618.460938 T:1702015920 ERROR: File "/usr/local/share/kodi/addons/plugin.xbianconfig/default.py", line 94, in show
12:16:30 86618.460938 T:1702015920 ERROR: self.onShow()
12:16:30 86618.460938 T:1702015920 ERROR: File "/usr/local/share/kodi/addons/plugin.xbianconfig/default.py", line 127, in onShow
12:16:30 86618.460938 T:1702015920 ERROR: catinstance = modu(self.CmdQueue,self.update_progress)
12:16:30 86618.460938 T:1702015920 ERROR: File "/usr/local/share/kodi/addons/plugin.xbianconfig/resources/lib/xbmcguie/category.py", line 29, in __init__
12:16:30 86618.460938 T:1702015920 ERROR: self.settings.append(setting())
12:16:30 86618.460938 T:1702015920 ERROR: File "/usr/local/share/kodi/addons/plugin.xbianconfig/resources/lib/xbmcguie/category.py", line 101, in __init__
12:16:30 86618.460938 T:1702015920 ERROR: self.onInit()
12:16:30 86618.460938 T:1702015920 ERROR: File "/usr/local/share/kodi/addons/plugin.xbianconfig/categories/10_system.py", line 574, in onInit
12:16:30 86618.468750 T:1702015920 ERROR: rc = self.getSetting(key)
12:16:30 86618.468750 T:1702015920 ERROR: File "/usr/local/share/kodi/addons/plugin.xbianconfig/resources/lib/xbmcguie/category.py", line 123, in getSetting
12:16:30 86618.468750 T:1702015920 ERROR: return getSetting(id)
12:16:30 86618.468750 T:1702015920 ERROR: File "/usr/local/share/kodi/addons/plugin.xbianconfig/resources/lib/utils.py", line 30, in getSetting
12:16:30 86618.468750 T:1702015920 ERROR: return pickle.load(open(settingPath,'r'))
12:16:30 86618.468750 T:1702015920 ERROR: File "/usr/lib/python2.7/pickle.py", line 1378, in load
12:16:30 86618.468750 T:1702015920 ERROR: return Unpickler(file).load()
12:16:30 86618.468750 T:1702015920 ERROR: File "/usr/lib/python2.7/pickle.py", line 858, in load
12:16:30 86618.476562 T:1702015920 ERROR: dispatch[key](self)
12:16:30 86618.476562 T:1702015920 ERROR: File "/usr/lib/python2.7/pickle.py", line 880, in load_eof
12:16:30 86618.476562 T:1702015920 ERROR: raise EOFError
12:16:30 86618.476562 T:1702015920 ERROR: EOFError
12:16:30 86618.476562 T:1702015920 ERROR: Exception in xbianSettingWindow None
12:16:30 86618.640625 T:1702015920 WARNING: CPythonInvoker(11, /usr/local/share/kodi/addons/plugin.xbianconfig/default.py): the python script "/usr/local/share/kodi/addons/plugin.xbianconfig/default.py" has left several classes in memory that we couldn't clean up. The classes include: N9XBMCAddon9xbmcaddon5AddonE

[IriDium]

How was the image installed? "dd" xbian-installer or Win32diskimager?

Are you sure you have installed the latest edition, also have you tried to upgrade?, that might solve the problem.

[A.T.E.]

(8th May, 2016 07:34 PM)IriDium Wrote:  How was the image installed? "dd" xbian-installer or Win32diskimager?

Are you sure you have installed the latest edition, also have you tried to upgrade?, that might solve the problem.

I installed it from the xbian-installer, and it was the latest edition when I did it (a couple of months ago, if I remember). What I am sure of is that this feature did not work since the beginning and that, because of that, I repeated the installation twice to be sure.
I have now upgraded (I have ticked the first option "upgrade all the packages", see attached log file), but the issue persists, after the reboot.

[Nachteule]

Just installed latest image, everything works ok.

Maybe best and fastest solution is downloading latest image and flashing it to sd-card again

[A.T.E.]

(8th May, 2016 09:33 PM)Nachteule Wrote:  Just installed latest image, everything works ok.

Maybe best and fastest solution is downloading latest image and flashing it to sd-card again

I have done it, and I can confirm you that the XBian menu works on a new installation of the newest distribution.

Now, next problem: how can I transfer *all* the configuration from the previous setup? In the past I tried an add-on named XBMC-Backup (later renamed Backup), which works, but which does not transfer *all*, thus requiring me to do some work.

In fact I have two SD cards: one with the current setup, XBian menu not working, but well configured, and the new one, with the XBian menu working, but "vanilla". I also have a NAS.

Should I perhaps copy the entire /home/xbian/.kodi folder? What aout the network settings?

[rikardo1979]

(9th May, 2016 03:47 PM)A.T.E. Wrote:  

(8th May, 2016 09:33 PM)Nachteule Wrote:  Just installed latest image, everything works ok.

Maybe best and fastest solution is downloading latest image and flashing it to sd-card again

I have done it, and I can confirm you that the XBian menu works on a new installation of the newest distribution.

Now, next problem: how can I transfer *all* the configuration from the previous setup? In the past I tried an add-on named XBMC-Backup (later renamed Backup), which works, but which does not transfer *all*, thus requiring me to do some work.

In fact I have two SD cards: one with the current setup, XBian menu not working, but well configured, and the new one, with the XBian menu working, but "vanilla". I also have a NAS.

Should I perhaps copy the entire /home/xbian/.kodi folder? What aout the network settings?

As because you have had issue with old installation I highly recommend you do not transfer any settings/files over to your new install!
It may cause more harm than good as we/you are not sure what was the root of your problem.
This may require a bit of time to set all again but you be sure to have fully working and stable system.

If you bring your old files etc your system may get corrupt again and become unstable

[Nachteule]

@A.T.E.

This can be done be xbian-config menu selection 7 (backup home). It builds a zipped archive from /home and put this file into folder /xbmc-backup. This folder can be accessed by Samba (make sure that Samba is enabled and running).

To restore your /home folder, simply put this archive file into folder /xbmc-backup/put_here_to_restore, it will be extracted and installed automatically.

But I agree with @rikardo1979, maybe it is not good idea to do this (backup of new /home folder may be good idea )

[A.T.E.]

I tried the xbian-config menu selection 7 (backup home). It created the zipped archive, which I copied to /xbmc-backup/put_here_to_restore in the other SD card where I had made the fresh install, but when I rebooted it failed to restore the settings.
Actually now I remember that last year, when I did an upgrade, I had tried that and it had failed as well.
What happens is that the .gz file disappears from /xbmc-backup/put_here_to_restore after the next reboot, but nothing is being copied. If you tell me where to look, I can provide the log file.

As I have two SD cards I can test things, so I made a tar archive of .kodi in the current setup, I renamed .kodi to something else in the new setup, I replaced it with the content of the tar file.
The result is that I got everything back, but the System/Settings/XBian menu failed to load, which indicates, as Rikardo1979 said, that the problem is somewhere inside the .kodi folder. And which might explain why the above mentioned restore did not work.

So I deleted it and I restored the original one. The XBian menu works now, but I have to reconfigure everything. I will possibly try to backup selected things from the .kodi folder.

[IriDium]

The backup is deleted on reboot. Just leave the backup file in the "put_here_to_restore folder" and wait. Something will eventually happen.

[Nachteule]

Just tested this function (never used before). Works like a charm

This operation is started in background automatically (triggered by inotify functionality) and is done by command btrfs-auto-snapshot.

After completion, backup file is removed from /xbmc-backup/put_here_to_restore and Kodi will be restarted (if running)

Of course, depending of size it will take some minutes to finish (not measured time but would assume that it took about 8-10 minutes for 700MB home at RPi3)

[A.T.E.]

I think I must had misunderstood: I thought I had to put the file in /xbmc-backup/put_here_to_restore and reboot in order to trigger the restore. If I am understanding now, I should instead put it there and wait for something automatic to happen.
I will try to keep it in mind for the future.

Anyway, regarding the initial issue: the newest XBian works like a charm, including its Kodi menu in the Settings; I gave up the idea of migrating the .kodi folder and I am now reconfiguring it manually.

On a side note: I see that the /boot/config.txt has been changed (it also include comments now); usb_max_current=1 is there already, but I had to add hdmi_ignore_cec_init=1, so that the RPi would not automatically wake up the TV or switch to it when it switches on.

Thanks for your support!

You can set this as "solved".

[rikardo1979]

(11th May, 2016 05:52 PM)A.T.E. Wrote:  but I had to add hdmi_ignore_cec_init=1, so that the RPi would not automatically wake up the TV or switch to it when it switches on.

Thanks for your support!

You can set this as "solved".

you can do this from within CEC settings in Kodi GUI System>Settings>Input devices>Peripherals

[A.T.E.]

The thing is that those settings refer to Kodi, while the line in the config.txt instructs the entire system before Kodi is loaded. So, if hdmi_ignore_cec_init=1 is absent, the RPi will send a HDMI CEC signal to the TV when it starts up, and the TV will change input source to it.
In fact I had specifically tested it: if that line is missing and the line in the Kodi / Peripherals menu "Switch source to this device on startup" is set to off, the TV will still change the input to the RPi.

[rikardo1979]

(11th May, 2016 07:49 PM)A.T.E. Wrote:  The thing is that those settings refer to Kodi, while the line in the config.txt instructs the entire system before Kodi is loaded. So, if hdmi_ignore_cec_init=1 is absent, the RPi will send a HDMI CEC signal to the TV when it starts up, and the TV will change input source to it.
In fact I had specifically tested it: if that line is missing and the line in the Kodi / Peripherals menu "Switch source to this device on startup" is set to off, the TV will still change the input to the RPi.

my does not coming ON

OP2

[Nachteule]

(11th May, 2016 07:49 PM)A.T.E. Wrote:  The thing is that those settings refer to Kodi, while the line in the config.txt instructs the entire system before Kodi is loaded. So, if hdmi_ignore_cec_init=1 is absent, the RPi will send a HDMI CEC signal to the TV when it starts up, and the TV will change input source to it.
In fact I had specifically tested it: if that line is missing and the line in the Kodi / Peripherals menu "Switch source to this device on startup" is set to off, the TV will still change the input to the RPi.

To clearify this point:
You can set this variable hdmi_ignore_cec_init in Kodi's XBian config under System->Connectivity Checkbox, Ignore CEC init, preventing wakeup of tv at reboot