HOWTO: Install Kodi on Raspbian

[Tom_A]

I ran apt-get yesterday and got no new update. Can you please post the output of
apt-cache showpkg kodi

I got this:

Code: Select all

Package: kodi
Versions: 
2:14.2~git20150311.e7ba06f-1wheezy (/var/lib/apt/lists/archive.mene.za.net_raspbian_dists_wheezy_unstable_binary-armhf_Packages) (/var/lib/dpkg/status)
 Description Language: 
                 File: /var/lib/apt/lists/archive.mene.za.net_raspbian_dists_wheezy_contrib_binary-armhf_Packages
                  MD5: fe8a5d04c10ac9c610a143988630b0e5

2:14.1-1~wheezy (/var/lib/apt/lists/archive.mene.za.net_raspbian_dists_wheezy_contrib_binary-armhf_Packages)
 Description Language: 
                 File: /var/lib/apt/lists/archive.mene.za.net_raspbian_dists_wheezy_contrib_binary-armhf_Packages
                  MD5: fe8a5d04c10ac9c610a143988630b0e5


Reverse Depends: 
  xbmc,kodi
  xbmc,kodi
Dependencies: 
2:14.2~git20150311.e7ba06f-1wheezy - kodi-bin (2 2:14.2~git20150311.e7ba06f-1wheezy) kodi-bin (3 2:14.2~git20150311.e7ba06f-1wheezy.1~) mesa-utils (0 (null)) x11-utils (0 (null)) ttf-liberation (0 (null)) ttf-dejavu-core (0 (null)) python-imaging (0 (null)) fbset (0 (null)) python (0 (null)) python-support (2 0.90.0) python-qt3 (0 (null)) samba-common-bin (0 (null)) upower (0 (null)) xbmc (3 2:14.0~) 
2:14.1-1~wheezy - kodi-bin (2 2:14.1-1~wheezy) kodi-bin (3 2:14.1-1~wheezy.1~) mesa-utils (0 (null)) x11-utils (0 (null)) ttf-liberation (0 (null)) ttf-dejavu-core (0 (null)) python-imaging (0 (null)) fbset (0 (null)) python (0 (null)) python-support (2 0.90.0) python-qt3 (0 (null)) samba-common-bin (0 (null)) upower (0 (null)) xbmc (3 2:14.0~) 
Provides: 
2:14.2~git20150311.e7ba06f-1wheezy - 
2:14.1-1~wheezy - 
Reverse Provides:

[gkreidl]

You got it from the unstable repository.

[Tom_A]

You got it from the unstable repository.

You're right. I forgot that I had to switch to unstable to get Kodi before it has been added to stable.

All fixed. I think I know why the script wasn't working on the unstable release as well.

[CKBlack007]

came here to "me too". I had a new NOOB install only days old and got the black screen on exit from kodi. running

Code: Select all

sudo apt-get update

fixed the problem.

[gkreidl]

came here to "me too". I had a new NOOB install only days old and got the black screen on exit from kodi. running

Code: Select all

sudo apt-get update

fixed the problem.

Did you also add the "unstable" part of Michael's repository? And did the update really fix the black screen problem?

[cpcbegin]

I press shutdown buttom and sometimes kodi closes and other times it doesn't.

After last time kodi close failed I typed ps aux | grep kodi and I got this:

Code: Select all

pi        2682  0.0  0.0   1764   360 ?        S    15:17   0:00 /bin/sh /usr/bin/kodi-standalone
pi        2690  0.0  0.0   1764   356 ?        S    15:17   0:00 /bin/sh /usr/bin/kodi --standalone
pi        2693 13.5 11.4 218456 86124 ?        Sl   15:17  12:10 /usr/lib/kodi/kodi.bin --standalone
pi       12752  0.0  0.2   5268  1736 pts/0    S+   16:47   0:00 grep --color=auto kodi

Last lines in $HOME/.kodi/temp/kodi.log

Code: Select all

