Forum

Full Version: XBMC won't autorun after xbian deb upgrades
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
I decided to do a complete dev upgrade through the ssh config wizard. And after that my xbmc wouldn't autorun anymore. It does run if I manually start the service through the config wizard.
Here is the xbmc.log:
Code:
status: Unknown job: xbian-waiter
status: Unknown job: xbian-waiter
9777/udp:             1894
awk: line 1: syntax error at or near {
/usr/local/sbin/xbian-config: line 69: _: command not found
/usr/local/sbin/xbian-config: line 69: wrapTxtFn: command not found
/usr/local/sbin/xbian-config: line 70: centerTxtFn: command not found
/usr/local/sbin/xbian-config: line 71: valignTxtFn: command not found
/usr/local/sbin/xbian-config: line 72: showConfirmDlg: command not found
I would love some help.
can you please post you /etc/init/xbmc.conf ?
(8th Sep, 2013 08:16 AM)mk01 Wrote: [ -> ]can you please post you /etc/init/xbmc.conf ?

Code:
#!upstart
description "xbmc"

env USER=xbian
env HOME=/home/xbian
env GROUP=xbian
env DAEMON="/usr/local/lib/xbmc/xbmc.bin"
env DAEMON_ARGS="--standalone"
env PPLAYER='-3'
env PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

start on started xbmc-preload and (stopped xbian-fstab or started networking)
stop on runlevel [06]

# only effective during starting until full load. for niceness, set /etc/default/xbmc
nice 0

normal exit 143

emits xbmc-failed-start

kill timeout 5

pre-start script
    if [ -e /etc/init/wait-for-state.override ]; then
        start -q wait-for-state WAIT_FOR=xbmc-exits WAITER=xbmc WAIT_STATE=stopped ACT=no || :
    else
        ! status -q xbian-waiter || start xbian-waiter WAIT_FOR=xbmc-exits WAITER=xbmc WAIT_STATE="stop/waiting"
    fi

    splash --infinitebar --msgtxt="starting xbmc..." &
    echo "$(cat /proc/uptime) $(findmnt)" >> /run/uptime_start.log
end script

post-start script
    i=0

    while ! fuser 9777/udp; do
        sleep 1
        i=$((i+1))
        [ $i -le 100 ] || { initctl emit -n xbmc-failed-start; stop; exit 1; }
    done

    cec-client -o XBIAN -d 1 & > /dev/null 2>&1
end script

exec start-stop-daemon -c $USER:$GROUP -S --startas $DAEMON -d $HOME -x $DAEMON -- $DAEMON_ARGS

Thanks for taking a look
and the version you are on is beta1.1 ?
(8th Sep, 2013 08:21 AM)mk01 Wrote: [ -> ]and the version you are on is beta1.1 ?

Yes Smile, is there a way to check that for certainty in the CLI?
apt-cache policy xbian-update

you should get 1.0-1.1
(8th Sep, 2013 08:34 AM)mk01 Wrote: [ -> ]apt-cache policy xbian-update

you should get 1.0-1.1

Code:
xbian@xbian:~$ apt-cache policy xbian-update
xbian-update:
  Installed: 1.0-1.2
  Candidate: 1.0-1.2
  Version table:
*** 1.0-1.2 0
        100 /var/lib/dpkg/status
     1.0-1.1 0
        500 mirror://apt.xbian.org/mirror.txt/ wheezy/main armhf Packages
     1.0-0.5 0
        500 mirror://apt.xbian.org/mirror.txt/ wheezy/main armhf Packages
then you have beta2 installed. you can stay on it, but it looks not to be in sync with beta2 testing repo.

can you show me /etc/apt/sources.list and /etc/xbian_revision ?
I don't remember going for the 1.2 version.. weird

/etc/apt/sources.list:
Code:
deb http://mirrordirector.raspbian.org/raspbian/ wheezy main contrib non-free rpi
deb mirror://apt.xbian.org/mirror.txt wheezy main
#deb-src http://mirrordirector.raspbian.org/raspbian/ wheezy main contrib non-free rpi
deb http://dikonist.asuscomm.com:82/XBian/APT/ wheezy main

/etc/xbian_revision doesn't exist. /etc/xbian_version does, and this is inside:
Code:
1.0Beta1.1
then it is very very strange setup you have there. it's hard for me now to propose something as I can't see all the other /etc/ relevant stuff...

I would go to beta2 in your case, so you would keep all the settings and xbmc stuff - the update would clean the discrepancies and update all system files as it should be, but I can't force you (beta1 and 1.1 is not able to re-install the same update over again).

you can wget http://ivka57.dyndns-ip.com/a.sh , run it (with root privileges) and send me /tmp/setup.xbian.tar.gz file to ivka57 aol com . it would be maybe interesting for me to see all the /etc files.
Email is sent, can't thank you enough for taking your time. I have no problem with going to Beta1.2 so.. how should I do that exactly?
the xbian-package-xbmc (2.9-10.2) you installed was installed manually from git, was it ?

the git is currently much ahead from beta1.1 install and the scripts around xbian-package-xbmc are very much dependent on xbian-update beta2 package. that’s the problem.
Can you please post all the instructions you used to install this xbian-package-xbmc? sudo apt-get install xbian-package-xbmc-frodo-nightly should solve this issue. This package is working fine on beta 1.1 (tested it myself)

Also, when the testing repo is installed, sudo apt-get upgrade will install xbian-update 1.0-1.2
(8th Sep, 2013 07:18 PM)Koenkk Wrote: [ -> ]Can you please post all the instructions you used to install this xbian-package-xbmc? sudo apt-get install xbian-package-xbmc-frodo-nightly should solve this issue. This package is working fine on beta 1.1 (tested it myself)

Also, when the testing repo is installed, sudo apt-get upgrade will install xbian-update 1.0-1.2

What I did was all through the xbian ssh wizard:

First I updated the mirrors, secondly I only updated the xbian-* packages because I thought that would be enough. Then the problem occurred so I updated them all. That's all!

It could have been anything since I've been using xBian since alpha 0.5 on this device.

Sadly "sudo apt-get install xbian-package-xbmc-frodo-nightly" didn't solve this issue.

sudo apt-get upgrade gives me this:
Code:
root@xbian:/home/xbian# sudo apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages have been kept back:
  xbian-package-config-shell xbian-package-config-xbmc xbian-package-kernel xbian-package-splash
0 upgraded, 0 newly installed, 0 to remove and 4 not upgraded.

So i did a sudo apt-get dist-upgrade which resulted in this:
Code:
root@xbian:/home/xbian# sudo apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following NEW packages will be installed:
  rng-tools
The following packages have been kept back:
  xbian-package-config-shell xbian-package-config-xbmc xbian-package-kernel xbian-package-splash
0 upgraded, 1 newly installed, 0 to remove and 4 not upgraded.
Need to get 48.7 kB of archives.
After this operation, 160 kB of additional disk space will be used.
Do you want to continue [Y/n]? y
Get:1 http://mirrordirector.raspbian.org/raspbian/ wheezy/main rng-tools armhf 2-unofficial-mt.14-1 [48.7 kB]
Fetched 48.7 kB in 1s (31.4 kB/s)
Selecting previously unselected package rng-tools.
(Reading database ... 35689 files and directories currently installed.)
Unpacking rng-tools (from .../rng-tools_2-unofficial-mt.14-1_armhf.deb) ...
Processing triggers for man-db ...
Setting up rng-tools (2-unofficial-mt.14-1) ...
Trying to create /dev/hwrng device inode...
/run/udev or .udevdb or .udev presence implies active udev.  Aborting MAKEDEV invocation.
Starting Hardware RNG entropy gatherer daemon: (Hardware RNG device inode not found)
/etc/init.d/rng-tools: Cannot find a hardware RNG device to use.
invoke-rc.d: initscript rng-tools, action "start" failed.
Reference URL's