Forum

So with the default xbmc folder it worked? If so, it means you have a failing plugin or something installed. What does the xbmc.log say?

Btw, I think, the restore command did not work completely. I just checked
the addons directory and it is nearly empty.

---

Where or how can I see the log file? I can enter XBian with the
Windows Explorer, as I said. So, I just need to know where to
find that log file.

---

Ahrm, no, I do not think, it is an addon, because
there are no addons anymore in the addons directory,
just those:

metadata.common.fanart.tv
metadata.tvdb.com
packages
services.xbmc.versioncheck

There are numerous topics about how to post the log contents (also sticky's on this forum).

Quote:So with the default xbmc folder it worked?

Please answer this one first.

(1st Oct, 2014 02:17 AM)CurlyMo Wrote: [ -> ]There are numerous topics about how to post the log contents (also sticky's on this forum).

Quote:So with the default xbmc folder it worked?

Please answer this one first.

No, no, it never started after a reboot.

Only, when I entered "start xbmc" manually in Putty
and then it was the ugly blue standard one with all
settings lost.

What does "ugly blue standard one" mean?

(1st Oct, 2014 02:28 AM)CurlyMo Wrote: [ -> ]What does "ugly blue standard one" mean?

Well, I guess like after a fresh install. I never
check into this, because the very first thing I
always do after setting up the correct IP, is
changing the skin to Quartz (best skin ever).

That means it is an issue with your custom configuration. Could be skin, addon, etc.

Alright, but why was it working on Beta 2
and when I made the update to RC 3 with
the command given (see earlier in this thread)
it does stop then?

And why does it still not work/boot correctly,
although I deleted all addons/skins/... etc.?

I mean, I am getting still the same Samba
screen message like before.

So, if you can tell me, where the boot up log
is saved, I will boot fresh and check that, immediately.

I suspect it's busy updating your databases and the time out is too small. What if you do the following:
Search for these 2 lines (lines 40-41 here):
and change that TIMEOUT=100 to TIMEOUT=100000 or any other big number. Then stop and start XBMC again, or reboot. It may indeed need a while if it's updating databases, but it shouldn't crash anymore.

If it works, change it back to 100. If it doesn't, change it back to 100 and upload the following log files somewhere:
* /home/xbian/.xbmc/temp/xbmc.log;
* /var/log/upstart/xbmc.log (you'll need "sudo" to read it);
* the output of the command "dmesg".

(1st Oct, 2014 03:21 AM)menakite Wrote: [ -> ]I suspect it's busy updating your databases and the time out is too small. What if you do the following:

Terminal

sudo nano /etc/init/xbmc.conf

Search for these 2 lines (lines 40-41 here):

Code:

post-start script
    /sbin/start -q wait-for-state TIMEOUT=100 WAIT_FOR=xbmc-loaded WAITER=xbmc WAIT_STATE=started ACT=no || { /sbin/initctl emit -n xbmc-failed-start; stop; exit 1; }

and change that TIMEOUT=100 to TIMEOUT=100000 or any other big number. Then stop and start XBMC again, or reboot. It may indeed need a while if it's updating databases, but it shouldn't crash anymore.

If it works, change it back to 100. If it doesn't, change it back to 100 and upload the following log files somewhere:
* /home/xbian/.xbmc/temp/xbmc.log;
* /var/log/upstart/xbmc.log (you'll need "sudo" to read it);
* the output of the command "dmesg".

The 100000 time change did not make any difference, but thanks and here is the output:

home/xbian/.xbmc/temp/xbmc.log (I am not sure about this, because it did not show the current time):


system-logs/upstart/xbmc.log:

dmesg:


Edited for sanity.

Can you post:

(1st Oct, 2014 04:10 AM)CurlyMo Wrote: [ -> ]Can you post:

Code:

apt-cache policy libcurl3-gnutls

And:

(1st Oct, 2014 05:00 AM)CurlyMo Wrote: [ -> ]And:

Code:

apt-cache policy xbian-package-xbmc

Can you maybe install xbmc version 13.2-RLS-1409264946, remove the .xbmc folder and reboot?