16:29:33 T:1961488384  NOTICE: Storing total System Uptime
16:29:33 T:1961488384  NOTICE: Saving settings
16:29:33 T:1961488384  NOTICE: stop all
16:29:33 T:1961488384  NOTICE: stop player
16:29:33 T:1961488384  NOTICE: ES: Stopping event server
16:29:34 T:1642066960  NOTICE: ES: UDP Event server stopped
16:29:34 T:1961488384  NOTICE: stopping upnp
16:29:34 T:1961488384  NOTICE: stopping zeroconf publishing
16:29:34 T:1961488384  NOTICE: Webserver: Stopping...
16:29:34 T:1961488384  NOTICE: WebServer: Stopped the webserver
16:29:34 T:1961488384  NOTICE: Webserver: Stopped...
16:29:34 T:1961488384  NOTICE: stop dvd detect media
16:29:35 T:1961488384  NOTICE: stop sap announcement listener
16:29:35 T:1961488384  NOTICE: clean cached files!
16:29:35 T:1961488384  NOTICE: unload skin
16:29:35 T:1835004944  NOTICE: [plugin.video.pulsar] pulsard: exiting pulsard daemon
16:29:35 T:1835004944  NOTICE: [plugin.video.pulsar] pulsard: pulsard daemon exited
16:29:35 T:1809839120  NOTICE: [plugin.video.pulsar]
16:29:36 T:1677718544  NOTICE: Previous line repeats 9 times.
16:29:36 T:1677718544  NOTICE: [plugin.video.pulsar] pulsar: exiting jsonrpc service
16:29:36 T:1784673296  NOTICE: [plugin.video.pulsar] pulsar: exiting pulsard
16:29:37 T:1776284688  NOTICE: StorageServer-2.5.4 Closed down
16:29:38 T:1961488384  NOTICE: stopped
16:29:38 T:1961488384  NOTICE: destroy
16:29:38 T:1961488384  NOTICE: closing down remote control service
16:29:38 T:1961488384  NOTICE: unload sections
16:29:38 T:1961488384  NOTICE: special://profile/ is mapped to: special://masterprofile/
16:29:38 T:1961488384  NOTICE: destroy
16:29:38 T:1961488384 WARNING: Attempted to remove window 10013 from the window manager when it didn't exist
16:29:38 T:1961488384 WARNING: Attempted to remove window 10014 from the window manager when it didn't exist
16:29:38 T:1961488384 WARNING: Attempted to remove window 10015 from the window manager when it didn't exist
16:29:38 T:1961488384 WARNING: Attempted to remove window 10016 from the window manager when it didn't exist
16:29:38 T:1961488384 WARNING: Attempted to remove window 10017 from the window manager when it didn't exist
16:29:38 T:1961488384 WARNING: Attempted to remove window 10018 from the window manager when it didn't exist
16:29:38 T:1961488384 WARNING: Attempted to remove window 10019 from the window manager when it didn't exist
16:29:38 T:1961488384 WARNING: Attempted to remove window 10021 from the window manager when it didn't exist
16:29:38 T:1961488384 WARNING: Attempted to remove window 10107 from the window manager when it didn't exist
16:29:38 T:1961488384 WARNING: Attempted to remove window 10115 from the window manager when it didn't exist
16:29:38 T:1961488384 WARNING: Attempted to remove window 10104 from the window manager when it didn't exist
16:29:38 T:1961488384  NOTICE: closing down remote control service
16:29:38 T:1961488384  NOTICE: unload sections
16:29:38 T:1961488384  NOTICE: application stopped...

[fraz0815]

Just FYI Michaels' version was added to raspbian repo, see http://forum.kodi.tv/showthread.php?tid ... pid1969525
Regarding the fix for 'exit bug' I think it didn't make it into helix/14.x branch, only master isengard/15, https://github.com/xbmc/xbmc/pull/6577

[DirkS]

Just FYI Michaels' version was added to raspbian repo

To be precise: it's in the RPF's raspbian repo.
So

Code: Select all

deb http://archive.raspberrypi.org/debian/ wheezy main

has to be in one of the apt source list files.
On a standard Raspbian install (Noobs or from image) it's already present in /etc/apt/sources.list.d/raspi.list

[Chateaudur]

Hi everyone,

Thanks for this topic, Kodi runs great on Raspbian, appart from the exit bug. Hope it gets fixed soon.

Question though: Kodi starts when Raspbian has finished booting up. How do I prevent that?
I found a conf file in kodi with enableautostart=0, sounds like it's not doing what it supposed to do.
Help would be appreciated

Thanks

[gkreidl]

Hi everyone,

Thanks for this topic, Kodi runs great on Raspbian, appart from the exit bug. Hope it gets fixed soon.

Question though: Kodi starts when Raspbian has finished booting up. How do I prevent that?
I found a conf file in kodi with enableautostart=0, sounds like it's not doing what it supposed to do.
Help would be appreciated

Thanks

I'm not sure what you did in the first place to enable booting into Kodi. I didn't happen to anybody else, AFAIK.

[Tom_A]

Question though: Kodi starts when Raspbian has finished booting up. How do I prevent that?
I found a conf file in kodi with enableautostart=0, sounds like it's not doing what it supposed to do.
Help would be appreciated

Thanks

I'm not sure what you did in the first place to enable booting into Kodi. I didn't happen to anybody else, AFAIK.

There are a few ways to start Kodi. It's recommended to start Kodi from the command line. If you start Kodi from lightdm by first logging out, selecting Kodi instead of the default desktop, and then logging in, when you restart , Kodi will be launched automatically. You did not say how you had launched Kodi, but this is the only way I can think of it starting automatically without setting the auto start flag or deliberately setting up a script to launch it.

I prefer to start from lightdm although it's not the recommended method as I like the auto login behavior. It should also be possible to disable lightdm auto login

[Chateaudur]

Well I boot to raspbian, and kodi starts automatically each time. Then I click exit and end up on my desktop as expected. Weird. I didn't do anything specific, my raspbian install it "out of the box", I simply installed kodi on top of it as explained in this topic. I do not know where to look in Linux to see what's set to start up automatically with the OS :/

[Tom_A]

Well I boot to raspbian, and kodi starts automatically each time. Then I click exit and end up on my desktop as expected. Weird. I didn't do anything specific, my raspbian install it "out of the box", I simply installed kodi on top of it as explained in this topic. I do not know where to look in Linux to see what's set to start up automatically with the OS :/

Do you end up logged in or do you end up at the login prompt when you exit Kodi?

[Chateaudur]

I'm logged in, and on my desktop

[Tom_A]

I'm logged in, and on my desktop

Code: Select all

sudo nano /etc/default/kodi

change ENABLED=1 to ENABLED=0

if you haven't done this yet. I'm not sure if this is the config file you found.

You can also try turning off the auto start of the desktop to see if that makes any difference. I originally experimented with loading Kodi (XBMC at the time) after I had loaded the desktop on Ubuntu. I was using the GUI to launch it. If you have somehow set this, then not launching the GUI should also prevent Kodi from launching and will give us some direction as to how to turn off the auto launch.

[dogmarcopolo]

i got a different problem following the instruction on a brand new Raspberry Pi 2:

when i start kodi-standalone, the color is messed up. instead of blue, i got sort of pinkish background. even if i exit out of kodi and restart x windows, the background is still messed up.

i even performed the following:

1. create a raspbian from image
2. apt-get install update
3. apt-get install upgrade

then following the instruction to the letters (cut-and-paste). still the pink background is there. any suggestion?

[gkreidl]

i got a different problem following the instruction on a brand new Raspberry Pi 2:

when i start kodi-standalone, the color is messed up. instead of blue, i got sort of pinkish background. even if i exit out of kodi and restart x windows, the background is still messed up.

i even performed the following:

1. create a raspbian from image
2. apt-get install update
3. apt-get install upgrade

then following the instruction to the letters (cut-and-paste). still the pink background is there. any suggestion?

GPU memory size?

[doktour]

Today 4/20/15 I did a sudo apt-get upgrade and kodi updated.
Now Kodi will no longer run on my raspberry pi II

I cannot get into kodi for the exact version, but it is the latest as of 4/20/15

Here is a link to the crash log

http://pastebin.com/T7ccmWmZ

Would someone kindly point me in the right direction to correct this.

Thank you

[scar4ace]

hey, thanks for an awesome guide!

I had followed the previous instructions (around late Feb) and got Kodi 14.1 installed on raspbian (using Michael Gorven library etc)

I can see now its been updated and become a much easier process and the package is Kodi 14.2. I tried out the install on a second SD card as a test purpose and works just fine. There are differences as well e.g. the power off button on the Kodi app now just says Exit (the previous one had shutdown) and also the service can be started/stopped much cleaner from terminal (sudo service kodi start/stop). It feels like the package is now more complete for running as standalone on raspbian.

Just wondering how I can update my old 14.1 to 14.2 on my main SD Card (I would like to keep all my settings, add-ons, and local media pointers etc).?

Thanks!

[gkreidl]

apt-get update/upgrade should work.

[Tom_A]

Has anyone noticed that the search from the Confluence home menu is not always available. I have two older installs that both allow me to search for content right from the home menu. The search is towards the middle right of the screen where controls are added if a video is playing back but you are at the home menu. I've looked through all the settings including the xml file that holds all the settings and can't find anything. I did find a hide search option but it looked like it was for a different skin.

[scar4ace]

apt-get update/upgrade should work.

Thanks!! This worked! I'm on 14.2 now.

Only difference between the update and 14.2 clean install is I cannot start/stop kodi with the simple command "sudo service kodi start/stop". Any idea why this is? I'd really prefer this method as it seems a cleaner shutdown to "kill" command for /usr/lib/kodi/kodi.bin

Worst case I can try exporting userdata to my test clean install card and see if that preserves my settings/add-ons/media library points.

Cheers!

[scar4ace]

Update - the "sudo service kodi start/stop" commands now work for me after kodi 14.1 to 14.2 update

Only change I made was in file /etc/default/kodi:

Code: Select all

# The user to run Kodi as
USER=kodi

changed to user 'pi'. It could be I had an instance running already as pi (on start-up) and then trying to stop it with the "service kodi" commands, I am guessing the system was defaulting user to 'kodi' as per the config file and hence crap out.

cheers

[Tom_A]

Has anyone noticed that the search from the Confluence home menu is not always available. I have two older installs that both allow me to search for content right from the home menu. The search is towards the middle right of the screen where controls are added if a video is playing back but you are at the home menu. I've looked through all the settings including the xml file that holds all the settings and can't find anything. I did find a hide search option but it looked like it was for a different skin.

I just copied a .kodi directory from one of my previous installs to a new install and can now see the search item on the home screen. There must be a setting somewhere in there, but there appears to no longer be a way to change it from the GUI and I can't find where exactly it is stored. I suppose just copying over the whole .kodi directory is a good way to have all the same plugins and settings easily moved over to new installs, however I would like to know where this setting is stored.

[Lombra]

What's the difference between this and using apt-get now? I've not tried either.