Official Kodi Wiki - User contributions [en]

HOW-TO:Autostart Kodi for Linux

2021-04-26T14:40:00Z

W3tech: /* Configure Kodi to autostart */

<section begin="intro" /><big>Any or all or a combination of these methods can be used to configure a Debian-based X Window System to boot directly to Kodi. This should work on any Linux using the X Window System, but these instructions are particular to Debian derivatives, such as Ubuntu. A server edition is best for running only Kodi, but this page assumes booting into a desktop OS, not a server distro. However, the instructions here can be used for a server distro with even less configuration than for a desktop. Experiment inside VirtualBox before you apply any of these to your system and make a backup.</big><section end="intro" />

__TOC__

== Installing the X11 Window System ==

Even if you are using something like [https://github.com/graysky2/kodi-standalone-service Kodi Standalone Service], you still need use a WM or a DE that installs the '''x-window-manager''' software package.

To ensure you have this installed use the '''which''' command.

<pre>
which x-window-manager
</pre>

If there is no such package, you can use '''apt''' to search your Linux distributions repository.

<pre>
apt-cache search x-window-manager
</pre>

This will generate a list of packages containing '''x-window-manager''', which cannot be installed alone. If you are not using a DE, you need to use a WM. And, you can also use a compositing WM like Compiz, for fast 3D effects.

[https://wiki.archlinux.org/index.php/Compiz Compiz - ArchWiki]

A note on using Kodi Standalone Service, this package runs Kodi as a '''systemd''' service and disables the login for user '''kodi''' and will not work when autologin is enabled. In fact, it will break the login process if you autologin user '''kodi''' and run Kodi Standalone Service at the same time. This package is installed automatically with the standard Kodi package when you install Kodi on Raspbian, but must be configured manually for all other Linux distributions. You can run the '''which''' command to find this package as well.

<pre>
which kodi-standalone
</pre>

Be advised, Kodi Standalone Service still launches the Kodi GUI and still requires a WM even though it is running as a '''systemd''' service. When you install a WM such as '''xfwm4''' (the WM for XFCE4), the CLI will tell you if it provides the '''x-window-manager''' package.

<pre>
Setting up xfwm4 (4.12.4-1) ...
update-alternatives: using /usr/bin/xfwm4 to provide /usr/bin/x-window-manager (x-window-manager) in auto mode
</pre>

If you do not see this message at the end of the installation, the WM you selected does not provide this software package and may not actually be a complete WM itself but only part of a package containing a WM.

For a great example on exactly how you would do this with '''xfwm4''', see this ArchWiki entry.

[https://wiki.archlinux.org/index.php/Xfwm XFWM - ArchWiki]

Most systems utilize the client version of the X11 software an Xsession requires.

For more X11 features and functionality, you may optionally upgrade to the server software packages for the X Window System.

<pre>apt install xauth xorg xinit xserver-xorg-core xserver-xorg xserver-common</pre>

The Ubuntu wiki is usually a good source of information.

[https://wiki.ubuntu.com/CustomXSession CustomXSession - Ubuntu Wiki]

Custom user sessions can be created with the X11 Window System to run scripts, autostart apps, and launch a WM or DE.

LightDM is used for autologin.

== Customize LightDM to autologin ==

You can utilize the ability to customize LightDM data manager by changing the builtin custom configuration file '''50-myconfig.conf''' using '''nano''' or another text editor. If you have no DE or WM you can install '''lightdm''', but should make sure to do a bit of research before you do. Most versions of Linux use LightDM, but many server versions do not. For Ubuntu Server with no DE, for example, installing '''lightdm''' is okay and necessary. Changing the behavior of LightDM is done using a custom '''50-myconfig.conf''' configuration file.

To see if you have '''lightdm''' use '''which'''.

<pre>
which lightdm
</pre>

If not, install it with '''apt'''.

<pre>
apt install lightdm
</pre>

Configure LightDM for autologin to boot directly to Kodi.

<pre>
nano /etc/lightdm/lightdm.conf
</pre>

Uncomment the following line.

<pre>
#autologin-user=
</pre>

And add the user you want to autologin. The user is named '''kodi''' in this example.

<pre>
autologin-user=kodi
</pre>

And then you can create /etc/lightdm/lightdm.conf.d/50-myconfig.conf, but ensure the settings in /etc/lightdm/lightdm.conf agree.

Create a custom configuration file called '''50-myconfig.conf''' using '''nano''' or other CLI text editor.

<pre>
mkdir /etc/lightdm/lightdm.conf.d/
nano /etc/lightdm/lightdm.conf.d/50-myconfig.conf
</pre>

Inside this new file add the following text.

<pre>
[SeatDefaults]
autologin-user=kodi
</pre>

CTRL +O +Enter +X to save and exit from '''nano'''.

== Configure Kodi to autostart ==

Configure Kodi to autostart.

A)

<pre>
sudo sed -i "1i @kodi" /etc/xdg/lxsession/LXDE-pi/autostart
</pre>

B)

<pre>
mkdir -p ~/.config/autostart
ln -s /usr/bin/kodi ~/.config/autostart
</pre>

This method of autostart requires a desktop environment or DE. This is done a bit differently by each DE. Some helpful links can easily be found in today's Web search using any search engine.

[http://edoceo.com/gui/xfce-autostart-apps Autostart Apps in XFCE]

And this link shows how to autostart an app in LXDE on Raspbian.

[http://www.raspberry-projects.com/pi/pi-operating-systems/raspbian/auto-running-programs-gui Auto running programs LXDE - Raspberry Pi Projects]

The Raspberry Pi is a bit more of a tweak, but these are excellent links that will tell you how. The first link is the most helpful to making sure Kodi autostarts in Pi, and utilizes a '''crontab'''. There are many settings on the Pi that control boot, and the first link gives the best most trouble-free way to boot directly to Kodi.

[https://www.leowkahman.com/2016/03/05/lamp-stack-on-raspberry-pi-with-kodi-running-at-startup/ LAMP stack on Raspberry Pi with Kodi running at startup]

In the above link, the author describes using Crontab (short for "Cron table") to boot directly to Kodi.

<pre>
apt install cron
crontab -e
</pre>

Cron will ask you to choose a text editor from available options. I choose option 2 for '''nano'''.

In the new Crontab, enter the following text.

<pre>
@reboot kodi --standalone
</pre>

Raspbian has a repository package for everything, so kodi-standalone can be run as a package rather than a command argument. You do not have to install '''kodi-standalone''' with Apt.

<pre>
apt install kodi-standalone
</pre>

For instance, if I were to install '''kodi-standalone''' after installing the standard '''kodi''' package, this is the message I get.

<pre>
root@raspberrypi:/home/pi# apt install kodi-standalone
Reading package lists... Done
Building dependency tree
Reading state information... Done
Note, selecting 'kodi' instead of 'kodi-standalone'
kodi is already the newest version (2:18.7-1~buster).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@raspberrypi:/home/pi#
</pre>

That is because it used to a separate package, but since then it has been made into a command. It is really only a trivial difference, instead of using:

<pre>
@reboot kodi --standalone
</pre>

You can use,

<pre>
@reboot kodi-standalone
</pre>

One or the other, not both.

You could also consider using Crontab to run a script, much like described on this page in the section entitled "Run kodi in a window manager" if you scroll down the page.

[https://wiki.archlinux.org/index.php/Kodi Kodi - Run kodi in a window manager]

Instead your Crontab could look like this.

<pre>
@reboot startx
</pre>

And create an '''~/.xinitrc''' file.

<pre>
nano ~/.xinitrc
</pre>

The '''~/.xinitrc''' file should look like this.

<pre>
#!/bin/bash
kodi --standalone #(this is proper syntax for most Kodi installs)
#kodi-standalone #(this is the syntax that works on Raspbian, not other Pi operating systems)
sudo chvt 2
sleep 1
sudo chvt 1
</pre>

Make sure to make '''~/.xinitrc''' executable by running.

<pre>
chmod +rx ~/.xinitrc
</pre>

To ensure no password is required by '''sudo''' for any user logging in when this script runs, you must edit /etc/sudoers or run the '''visudo''' command if it is installed to edit /etc/sudoers.

You can install '''visudo''' from your Linux distributions default repository.

<pre>
apt install sudo
</pre>

To use '''visudo''' simply run the command in the terminal.

<pre>
visudo
</pre>

For any non-root users, create an entry in /etc/sudoers with '''nano'''.

<pre>
nano /etc/sudoers
</pre>

Create an entry on any line that is comfortable to you like shown here.

<pre>
kodi ALL=NOPASSWD: /usr/bin/chvt
# pi ALL=NOPASSWD: /usr/bin/chvt #(if you do not add user kodi)
</pre>

The above example is for users '''pi''' and '''kodi'''.

If you decide not use a Cron table, you can always remove it again.

<pre>
crontab -r
</pre>

This is a quick reference for Crontab.

[http://www.adminschoice.com/crontab-quick-reference Crontab Quick Reference]

These linked pages facilitate more tweaks and settings relevant to other uses of the X Window System on Pi.

[http://ozzmaker.com/enable-x-windows-on-piscreen/ Enable X Window System on PiScreen]

Other things to tweak on Raspbian.

[https://yingtongli.me/blog/2016/12/21/splash.html Raspbian splash screen guide - Clean up the boot process]

[https://scribles.net/lightning-bolt-under-voltage-warning-on-raspberry-pi/ Under voltage warning and disabling splash screen on Raspbian]

[https://raspberrypi.stackexchange.com/questions/59310/remove-boot-messages-all-text-in-jessie Remove boot messages all text in Raspbian - Raspberry Pi Stack Exchange]

And, if you would rather, it is easier to follow the process provided by this link to modify the Raspbian image before installing it onto the microSD card.

[https://wiki.debian.org/RaspberryPi/qemu-user-static Modifying Raspbian with qemu-user-static]

The above link describes removing the DE from a Raspbian image, though Raspbian Lite is a much better starting point for using Qemu for this purpose.

You can also use the X11 Window System to autostart Kodi by placing a startup script in the /etc/X11/Xsession.d/ directory.

[https://debian-administration.org/article/50/Running_applications_automatically_when_X_starts Running applications automatically when X starts]

<pre>
nano /etc/X11/Xsession.d/startup-local
</pre>

Insert this text into the new file. Use CTRL + O + Enter + X to save the file.

<pre>
#!/bin/sh
/usr/bin/kodi
</pre>

If you have a WM, such as Blackbox you can add it here as well.

<pre>
#!/bin/sh
blackbox &
/usr/bin/kodi
</pre>

Set permissions to make it executable. Use the ampersand to run each command in the background till the last line or your script will get stuck on the first line.

<pre>
chmod 755 /etc/X11/Xsession.d/startup-local
</pre>

If Kodi is not installed at the standard path, find it using the '''which''' command.

<pre>
which kodi
</pre>

This feature is available on X Window System operating systems most Linux distributions use the X Window System.

== Create custom Xsession script ==

To create a custom Xsession script with a text editor we start with an '''xinitrc''' script. For more detail on how to create and use '''xinit''', there is a great guide available here.

[https://en.wikibooks.org/wiki/Guide_to_X11/Starting_Sessions Guide to X11 - Starting Sessions - WikiBooks]

<pre>
nano ~/.xinitrc
</pre>

To run Kodi full-screen make sure the text reads:

<pre>
#!/usr/bin/env bash
exec gnome-session &
/usr/bin/kodi -fs
</pre>

Replace the '''gnome-session''' with the DE or WM command you are using. See the last section for examples.

To make '''~/.xinitrc''' executable use.

<pre>
chmod +x ~/.xinitrc
</pre>

Use '''sudo''' and the '''~/.xinitrc''' file to configure '''~/.xsession'''.

<pre>
sudo -H -u kodi bash -c "ln -s ~/.xinitrc /home/kodi/.xsession"
</pre>

Make sure the path goes to user's home directory. In this example, the user is '''kodi'''.

You need to use '''sudo''' to run this command. If you do not have '''sudo''', install it.

<pre>
apt install sudo
</pre>

If you create a symbolic link and want to remove it, simply remove the existing '''.xsession''' file you created.

<pre>
rm /home/kodi/.xsession
</pre>

On some systems using a DE such as Gnome, not all systems using Gnome, it may be necessary for '''.xsession''' to be '''.xsessionrc'''. Though this is more likely the case for organization network computers than a personal one, where configurations may vary on a diversity of machines. Most of the time, it will be '''.xsession''' rather than '''.xsessionrc''' that you want to create.

You can also create the '''.xsession''' script directly in the home directory, rather than link it from '''~/.xinitrc'''. This is necessary if you create multiple custom Xsession scripts for multiple users, and you do not in that case link '''~/.xinitrc''' to '''.xsession'''.

To enable multiple displays edit the '''.bashrc''' file.

<pre>
nano ~/.bashrc
</pre>

Add the following text.

<pre>
if [[ ! $DISPLAY && $XDG_VTNR -le 3 ]]; then
exec startx
fi
</pre>

For two monitors add the following as shown.

<pre>
if [[ ! $DISPLAY && $XDG_VTNR -le 2 ]]; then
exec startx
fi
</pre>

For a single monitor use:

<pre>
if [[ ! $DISPLAY && $XDG_VTNR -eq 1 ]]; then
exec startx
fi
</pre>

If you wish to remain logged in after quitting X, remove the '''exec''' from the above. Other configurations can be applied, but are irrelevant to autostarting Kodi.

[https://wiki.archlinux.org/index.php/Xinit#Autostart_X_at_login Xinit Autostart X at login]

If you are using LightDM and you just want to create a new login entry for user '''kodi''', you must create a new file.

<pre>
nano /usr/share/xsessions/custom.desktop
</pre>

And insert the following text.

<pre>
[Desktop Entry]
Name=Xsession
Exec=/etc/X11/Xsession
</pre>

This will create a new login option for the custom Xsession. Only this one entry is necessary for LightDM and X11 to find the '''~/.xsession''' script in each user's home directory.

You can use any window manager or desktop enviroment with a custom Xsession script as long as it is installed.

You do this by creating '''~/.xinitrc''' script that contains the command to start the WM or DE.

For instance, if you are using FluxBox.

<pre>
#!/usr/bin/env bash
exec fluxbox &
/usr/bin/kodi -fs
</pre>

The <code>-fs</code> option is full-screen.

To run Gnome in the background, but launch Kodi in the foreground.

<pre>
#!/usr/bin/env bash
exec gnome-session &
/usr/bin/kodi -fs
</pre>

Use the '''~/.xinitrc''' file to configure '''~/.xsession''' to create a custom login for any user, not just Kodi.

<pre>
sudo -H -u [username] bash -c "ln -s ~/.xinitrc ~/.xsession"
</pre>

You must reconfigure Xserver for any user that is not a privileged user to be able to start a custom Xsession.

<pre>
dpkg-reconfigure xserver-xorg-legacy
dpkg-reconfigure xserver-xorg
</pre>

When you reconfigure X11 with these commands, choose to allow non-root users (anybody) to start an Xsession. You should see your changes take effect after rebooting.

[[Category:Linux]]

HOW-TO:Autostart Kodi for Linux

2021-04-26T14:36:37Z

W3tech: /* Configure Kodi to autostart */

<section begin="intro" /><big>Any or all or a combination of these methods can be used to configure a Debian-based X Window System to boot directly to Kodi. This should work on any Linux using the X Window System, but these instructions are particular to Debian derivatives, such as Ubuntu. A server edition is best for running only Kodi, but this page assumes booting into a desktop OS, not a server distro. However, the instructions here can be used for a server distro with even less configuration than for a desktop. Experiment inside VirtualBox before you apply any of these to your system and make a backup.</big><section end="intro" />

__TOC__

== Installing the X11 Window System ==

Even if you are using something like [https://github.com/graysky2/kodi-standalone-service Kodi Standalone Service], you still need use a WM or a DE that installs the '''x-window-manager''' software package.

To ensure you have this installed use the '''which''' command.

<pre>
which x-window-manager
</pre>

If there is no such package, you can use '''apt''' to search your Linux distributions repository.

<pre>
apt-cache search x-window-manager
</pre>

This will generate a list of packages containing '''x-window-manager''', which cannot be installed alone. If you are not using a DE, you need to use a WM. And, you can also use a compositing WM like Compiz, for fast 3D effects.

[https://wiki.archlinux.org/index.php/Compiz Compiz - ArchWiki]

A note on using Kodi Standalone Service, this package runs Kodi as a '''systemd''' service and disables the login for user '''kodi''' and will not work when autologin is enabled. In fact, it will break the login process if you autologin user '''kodi''' and run Kodi Standalone Service at the same time. This package is installed automatically with the standard Kodi package when you install Kodi on Raspbian, but must be configured manually for all other Linux distributions. You can run the '''which''' command to find this package as well.

<pre>
which kodi-standalone
</pre>

Be advised, Kodi Standalone Service still launches the Kodi GUI and still requires a WM even though it is running as a '''systemd''' service. When you install a WM such as '''xfwm4''' (the WM for XFCE4), the CLI will tell you if it provides the '''x-window-manager''' package.

<pre>
Setting up xfwm4 (4.12.4-1) ...
update-alternatives: using /usr/bin/xfwm4 to provide /usr/bin/x-window-manager (x-window-manager) in auto mode
</pre>

If you do not see this message at the end of the installation, the WM you selected does not provide this software package and may not actually be a complete WM itself but only part of a package containing a WM.

For a great example on exactly how you would do this with '''xfwm4''', see this ArchWiki entry.

[https://wiki.archlinux.org/index.php/Xfwm XFWM - ArchWiki]

Most systems utilize the client version of the X11 software an Xsession requires.

For more X11 features and functionality, you may optionally upgrade to the server software packages for the X Window System.

<pre>apt install xauth xorg xinit xserver-xorg-core xserver-xorg xserver-common</pre>

The Ubuntu wiki is usually a good source of information.

[https://wiki.ubuntu.com/CustomXSession CustomXSession - Ubuntu Wiki]

Custom user sessions can be created with the X11 Window System to run scripts, autostart apps, and launch a WM or DE.

LightDM is used for autologin.

== Customize LightDM to autologin ==

You can utilize the ability to customize LightDM data manager by changing the builtin custom configuration file '''50-myconfig.conf''' using '''nano''' or another text editor. If you have no DE or WM you can install '''lightdm''', but should make sure to do a bit of research before you do. Most versions of Linux use LightDM, but many server versions do not. For Ubuntu Server with no DE, for example, installing '''lightdm''' is okay and necessary. Changing the behavior of LightDM is done using a custom '''50-myconfig.conf''' configuration file.

To see if you have '''lightdm''' use '''which'''.

<pre>
which lightdm
</pre>

If not, install it with '''apt'''.

<pre>
apt install lightdm
</pre>

Configure LightDM for autologin to boot directly to Kodi.

<pre>
nano /etc/lightdm/lightdm.conf
</pre>

Uncomment the following line.

<pre>
#autologin-user=
</pre>

And add the user you want to autologin. The user is named '''kodi''' in this example.

<pre>
autologin-user=kodi
</pre>

And then you can create /etc/lightdm/lightdm.conf.d/50-myconfig.conf, but ensure the settings in /etc/lightdm/lightdm.conf agree.

Create a custom configuration file called '''50-myconfig.conf''' using '''nano''' or other CLI text editor.

<pre>
mkdir /etc/lightdm/lightdm.conf.d/
nano /etc/lightdm/lightdm.conf.d/50-myconfig.conf
</pre>

Inside this new file add the following text.

<pre>
[SeatDefaults]
autologin-user=kodi
</pre>

CTRL +O +Enter +X to save and exit from '''nano'''.

== Configure Kodi to autostart ==

Configure Kodi to autostart.

A)

<pre>
sudo sed -i "1i @kodi" /etc/xdg/lxsession/LXDE-pi/autostart
</pre>

B)

<pre>
mkdir -p ~/.config/autostart
ln -s /usr/bin/kodi ~/.config/autostart
</pre>

This method of autostart requires a desktop environment or DE. This is done a bit differently by each DE. Some helpful links can easily be found in today's Web search using any search engine.

[http://edoceo.com/gui/xfce-autostart-apps Autostart Apps in XFCE]

And this link shows how to autostart an app in LXDE on Raspbian.

[http://www.raspberry-projects.com/pi/pi-operating-systems/raspbian/auto-running-programs-gui Auto running programs LXDE - Raspberry Pi Projects]

The Raspberry Pi is a bit more of a tweak, but these are excellent links that will tell you how. The first link is the most helpful to making sure Kodi autostarts in Pi, and utilizes a '''crontab'''. There are many settings on the Pi that control boot, and the first link gives the best most trouble-free way to boot directly to Kodi.

[https://www.leowkahman.com/2016/03/05/lamp-stack-on-raspberry-pi-with-kodi-running-at-startup/ LAMP stack on Raspberry Pi with Kodi running at startup]

In the above link, the author describes using Crontab (short for "Cron table") to boot directly to Kodi.

<pre>
apt install cron
crontab -e
</pre>

Cron will ask you to choose a text editor from available options. I choose option 2 for '''nano'''.

In the new Crontab, enter the following text.

<pre>
@reboot kodi --standalone
</pre>

You could also consider using Crontab to run a script, much like described on this page in the section entitled "Run kodi in a window manager" if you scroll down the page.

[https://wiki.archlinux.org/index.php/Kodi Kodi - Run kodi in a window manager]

Instead your Crontab could look like this.

<pre>
@reboot startx
</pre>

And create an '''~/.xinitrc''' file.

<pre>
nano ~/.xinitrc
</pre>

The '''~/.xinitrc''' file should look like this.

<pre>
#!/bin/bash
kodi --standalone #(this is proper syntax for most Kodi installs)
#kodi-standalone #(this is the syntax that works on Raspbian, not other Pi operating systems)
sudo chvt 2
sleep 1
sudo chvt 1
</pre>

Raspbian has a repository package for everything, so kodi-standalone can be run as a package rather than a command argument. You do not have to install '''kodi-standalone''' with Apt.

<pre>
apt install kodi-standalone
</pre>

For instance, if I were to install '''kodi-standalone''' after installing the standard '''kodi''' package, this is the message I get.

<pre>
root@raspberrypi:/home/pi# apt install kodi-standalone
Reading package lists... Done
Building dependency tree
Reading state information... Done
Note, selecting 'kodi' instead of 'kodi-standalone'
kodi is already the newest version (2:18.7-1~buster).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@raspberrypi:/home/pi#
</pre>

That is because it used to a separate package, but since then it has been made into a command. It is really only a trivial difference, instead of using:

<pre>
@reboot kodi --standalone
</pre>

You can use,

<pre>
@reboot kodi-standalone
</pre>

One or the other, not both.

Make sure to make '''~/.xinitrc''' executable by running.

<pre>
chmod +rx ~/.xinitrc
</pre>

To ensure no password is required by '''sudo''' for any user logging in when this script runs, you must edit /etc/sudoers or run the '''visudo''' command if it is installed to edit /etc/sudoers.

You can install '''visudo''' from your Linux distributions default repository.

<pre>
apt install sudo
</pre>

To use '''visudo''' simply run the command in the terminal.

<pre>
visudo
</pre>

For any non-root users, create an entry in /etc/sudoers with '''nano'''.

<pre>
nano /etc/sudoers
</pre>

Create an entry on any line that is comfortable to you like shown here.

<pre>
kodi ALL=NOPASSWD: /usr/bin/chvt
# pi ALL=NOPASSWD: /usr/bin/chvt #(if you do not add user kodi)
</pre>

The above example is for users '''pi''' and '''kodi'''.

If you decide not use a Cron table, you can always remove it again.

<pre>
crontab -r
</pre>

This is a quick reference for Crontab.

[http://www.adminschoice.com/crontab-quick-reference Crontab Quick Reference]

These linked pages facilitate more tweaks and settings relevant to other uses of the X Window System on Pi.

[http://ozzmaker.com/enable-x-windows-on-piscreen/ Enable X Window System on PiScreen]

Other things to tweak on Raspbian.

[https://yingtongli.me/blog/2016/12/21/splash.html Raspbian splash screen guide - Clean up the boot process]

[https://scribles.net/lightning-bolt-under-voltage-warning-on-raspberry-pi/ Under voltage warning and disabling splash screen on Raspbian]

[https://raspberrypi.stackexchange.com/questions/59310/remove-boot-messages-all-text-in-jessie Remove boot messages all text in Raspbian - Raspberry Pi Stack Exchange]

And, if you would rather, it is easier to follow the process provided by this link to modify the Raspbian image before installing it onto the microSD card.

[https://wiki.debian.org/RaspberryPi/qemu-user-static Modifying Raspbian with qemu-user-static]

The above link describes removing the DE from a Raspbian image, though Raspbian Lite is a much better starting point for using Qemu for this purpose.

You can also use the X11 Window System to autostart Kodi by placing a startup script in the /etc/X11/Xsession.d/ directory.

[https://debian-administration.org/article/50/Running_applications_automatically_when_X_starts Running applications automatically when X starts]

<pre>
nano /etc/X11/Xsession.d/startup-local
</pre>

Insert this text into the new file. Use CTRL + O + Enter + X to save the file.

<pre>
#!/bin/sh
/usr/bin/kodi
</pre>

If you have a WM, such as Blackbox you can add it here as well.

<pre>
#!/bin/sh
blackbox &
/usr/bin/kodi
</pre>

Set permissions to make it executable. Use the ampersand to run each command in the background till the last line or your script will get stuck on the first line.

<pre>
chmod 755 /etc/X11/Xsession.d/startup-local
</pre>

If Kodi is not installed at the standard path, find it using the '''which''' command.

<pre>
which kodi
</pre>

This feature is available on X Window System operating systems most Linux distributions use the X Window System.

== Create custom Xsession script ==

To create a custom Xsession script with a text editor we start with an '''xinitrc''' script. For more detail on how to create and use '''xinit''', there is a great guide available here.

[https://en.wikibooks.org/wiki/Guide_to_X11/Starting_Sessions Guide to X11 - Starting Sessions - WikiBooks]

<pre>
nano ~/.xinitrc
</pre>

To run Kodi full-screen make sure the text reads:

<pre>
#!/usr/bin/env bash
exec gnome-session &
/usr/bin/kodi -fs
</pre>

Replace the '''gnome-session''' with the DE or WM command you are using. See the last section for examples.

To make '''~/.xinitrc''' executable use.

<pre>
chmod +x ~/.xinitrc
</pre>

Use '''sudo''' and the '''~/.xinitrc''' file to configure '''~/.xsession'''.

<pre>
sudo -H -u kodi bash -c "ln -s ~/.xinitrc /home/kodi/.xsession"
</pre>

Make sure the path goes to user's home directory. In this example, the user is '''kodi'''.

You need to use '''sudo''' to run this command. If you do not have '''sudo''', install it.

<pre>
apt install sudo
</pre>

If you create a symbolic link and want to remove it, simply remove the existing '''.xsession''' file you created.

<pre>
rm /home/kodi/.xsession
</pre>

On some systems using a DE such as Gnome, not all systems using Gnome, it may be necessary for '''.xsession''' to be '''.xsessionrc'''. Though this is more likely the case for organization network computers than a personal one, where configurations may vary on a diversity of machines. Most of the time, it will be '''.xsession''' rather than '''.xsessionrc''' that you want to create.

You can also create the '''.xsession''' script directly in the home directory, rather than link it from '''~/.xinitrc'''. This is necessary if you create multiple custom Xsession scripts for multiple users, and you do not in that case link '''~/.xinitrc''' to '''.xsession'''.

To enable multiple displays edit the '''.bashrc''' file.

<pre>
nano ~/.bashrc
</pre>

Add the following text.

<pre>
if [[ ! $DISPLAY && $XDG_VTNR -le 3 ]]; then
exec startx
fi
</pre>

For two monitors add the following as shown.

<pre>
if [[ ! $DISPLAY && $XDG_VTNR -le 2 ]]; then
exec startx
fi
</pre>

For a single monitor use:

<pre>
if [[ ! $DISPLAY && $XDG_VTNR -eq 1 ]]; then
exec startx
fi
</pre>

If you wish to remain logged in after quitting X, remove the '''exec''' from the above. Other configurations can be applied, but are irrelevant to autostarting Kodi.

[https://wiki.archlinux.org/index.php/Xinit#Autostart_X_at_login Xinit Autostart X at login]

If you are using LightDM and you just want to create a new login entry for user '''kodi''', you must create a new file.

<pre>
nano /usr/share/xsessions/custom.desktop
</pre>

And insert the following text.

<pre>
[Desktop Entry]
Name=Xsession
Exec=/etc/X11/Xsession
</pre>

This will create a new login option for the custom Xsession. Only this one entry is necessary for LightDM and X11 to find the '''~/.xsession''' script in each user's home directory.

You can use any window manager or desktop enviroment with a custom Xsession script as long as it is installed.

You do this by creating '''~/.xinitrc''' script that contains the command to start the WM or DE.

For instance, if you are using FluxBox.

<pre>
#!/usr/bin/env bash
exec fluxbox &
/usr/bin/kodi -fs
</pre>

The <code>-fs</code> option is full-screen.

To run Gnome in the background, but launch Kodi in the foreground.

<pre>
#!/usr/bin/env bash
exec gnome-session &
/usr/bin/kodi -fs
</pre>

Use the '''~/.xinitrc''' file to configure '''~/.xsession''' to create a custom login for any user, not just Kodi.

<pre>
sudo -H -u [username] bash -c "ln -s ~/.xinitrc ~/.xsession"
</pre>

You must reconfigure Xserver for any user that is not a privileged user to be able to start a custom Xsession.

<pre>
dpkg-reconfigure xserver-xorg-legacy
dpkg-reconfigure xserver-xorg
</pre>

When you reconfigure X11 with these commands, choose to allow non-root users (anybody) to start an Xsession. You should see your changes take effect after rebooting.

[[Category:Linux]]

HOW-TO:Autostart Kodi for Linux

2019-08-09T01:41:53Z

W3tech: Corrected typo.

<section begin="intro" /><big>Any or all or a combination of these methods can be used to configure a Debian-based X Window System to boot directly to Kodi. This should work on any Linux using the X Window System, but these instructions are particular to Debian derivatives, such as Ubuntu. A server edition is best for running only Kodi, but this page assumes booting into a desktop OS, not a server distro. However, the instructions here can be used for a server distro with even less configuration than for a desktop. Experiment inside VirtualBox before you apply any of these to your system and make a backup.</big><section end="intro" />

__TOC__

== Installing the X11 Window System ==

Even if you are using something like [https://github.com/graysky2/kodi-standalone-service Kodi Standalone Service], you still need use a WM or a DE that installs the '''x-window-manager''' software package.

To ensure you have this installed use the '''which''' command.

<pre>
which x-window-manager
</pre>

If there is no such package, you can use '''apt''' to search your Linux distributions repository.

<pre>
apt-cache search x-window-manager
</pre>

This will generate a list of packages containing '''x-window-manager''', which cannot be installed alone. If you are not using a DE, you need to use a WM. And, you can also use a compositing WM like Compiz, for fast 3D effects.

[https://wiki.archlinux.org/index.php/Compiz Compiz - ArchWiki]

A note on using Kodi Standalone Service, this package runs Kodi as a '''systemd''' service and disables the login for user '''kodi''' and will not work when autologin is enabled. In fact, it will break the login process if you autologin user '''kodi''' and run Kodi Standalone Service at the same time. This package is installed automatically with the standard Kodi package when you install Kodi on Raspbian, but must be configured manually for all other Linux distributions. You can run the '''which''' command to find this package as well.

<pre>
which kodi-standalone
</pre>

Be advised, Kodi Standalone Service still launches the Kodi GUI and still requires a WM even though it is running as a '''systemd''' service. When you install a WM such as '''xfwm4''' (the WM for XFCE4), the CLI will tell you if it provides the '''x-window-manager''' package.

<pre>
Setting up xfwm4 (4.12.4-1) ...
update-alternatives: using /usr/bin/xfwm4 to provide /usr/bin/x-window-manager (x-window-manager) in auto mode
</pre>

If you do not see this message at the end of the installation, the WM you selected does not provide this software package and may not actually be a complete WM itself but only part of a package containing a WM.

For a great example on exactly how you would do this with '''xfwm4''', see this ArchWiki entry.

[https://wiki.archlinux.org/index.php/Xfwm XFWM - ArchWiki]

Most systems utilize the client version of the X11 software an Xsession requires.

For more X11 features and functionality, you may optionally upgrade to the server software packages for the X Window System.

<pre>apt install xauth xorg xinit xserver-xorg-core xserver-xorg xserver-common</pre>

The Ubuntu wiki is usually a good source of information.

[https://wiki.ubuntu.com/CustomXSession CustomXSession - Ubuntu Wiki]

Custom user sessions can be created with the X11 Window System to run scripts, autostart apps, and launch a WM or DE.

LightDM is used for autologin.

== Customize LightDM to autologin ==

You can utilize the ability to customize LightDM data manager by changing the builtin custom configuration file '''50-myconfig.conf''' using '''nano''' or another text editor. If you have no DE or WM you can install '''lightdm''', but should make sure to do a bit of research before you do. Most versions of Linux use LightDM, but many server versions do not. For Ubuntu Server with no DE, for example, installing '''lightdm''' is okay and necessary. Changing the behavior of LightDM is done using a custom '''50-myconfig.conf''' configuration file.

To see if you have '''lightdm''' use '''which'''.

<pre>
which lightdm
</pre>

If not, install it with '''apt'''.

<pre>
apt install lightdm
</pre>

Configure LightDM for autologin to boot directly to Kodi.

<pre>
nano /etc/lightdm/lightdm.conf
</pre>

Uncomment the following line.

<pre>
#autologin-user=
</pre>

And add the user you want to autologin. The user is named '''kodi''' in this example.

<pre>
autologin-user=kodi
</pre>

And then you can create /etc/lightdm/lightdm.conf.d/50-myconfig.conf, but ensure the settings in /etc/lightdm/lightdm.conf agree.

Create a custom configuration file called '''50-myconfig.conf''' using '''nano''' or other CLI text editor.

<pre>
mkdir /etc/lightdm/lightdm.conf.d/
nano /etc/lightdm/lightdm.conf.d/50-myconfig.conf
</pre>

Inside this new file add the following text.

<pre>
[SeatDefaults]
autologin-user=kodi
</pre>

CTRL +O +Enter +X to save and exit from '''nano'''.

== Configure Kodi to autostart ==

Configure Kodi to autostart.

<pre>
mkdir -p ~/.config/autostart
ln -s /usr/bin/kodi ~/.config/autostart
</pre>

This method of autostart requires a desktop environment or DE. This is done a bit differently by each DE. Some helpful links can easily be found in today's Web search using any search engine.

[http://edoceo.com/gui/xfce-autostart-apps Autostart Apps in XFCE]

And this link shows how to autostart an app in LXDE on Raspbian.

[http://www.raspberry-projects.com/pi/pi-operating-systems/raspbian/auto-running-programs-gui Auto running programs LXDE - Raspberry Pi Projects]

The Raspberry Pi is a bit more of a tweak, but these are excellent links that will tell you how. The first link is the most helpful to making sure Kodi autostarts in Pi, and utilizes a '''crontab'''. There are many settings on the Pi that control boot, and the first link gives the best most trouble-free way to boot directly to Kodi.

[https://www.leowkahman.com/2016/03/05/lamp-stack-on-raspberry-pi-with-kodi-running-at-startup/ LAMP stack on Raspberry Pi with Kodi running at startup]

In the above link, the author describes using Crontab (short for "Cron table") to boot directly to Kodi.

<pre>
apt install cron
crontab -e
</pre>

Cron will ask you to choose a text editor from available options. I choose option 2 for '''nano'''.

In the new Crontab, enter the following text.

<pre>
@reboot kodi --standalone
</pre>

You could also consider using Crontab to run a script, much like described on this page in the section entitled "Run kodi in a window manager" if you scroll down the page.

[https://wiki.archlinux.org/index.php/Kodi Kodi - Run kodi in a window manager]

Instead your Crontab could look like this.

<pre>
@reboot startx
</pre>

And create an '''~/.xinitrc''' file.

<pre>
nano ~/.xinitrc
</pre>

The '''~/.xinitrc''' file should look like this.

<pre>
#!/bin/bash
kodi --standalone #(this is proper syntax for most Kodi installs)
#kodi-standalone #(this is the syntax that works on Raspbian, not other Pi operating systems)
sudo chvt 2
sleep 1
sudo chvt 1
</pre>

Raspbian has a repository package for everything, so kodi-standalone can be run as a package rather than a command argument.

Make sure to make '''~/.xinitrc''' executable by running.

<pre>
chmod +x ~/.xinitrc
</pre>

To ensure no password is required by '''sudo''' for any user logging in when this script runs, you must edit /etc/sudoers or run the '''visudo''' command if it is installed to edit /etc/sudoers.

You can install '''visudo''' from your Linux distributions default repository.

<pre>
apt install sudo
</pre>

To use '''visudo''' simply run the command in the terminal.

<pre>
visudo
</pre>

For any non-root users, create an entry in /etc/sudoers with '''nano'''.

<pre>
nano /etc/sudoers
</pre>

Create an entry on any line that is comfortable to you like shown here.

<pre>
kodi ALL=NOPASSWD: /usr/bin/chvt
# pi ALL=NOPASSWD: /usr/bin/chvt #(if you do not add user kodi)
</pre>

The above example is for users '''pi''' and '''kodi'''.

If you decide not use a Cron table, you can always remove it again.

<pre>
crontab -r
</pre>

This is a quick reference for Crontab.

[http://www.adminschoice.com/crontab-quick-reference Crontab Quick Reference]

These linked pages facilitate more tweaks and settings relevant to other uses of the X Window System on Pi.

[http://ozzmaker.com/enable-x-windows-on-piscreen/ Enable X Window System on PiScreen]

Other things to tweak on Raspbian.

[https://yingtongli.me/blog/2016/12/21/splash.html Raspbian splash screen guide - Clean up the boot process]

[https://scribles.net/lightning-bolt-under-voltage-warning-on-raspberry-pi/ Under voltage warning and disabling splash screen on Raspbian]

[https://raspberrypi.stackexchange.com/questions/59310/remove-boot-messages-all-text-in-jessie Remove boot messages all text in Raspbian - Raspberry Pi Stack Exchange]

And, if you would rather, it is easier to follow the process provided by this link to modify the Raspbian image before installing it onto the microSD card.

[https://wiki.debian.org/RaspberryPi/qemu-user-static Modifying Raspbian with qemu-user-static]

The above link describes removing the DE from a Raspbian image, though Raspbian Lite is a much better starting point for using Qemu for this purpose.

You can also use the X11 Window System to autostart Kodi by placing a startup script in the /etc/X11/Xsession.d/ directory.

[https://debian-administration.org/article/50/Running_applications_automatically_when_X_starts Running applications automatically when X starts]

<pre>
nano /etc/X11/Xsession.d/startup-local
</pre>

Insert this text into the new file. Use CTRL + O + Enter + X to save the file.

<pre>
#!/bin/sh
/usr/bin/kodi
</pre>

If you have a WM, such as Blackbox you can add it here as well.

<pre>
#!/bin/sh
blackbox &
/usr/bin/kodi
</pre>

Set permissions to make it executable. Use the ampersand to run each command in the background till the last line or your script will get stuck on the first line.

<pre>
chmod 755 /etc/X11/Xsession.d/startup-local
</pre>

If Kodi is not installed at the standard path, find it using the '''which''' command.

<pre>
which kodi
</pre>

This feature is available on X Window System operating systems most Linux distributions use the X Window System.

== Create custom Xsession script ==

To create a custom Xsession script with a text editor we start with an '''xinitrc''' script. For more detail on how to create and use '''xinit''', there is a great guide available here.

[https://en.wikibooks.org/wiki/Guide_to_X11/Starting_Sessions Guide to X11 - Starting Sessions - WikiBooks]

<pre>
nano ~/.xinitrc
</pre>

To run Kodi full-screen make sure the text reads:

<pre>
#!/usr/bin/env bash
exec gnome-session &
/usr/bin/kodi -fs
</pre>

Replace the '''gnome-session''' with the DE or WM command you are using. See the last section for examples.

To make '''~/.xinitrc''' executable use.

<pre>
chmod +x ~/.xinitrc
</pre>

Use '''sudo''' and the '''~/.xinitrc''' file to configure '''~/.xsession'''.

<pre>
sudo -H -u kodi bash -c "ln -s ~/.xinitrc /home/kodi/.xsession"
</pre>

Make sure the path goes to user's home directory. In this example, the user is '''kodi'''.

You need to use '''sudo''' to run this command. If you do not have '''sudo''', install it.

<pre>
apt install sudo
</pre>

If you create a symbolic link and want to remove it, simply remove the existing '''.xsession''' file you created.

<pre>
rm /home/kodi/.xsession
</pre>

On some systems using a DE such as Gnome, not all systems using Gnome, it may be necessary for '''.xsession''' to be '''.xsessionrc'''. Though this is more likely the case for organization network computers than a personal one, where configurations may vary on a diversity of machines. Most of the time, it will be '''.xsession''' rather than '''.xsessionrc''' that you want to create.

You can also create the '''.xsession''' script directly in the home directory, rather than link it from '''~/.xinitrc'''. This is necessary if you create multiple custom Xsession scripts for multiple users, and you do not in that case link '''~/.xinitrc''' to '''.xsession'''.

To enable multiple displays edit the '''.bashrc''' file.

<pre>
nano ~/.bashrc
</pre>

Add the following text.

<pre>
if [[ ! $DISPLAY && $XDG_VTNR -le 3 ]]; then
exec startx
fi
</pre>

For two monitors add the following as shown.

<pre>
if [[ ! $DISPLAY && $XDG_VTNR -le 2 ]]; then
exec startx
fi
</pre>

For a single monitor use:

<pre>
if [[ ! $DISPLAY && $XDG_VTNR -eq 1 ]]; then
exec startx
fi
</pre>

If you wish to remain logged in after quitting X, remove the '''exec''' from the above. Other configurations can be applied, but are irrelevant to autostarting Kodi.

[https://wiki.archlinux.org/index.php/Xinit#Autostart_X_at_login Xinit Autostart X at login]

If you are using LightDM and you just want to create a new login entry for user '''kodi''', you must create a new file.

<pre>
nano /usr/share/xsessions/custom.desktop
</pre>

And insert the following text.

<pre>
[Desktop Entry]
Name=Xsession
Exec=/etc/X11/Xsession
</pre>

This will create a new login option for the custom Xsession. Only this one entry is necessary for LightDM and X11 to find the '''~/.xsession''' script in each user's home directory.

You can use any window manager or desktop enviroment with a custom Xsession script as long as it is installed.

You do this by creating '''~/.xinitrc''' script that contains the command to start the WM or DE.

For instance, if you are using FluxBox.

<pre>
#!/usr/bin/env bash
exec fluxbox &
/usr/bin/kodi -fs
</pre>

The <code>-fs</code> option is full-screen.

To run Gnome in the background, but launch Kodi in the foreground.

<pre>
#!/usr/bin/env bash
exec gnome-session &
/usr/bin/kodi -fs
</pre>

Use the '''~/.xinitrc''' file to configure '''~/.xsession''' to create a custom login for any user, not just Kodi.

<pre>
sudo -H -u [username] bash -c "ln -s ~/.xinitrc ~/.xsession"
</pre>

You must reconfigure Xserver for any user that is not a privileged user to be able to start a custom Xsession.

<pre>
dpkg-reconfigure xserver-xorg-legacy
dpkg-reconfigure xserver-xorg
</pre>

When you reconfigure X11 with these commands, choose to allow non-root users (anybody) to start an Xsession. You should see your changes take effect after rebooting.

HOW-TO:Autostart Kodi for Linux

2018-12-19T15:25:01Z

W3tech: /* Create custom Xsession script */

<section begin="intro" /><big>Any or all or a combination of these methods can be used to configure a Debian-based X Window System to boot directly to Kodi. This should work on any Linux using the X Window System, but these instructions are particular to Debian derivatives, such as Ubuntu. A server edition is best for running only Kodi, but this page assumes booting into a desktop OS, not a server distro. However, the instructions here can be used for a server distro with even less configuration than for a desktop. Experiment inside VirtualBox before you apply any of these to your system and make a backup.</big><section end="intro" />

__TOC__

== Installing the X11 Window System ==

Even if you are using something like [https://github.com/graysky2/kodi-standalone-service Kodi Standalone Service], you still need use a WM or a DE that installs the '''x-window-manager''' software package.

To ensure you have this installed use the '''which''' command.

<pre>
which x-window-manager
</pre>

If there is no such package, you can use '''apt''' to search your Linux distributions repository.

<pre>
apt-cache search x-window-manager
</pre>

This will general a list of packages containing '''x-window-manager''', which cannot be installed alone. If you are not using a DE, you need to use a WM. And, you can also use a compositing WM like Compiz, for fast 3D effects.

[https://wiki.archlinux.org/index.php/Compiz Compiz - ArchWiki]

A note on using Kodi Standalone Service, this package runs Kodi as a '''systemd''' service and disables the login for user '''kodi''' and will not work when autologin is enabled. In fact, it will break the login process if you autologin user '''kodi''' and run Kodi Standalone Service at the same time. This package is installed automatically with the standard Kodi package when you install Kodi on Raspbian, but must be configured manually for all other Linux distributions. You can run the '''which''' command to find this package as well.

<pre>
which kodi-standalone
</pre>

Be advised, Kodi Standalone Service still launches the Kodi GUI and still requires a WM even though it is running as a '''systemd''' service. When you install a WM such as '''xfwm4''' (the WM for XFCE4), the CLI will tell you if it provides the '''x-window-manager''' package.

<pre>
Setting up xfwm4 (4.12.4-1) ...
update-alternatives: using /usr/bin/xfwm4 to provide /usr/bin/x-window-manager (x-window-manager) in auto mode
</pre>

If you do not see this message at the end of the installation, the WM you selected does not provide this software package and may not actually be a complete WM itself but only part of a package containing a WM.

For a great example on exactly how you would do this with '''xfwm4''', see this ArchWiki entry.

[https://wiki.archlinux.org/index.php/Xfwm XFWM - ArchWiki]

Most systems utilize the client version of the X11 software an Xsession requires.

For more X11 features and functionality, you may optionally upgrade to the server software packages for the X Window System.

<pre>apt install xauth xorg xinit xserver-xorg-core xserver-xorg xserver-common</pre>

The Ubuntu wiki is usually a good source of information.

[https://wiki.ubuntu.com/CustomXSession CustomXSession - Ubuntu Wiki]

Custom user sessions can be created with the X11 Window System to run scripts, autostart apps, and launch a WM or DE.

LightDM is used for autologin.

== Customize LightDM to autologin ==

You can utilize the ability to customize LightDM data manager by changing the builtin custom configuration file '''50-myconfig.conf''' using '''nano''' or another text editor. If you have no DE or WM you can install '''lightdm''', but should make sure to do a bit of research before you do. Most versions of Linux use LightDM, but many server versions do not. For Ubuntu Server with no DE, for example, installing '''lightdm''' is okay and necessary. Changing the behavior of LightDM is done using a custom '''50-myconfig.conf''' configuration file.

To see if you have '''lightdm''' use '''which'''.

<pre>
which lightdm
</pre>

If not, install it with '''apt'''.

<pre>
apt install lightdm
</pre>

Configure LightDM for autologin to boot directly to Kodi.

<pre>
nano /etc/lightdm/lightdm.conf
</pre>

Uncomment the following line.

<pre>
#autologin-user=
</pre>

And add the user you want to autologin. The user is named '''kodi''' in this example.

<pre>
autologin-user=kodi
</pre>

And then you can create /etc/lightdm/lightdm.conf.d/50-myconfig.conf, but ensure the settings in /etc/lightdm/lightdm.conf agree.

Create a custom configuration file called '''50-myconfig.conf''' using '''nano''' or other CLI text editor.

<pre>
mkdir /etc/lightdm/lightdm.conf.d/
nano /etc/lightdm/lightdm.conf.d/50-myconfig.conf
</pre>

Inside this new file add the following text.

<pre>
[SeatDefaults]
autologin-user=kodi
</pre>

CTRL +O +Enter +X to save and exit from '''nano'''.

== Configure Kodi to autostart ==

Configure Kodi to autostart.

<pre>
mkdir -p ~/.config/autostart
ln -s /usr/bin/kodi ~/.config/autostart
</pre>

This method of autostart requires a desktop environment or DE. This is done a bit differently by each DE. Some helpful links can easily be found in today's Web search using any search engine.

[http://edoceo.com/gui/xfce-autostart-apps Autostart Apps in XFCE]

And this link shows how to autostart an app in LXDE on Raspbian.

[http://www.raspberry-projects.com/pi/pi-operating-systems/raspbian/auto-running-programs-gui Auto running programs LXDE - Raspberry Pi Projects]

The Raspberry Pi is a bit more of a tweak, but these are excellent links that will tell you how. The first link is the most helpful to making sure Kodi autostarts in Pi, and utilizes a '''crontab'''. There are many settings on the Pi that control boot, and the first link gives the best most trouble-free way to boot directly to Kodi.

[https://www.leowkahman.com/2016/03/05/lamp-stack-on-raspberry-pi-with-kodi-running-at-startup/ LAMP stack on Raspberry Pi with Kodi running at startup]

In the above link, the author describes using Crontab (short for "Cron table") to boot directly to Kodi.

<pre>
apt install cron
crontab -e
</pre>

Cron will ask you to choose a text editor from available options. I choose option 2 for '''nano'''.

In the new Crontab, enter the following text.

<pre>
@reboot kodi --standalone
</pre>

You could also consider using Crontab to run a script, much like described on this page in the section entitled "Run kodi in a window manager" if you scroll down the page.

[https://wiki.archlinux.org/index.php/Kodi Kodi - Run kodi in a window manager]

Instead your Crontab could look like this.

<pre>
@reboot startx
</pre>

And create an '''~/.xinitrc''' file.

<pre>
nano ~/.xinitrc
</pre>

The '''~/.xinitrc''' file should look like this.

<pre>
#!/bin/bash
kodi --standalone #(this is proper syntax for most Kodi installs)
#kodi-standalone #(this is the syntax that works on Raspbian, not other Pi operating systems)
sudo chvt 2
sleep 1
sudo chvt 1
</pre>

Raspbian has a repository package for everything, so kodi-standalone can be run as a package rather than a command argument.

Make sure to make '''~/.xinitrc''' executable by running.

<pre>
chmod +x ~/.xinitrc
</pre>

To ensure no password is required by '''sudo''' for any user logging in when this script runs, you must edit /etc/sudoers or run the '''visudo''' command if it is installed to edit /etc/sudoers.

You can install '''visudo''' from your Linux distributions default repository.

<pre>
apt install sudo
</pre>

To use '''visudo''' simply run the command in the terminal.

<pre>
visudo
</pre>

For any non-root users, create an entry in /etc/sudoers with '''nano'''.

<pre>
nano /etc/sudoers
</pre>

Create an entry on any line that is comfortable to you like shown here.

<pre>
kodi ALL=NOPASSWD: /usr/bin/chvt
# pi ALL=NOPASSWD: /usr/bin/chvt #(if you do not add user kodi)
</pre>

The above example is for users '''pi''' and '''kodi'''.

If you decide not use a Cron table, you can always remove it again.

<pre>
crontab -r
</pre>

This is a quick reference for Crontab.

[http://www.adminschoice.com/crontab-quick-reference Crontab Quick Reference]

These linked pages facilitate more tweaks and settings relevant to other uses of the X Window System on Pi.

[http://ozzmaker.com/enable-x-windows-on-piscreen/ Enable X Window System on PiScreen]

Other things to tweak on Raspbian.

[https://yingtongli.me/blog/2016/12/21/splash.html Raspbian splash screen guide - Clean up the boot process]

[https://scribles.net/lightning-bolt-under-voltage-warning-on-raspberry-pi/ Under voltage warning and disabling splash screen on Raspbian]

[https://raspberrypi.stackexchange.com/questions/59310/remove-boot-messages-all-text-in-jessie Remove boot messages all text in Raspbian - Raspberry Pi Stack Exchange]

And, if you would rather, it is easier to follow the process provided by this link to modify the Raspbian image before installing it onto the microSD card.

[https://wiki.debian.org/RaspberryPi/qemu-user-static Modifying Raspbian with qemu-user-static]

The above link describes removing the DE from a Raspbian image, though Raspbian Lite is a much better starting point for using Qemu for this purpose.

You can also use the X11 Window System to autostart Kodi by placing a startup script in the /etc/X11/Xsession.d/ directory.

[https://debian-administration.org/article/50/Running_applications_automatically_when_X_starts Running applications automatically when X starts]

<pre>
nano /etc/X11/Xsession.d/startup-local
</pre>

Insert this text into the new file. Use CTRL + O + Enter + X to save the file.

<pre>
#!/bin/sh
/usr/bin/kodi
</pre>

If you have a WM, such as Blackbox you can add it here as well.

<pre>
#!/bin/sh
blackbox &
/usr/bin/kodi
</pre>

Set permissions to make it executable. Use the ampersand to run each command in the background till the last line or your script will get stuck on the first line.

<pre>
chmod 755 /etc/X11/Xsession.d/startup-local
</pre>

If Kodi is not installed at the standard path, find it using the '''which''' command.

<pre>
which kodi
</pre>

This feature is available on X Window System operating systems most Linux distributions use the X Window System.

== Create custom Xsession script ==

To create a custom Xsession script with a text editor we start with an '''xinitrc''' script. For more detail on how to create and use '''xinit''', there is a great guide available here.

[https://en.wikibooks.org/wiki/Guide_to_X11/Starting_Sessions Guide to X11 - Starting Sessions - WikiBooks]

<pre>
nano ~/.xinitrc
</pre>

To run Kodi full-screen make sure the text reads:

<pre>
#!/usr/bin/env bash
exec gnome-session &
/usr/bin/kodi -fs
</pre>

Replace the '''gnome-session''' with the DE or WM command you are using. See the last section for examples.

To make '''~/.xinitrc''' executable use.

<pre>
chmod +x ~/.xinitrc
</pre>

Use '''sudo''' and the '''~/.xinitrc''' file to configure '''~/.xsession'''.

<pre>
sudo -H -u kodi bash -c "ln -s ~/.xinitrc /home/kodi/.xsession"
</pre>

Make sure the path goes to user's home directory. In this example, the user is '''kodi'''.

You need to use '''sudo''' to run this command. If you do not have '''sudo''', install it.

<pre>
apt install sudo
</pre>

If you create a symbolic link and want to remove it, simply remove the existing '''.xsession''' file you created.

<pre>
rm /home/kodi/.xsession
</pre>

On some systems using a DE such as Gnome, not all systems using Gnome, it may be necessary for '''.xsession''' to be '''.xsessionrc'''. Though this is more likely the case for organization network computers than a personal one, where configurations may vary on a diversity of machines. Most of the time, it will be '''.xsession''' rather than '''.xsessionrc''' that you want to create.

You can also create the '''.xsession''' script directly in the home directory, rather than link it from '''~/.xinitrc'''. This is necessary if you create multiple custom Xsession scripts for multiple users, and you do not in that case link '''~/.xinitrc''' to '''.xsession'''.

To enable multiple displays edit the '''.bashrc''' file.

<pre>
nano ~/.bashrc
</pre>

Add the following text.

<pre>
if [[ ! $DISPLAY && $XDG_VTNR -le 3 ]]; then
exec startx
fi
</pre>

For two monitors add the following as shown.

<pre>
if [[ ! $DISPLAY && $XDG_VTNR -le 2 ]]; then
exec startx
fi
</pre>

For a single monitor use:

<pre>
if [[ ! $DISPLAY && $XDG_VTNR -eq 1 ]]; then
exec startx
fi
</pre>

If you wish to remain logged in after quitting X, remove the '''exec''' from the above. Other configurations can be applied, but are irrelevant to autostarting Kodi.

[https://wiki.archlinux.org/index.php/Xinit#Autostart_X_at_login Xinit Autostart X at login]

If you are using LightDM and you just want to create a new login entry for user '''kodi''', you must create a new file.

<pre>
nano /usr/share/xsessions/custom.desktop
</pre>

And insert the following text.

<pre>
[Desktop Entry]
Name=Xsession
Exec=/etc/X11/Xsession
</pre>

This will create a new login option for the custom Xsession. Only this one entry is necessary for LightDM and X11 to find the '''~/.xsession''' script in each user's home directory.

You can use any window manager or desktop enviroment with a custom Xsession script as long as it is installed.

You do this by creating '''~/.xinitrc''' script that contains the command to start the WM or DE.

For instance, if you are using FluxBox.

<pre>
#!/usr/bin/env bash
exec fluxbox &
/usr/bin/kodi -fs
</pre>

The <code>-fs</code> option is full-screen.

To run Gnome in the background, but launch Kodi in the foreground.

<pre>
#!/usr/bin/env bash
exec gnome-session &
/usr/bin/kodi -fs
</pre>

Use the '''~/.xinitrc''' file to configure '''~/.xsession''' to create a custom login for any user, not just Kodi.

<pre>
sudo -H -u [username] bash -c "ln -s ~/.xinitrc ~/.xsession"
</pre>

You must reconfigure Xserver for any user that is not a privileged user to be able to start a custom Xsession.

<pre>
dpkg-reconfigure xserver-xorg-legacy
dpkg-reconfigure xserver-xorg
</pre>

When you reconfigure X11 with these commands, choose to allow non-root users (anybody) to start an Xsession. You should see your changes take effect after rebooting.

HOW-TO:Autostart Kodi for Linux

2018-12-19T15:22:06Z

W3tech: /* Configure Kodi to autostart */

<section begin="intro" /><big>Any or all or a combination of these methods can be used to configure a Debian-based X Window System to boot directly to Kodi. This should work on any Linux using the X Window System, but these instructions are particular to Debian derivatives, such as Ubuntu. A server edition is best for running only Kodi, but this page assumes booting into a desktop OS, not a server distro. However, the instructions here can be used for a server distro with even less configuration than for a desktop. Experiment inside VirtualBox before you apply any of these to your system and make a backup.</big><section end="intro" />

__TOC__

== Installing the X11 Window System ==

Even if you are using something like [https://github.com/graysky2/kodi-standalone-service Kodi Standalone Service], you still need use a WM or a DE that installs the '''x-window-manager''' software package.

To ensure you have this installed use the '''which''' command.

<pre>
which x-window-manager
</pre>

If there is no such package, you can use '''apt''' to search your Linux distributions repository.

<pre>
apt-cache search x-window-manager
</pre>

This will general a list of packages containing '''x-window-manager''', which cannot be installed alone. If you are not using a DE, you need to use a WM. And, you can also use a compositing WM like Compiz, for fast 3D effects.

[https://wiki.archlinux.org/index.php/Compiz Compiz - ArchWiki]

A note on using Kodi Standalone Service, this package runs Kodi as a '''systemd''' service and disables the login for user '''kodi''' and will not work when autologin is enabled. In fact, it will break the login process if you autologin user '''kodi''' and run Kodi Standalone Service at the same time. This package is installed automatically with the standard Kodi package when you install Kodi on Raspbian, but must be configured manually for all other Linux distributions. You can run the '''which''' command to find this package as well.

<pre>
which kodi-standalone
</pre>

Be advised, Kodi Standalone Service still launches the Kodi GUI and still requires a WM even though it is running as a '''systemd''' service. When you install a WM such as '''xfwm4''' (the WM for XFCE4), the CLI will tell you if it provides the '''x-window-manager''' package.

<pre>
Setting up xfwm4 (4.12.4-1) ...
update-alternatives: using /usr/bin/xfwm4 to provide /usr/bin/x-window-manager (x-window-manager) in auto mode
</pre>

If you do not see this message at the end of the installation, the WM you selected does not provide this software package and may not actually be a complete WM itself but only part of a package containing a WM.

For a great example on exactly how you would do this with '''xfwm4''', see this ArchWiki entry.

[https://wiki.archlinux.org/index.php/Xfwm XFWM - ArchWiki]

Most systems utilize the client version of the X11 software an Xsession requires.

For more X11 features and functionality, you may optionally upgrade to the server software packages for the X Window System.

<pre>apt install xauth xorg xinit xserver-xorg-core xserver-xorg xserver-common</pre>

The Ubuntu wiki is usually a good source of information.

[https://wiki.ubuntu.com/CustomXSession CustomXSession - Ubuntu Wiki]

Custom user sessions can be created with the X11 Window System to run scripts, autostart apps, and launch a WM or DE.

LightDM is used for autologin.

== Customize LightDM to autologin ==

You can utilize the ability to customize LightDM data manager by changing the builtin custom configuration file '''50-myconfig.conf''' using '''nano''' or another text editor. If you have no DE or WM you can install '''lightdm''', but should make sure to do a bit of research before you do. Most versions of Linux use LightDM, but many server versions do not. For Ubuntu Server with no DE, for example, installing '''lightdm''' is okay and necessary. Changing the behavior of LightDM is done using a custom '''50-myconfig.conf''' configuration file.

To see if you have '''lightdm''' use '''which'''.

<pre>
which lightdm
</pre>

If not, install it with '''apt'''.

<pre>
apt install lightdm
</pre>

Configure LightDM for autologin to boot directly to Kodi.

<pre>
nano /etc/lightdm/lightdm.conf
</pre>

Uncomment the following line.

<pre>
#autologin-user=
</pre>

And add the user you want to autologin. The user is named '''kodi''' in this example.

<pre>
autologin-user=kodi
</pre>

And then you can create /etc/lightdm/lightdm.conf.d/50-myconfig.conf, but ensure the settings in /etc/lightdm/lightdm.conf agree.

Create a custom configuration file called '''50-myconfig.conf''' using '''nano''' or other CLI text editor.

<pre>
mkdir /etc/lightdm/lightdm.conf.d/
nano /etc/lightdm/lightdm.conf.d/50-myconfig.conf
</pre>

Inside this new file add the following text.

<pre>
[SeatDefaults]
autologin-user=kodi
</pre>

CTRL +O +Enter +X to save and exit from '''nano'''.

== Configure Kodi to autostart ==

Configure Kodi to autostart.

<pre>
mkdir -p ~/.config/autostart
ln -s /usr/bin/kodi ~/.config/autostart
</pre>

This method of autostart requires a desktop environment or DE. This is done a bit differently by each DE. Some helpful links can easily be found in today's Web search using any search engine.

[http://edoceo.com/gui/xfce-autostart-apps Autostart Apps in XFCE]

And this link shows how to autostart an app in LXDE on Raspbian.

[http://www.raspberry-projects.com/pi/pi-operating-systems/raspbian/auto-running-programs-gui Auto running programs LXDE - Raspberry Pi Projects]

The Raspberry Pi is a bit more of a tweak, but these are excellent links that will tell you how. The first link is the most helpful to making sure Kodi autostarts in Pi, and utilizes a '''crontab'''. There are many settings on the Pi that control boot, and the first link gives the best most trouble-free way to boot directly to Kodi.

[https://www.leowkahman.com/2016/03/05/lamp-stack-on-raspberry-pi-with-kodi-running-at-startup/ LAMP stack on Raspberry Pi with Kodi running at startup]

In the above link, the author describes using Crontab (short for "Cron table") to boot directly to Kodi.

<pre>
apt install cron
crontab -e
</pre>

Cron will ask you to choose a text editor from available options. I choose option 2 for '''nano'''.

In the new Crontab, enter the following text.

<pre>
@reboot kodi --standalone
</pre>

You could also consider using Crontab to run a script, much like described on this page in the section entitled "Run kodi in a window manager" if you scroll down the page.

[https://wiki.archlinux.org/index.php/Kodi Kodi - Run kodi in a window manager]

Instead your Crontab could look like this.

<pre>
@reboot startx
</pre>

And create an '''~/.xinitrc''' file.

<pre>
nano ~/.xinitrc
</pre>

The '''~/.xinitrc''' file should look like this.

<pre>
#!/bin/bash
kodi --standalone #(this is proper syntax for most Kodi installs)
#kodi-standalone #(this is the syntax that works on Raspbian, not other Pi operating systems)
sudo chvt 2
sleep 1
sudo chvt 1
</pre>

Raspbian has a repository package for everything, so kodi-standalone can be run as a package rather than a command argument.

Make sure to make '''~/.xinitrc''' executable by running.

<pre>
chmod +x ~/.xinitrc
</pre>

To ensure no password is required by '''sudo''' for any user logging in when this script runs, you must edit /etc/sudoers or run the '''visudo''' command if it is installed to edit /etc/sudoers.

You can install '''visudo''' from your Linux distributions default repository.

<pre>
apt install sudo
</pre>

To use '''visudo''' simply run the command in the terminal.

<pre>
visudo
</pre>

For any non-root users, create an entry in /etc/sudoers with '''nano'''.

<pre>
nano /etc/sudoers
</pre>

Create an entry on any line that is comfortable to you like shown here.

<pre>
kodi ALL=NOPASSWD: /usr/bin/chvt
# pi ALL=NOPASSWD: /usr/bin/chvt #(if you do not add user kodi)
</pre>

The above example is for users '''pi''' and '''kodi'''.

If you decide not use a Cron table, you can always remove it again.

<pre>
crontab -r
</pre>

This is a quick reference for Crontab.

[http://www.adminschoice.com/crontab-quick-reference Crontab Quick Reference]

These linked pages facilitate more tweaks and settings relevant to other uses of the X Window System on Pi.

[http://ozzmaker.com/enable-x-windows-on-piscreen/ Enable X Window System on PiScreen]

Other things to tweak on Raspbian.

[https://yingtongli.me/blog/2016/12/21/splash.html Raspbian splash screen guide - Clean up the boot process]

[https://scribles.net/lightning-bolt-under-voltage-warning-on-raspberry-pi/ Under voltage warning and disabling splash screen on Raspbian]

[https://raspberrypi.stackexchange.com/questions/59310/remove-boot-messages-all-text-in-jessie Remove boot messages all text in Raspbian - Raspberry Pi Stack Exchange]

And, if you would rather, it is easier to follow the process provided by this link to modify the Raspbian image before installing it onto the microSD card.

[https://wiki.debian.org/RaspberryPi/qemu-user-static Modifying Raspbian with qemu-user-static]

The above link describes removing the DE from a Raspbian image, though Raspbian Lite is a much better starting point for using Qemu for this purpose.

You can also use the X11 Window System to autostart Kodi by placing a startup script in the /etc/X11/Xsession.d/ directory.

[https://debian-administration.org/article/50/Running_applications_automatically_when_X_starts Running applications automatically when X starts]

<pre>
nano /etc/X11/Xsession.d/startup-local
</pre>

Insert this text into the new file. Use CTRL + O + Enter + X to save the file.

<pre>
#!/bin/sh
/usr/bin/kodi
</pre>

If you have a WM, such as Blackbox you can add it here as well.

<pre>
#!/bin/sh
blackbox &
/usr/bin/kodi
</pre>

Set permissions to make it executable. Use the ampersand to run each command in the background till the last line or your script will get stuck on the first line.

<pre>
chmod 755 /etc/X11/Xsession.d/startup-local
</pre>

If Kodi is not installed at the standard path, find it using the '''which''' command.

<pre>
which kodi
</pre>

This feature is available on X Window System operating systems most Linux distributions use the X Window System.

== Create custom Xsession script ==

To create a custom Xsession script with a text editor we start with an '''xinitrc''' script. For more detail on how to create and use '''xinit''', there is a great guide available here.

[https://en.wikibooks.org/wiki/Guide_to_X11/Starting_Sessions Guide to X11 - Starting Sessions - WikiBooks]

<pre>
nano ~/.xinitrc
</pre>

To run Kodi full-screen make sure the text reads:

<pre>
#!/usr/bin/env bash
exec gnome-session
/usr/bin/kodi -fs
</pre>

Replace the '''gnome-session''' with the DE or WM command you are using. See the last section for examples.

To make '''~/.xinitrc''' executable use.

<pre>
chmod +x ~/.xinitrc
</pre>

Use '''sudo''' and the '''~/.xinitrc''' file to configure '''~/.xsession'''.

<pre>
sudo -H -u kodi bash -c "ln -s ~/.xinitrc /home/kodi/.xsession"
</pre>

Make sure the path goes to user's home directory. In this example, the user is '''kodi'''.

You need to use '''sudo''' to run this command. If you do not have '''sudo''', install it.

<pre>
apt install sudo
</pre>

If you create a symbolic link and want to remove it, simply remove the existing '''.xsession''' file you created.

<pre>
rm /home/kodi/.xsession
</pre>

On some systems using a DE such as Gnome, not all systems using Gnome, it may be necessary for '''.xsession''' to be '''.xsessionrc'''. Though this is more likely the case for organization network computers than a personal one, where configurations may vary on a diversity of machines. Most of the time, it will be '''.xsession''' rather than '''.xsessionrc''' that you want to create.

You can also create the '''.xsession''' script directly in the home directory, rather than link it from '''~/.xinitrc'''. This is necessary if you create multiple custom Xsession scripts for multiple users, and you do not in that case link '''~/.xinitrc''' to '''.xsession'''.

To enable multiple displays edit the '''.bashrc''' file.

<pre>
nano ~/.bashrc
</pre>

Add the following text.

<pre>
if [[ ! $DISPLAY && $XDG_VTNR -le 3 ]]; then
exec startx
fi
</pre>

For two monitors add the following as shown.

<pre>
if [[ ! $DISPLAY && $XDG_VTNR -le 2 ]]; then
exec startx
fi
</pre>

For a single monitor use:

<pre>
if [[ ! $DISPLAY && $XDG_VTNR -eq 1 ]]; then
exec startx
fi
</pre>

If you wish to remain logged in after quitting X, remove the '''exec''' from the above. Other configurations can be applied, but are irrelevant to autostarting Kodi.

[https://wiki.archlinux.org/index.php/Xinit#Autostart_X_at_login Xinit Autostart X at login]

If you are using LightDM and you just want to create a new login entry for user '''kodi''', you must create a new file.

<pre>
nano /usr/share/xsessions/custom.desktop
</pre>

And insert the following text.

<pre>
[Desktop Entry]
Name=Xsession
Exec=/etc/X11/Xsession
</pre>

This will create a new login option for the custom Xsession. Only this one entry is necessary for LightDM and X11 to find the '''~/.xsession''' script in each user's home directory.

You can use any window manager or desktop enviroment with a custom Xsession script as long as it is installed.

You do this by creating '''~/.xinitrc''' script that contains the command to start the WM or DE.

For instance, if you are using FluxBox.

<pre>
#!/usr/bin/env bash
exec fluxbox &
/usr/bin/kodi -fs
</pre>

The <code>-fs</code> option is full-screen.

To run Gnome in the background, but launch Kodi in the foreground.

<pre>
#!/usr/bin/env bash
exec gnome-session &
/usr/bin/kodi -fs
</pre>

Use the '''~/.xinitrc''' file to configure '''~/.xsession''' to create a custom login for any user, not just Kodi.

<pre>
sudo -H -u [username] bash -c "ln -s ~/.xinitrc ~/.xsession"
</pre>

You must reconfigure Xserver for any user that is not a privileged user to be able to start a custom Xsession.

<pre>
dpkg-reconfigure xserver-xorg-legacy
dpkg-reconfigure xserver-xorg
</pre>

When you reconfigure X11 with these commands, choose to allow non-root users (anybody) to start an Xsession. You should see your changes take effect after rebooting.

User:W3tech

2018-11-16T03:10:51Z

W3tech:

I am W3Techie, developer/webmaster and sometimes programmer.

My interest is developing Kodi-embedded Linux. Not just making an OS boot to Kodi, but actually creating metapackages with supporting software.

I am also interested in improving documentation for Kodi both on the wiki and anywhere else online it can be improved. Like most great software there is never enough documentation. Most people have no idea all the crazy things you can do with Kodi. And today development has become easier than ever.

You can talk to me [[User talk:w3tech|here]].

User:W3tech

2018-11-14T14:37:26Z

W3tech: ,

User:W3tech

2018-11-14T14:36:50Z

W3tech: Corrected grammar.

I am W3Techie, developer/webmaster and sometimes programmer.

My interest is developing Kodi-embedded Linux. Not just making an OS boot to Kodi but actually creating metapackages with supporting software.

I am also interested in improving documentation for Kodi both on the wiki and anywhere else online it can be improved. Like most great software there is never enough documentation. Most people have no idea all the crazy things you can do with Kodi. And today development has become easier than ever.

You can talk to me here.

User:W3tech

2018-11-14T14:27:26Z

W3tech: Adding some basic info about me.

I am W3Techie, developer/webmaster and sometimes programmer.

My interest is developing Kodi-embedded Linux not just making an OS boot to Kodi but actually creating metapackages with supporting software.

I am also interested in improving documentation for Kodi both on the wiki and anywhere else online it can be improved. Like most great software there is never enough documentation. Most people have no idea all the crazy things you can do with Kodi. And today development has become easier than ever.

You can talk to me here.

Archive:Xbmcaddon module

2018-11-14T00:23:00Z

W3tech: Added link to Kodi documentation.

{{mininav|[[Development]]|[[Add-on development]]|[[Python development]]}}

The documentation for the xbmcaddon module may be found here https://codedocs.xyz/AlwinEsch/kodi/group__python__xbmcaddon.html. The '''getSetting''' and '''setSetting''' commands may be used to store state information between calls, in addition to accessing configuration information. '''openSettings''' pops up the configuration dialog allowing the user to change the configuration of your plugin source. '''getLocalizedString''' retrieves translated strings, and '''getAddonInfo''' returns pertinent information about your pluginsource should you want to display this via some other means.

import xbmcaddon
__settings__ = xbmcaddon.Addon(id='<your addons ID>')
__language__ = __settings__.getLocalizedString
__language__(30204) # this will return localized string from resources/language/<name_of_language>/strings.xml
__settings__.getSetting( "foo" ) # this will return "foo" setting value
__settings__.setSetting( "foo" ) # this will set "foo" setting value
__settings__.openSettings() # this will open settings window

please note that <your addons ID> mentioned above must be the same as addon id="<your addons ID> in addons.xml

== See also ==
'''Development:'''
* [[Add-on development]]
* [[Python development]]

[[Category:Add-on development]]
[[Category:Development]]

HOW-TO:Autostart Kodi for Linux

2018-06-16T23:01:42Z

W3tech: /* Configure Kodi to autostart */

<section begin="intro" /><big>Any or all or a combination of these methods can be used to configure a Debian-based X Window System to boot directly to Kodi. This should work on any Linux using the X Window System, but these instructions are particular to Debian derivatives, such as Ubuntu. A server edition is best for running only Kodi, but this page assumes booting into a desktop OS, not a server distro. However, the instructions here can be used for a server distro with even less configuration than for a desktop. Experiment inside VirtualBox before you apply any of these to your system and make a backup.</big><section end="intro" />

__TOC__

== Installing the X11 Window System ==

Even if you are using something like [https://github.com/graysky2/kodi-standalone-service Kodi Standalone Service], you still need use a WM or a DE that installs the '''x-window-manager''' software package.

To ensure you have this installed use the '''which''' command.

<pre>
which x-window-manager
</pre>

If there is no such package, you can use '''apt''' to search your Linux distributions repository.

<pre>
apt-cache search x-window-manager
</pre>

This will general a list of packages containing '''x-window-manager''', which cannot be installed alone. If you are not using a DE, you need to use a WM. And, you can also use a compositing WM like Compiz, for fast 3D effects.

[https://wiki.archlinux.org/index.php/Compiz Compiz - ArchWiki]

A note on using Kodi Standalone Service, this package runs Kodi as a '''systemd''' service and disables the login for user '''kodi''' and will not work when autologin is enabled. In fact, it will break the login process if you autologin user '''kodi''' and run Kodi Standalone Service at the same time. This package is installed automatically with the standard Kodi package when you install Kodi on Raspbian, but must be configured manually for all other Linux distributions. You can run the '''which''' command to find this package as well.

<pre>
which kodi-standalone
</pre>

Be advised, Kodi Standalone Service still launches the Kodi GUI and still requires a WM even though it is running as a '''systemd''' service. When you install a WM such as '''xfwm4''' (the WM for XFCE4), the CLI will tell you if it provides the '''x-window-manager''' package.

<pre>
Setting up xfwm4 (4.12.4-1) ...
update-alternatives: using /usr/bin/xfwm4 to provide /usr/bin/x-window-manager (x-window-manager) in auto mode
</pre>

If you do not see this message at the end of the installation, the WM you selected does not provide this software package and may not actually be a complete WM itself but only part of a package containing a WM.

For a great example on exactly how you would do this with '''xfwm4''', see this ArchWiki entry.

[https://wiki.archlinux.org/index.php/Xfwm XFWM - ArchWiki]

Most systems utilize the client version of the X11 software an Xsession requires.

For more X11 features and functionality, you may optionally upgrade to the server software packages for the X Window System.

<pre>apt install xauth xorg xinit xserver-xorg-core xserver-xorg xserver-common</pre>

The Ubuntu wiki is usually a good source of information.

[https://wiki.ubuntu.com/CustomXSession CustomXSession - Ubuntu Wiki]

Custom user sessions can be created with the X11 Window System to run scripts, autostart apps, and launch a WM or DE.

LightDM is used for autologin.

== Customize LightDM to autologin ==

You can utilize the ability to customize LightDM data manager by changing the builtin custom configuration file '''50-myconfig.conf''' using '''nano''' or another text editor. If you have no DE or WM you can install '''lightdm''', but should make sure to do a bit of research before you do. Most versions of Linux use LightDM, but many server versions do not. For Ubuntu Server with no DE, for example, installing '''lightdm''' is okay and necessary. Changing the behavior of LightDM is done using a custom '''50-myconfig.conf''' configuration file.

To see if you have '''lightdm''' use '''which'''.

<pre>
which lightdm
</pre>

If not, install it with '''apt'''.

<pre>
apt install lightdm
</pre>

Configure LightDM for autologin to boot directly to Kodi.

<pre>
nano /etc/lightdm/lightdm.conf
</pre>

Uncomment the following line.

<pre>
#autologin-user=
</pre>

And add the user you want to autologin. The user is named '''kodi''' in this example.

<pre>
autologin-user=kodi
</pre>

And then you can create /etc/lightdm/lightdm.conf.d/50-myconfig.conf, but ensure the settings in /etc/lightdm/lightdm.conf agree.

Create a custom configuration file called '''50-myconfig.conf''' using '''nano''' or other CLI text editor.

<pre>
mkdir /etc/lightdm/lightdm.conf.d/
nano /etc/lightdm/lightdm.conf.d/50-myconfig.conf
</pre>

Inside this new file add the following text.

<pre>
[SeatDefaults]
autologin-user=kodi
</pre>

CTRL +O +Enter +X to save and exit from '''nano'''.

== Configure Kodi to autostart ==

Configure Kodi to autostart.

<pre>
mkdir -p ~/.config/autostart
ln -s /usr/bin/kodi ~/.config/autostart
</pre>

This method of autostart requires a desktop environment or DE. This is done a bit differently by each DE. Some helpful links can easily be found in today's Web search using any search engine.

[http://edoceo.com/gui/xfce-autostart-apps Autostart Apps in XFCE]

And this link shows how to autostart an app in LXDE on Raspbian.

[http://www.raspberry-projects.com/pi/pi-operating-systems/raspbian/auto-running-programs-gui Auto running programs LXDE - Raspberry Pi Projects]

The Raspberry Pi is a bit more of a tweak, but these are excellent links that will tell you how. The first link is the most helpful to making sure Kodi autostarts in Pi, and utilizes a '''crontab'''. There are many settings on the Pi that control boot, and the first link gives the best most trouble-free way to boot directly to Kodi.

[https://www.leowkahman.com/2016/03/05/lamp-stack-on-raspberry-pi-with-kodi-running-at-startup/ LAMP stack on Raspberry Pi with Kodi running at startup]

In the above link, the author describes using Crontab (short for "Cron table") to boot directly to Kodi.

<pre>
apt install cron
crontab -e
</pre>

Cron will ask you to choose a text editor from available options. I choose option 2 for '''nano'''.

In the new Crontab, enter the following text.

<pre>
@reboot kodi --standalone
</pre>

You could also consider using Crontab to run a script, much like described on this page in the section entitled "Run kodi in a window manager" if you scroll down the page.

[https://wiki.archlinux.org/index.php/Kodi Kodi - Run kodi in a window manager]

Instead your Crontab could look like this.

<pre>
@reboot startx
</pre>

And create an '''~/.xinitrc''' file.

<pre>
nano ~/.xinitrc
</pre>

The '''~/.xinitrc''' file should look like this.

<pre>
#!/bin/bash
kodi --standalone #(this is proper syntax for most Kodi installs)
#kodi-standalone #(this is the syntax that works on Raspbian, not other Pi operating systems)
sudo chvt 2
sleep 1
sudo chvt 1
</pre>

Raspbian has a repository package for everything, so kodi-standalone can be run as a package rather than a command argument.

Make sure to make '''~/.xinitrc''' executable by running.

<pre>
chmod +x ~/.xinitrc
</pre>

To ensure no password is required by '''sudo''' for any user logging in when this script runs, you must edit /etc/sudoers or run the '''visudo''' command if it is installed to edit /etc/sudoers.

You can install '''visudo''' from your Linux distributions default repository.

<pre>
apt install sudo
</pre>

To use '''visudo''' simply run the command in the terminal.

<pre>
visudo
</pre>

For any non-root users, create an entry in /etc/sudoers with '''nano'''.

<pre>
nano /etc/sudoers
</pre>

Create an entry on any line that is comfortable to you like shown here.

<pre>
kodi ALL=NOPASSWD: /usr/bin/chvt
# pi ALL=NOPASSWD: /usr/bin/chvt #(if you do not add user kodi)
</pre>

The above example is for users '''pi''' and '''kodi'''.

If you decide not use a Cron table, you can always remove it again.

<pre>
crontab -r
</pre>

This is a quick reference for Crontab.

[http://www.adminschoice.com/crontab-quick-reference Crontab Quick Reference]

These linked pages facilitate more tweaks and settings relevant to other uses of the X Window System on Pi.

[http://ozzmaker.com/enable-x-windows-on-piscreen/ Enable X Window System on PiScreen]

Other things to tweak on Raspbian.

[https://yingtongli.me/blog/2016/12/21/splash.html Raspbian splash screen guide - Clean up the boot process]

[https://scribles.net/lightning-bolt-under-voltage-warning-on-raspberry-pi/ Under voltage warning and disabling splash screen on Raspbian]

[https://raspberrypi.stackexchange.com/questions/59310/remove-boot-messages-all-text-in-jessie Remove boot messages all text in Raspbian - Raspberry Pi Stack Exchange]

And, if you would rather, it is easier to follow the process provided by this link to modify the Raspbian image before installing it onto the microSD card.

[https://wiki.debian.org/RaspberryPi/qemu-user-static Modifying Raspbian with qemu-user-static]

The above link describes removing the DE from a Raspbian image, though Raspbian Lite is a much better starting point for using Qemu for this purpose.

You can also use the X11 Window System to autostart Kodi by placing a startup script in the /etc/X11/Xsession.d/ directory.

[https://debian-administration.org/article/50/Running_applications_automatically_when_X_starts Running applications automatically when X starts]

<pre>
nano /etc/X11/Xsession.d/startup-local
</pre>

Insert this text into the new file. Use CTRL + O + Enter + X to save the file.

<pre>
#!/bin/sh
/usr/bin/kodi
</pre>

If you have a WM, such as Blackbox you can add it here as well.

<pre>
#!/bin/sh
blackbox &
/usr/bin/kodi
</pre>

Set permissions to make it executable. Use the ampersand to run an application in the background, such as a WM you only need to for the purpose of launching Kodi but not if you don't want to use the WM itself. Kodi will not launch without a DE or WM, but placing the ampersand "&" at the end of the command makes it run in the background where it can do its job out of sight. Also, make sure to start a WM or DE before running an application in the foreground. This is not necessary for apps running in the background.

<pre>
chmod 755 /etc/X11/Xsession.d/startup-local
</pre>

If Kodi is not installed at the standard path, find it using the '''which''' command.

<pre>
which kodi
</pre>

This feature is available on X Window System operating systems most Linux distributions use the X Window System.

== Create custom Xsession script ==

To create a custom Xsession script with a text editor we start with an '''xinitrc''' script. For more detail on how to create and use '''xinit''', there is a great guide available here.

[https://en.wikibooks.org/wiki/Guide_to_X11/Starting_Sessions Guide to X11 - Starting Sessions - WikiBooks]

<pre>
nano ~/.xinitrc
</pre>

To run Kodi full-screen make sure the text reads:

<pre>
#!/usr/bin/env bash
exec gnome-session
/usr/bin/kodi -fs
</pre>

Replace the '''gnome-session''' with the DE or WM command you are using. See the last section for examples.

To make '''~/.xinitrc''' executable use.

<pre>
chmod +x ~/.xinitrc
</pre>

Use '''sudo''' and the '''~/.xinitrc''' file to configure '''~/.xsession'''.

<pre>
sudo -H -u kodi bash -c "ln -s ~/.xinitrc /home/kodi/.xsession"
</pre>

Make sure the path goes to user's home directory. In this example, the user is '''kodi'''.

You need to use '''sudo''' to run this command. If you do not have '''sudo''', install it.

<pre>
apt install sudo
</pre>

If you create a symbolic link and want to remove it, simply remove the existing '''.xsession''' file you created.

<pre>
rm /home/kodi/.xsession
</pre>

On some systems using a DE such as Gnome, not all systems using Gnome, it may be necessary for '''.xsession''' to be '''.xsessionrc'''. Though this is more likely the case for organization network computers than a personal one, where configurations may vary on a diversity of machines. Most of the time, it will be '''.xsession''' rather than '''.xsessionrc''' that you want to create.

You can also create the '''.xsession''' script directly in the home directory, rather than link it from '''~/.xinitrc'''. This is necessary if you create multiple custom Xsession scripts for multiple users, and you do not in that case link '''~/.xinitrc''' to '''.xsession'''.

To enable multiple displays edit the '''.bashrc''' file.

<pre>
nano ~/.bashrc
</pre>

Add the following text.

<pre>
if [[ ! $DISPLAY && $XDG_VTNR -le 3 ]]; then
exec startx
fi
</pre>

For two monitors add the following as shown.

<pre>
if [[ ! $DISPLAY && $XDG_VTNR -le 2 ]]; then
exec startx
fi
</pre>

For a single monitor use:

<pre>
if [[ ! $DISPLAY && $XDG_VTNR -eq 1 ]]; then
exec startx
fi
</pre>

If you wish to remain logged in after quitting X, remove the '''exec''' from the above. Other configurations can be applied, but are irrelevant to autostarting Kodi.

[https://wiki.archlinux.org/index.php/Xinit#Autostart_X_at_login Xinit Autostart X at login]

If you are using LightDM and you just want to create a new login entry for user '''kodi''', you must create a new file.

<pre>
nano /usr/share/xsessions/custom.desktop
</pre>

And insert the following text.

<pre>
[Desktop Entry]
Name=Xsession
Exec=/etc/X11/Xsession
</pre>

This will create a new login option for the custom Xsession. Only this one entry is necessary for LightDM and X11 to find the '''~/.xsession''' script in each user's home directory.

You can use any window manager or desktop enviroment with a custom Xsession script as long as it is installed.

You do this by creating '''~/.xinitrc''' script that contains the command to start the WM or DE.

For instance, if you are using FluxBox.

<pre>
#!/usr/bin/env bash
exec fluxbox &
/usr/bin/kodi -fs
</pre>

The <code>-fs</code> option is full-screen.

To run Gnome in the background, but launch Kodi in the foreground.

<pre>
#!/usr/bin/env bash
exec gnome-session &
/usr/bin/kodi -fs
</pre>

Use the '''~/.xinitrc''' file to configure '''~/.xsession''' to create a custom login for any user, not just Kodi.

<pre>
sudo -H -u [username] bash -c "ln -s ~/.xinitrc ~/.xsession"
</pre>

You must reconfigure Xserver for any user that is not a privileged user to be able to start a custom Xsession.

<pre>
dpkg-reconfigure xserver-xorg-legacy
dpkg-reconfigure xserver-xorg
</pre>

When you reconfigure X11 with these commands, choose to allow non-root users (anybody) to start an Xsession. You should see your changes take effect after rebooting.

HOW-TO:Autostart Kodi for Linux

2018-06-16T22:53:21Z

W3tech: /* Configure Kodi to autostart */

<section begin="intro" /><big>Any or all or a combination of these methods can be used to configure a Debian-based X Window System to boot directly to Kodi. This should work on any Linux using the X Window System, but these instructions are particular to Debian derivatives, such as Ubuntu. A server edition is best for running only Kodi, but this page assumes booting into a desktop OS, not a server distro. However, the instructions here can be used for a server distro with even less configuration than for a desktop. Experiment inside VirtualBox before you apply any of these to your system and make a backup.</big><section end="intro" />

__TOC__

== Installing the X11 Window System ==

Even if you are using something like [https://github.com/graysky2/kodi-standalone-service Kodi Standalone Service], you still need use a WM or a DE that installs the '''x-window-manager''' software package.

To ensure you have this installed use the '''which''' command.

<pre>
which x-window-manager
</pre>

If there is no such package, you can use '''apt''' to search your Linux distributions repository.

<pre>
apt-cache search x-window-manager
</pre>

This will general a list of packages containing '''x-window-manager''', which cannot be installed alone. If you are not using a DE, you need to use a WM. And, you can also use a compositing WM like Compiz, for fast 3D effects.

[https://wiki.archlinux.org/index.php/Compiz Compiz - ArchWiki]

A note on using Kodi Standalone Service, this package runs Kodi as a '''systemd''' service and disables the login for user '''kodi''' and will not work when autologin is enabled. In fact, it will break the login process if you autologin user '''kodi''' and run Kodi Standalone Service at the same time. This package is installed automatically with the standard Kodi package when you install Kodi on Raspbian, but must be configured manually for all other Linux distributions. You can run the '''which''' command to find this package as well.

<pre>
which kodi-standalone
</pre>

Be advised, Kodi Standalone Service still launches the Kodi GUI and still requires a WM even though it is running as a '''systemd''' service. When you install a WM such as '''xfwm4''' (the WM for XFCE4), the CLI will tell you if it provides the '''x-window-manager''' package.

<pre>
Setting up xfwm4 (4.12.4-1) ...
update-alternatives: using /usr/bin/xfwm4 to provide /usr/bin/x-window-manager (x-window-manager) in auto mode
</pre>

If you do not see this message at the end of the installation, the WM you selected does not provide this software package and may not actually be a complete WM itself but only part of a package containing a WM.

For a great example on exactly how you would do this with '''xfwm4''', see this ArchWiki entry.

[https://wiki.archlinux.org/index.php/Xfwm XFWM - ArchWiki]

Most systems utilize the client version of the X11 software an Xsession requires.

For more X11 features and functionality, you may optionally upgrade to the server software packages for the X Window System.

<pre>apt install xauth xorg xinit xserver-xorg-core xserver-xorg xserver-common</pre>

The Ubuntu wiki is usually a good source of information.

[https://wiki.ubuntu.com/CustomXSession CustomXSession - Ubuntu Wiki]

Custom user sessions can be created with the X11 Window System to run scripts, autostart apps, and launch a WM or DE.

LightDM is used for autologin.

== Customize LightDM to autologin ==

You can utilize the ability to customize LightDM data manager by changing the builtin custom configuration file '''50-myconfig.conf''' using '''nano''' or another text editor. If you have no DE or WM you can install '''lightdm''', but should make sure to do a bit of research before you do. Most versions of Linux use LightDM, but many server versions do not. For Ubuntu Server with no DE, for example, installing '''lightdm''' is okay and necessary. Changing the behavior of LightDM is done using a custom '''50-myconfig.conf''' configuration file.

To see if you have '''lightdm''' use '''which'''.

<pre>
which lightdm
</pre>

If not, install it with '''apt'''.

<pre>
apt install lightdm
</pre>

Configure LightDM for autologin to boot directly to Kodi.

<pre>
nano /etc/lightdm/lightdm.conf
</pre>

Uncomment the following line.

<pre>
#autologin-user=
</pre>

And add the user you want to autologin. The user is named '''kodi''' in this example.

<pre>
autologin-user=kodi
</pre>

And then you can create /etc/lightdm/lightdm.conf.d/50-myconfig.conf, but ensure the settings in /etc/lightdm/lightdm.conf agree.

Create a custom configuration file called '''50-myconfig.conf''' using '''nano''' or other CLI text editor.

<pre>
mkdir /etc/lightdm/lightdm.conf.d/
nano /etc/lightdm/lightdm.conf.d/50-myconfig.conf
</pre>

Inside this new file add the following text.

<pre>
[SeatDefaults]
autologin-user=kodi
</pre>

CTRL +O +Enter +X to save and exit from '''nano'''.

== Configure Kodi to autostart ==

Configure Kodi to autostart.

<pre>
mkdir -p ~/.config/autostart
ln -s /usr/bin/kodi ~/.config/autostart
</pre>

This method of autostart requires a desktop environment or DE. This is done a bit differently by each DE. Some helpful links can easily be found in today's Web search using any search engine.

[http://edoceo.com/gui/xfce-autostart-apps Autostart Apps in XFCE]

And this link shows how to autostart an app in LXDE on Raspbian.

[http://www.raspberry-projects.com/pi/pi-operating-systems/raspbian/auto-running-programs-gui Auto running programs LXDE - Raspberry Pi Projects]

The Raspberry Pi is a bit more of a tweak, but these are excellent links that will tell you how. The first link is the most helpful to making sure Kodi autostarts in Pi, and utilizes a '''crontab'''. There are many settings on the Pi that control boot, and the first link gives the best most trouble-free way to boot directly to Kodi.

[https://www.leowkahman.com/2016/03/05/lamp-stack-on-raspberry-pi-with-kodi-running-at-startup/ LAMP stack on Raspberry Pi with Kodi running at startup]

In the above link, the author describes using Crontab (short for "Cron table") to boot directly to Kodi.

<pre>
apt install cron
crontab -e
</pre>

Cron will ask you to choose a text editor from available options. I choose option 2 for '''nano'''.

In the new Crontab, enter the following text.

<pre>
@reboot kodi --standalone
</pre>

You could also consider using Crontab to run a script, much like described on this page in the section entitled "Run kodi in a window manager" if you scroll down the page.

[https://wiki.archlinux.org/index.php/Kodi Kodi - Run kodi in a window manager]

Instead your Crontab could look like this.

<pre>
@reboot startx
</pre>

And create an '''~/.xinitrc''' file.

<pre>
nano ~/.xinitrc
</pre>

The '''~/.xinitrc''' file should look like this.

<pre>
#!/bin/bash
kodi --standalone #(this is proper syntax for most Kodi installs)
#kodi-standalone #(this is the syntax that works on Raspbian, not other Pi operating systems)
sudo chvt 2
sleep 1
sudo chvt 1
</pre>

Raspbian has a repository package for everything, so kodi-standalone can be run as a package rather than a command argument.

Make sure to make '''~/.xinitrc''' executable by running.

<pre>
chmod +x ~/.xinitrc
</pre>

To ensure no password is required by '''sudo''' for any user logging in when this script runs, you must edit /etc/sudoers or run the '''visudo''' command if it is installed to edit /etc/sudoers.

You can install '''visudo''' from your Linux distributions default repository.

<pre>
apt install sudo
</pre>

To use '''visudo''' simply run the command in the terminal.

<pre>
visudo
</pre>

For any non-root users, create an entry in /etc/sudoers with '''nano'''.

<pre>
nano /etc/sudoers
</pre>

Create an entry on any line that is comfortable to you like shown here.

<pre>
kodi ALL=NOPASSWD: /usr/bin/chvt
pi ALL=NOPASSWD: /usr/bin/chvt
</pre>

The above example is for users '''pi''' and '''kodi'''.

If you decide not use a Cron table, you can always remove it again.

<pre>
crontab -r
</pre>

This is a quick reference for Crontab.

[http://www.adminschoice.com/crontab-quick-reference Crontab Quick Reference]

These linked pages facilitate more tweaks and settings relevant to other uses of the X Window System on Pi.

[http://ozzmaker.com/enable-x-windows-on-piscreen/ Enable X Window System on PiScreen]

Other things to tweak on Raspbian.

[https://yingtongli.me/blog/2016/12/21/splash.html Raspbian splash screen guide - Clean up the boot process]

[https://scribles.net/lightning-bolt-under-voltage-warning-on-raspberry-pi/ Under voltage warning and disabling splash screen on Raspbian]

[https://raspberrypi.stackexchange.com/questions/59310/remove-boot-messages-all-text-in-jessie Remove boot messages all text in Raspbian - Raspberry Pi Stack Exchange]

And, if you would rather, it is easier to follow the process provided by this link to modify the Raspbian image before installing it onto the microSD card.

[https://wiki.debian.org/RaspberryPi/qemu-user-static Modifying Raspbian with qemu-user-static]

The above link describes removing the DE from a Raspbian image, though Raspbian Lite is a much better starting point for using Qemu for this purpose.

You can also use the X11 Window System to autostart Kodi by placing a startup script in the /etc/X11/Xsession.d/ directory.

[https://debian-administration.org/article/50/Running_applications_automatically_when_X_starts Running applications automatically when X starts]

<pre>
nano /etc/X11/Xsession.d/startup-local
</pre>

Insert this text into the new file. Use CTRL + O + Enter + X to save the file.

<pre>
#!/bin/sh
/usr/bin/kodi
</pre>

If you have a WM, such as Blackbox you can add it here as well.

<pre>
#!/bin/sh
blackbox &
/usr/bin/kodi
</pre>

Set permissions to make it executable. Use the ampersand to run an application in the background, such as a WM you only need to for the purpose of launching Kodi but not if you don't want to use the WM itself. Kodi will not launch without a DE or WM, but placing the ampersand "&" at the end of the command makes it run in the background where it can do its job out of sight. Also, make sure to start a WM or DE before running an application in the foreground. This is not necessary for apps running in the background.

<pre>
chmod 755 /etc/X11/Xsession.d/startup-local
</pre>

If Kodi is not installed at the standard path, find it using the '''which''' command.

<pre>
which kodi
</pre>

This feature is available on X Window System operating systems most Linux distributions use the X Window System.

== Create custom Xsession script ==

To create a custom Xsession script with a text editor we start with an '''xinitrc''' script. For more detail on how to create and use '''xinit''', there is a great guide available here.

[https://en.wikibooks.org/wiki/Guide_to_X11/Starting_Sessions Guide to X11 - Starting Sessions - WikiBooks]

<pre>
nano ~/.xinitrc
</pre>

To run Kodi full-screen make sure the text reads:

<pre>
#!/usr/bin/env bash
exec gnome-session
/usr/bin/kodi -fs
</pre>

Replace the '''gnome-session''' with the DE or WM command you are using. See the last section for examples.

To make '''~/.xinitrc''' executable use.

<pre>
chmod +x ~/.xinitrc
</pre>

Use '''sudo''' and the '''~/.xinitrc''' file to configure '''~/.xsession'''.

<pre>
sudo -H -u kodi bash -c "ln -s ~/.xinitrc /home/kodi/.xsession"
</pre>

Make sure the path goes to user's home directory. In this example, the user is '''kodi'''.

You need to use '''sudo''' to run this command. If you do not have '''sudo''', install it.

<pre>
apt install sudo
</pre>

If you create a symbolic link and want to remove it, simply remove the existing '''.xsession''' file you created.

<pre>
rm /home/kodi/.xsession
</pre>

On some systems using a DE such as Gnome, not all systems using Gnome, it may be necessary for '''.xsession''' to be '''.xsessionrc'''. Though this is more likely the case for organization network computers than a personal one, where configurations may vary on a diversity of machines. Most of the time, it will be '''.xsession''' rather than '''.xsessionrc''' that you want to create.

You can also create the '''.xsession''' script directly in the home directory, rather than link it from '''~/.xinitrc'''. This is necessary if you create multiple custom Xsession scripts for multiple users, and you do not in that case link '''~/.xinitrc''' to '''.xsession'''.

To enable multiple displays edit the '''.bashrc''' file.

<pre>
nano ~/.bashrc
</pre>

Add the following text.

<pre>
if [[ ! $DISPLAY && $XDG_VTNR -le 3 ]]; then
exec startx
fi
</pre>

For two monitors add the following as shown.

<pre>
if [[ ! $DISPLAY && $XDG_VTNR -le 2 ]]; then
exec startx
fi
</pre>

For a single monitor use:

<pre>
if [[ ! $DISPLAY && $XDG_VTNR -eq 1 ]]; then
exec startx
fi
</pre>

If you wish to remain logged in after quitting X, remove the '''exec''' from the above. Other configurations can be applied, but are irrelevant to autostarting Kodi.

[https://wiki.archlinux.org/index.php/Xinit#Autostart_X_at_login Xinit Autostart X at login]

If you are using LightDM and you just want to create a new login entry for user '''kodi''', you must create a new file.

<pre>
nano /usr/share/xsessions/custom.desktop
</pre>

And insert the following text.

<pre>
[Desktop Entry]
Name=Xsession
Exec=/etc/X11/Xsession
</pre>

This will create a new login option for the custom Xsession. Only this one entry is necessary for LightDM and X11 to find the '''~/.xsession''' script in each user's home directory.

You can use any window manager or desktop enviroment with a custom Xsession script as long as it is installed.

You do this by creating '''~/.xinitrc''' script that contains the command to start the WM or DE.

For instance, if you are using FluxBox.

<pre>
#!/usr/bin/env bash
exec fluxbox &
/usr/bin/kodi -fs
</pre>

The <code>-fs</code> option is full-screen.

To run Gnome in the background, but launch Kodi in the foreground.

<pre>
#!/usr/bin/env bash
exec gnome-session &
/usr/bin/kodi -fs
</pre>

Use the '''~/.xinitrc''' file to configure '''~/.xsession''' to create a custom login for any user, not just Kodi.

<pre>
sudo -H -u [username] bash -c "ln -s ~/.xinitrc ~/.xsession"
</pre>

You must reconfigure Xserver for any user that is not a privileged user to be able to start a custom Xsession.

<pre>
dpkg-reconfigure xserver-xorg-legacy
dpkg-reconfigure xserver-xorg
</pre>

When you reconfigure X11 with these commands, choose to allow non-root users (anybody) to start an Xsession. You should see your changes take effect after rebooting.

HOW-TO:Autostart Kodi for Linux

2018-06-16T18:33:23Z

W3tech: /* Create custom Xsession script */

<section begin="intro" /><big>Any or all or a combination of these methods can be used to configure a Debian-based X Window System to boot directly to Kodi. This should work on any Linux using the X Window System, but these instructions are particular to Debian derivatives, such as Ubuntu. A server edition is best for running only Kodi, but this page assumes booting into a desktop OS, not a server distro. However, the instructions here can be used for a server distro with even less configuration than for a desktop. Experiment inside VirtualBox before you apply any of these to your system and make a backup.</big><section end="intro" />

__TOC__

== Installing the X11 Window System ==

Even if you are using something like [https://github.com/graysky2/kodi-standalone-service Kodi Standalone Service], you still need use a WM or a DE that installs the '''x-window-manager''' software package.

To ensure you have this installed use the '''which''' command.

<pre>
which x-window-manager
</pre>

If there is no such package, you can use '''apt''' to search your Linux distributions repository.

<pre>
apt-cache search x-window-manager
</pre>

This will general a list of packages containing '''x-window-manager''', which cannot be installed alone. If you are not using a DE, you need to use a WM. And, you can also use a compositing WM like Compiz, for fast 3D effects.

[https://wiki.archlinux.org/index.php/Compiz Compiz - ArchWiki]

A note on using Kodi Standalone Service, this package runs Kodi as a '''systemd''' service and disables the login for user '''kodi''' and will not work when autologin is enabled. In fact, it will break the login process if you autologin user '''kodi''' and run Kodi Standalone Service at the same time. This package is installed automatically with the standard Kodi package when you install Kodi on Raspbian, but must be configured manually for all other Linux distributions. You can run the '''which''' command to find this package as well.

<pre>
which kodi-standalone
</pre>

Be advised, Kodi Standalone Service still launches the Kodi GUI and still requires a WM even though it is running as a '''systemd''' service. When you install a WM such as '''xfwm4''' (the WM for XFCE4), the CLI will tell you if it provides the '''x-window-manager''' package.

<pre>
Setting up xfwm4 (4.12.4-1) ...
update-alternatives: using /usr/bin/xfwm4 to provide /usr/bin/x-window-manager (x-window-manager) in auto mode
</pre>

If you do not see this message at the end of the installation, the WM you selected does not provide this software package and may not actually be a complete WM itself but only part of a package containing a WM.

For a great example on exactly how you would do this with '''xfwm4''', see this ArchWiki entry.

[https://wiki.archlinux.org/index.php/Xfwm XFWM - ArchWiki]

Most systems utilize the client version of the X11 software an Xsession requires.

For more X11 features and functionality, you may optionally upgrade to the server software packages for the X Window System.

<pre>apt install xauth xorg xinit xserver-xorg-core xserver-xorg xserver-common</pre>

The Ubuntu wiki is usually a good source of information.

[https://wiki.ubuntu.com/CustomXSession CustomXSession - Ubuntu Wiki]

Custom user sessions can be created with the X11 Window System to run scripts, autostart apps, and launch a WM or DE.

LightDM is used for autologin.

== Customize LightDM to autologin ==

You can utilize the ability to customize LightDM data manager by changing the builtin custom configuration file '''50-myconfig.conf''' using '''nano''' or another text editor. If you have no DE or WM you can install '''lightdm''', but should make sure to do a bit of research before you do. Most versions of Linux use LightDM, but many server versions do not. For Ubuntu Server with no DE, for example, installing '''lightdm''' is okay and necessary. Changing the behavior of LightDM is done using a custom '''50-myconfig.conf''' configuration file.

To see if you have '''lightdm''' use '''which'''.

<pre>
which lightdm
</pre>

If not, install it with '''apt'''.

<pre>
apt install lightdm
</pre>

Configure LightDM for autologin to boot directly to Kodi.

<pre>
nano /etc/lightdm/lightdm.conf
</pre>

Uncomment the following line.

<pre>
#autologin-user=
</pre>

And add the user you want to autologin. The user is named '''kodi''' in this example.

<pre>
autologin-user=kodi
</pre>

And then you can create /etc/lightdm/lightdm.conf.d/50-myconfig.conf, but ensure the settings in /etc/lightdm/lightdm.conf agree.

Create a custom configuration file called '''50-myconfig.conf''' using '''nano''' or other CLI text editor.

<pre>
mkdir /etc/lightdm/lightdm.conf.d/
nano /etc/lightdm/lightdm.conf.d/50-myconfig.conf
</pre>

Inside this new file add the following text.

<pre>
[SeatDefaults]
autologin-user=kodi
</pre>

CTRL +O +Enter +X to save and exit from '''nano'''.

== Configure Kodi to autostart ==

Configure Kodi to autostart.

<pre>
mkdir -p ~/.config/autostart
ln -s /usr/bin/kodi ~/.config/autostart
</pre>

This method of autostart requires a desktop environment or DE. This is done a bit differently by each DE. Some helpful links can easily be found in today's Web search using any search engine.

[http://edoceo.com/gui/xfce-autostart-apps Autostart Apps in XFCE]

And this link shows how to autostart an app in LXDE on Raspbian.

[http://www.raspberry-projects.com/pi/pi-operating-systems/raspbian/auto-running-programs-gui Auto running programs LXDE - Raspberry Pi Projects]

The Raspberry Pi is a bit more of a tweak, but these are excellent links that will tell you how. The first link is the most helpful to making sure Kodi autostarts in Pi, and utilizes a '''crontab'''. There are many settings on the Pi that control boot, and the first link gives the best most trouble-free way to boot directly to Kodi.

[https://www.leowkahman.com/2016/03/05/lamp-stack-on-raspberry-pi-with-kodi-running-at-startup/ LAMP stack on Raspberry Pi with Kodi running at startup]

In the above link, the author describes using Crontab (short for "Cron table") to boot directly to Kodi.

<pre>
apt install cron
crontab -e
</pre>

Cron will ask you to choose a text editor from available options. I choose option 2 for '''nano'''.

In the new Crontab, enter the following text.

<pre>
@reboot kodi --standalone
</pre>

You could also consider using Crontab to run a script, much like described on this page in the section entitled "Run kodi in a window manager" if you scroll down the page.

[https://wiki.archlinux.org/index.php/Kodi Kodi - Run kodi in a window manager]

Instead your Crontab could look like this.

<pre>
@reboot startx
</pre>

And create an '''~/.xinitrc''' file.

<pre>
nano ~/.xinitrc
</pre>

The '''~/.xinitrc''' file should look like this.

<pre>
#!/bin/bash
kodi --standalone #(this is proper syntax for most Kodi installs)
#kodi-standalone #(this is the syntax that works on Raspbian, not other Pi operating systems)
sudo chvt 2
sleep 1
sudo chvt 1
</pre>

Raspbian has a repository package for everything, so kodi-standalone can be run as a package rather than a command argument.

Make sure to make '''~/.xinitrc''' executable by running.

<pre>
chmod +x ~/.xinitrc
</pre>

To ensure no password is required by '''sudo''' for any user logging in when this script runs, you must edit /etc/sudoers or run the '''visudo''' command if it is installed to edit /etc/sudoers. You can install '''visudo''' from your Linux distributions default repository.

<pre>
apt install sudo
</pre>

For any non-root users, create an entry in this file like shown here.

<pre>
kodi ALL=NOPASSWD: /usr/bin/chvt
pi ALL=NOPASSWD: /usr/bin/chvt
</pre>

The above example is for users '''pi''' and '''kodi'''.

If you decide not use a Cron table, you can always remove it again.

<pre>
crontab -r
</pre>

This is a quick reference for Crontab.

[http://www.adminschoice.com/crontab-quick-reference Crontab Quick Reference]

These linked pages facilitate more tweaks and settings relevant to other uses of the X Window System on Pi.

[http://ozzmaker.com/enable-x-windows-on-piscreen/ Enable X Window System on PiScreen]

Other things to tweak on Raspbian.

[https://yingtongli.me/blog/2016/12/21/splash.html Raspbian splash screen guide - Clean up the boot process]

[https://scribles.net/lightning-bolt-under-voltage-warning-on-raspberry-pi/ Under voltage warning and disabling splash screen on Raspbian]

[https://raspberrypi.stackexchange.com/questions/59310/remove-boot-messages-all-text-in-jessie Remove boot messages all text in Raspbian - Raspberry Pi Stack Exchange]

And, if you would rather, it is easier to follow the process provided by this link to modify the Raspbian image before installing it onto the microSD card.

[https://wiki.debian.org/RaspberryPi/qemu-user-static Modifying Raspbian with qemu-user-static]

The above link describes removing the DE from a Raspbian image, though Raspbian Lite is a much better starting point for using Qemu for this purpose.

You can also use the X11 Window System to autostart Kodi by placing a startup script in the /etc/X11/Xsession.d/ directory.

[https://debian-administration.org/article/50/Running_applications_automatically_when_X_starts Running applications automatically when X starts]

<pre>
nano /etc/X11/Xsession.d/startup-local
</pre>

Insert this text into the new file. Use CTRL + O + Enter + X to save the file.

<pre>
#!/bin/sh
/usr/bin/kodi
</pre>

If you have a WM, such as Blackbox you can add it here as well.

<pre>
#!/bin/sh
blackbox &
/usr/bin/kodi
</pre>

Set permissions to make it executable. Use the ampersand to run an application in the background, such as a WM you only need to for the purpose of launching Kodi but not if you don't want to use the WM itself. Kodi will not launch without a DE or WM, but placing the ampersand "&" at the end of the command makes it run in the background where it can do its job out of sight. Also, make sure to start a WM or DE before running an application in the foreground. This is not necessary for apps running in the background.

<pre>
chmod 755 /etc/X11/Xsession.d/startup-local
</pre>

If Kodi is not installed at the standard path, find it using the '''which''' command.

<pre>
which kodi
</pre>

This feature is available on X Window System operating systems most Linux distributions use the X Window System.

== Create custom Xsession script ==

To create a custom Xsession script with a text editor we start with an '''xinitrc''' script. For more detail on how to create and use '''xinit''', there is a great guide available here.

[https://en.wikibooks.org/wiki/Guide_to_X11/Starting_Sessions Guide to X11 - Starting Sessions - WikiBooks]

<pre>
nano ~/.xinitrc
</pre>

To run Kodi full-screen make sure the text reads:

<pre>
#!/usr/bin/env bash
exec gnome-session
/usr/bin/kodi -fs
</pre>

Replace the '''gnome-session''' with the DE or WM command you are using. See the last section for examples.

To make '''~/.xinitrc''' executable use.

<pre>
chmod +x ~/.xinitrc
</pre>

Use '''sudo''' and the '''~/.xinitrc''' file to configure '''~/.xsession'''.

<pre>
sudo -H -u kodi bash -c "ln -s ~/.xinitrc /home/kodi/.xsession"
</pre>

Make sure the path goes to user's home directory. In this example, the user is '''kodi'''.

You need to use '''sudo''' to run this command. If you do not have '''sudo''', install it.

<pre>
apt install sudo
</pre>

If you create a symbolic link and want to remove it, simply remove the existing '''.xsession''' file you created.

<pre>
rm /home/kodi/.xsession
</pre>

On some systems using a DE such as Gnome, not all systems using Gnome, it may be necessary for '''.xsession''' to be '''.xsessionrc'''. Though this is more likely the case for organization network computers than a personal one, where configurations may vary on a diversity of machines. Most of the time, it will be '''.xsession''' rather than '''.xsessionrc''' that you want to create.

You can also create the '''.xsession''' script directly in the home directory, rather than link it from '''~/.xinitrc'''. This is necessary if you create multiple custom Xsession scripts for multiple users, and you do not in that case link '''~/.xinitrc''' to '''.xsession'''.

To enable multiple displays edit the '''.bashrc''' file.

<pre>
nano ~/.bashrc
</pre>

Add the following text.

<pre>
if [[ ! $DISPLAY && $XDG_VTNR -le 3 ]]; then
exec startx
fi
</pre>

For two monitors add the following as shown.

<pre>
if [[ ! $DISPLAY && $XDG_VTNR -le 2 ]]; then
exec startx
fi
</pre>

For a single monitor use:

<pre>
if [[ ! $DISPLAY && $XDG_VTNR -eq 1 ]]; then
exec startx
fi
</pre>

If you wish to remain logged in after quitting X, remove the '''exec''' from the above. Other configurations can be applied, but are irrelevant to autostarting Kodi.

[https://wiki.archlinux.org/index.php/Xinit#Autostart_X_at_login Xinit Autostart X at login]

If you are using LightDM and you just want to create a new login entry for user '''kodi''', you must create a new file.

<pre>
nano /usr/share/xsessions/custom.desktop
</pre>

And insert the following text.

<pre>
[Desktop Entry]
Name=Xsession
Exec=/etc/X11/Xsession
</pre>

This will create a new login option for the custom Xsession. Only this one entry is necessary for LightDM and X11 to find the '''~/.xsession''' script in each user's home directory.

You can use any window manager or desktop enviroment with a custom Xsession script as long as it is installed.

You do this by creating '''~/.xinitrc''' script that contains the command to start the WM or DE.

For instance, if you are using FluxBox.

<pre>
#!/usr/bin/env bash
exec fluxbox &
/usr/bin/kodi -fs
</pre>

The <code>-fs</code> option is full-screen.

To run Gnome in the background, but launch Kodi in the foreground.

<pre>
#!/usr/bin/env bash
exec gnome-session &
/usr/bin/kodi -fs
</pre>

Use the '''~/.xinitrc''' file to configure '''~/.xsession''' to create a custom login for any user, not just Kodi.

<pre>
sudo -H -u [username] bash -c "ln -s ~/.xinitrc ~/.xsession"
</pre>

You must reconfigure Xserver for any user that is not a privileged user to be able to start a custom Xsession.

<pre>
dpkg-reconfigure xserver-xorg-legacy
dpkg-reconfigure xserver-xorg
</pre>

When you reconfigure X11 with these commands, choose to allow non-root users (anybody) to start an Xsession. You should see your changes take effect after rebooting.

HOW-TO:Autostart Kodi for Linux

2018-06-16T18:32:11Z

W3tech: /* Create custom Xsession script */

<section begin="intro" /><big>Any or all or a combination of these methods can be used to configure a Debian-based X Window System to boot directly to Kodi. This should work on any Linux using the X Window System, but these instructions are particular to Debian derivatives, such as Ubuntu. A server edition is best for running only Kodi, but this page assumes booting into a desktop OS, not a server distro. However, the instructions here can be used for a server distro with even less configuration than for a desktop. Experiment inside VirtualBox before you apply any of these to your system and make a backup.</big><section end="intro" />

__TOC__

== Installing the X11 Window System ==

Even if you are using something like [https://github.com/graysky2/kodi-standalone-service Kodi Standalone Service], you still need use a WM or a DE that installs the '''x-window-manager''' software package.

To ensure you have this installed use the '''which''' command.

<pre>
which x-window-manager
</pre>

If there is no such package, you can use '''apt''' to search your Linux distributions repository.

<pre>
apt-cache search x-window-manager
</pre>

This will general a list of packages containing '''x-window-manager''', which cannot be installed alone. If you are not using a DE, you need to use a WM. And, you can also use a compositing WM like Compiz, for fast 3D effects.

[https://wiki.archlinux.org/index.php/Compiz Compiz - ArchWiki]

A note on using Kodi Standalone Service, this package runs Kodi as a '''systemd''' service and disables the login for user '''kodi''' and will not work when autologin is enabled. In fact, it will break the login process if you autologin user '''kodi''' and run Kodi Standalone Service at the same time. This package is installed automatically with the standard Kodi package when you install Kodi on Raspbian, but must be configured manually for all other Linux distributions. You can run the '''which''' command to find this package as well.

<pre>
which kodi-standalone
</pre>

Be advised, Kodi Standalone Service still launches the Kodi GUI and still requires a WM even though it is running as a '''systemd''' service. When you install a WM such as '''xfwm4''' (the WM for XFCE4), the CLI will tell you if it provides the '''x-window-manager''' package.

<pre>
Setting up xfwm4 (4.12.4-1) ...
update-alternatives: using /usr/bin/xfwm4 to provide /usr/bin/x-window-manager (x-window-manager) in auto mode
</pre>

If you do not see this message at the end of the installation, the WM you selected does not provide this software package and may not actually be a complete WM itself but only part of a package containing a WM.

For a great example on exactly how you would do this with '''xfwm4''', see this ArchWiki entry.

[https://wiki.archlinux.org/index.php/Xfwm XFWM - ArchWiki]

Most systems utilize the client version of the X11 software an Xsession requires.

For more X11 features and functionality, you may optionally upgrade to the server software packages for the X Window System.

<pre>apt install xauth xorg xinit xserver-xorg-core xserver-xorg xserver-common</pre>

The Ubuntu wiki is usually a good source of information.

[https://wiki.ubuntu.com/CustomXSession CustomXSession - Ubuntu Wiki]

Custom user sessions can be created with the X11 Window System to run scripts, autostart apps, and launch a WM or DE.

LightDM is used for autologin.

== Customize LightDM to autologin ==

You can utilize the ability to customize LightDM data manager by changing the builtin custom configuration file '''50-myconfig.conf''' using '''nano''' or another text editor. If you have no DE or WM you can install '''lightdm''', but should make sure to do a bit of research before you do. Most versions of Linux use LightDM, but many server versions do not. For Ubuntu Server with no DE, for example, installing '''lightdm''' is okay and necessary. Changing the behavior of LightDM is done using a custom '''50-myconfig.conf''' configuration file.

To see if you have '''lightdm''' use '''which'''.

<pre>
which lightdm
</pre>

If not, install it with '''apt'''.

<pre>
apt install lightdm
</pre>

Configure LightDM for autologin to boot directly to Kodi.

<pre>
nano /etc/lightdm/lightdm.conf
</pre>

Uncomment the following line.

<pre>
#autologin-user=
</pre>

And add the user you want to autologin. The user is named '''kodi''' in this example.

<pre>
autologin-user=kodi
</pre>

And then you can create /etc/lightdm/lightdm.conf.d/50-myconfig.conf, but ensure the settings in /etc/lightdm/lightdm.conf agree.

Create a custom configuration file called '''50-myconfig.conf''' using '''nano''' or other CLI text editor.

<pre>
mkdir /etc/lightdm/lightdm.conf.d/
nano /etc/lightdm/lightdm.conf.d/50-myconfig.conf
</pre>

Inside this new file add the following text.

<pre>
[SeatDefaults]
autologin-user=kodi
</pre>

CTRL +O +Enter +X to save and exit from '''nano'''.

== Configure Kodi to autostart ==

Configure Kodi to autostart.

<pre>
mkdir -p ~/.config/autostart
ln -s /usr/bin/kodi ~/.config/autostart
</pre>

This method of autostart requires a desktop environment or DE. This is done a bit differently by each DE. Some helpful links can easily be found in today's Web search using any search engine.

[http://edoceo.com/gui/xfce-autostart-apps Autostart Apps in XFCE]

And this link shows how to autostart an app in LXDE on Raspbian.

[http://www.raspberry-projects.com/pi/pi-operating-systems/raspbian/auto-running-programs-gui Auto running programs LXDE - Raspberry Pi Projects]

The Raspberry Pi is a bit more of a tweak, but these are excellent links that will tell you how. The first link is the most helpful to making sure Kodi autostarts in Pi, and utilizes a '''crontab'''. There are many settings on the Pi that control boot, and the first link gives the best most trouble-free way to boot directly to Kodi.

[https://www.leowkahman.com/2016/03/05/lamp-stack-on-raspberry-pi-with-kodi-running-at-startup/ LAMP stack on Raspberry Pi with Kodi running at startup]

In the above link, the author describes using Crontab (short for "Cron table") to boot directly to Kodi.

<pre>
apt install cron
crontab -e
</pre>

Cron will ask you to choose a text editor from available options. I choose option 2 for '''nano'''.

In the new Crontab, enter the following text.

<pre>
@reboot kodi --standalone
</pre>

You could also consider using Crontab to run a script, much like described on this page in the section entitled "Run kodi in a window manager" if you scroll down the page.

[https://wiki.archlinux.org/index.php/Kodi Kodi - Run kodi in a window manager]

Instead your Crontab could look like this.

<pre>
@reboot startx
</pre>

And create an '''~/.xinitrc''' file.

<pre>
nano ~/.xinitrc
</pre>

The '''~/.xinitrc''' file should look like this.

<pre>
#!/bin/bash
kodi --standalone #(this is proper syntax for most Kodi installs)
#kodi-standalone #(this is the syntax that works on Raspbian, not other Pi operating systems)
sudo chvt 2
sleep 1
sudo chvt 1
</pre>

Raspbian has a repository package for everything, so kodi-standalone can be run as a package rather than a command argument.

Make sure to make '''~/.xinitrc''' executable by running.

<pre>
chmod +x ~/.xinitrc
</pre>

To ensure no password is required by '''sudo''' for any user logging in when this script runs, you must edit /etc/sudoers or run the '''visudo''' command if it is installed to edit /etc/sudoers. You can install '''visudo''' from your Linux distributions default repository.

<pre>
apt install sudo
</pre>

For any non-root users, create an entry in this file like shown here.

<pre>
kodi ALL=NOPASSWD: /usr/bin/chvt
pi ALL=NOPASSWD: /usr/bin/chvt
</pre>

The above example is for users '''pi''' and '''kodi'''.

If you decide not use a Cron table, you can always remove it again.

<pre>
crontab -r
</pre>

This is a quick reference for Crontab.

[http://www.adminschoice.com/crontab-quick-reference Crontab Quick Reference]

These linked pages facilitate more tweaks and settings relevant to other uses of the X Window System on Pi.

[http://ozzmaker.com/enable-x-windows-on-piscreen/ Enable X Window System on PiScreen]

Other things to tweak on Raspbian.

[https://yingtongli.me/blog/2016/12/21/splash.html Raspbian splash screen guide - Clean up the boot process]

[https://scribles.net/lightning-bolt-under-voltage-warning-on-raspberry-pi/ Under voltage warning and disabling splash screen on Raspbian]

[https://raspberrypi.stackexchange.com/questions/59310/remove-boot-messages-all-text-in-jessie Remove boot messages all text in Raspbian - Raspberry Pi Stack Exchange]

And, if you would rather, it is easier to follow the process provided by this link to modify the Raspbian image before installing it onto the microSD card.

[https://wiki.debian.org/RaspberryPi/qemu-user-static Modifying Raspbian with qemu-user-static]

The above link describes removing the DE from a Raspbian image, though Raspbian Lite is a much better starting point for using Qemu for this purpose.

You can also use the X11 Window System to autostart Kodi by placing a startup script in the /etc/X11/Xsession.d/ directory.

[https://debian-administration.org/article/50/Running_applications_automatically_when_X_starts Running applications automatically when X starts]

<pre>
nano /etc/X11/Xsession.d/startup-local
</pre>

Insert this text into the new file. Use CTRL + O + Enter + X to save the file.

<pre>
#!/bin/sh
/usr/bin/kodi
</pre>

If you have a WM, such as Blackbox you can add it here as well.

<pre>
#!/bin/sh
blackbox &
/usr/bin/kodi
</pre>

Set permissions to make it executable. Use the ampersand to run an application in the background, such as a WM you only need to for the purpose of launching Kodi but not if you don't want to use the WM itself. Kodi will not launch without a DE or WM, but placing the ampersand "&" at the end of the command makes it run in the background where it can do its job out of sight. Also, make sure to start a WM or DE before running an application in the foreground. This is not necessary for apps running in the background.

<pre>
chmod 755 /etc/X11/Xsession.d/startup-local
</pre>

If Kodi is not installed at the standard path, find it using the '''which''' command.

<pre>
which kodi
</pre>

This feature is available on X Window System operating systems most Linux distributions use the X Window System.

== Create custom Xsession script ==

To create a custom Xsession script with a text editor we start with an '''xinitrc''' script. For more detail on how to create and use '''xinit''', there is a great guide available here.

[https://en.wikibooks.org/wiki/Guide_to_X11/Starting_Sessions Guide to X11 - Starting Sessions - WikiBooks]

<pre>
nano ~/.xinitrc
</pre>

To run Kodi full-screen make sure the text reads:

<pre>
#!/usr/bin/env bash
exec gnome-session
/usr/bin/kodi -fs
</pre>

Replace the '''gnome-session''' with the DE or WM command you are using. See the last section for examples.

To make '''~/.xinitrc''' executable use.

<pre>
chmod +x ~/.xinitrc
</pre>

Use '''sudo''' and the '''~/.xinitrc''' file to configure '''~/.xsession'''.

<pre>
sudo -H -u kodi bash -c "ln -s ~/.xinitrc /home/kodi/.xsession"
</pre>

Make sure the path goes to user's home directory. In this example, the user is '''kodi'''.

You need to use '''sudo''' to run this command. If you do not have '''sudo''', install it.

<pre>
apt install sudo
</pre>

If you create a symbolic link and want to remove it, simply remove the existing '''.xsession''' file you created.

<pre>
rm /home/kodi/.xsession
</pre>

On some systems using a DE such as Gnome, not all systems using Gnome, it may be necessary for '''.xsession''' to be '''.xsessionrc'''. Though this is more likely the case for organization network computers than a personal one, where configurations may vary on a diversity of machines. Most of the time, it will be '''.xsession''' rather than '''.xsessionrc''' that you want to create.

You can also create the '''.xsession''' script directly in the home directory, rather than link it from '''~/.xinitrc'''. This is necessary if you create multiple custom Xsession scripts for multiple users, and you do not in that case link '''~/.xinitrc''' to '''.xsession'''.

To enable multiple displays edit the '''.bashrc''' file.

<pre>
nano ~/.bashrc
</pre>

<pre>
if [[ ! $DISPLAY && $XDG_VTNR -le 3 ]]; then
exec startx
fi
</pre>

For two monitors add the following as shown.

<pre>
if [[ ! $DISPLAY && $XDG_VTNR -le 2 ]]; then
exec startx
fi
</pre>

For a single monitor use:

<pre>
if [[ ! $DISPLAY && $XDG_VTNR -eq 1 ]]; then
exec startx
fi
</pre>

If you wish to remain logged in after quitting X, remove the '''exec''' from the above. Other configurations can be applied, but are irrelevant to autostarting Kodi.

[https://wiki.archlinux.org/index.php/Xinit#Autostart_X_at_login Xinit Autostart X at login]

If you are using LightDM and you just want to create a new login entry for user '''kodi''', you must create a new file.

<pre>
nano /usr/share/xsessions/custom.desktop
</pre>

And insert the following text.

<pre>
[Desktop Entry]
Name=Xsession
Exec=/etc/X11/Xsession
</pre>

This will create a new login option for the custom Xsession. Only this one entry is necessary for LightDM and X11 to find the '''~/.xsession''' script in each user's home directory.

You can use any window manager or desktop enviroment with a custom Xsession script as long as it is installed.

You do this by creating '''~/.xinitrc''' script that contains the command to start the WM or DE.

For instance, if you are using FluxBox.

<pre>
#!/usr/bin/env bash
exec fluxbox &
/usr/bin/kodi -fs
</pre>

The <code>-fs</code> option is full-screen.

To run Gnome in the background, but launch Kodi in the foreground.

<pre>
#!/usr/bin/env bash
exec gnome-session &
/usr/bin/kodi -fs
</pre>

Use the '''~/.xinitrc''' file to configure '''~/.xsession''' to create a custom login for any user, not just Kodi.

<pre>
sudo -H -u [username] bash -c "ln -s ~/.xinitrc ~/.xsession"
</pre>

You must reconfigure Xserver for any user that is not a privileged user to be able to start a custom Xsession.

<pre>
dpkg-reconfigure xserver-xorg-legacy
dpkg-reconfigure xserver-xorg
</pre>

When you reconfigure X11 with these commands, choose to allow non-root users (anybody) to start an Xsession. You should see your changes take effect after rebooting.

HOW-TO:Autostart Kodi for Linux

2018-06-16T18:28:42Z

W3tech: /* Create custom Xsession script */

<section begin="intro" /><big>Any or all or a combination of these methods can be used to configure a Debian-based X Window System to boot directly to Kodi. This should work on any Linux using the X Window System, but these instructions are particular to Debian derivatives, such as Ubuntu. A server edition is best for running only Kodi, but this page assumes booting into a desktop OS, not a server distro. However, the instructions here can be used for a server distro with even less configuration than for a desktop. Experiment inside VirtualBox before you apply any of these to your system and make a backup.</big><section end="intro" />

__TOC__

== Installing the X11 Window System ==

Even if you are using something like [https://github.com/graysky2/kodi-standalone-service Kodi Standalone Service], you still need use a WM or a DE that installs the '''x-window-manager''' software package.

To ensure you have this installed use the '''which''' command.

<pre>
which x-window-manager
</pre>

If there is no such package, you can use '''apt''' to search your Linux distributions repository.

<pre>
apt-cache search x-window-manager
</pre>

This will general a list of packages containing '''x-window-manager''', which cannot be installed alone. If you are not using a DE, you need to use a WM. And, you can also use a compositing WM like Compiz, for fast 3D effects.

[https://wiki.archlinux.org/index.php/Compiz Compiz - ArchWiki]

A note on using Kodi Standalone Service, this package runs Kodi as a '''systemd''' service and disables the login for user '''kodi''' and will not work when autologin is enabled. In fact, it will break the login process if you autologin user '''kodi''' and run Kodi Standalone Service at the same time. This package is installed automatically with the standard Kodi package when you install Kodi on Raspbian, but must be configured manually for all other Linux distributions. You can run the '''which''' command to find this package as well.

<pre>
which kodi-standalone
</pre>

Be advised, Kodi Standalone Service still launches the Kodi GUI and still requires a WM even though it is running as a '''systemd''' service. When you install a WM such as '''xfwm4''' (the WM for XFCE4), the CLI will tell you if it provides the '''x-window-manager''' package.

<pre>
Setting up xfwm4 (4.12.4-1) ...
update-alternatives: using /usr/bin/xfwm4 to provide /usr/bin/x-window-manager (x-window-manager) in auto mode
</pre>

If you do not see this message at the end of the installation, the WM you selected does not provide this software package and may not actually be a complete WM itself but only part of a package containing a WM.

For a great example on exactly how you would do this with '''xfwm4''', see this ArchWiki entry.

[https://wiki.archlinux.org/index.php/Xfwm XFWM - ArchWiki]

Most systems utilize the client version of the X11 software an Xsession requires.

For more X11 features and functionality, you may optionally upgrade to the server software packages for the X Window System.

<pre>apt install xauth xorg xinit xserver-xorg-core xserver-xorg xserver-common</pre>

The Ubuntu wiki is usually a good source of information.

[https://wiki.ubuntu.com/CustomXSession CustomXSession - Ubuntu Wiki]

Custom user sessions can be created with the X11 Window System to run scripts, autostart apps, and launch a WM or DE.

LightDM is used for autologin.

== Customize LightDM to autologin ==

You can utilize the ability to customize LightDM data manager by changing the builtin custom configuration file '''50-myconfig.conf''' using '''nano''' or another text editor. If you have no DE or WM you can install '''lightdm''', but should make sure to do a bit of research before you do. Most versions of Linux use LightDM, but many server versions do not. For Ubuntu Server with no DE, for example, installing '''lightdm''' is okay and necessary. Changing the behavior of LightDM is done using a custom '''50-myconfig.conf''' configuration file.

To see if you have '''lightdm''' use '''which'''.

<pre>
which lightdm
</pre>

If not, install it with '''apt'''.

<pre>
apt install lightdm
</pre>

Configure LightDM for autologin to boot directly to Kodi.

<pre>
nano /etc/lightdm/lightdm.conf
</pre>

Uncomment the following line.

<pre>
#autologin-user=
</pre>

And add the user you want to autologin. The user is named '''kodi''' in this example.

<pre>
autologin-user=kodi
</pre>

And then you can create /etc/lightdm/lightdm.conf.d/50-myconfig.conf, but ensure the settings in /etc/lightdm/lightdm.conf agree.

Create a custom configuration file called '''50-myconfig.conf''' using '''nano''' or other CLI text editor.

<pre>
mkdir /etc/lightdm/lightdm.conf.d/
nano /etc/lightdm/lightdm.conf.d/50-myconfig.conf
</pre>

Inside this new file add the following text.

<pre>
[SeatDefaults]
autologin-user=kodi
</pre>

CTRL +O +Enter +X to save and exit from '''nano'''.

== Configure Kodi to autostart ==

Configure Kodi to autostart.

<pre>
mkdir -p ~/.config/autostart
ln -s /usr/bin/kodi ~/.config/autostart
</pre>

This method of autostart requires a desktop environment or DE. This is done a bit differently by each DE. Some helpful links can easily be found in today's Web search using any search engine.

[http://edoceo.com/gui/xfce-autostart-apps Autostart Apps in XFCE]

And this link shows how to autostart an app in LXDE on Raspbian.

[http://www.raspberry-projects.com/pi/pi-operating-systems/raspbian/auto-running-programs-gui Auto running programs LXDE - Raspberry Pi Projects]

The Raspberry Pi is a bit more of a tweak, but these are excellent links that will tell you how. The first link is the most helpful to making sure Kodi autostarts in Pi, and utilizes a '''crontab'''. There are many settings on the Pi that control boot, and the first link gives the best most trouble-free way to boot directly to Kodi.

[https://www.leowkahman.com/2016/03/05/lamp-stack-on-raspberry-pi-with-kodi-running-at-startup/ LAMP stack on Raspberry Pi with Kodi running at startup]

In the above link, the author describes using Crontab (short for "Cron table") to boot directly to Kodi.

<pre>
apt install cron
crontab -e
</pre>

Cron will ask you to choose a text editor from available options. I choose option 2 for '''nano'''.

In the new Crontab, enter the following text.

<pre>
@reboot kodi --standalone
</pre>

You could also consider using Crontab to run a script, much like described on this page in the section entitled "Run kodi in a window manager" if you scroll down the page.

[https://wiki.archlinux.org/index.php/Kodi Kodi - Run kodi in a window manager]

Instead your Crontab could look like this.

<pre>
@reboot startx
</pre>

And create an '''~/.xinitrc''' file.

<pre>
nano ~/.xinitrc
</pre>

The '''~/.xinitrc''' file should look like this.

<pre>
#!/bin/bash
kodi --standalone #(this is proper syntax for most Kodi installs)
#kodi-standalone #(this is the syntax that works on Raspbian, not other Pi operating systems)
sudo chvt 2
sleep 1
sudo chvt 1
</pre>

Raspbian has a repository package for everything, so kodi-standalone can be run as a package rather than a command argument.

Make sure to make '''~/.xinitrc''' executable by running.

<pre>
chmod +x ~/.xinitrc
</pre>

To ensure no password is required by '''sudo''' for any user logging in when this script runs, you must edit /etc/sudoers or run the '''visudo''' command if it is installed to edit /etc/sudoers. You can install '''visudo''' from your Linux distributions default repository.

<pre>
apt install sudo
</pre>

For any non-root users, create an entry in this file like shown here.

<pre>
kodi ALL=NOPASSWD: /usr/bin/chvt
pi ALL=NOPASSWD: /usr/bin/chvt
</pre>

The above example is for users '''pi''' and '''kodi'''.

If you decide not use a Cron table, you can always remove it again.

<pre>
crontab -r
</pre>

This is a quick reference for Crontab.

[http://www.adminschoice.com/crontab-quick-reference Crontab Quick Reference]

These linked pages facilitate more tweaks and settings relevant to other uses of the X Window System on Pi.

[http://ozzmaker.com/enable-x-windows-on-piscreen/ Enable X Window System on PiScreen]

Other things to tweak on Raspbian.

[https://yingtongli.me/blog/2016/12/21/splash.html Raspbian splash screen guide - Clean up the boot process]

[https://scribles.net/lightning-bolt-under-voltage-warning-on-raspberry-pi/ Under voltage warning and disabling splash screen on Raspbian]

[https://raspberrypi.stackexchange.com/questions/59310/remove-boot-messages-all-text-in-jessie Remove boot messages all text in Raspbian - Raspberry Pi Stack Exchange]

And, if you would rather, it is easier to follow the process provided by this link to modify the Raspbian image before installing it onto the microSD card.

[https://wiki.debian.org/RaspberryPi/qemu-user-static Modifying Raspbian with qemu-user-static]

The above link describes removing the DE from a Raspbian image, though Raspbian Lite is a much better starting point for using Qemu for this purpose.

You can also use the X11 Window System to autostart Kodi by placing a startup script in the /etc/X11/Xsession.d/ directory.

[https://debian-administration.org/article/50/Running_applications_automatically_when_X_starts Running applications automatically when X starts]

<pre>
nano /etc/X11/Xsession.d/startup-local
</pre>

Insert this text into the new file. Use CTRL + O + Enter + X to save the file.

<pre>
#!/bin/sh
/usr/bin/kodi
</pre>

If you have a WM, such as Blackbox you can add it here as well.

<pre>
#!/bin/sh
blackbox &
/usr/bin/kodi
</pre>

Set permissions to make it executable. Use the ampersand to run an application in the background, such as a WM you only need to for the purpose of launching Kodi but not if you don't want to use the WM itself. Kodi will not launch without a DE or WM, but placing the ampersand "&" at the end of the command makes it run in the background where it can do its job out of sight. Also, make sure to start a WM or DE before running an application in the foreground. This is not necessary for apps running in the background.

<pre>
chmod 755 /etc/X11/Xsession.d/startup-local
</pre>

If Kodi is not installed at the standard path, find it using the '''which''' command.

<pre>
which kodi
</pre>

This feature is available on X Window System operating systems most Linux distributions use the X Window System.

== Create custom Xsession script ==

To create a custom Xsession script with a text editor we start with an '''xinitrc''' script. For more detail on how to create and use '''xinit''', there is a great guide available here.

[https://en.wikibooks.org/wiki/Guide_to_X11/Starting_Sessions Guide to X11 - Starting Sessions - WikiBooks]

<pre>
nano ~/.xinitrc
</pre>

To run Kodi full-screen make sure the text reads:

<pre>
#!/usr/bin/env bash
exec gnome-session
/usr/bin/kodi -fs
</pre>

Replace the '''gnome-session''' with the DE or WM command you are using. See the last section for examples.

To make '''~/.xinitrc''' executable use.

<pre>
chmod +x ~/.xinitrc
</pre>

Use '''sudo''' and the '''~/.xinitrc''' file to configure '''~/.xsession'''.

<pre>
sudo -H -u kodi bash -c "ln -s ~/.xinitrc /home/kodi/.xsession"
</pre>

Make sure the path goes to user's home directory. In this example, the user is '''kodi'''.

You need to use '''sudo''' to run this command. If you do not have '''sudo''', install it.

<pre>
apt install sudo
</pre>

If you create a symbolic link and want to remove it, simply remove the existing '''.xsession''' file you created.

<pre>
rm /home/kodi/.xsession
</pre>

On some systems using a DE such as Gnome, not all systems using Gnome, it may be necessary for '''.xsession''' to be '''.xsessionrc'''. Though this is more likely the case for organization network computers than a personal one, where configurations may vary on a diversity of machines. Most of the time, it will be '''.xsession''' rather than '''.xsessionrc''' that you want to create.

You can also create the '''.xsession''' script directly in the home directory, rather than link it from '''~/.xinitrc'''. This is necessary if you create multiple custom Xsession scripts for multiple users, and you do not in that case link '''~/.xinitrc''' to '''.xsession'''.

To enable multiple displays edit the '''.bashrc''' file.

<pre>
nano ~/.bashrc
</pre>

Add the following as shown.

<pre>
if [[ ! $DISPLAY && $XDG_VTNR -eq 1 ]]; then
exec startx
fi
</pre>

If you wish to remain logged in after quitting X, remove the '''exec''' from the above. Other configurations can be applied, but are irrelevant to autostarting Kodi.

[https://wiki.archlinux.org/index.php/Xinit#Autostart_X_at_login Xinit Autostart X at login]

If you are using LightDM and you just want to create a new login entry for user '''kodi''', you must create a new file.

<pre>
nano /usr/share/xsessions/custom.desktop
</pre>

And insert the following text.

<pre>
[Desktop Entry]
Name=Xsession
Exec=/etc/X11/Xsession
</pre>

This will create a new login option for the custom Xsession. Only this one entry is necessary for LightDM and X11 to find the '''~/.xsession''' script in each user's home directory.

You can use any window manager or desktop enviroment with a custom Xsession script as long as it is installed.

You do this by creating '''~/.xinitrc''' script that contains the command to start the WM or DE.

For instance, if you are using FluxBox.

<pre>
#!/usr/bin/env bash
exec fluxbox &
/usr/bin/kodi -fs
</pre>

The <code>-fs</code> option is full-screen.

To run Gnome in the background, but launch Kodi in the foreground.

<pre>
#!/usr/bin/env bash
exec gnome-session &
/usr/bin/kodi -fs
</pre>

Use the '''~/.xinitrc''' file to configure '''~/.xsession''' to create a custom login for any user, not just Kodi.

<pre>
sudo -H -u [username] bash -c "ln -s ~/.xinitrc ~/.xsession"
</pre>

You must reconfigure Xserver for any user that is not a privileged user to be able to start a custom Xsession.

<pre>
dpkg-reconfigure xserver-xorg-legacy
dpkg-reconfigure xserver-xorg
</pre>

When you reconfigure X11 with these commands, choose to allow non-root users (anybody) to start an Xsession. You should see your changes take effect after rebooting.

HOW-TO:Autostart Kodi for Linux

2018-06-16T18:11:55Z

W3tech: /* Configure Kodi to autostart */

<section begin="intro" /><big>Any or all or a combination of these methods can be used to configure a Debian-based X Window System to boot directly to Kodi. This should work on any Linux using the X Window System, but these instructions are particular to Debian derivatives, such as Ubuntu. A server edition is best for running only Kodi, but this page assumes booting into a desktop OS, not a server distro. However, the instructions here can be used for a server distro with even less configuration than for a desktop. Experiment inside VirtualBox before you apply any of these to your system and make a backup.</big><section end="intro" />

__TOC__

== Installing the X11 Window System ==

Even if you are using something like [https://github.com/graysky2/kodi-standalone-service Kodi Standalone Service], you still need use a WM or a DE that installs the '''x-window-manager''' software package.

To ensure you have this installed use the '''which''' command.

<pre>
which x-window-manager
</pre>

If there is no such package, you can use '''apt''' to search your Linux distributions repository.

<pre>
apt-cache search x-window-manager
</pre>

This will general a list of packages containing '''x-window-manager''', which cannot be installed alone. If you are not using a DE, you need to use a WM. And, you can also use a compositing WM like Compiz, for fast 3D effects.

[https://wiki.archlinux.org/index.php/Compiz Compiz - ArchWiki]

A note on using Kodi Standalone Service, this package runs Kodi as a '''systemd''' service and disables the login for user '''kodi''' and will not work when autologin is enabled. In fact, it will break the login process if you autologin user '''kodi''' and run Kodi Standalone Service at the same time. This package is installed automatically with the standard Kodi package when you install Kodi on Raspbian, but must be configured manually for all other Linux distributions. You can run the '''which''' command to find this package as well.

<pre>
which kodi-standalone
</pre>

Be advised, Kodi Standalone Service still launches the Kodi GUI and still requires a WM even though it is running as a '''systemd''' service. When you install a WM such as '''xfwm4''' (the WM for XFCE4), the CLI will tell you if it provides the '''x-window-manager''' package.

<pre>
Setting up xfwm4 (4.12.4-1) ...
update-alternatives: using /usr/bin/xfwm4 to provide /usr/bin/x-window-manager (x-window-manager) in auto mode
</pre>

If you do not see this message at the end of the installation, the WM you selected does not provide this software package and may not actually be a complete WM itself but only part of a package containing a WM.

For a great example on exactly how you would do this with '''xfwm4''', see this ArchWiki entry.

[https://wiki.archlinux.org/index.php/Xfwm XFWM - ArchWiki]

Most systems utilize the client version of the X11 software an Xsession requires.

For more X11 features and functionality, you may optionally upgrade to the server software packages for the X Window System.

<pre>apt install xauth xorg xinit xserver-xorg-core xserver-xorg xserver-common</pre>

The Ubuntu wiki is usually a good source of information.

[https://wiki.ubuntu.com/CustomXSession CustomXSession - Ubuntu Wiki]

Custom user sessions can be created with the X11 Window System to run scripts, autostart apps, and launch a WM or DE.

LightDM is used for autologin.

== Customize LightDM to autologin ==

You can utilize the ability to customize LightDM data manager by changing the builtin custom configuration file '''50-myconfig.conf''' using '''nano''' or another text editor. If you have no DE or WM you can install '''lightdm''', but should make sure to do a bit of research before you do. Most versions of Linux use LightDM, but many server versions do not. For Ubuntu Server with no DE, for example, installing '''lightdm''' is okay and necessary. Changing the behavior of LightDM is done using a custom '''50-myconfig.conf''' configuration file.

To see if you have '''lightdm''' use '''which'''.

<pre>
which lightdm
</pre>

If not, install it with '''apt'''.

<pre>
apt install lightdm
</pre>

Configure LightDM for autologin to boot directly to Kodi.

<pre>
nano /etc/lightdm/lightdm.conf
</pre>

Uncomment the following line.

<pre>
#autologin-user=
</pre>

And add the user you want to autologin. The user is named '''kodi''' in this example.

<pre>
autologin-user=kodi
</pre>

And then you can create /etc/lightdm/lightdm.conf.d/50-myconfig.conf, but ensure the settings in /etc/lightdm/lightdm.conf agree.

Create a custom configuration file called '''50-myconfig.conf''' using '''nano''' or other CLI text editor.

<pre>
mkdir /etc/lightdm/lightdm.conf.d/
nano /etc/lightdm/lightdm.conf.d/50-myconfig.conf
</pre>

Inside this new file add the following text.

<pre>
[SeatDefaults]
autologin-user=kodi
</pre>

CTRL +O +Enter +X to save and exit from '''nano'''.

== Configure Kodi to autostart ==

Configure Kodi to autostart.

<pre>
mkdir -p ~/.config/autostart
ln -s /usr/bin/kodi ~/.config/autostart
</pre>

This method of autostart requires a desktop environment or DE. This is done a bit differently by each DE. Some helpful links can easily be found in today's Web search using any search engine.

[http://edoceo.com/gui/xfce-autostart-apps Autostart Apps in XFCE]

And this link shows how to autostart an app in LXDE on Raspbian.

[http://www.raspberry-projects.com/pi/pi-operating-systems/raspbian/auto-running-programs-gui Auto running programs LXDE - Raspberry Pi Projects]

The Raspberry Pi is a bit more of a tweak, but these are excellent links that will tell you how. The first link is the most helpful to making sure Kodi autostarts in Pi, and utilizes a '''crontab'''. There are many settings on the Pi that control boot, and the first link gives the best most trouble-free way to boot directly to Kodi.

[https://www.leowkahman.com/2016/03/05/lamp-stack-on-raspberry-pi-with-kodi-running-at-startup/ LAMP stack on Raspberry Pi with Kodi running at startup]

In the above link, the author describes using Crontab (short for "Cron table") to boot directly to Kodi.

<pre>
apt install cron
crontab -e
</pre>

Cron will ask you to choose a text editor from available options. I choose option 2 for '''nano'''.

In the new Crontab, enter the following text.

<pre>
@reboot kodi --standalone
</pre>

You could also consider using Crontab to run a script, much like described on this page in the section entitled "Run kodi in a window manager" if you scroll down the page.

[https://wiki.archlinux.org/index.php/Kodi Kodi - Run kodi in a window manager]

Instead your Crontab could look like this.

<pre>
@reboot startx
</pre>

And create an '''~/.xinitrc''' file.

<pre>
nano ~/.xinitrc
</pre>

The '''~/.xinitrc''' file should look like this.

<pre>
#!/bin/bash
kodi --standalone #(this is proper syntax for most Kodi installs)
#kodi-standalone #(this is the syntax that works on Raspbian, not other Pi operating systems)
sudo chvt 2
sleep 1
sudo chvt 1
</pre>

Raspbian has a repository package for everything, so kodi-standalone can be run as a package rather than a command argument.

Make sure to make '''~/.xinitrc''' executable by running.

<pre>
chmod +x ~/.xinitrc
</pre>

To ensure no password is required by '''sudo''' for any user logging in when this script runs, you must edit /etc/sudoers or run the '''visudo''' command if it is installed to edit /etc/sudoers. You can install '''visudo''' from your Linux distributions default repository.

<pre>
apt install sudo
</pre>

For any non-root users, create an entry in this file like shown here.

<pre>
kodi ALL=NOPASSWD: /usr/bin/chvt
pi ALL=NOPASSWD: /usr/bin/chvt
</pre>

The above example is for users '''pi''' and '''kodi'''.

If you decide not use a Cron table, you can always remove it again.

<pre>
crontab -r
</pre>

This is a quick reference for Crontab.

[http://www.adminschoice.com/crontab-quick-reference Crontab Quick Reference]

These linked pages facilitate more tweaks and settings relevant to other uses of the X Window System on Pi.

[http://ozzmaker.com/enable-x-windows-on-piscreen/ Enable X Window System on PiScreen]

Other things to tweak on Raspbian.

[https://yingtongli.me/blog/2016/12/21/splash.html Raspbian splash screen guide - Clean up the boot process]

[https://scribles.net/lightning-bolt-under-voltage-warning-on-raspberry-pi/ Under voltage warning and disabling splash screen on Raspbian]

[https://raspberrypi.stackexchange.com/questions/59310/remove-boot-messages-all-text-in-jessie Remove boot messages all text in Raspbian - Raspberry Pi Stack Exchange]

And, if you would rather, it is easier to follow the process provided by this link to modify the Raspbian image before installing it onto the microSD card.

[https://wiki.debian.org/RaspberryPi/qemu-user-static Modifying Raspbian with qemu-user-static]

The above link describes removing the DE from a Raspbian image, though Raspbian Lite is a much better starting point for using Qemu for this purpose.

You can also use the X11 Window System to autostart Kodi by placing a startup script in the /etc/X11/Xsession.d/ directory.

[https://debian-administration.org/article/50/Running_applications_automatically_when_X_starts Running applications automatically when X starts]

<pre>
nano /etc/X11/Xsession.d/startup-local
</pre>

Insert this text into the new file. Use CTRL + O + Enter + X to save the file.

<pre>
#!/bin/sh
/usr/bin/kodi
</pre>

If you have a WM, such as Blackbox you can add it here as well.

<pre>
#!/bin/sh
blackbox &
/usr/bin/kodi
</pre>

Set permissions to make it executable. Use the ampersand to run an application in the background, such as a WM you only need to for the purpose of launching Kodi but not if you don't want to use the WM itself. Kodi will not launch without a DE or WM, but placing the ampersand "&" at the end of the command makes it run in the background where it can do its job out of sight. Also, make sure to start a WM or DE before running an application in the foreground. This is not necessary for apps running in the background.

<pre>
chmod 755 /etc/X11/Xsession.d/startup-local
</pre>

If Kodi is not installed at the standard path, find it using the '''which''' command.

<pre>
which kodi
</pre>

This feature is available on X Window System operating systems most Linux distributions use the X Window System.

== Create custom Xsession script ==

To create a custom Xsession script with a text editor we start with an '''xinitrc''' script. For more detail on how to create and use '''xinit''', there is a great guide available here.

[https://en.wikibooks.org/wiki/Guide_to_X11/Starting_Sessions Guide to X11 - Starting Sessions - WikiBooks]

<pre>
nano ~/.xinitrc
</pre>

To run Kodi full-screen make sure the text reads:

<pre>
#!/usr/bin/env bash
exec gnome-session
/usr/bin/kodi -fs
</pre>

Replace the '''gnome-session''' with the DE or WM command you are using. See the last section for examples.

To make '''~/.xinitrc''' executable use.

<pre>
chmod +x ~/.xinitrc
</pre>

Use '''sudo''' and the '''~/.xinitrc''' file to configure '''~/.xsession'''.

<pre>
sudo -H -u kodi bash -c "ln -s ~/.xinitrc /home/kodi/.xsession"
</pre>

Make sure the path goes to user's home directory. In this example, the user is '''kodi'''.

You need to use '''sudo''' to run this command. If you do not have '''sudo''', install it.

<pre>
apt install sudo
</pre>

If you create a symbolic link and want to remove it, simply remove the existing '''.xsession''' file you created.

<pre>
rm /home/kodi/.xsession
</pre>

On some systems using a DE such as Gnome, not all systems using Gnome, it may be necessary for '''.xsession''' to be '''.xsessionrc'''. Though this is more likely the case for organization network computers than a personal one, where configurations may vary on a diversity of machines. Most of the time, it will be '''.xsession''' rather than '''.xsessionrc''' that you want to create.

You can also create the '''.xsession''' script directly in the home directory, rather than link it from '''~/.xinitrc'''. This is necessary if you create multiple custom Xsession scripts for multiple users, and you do not in that case link '''~/.xinitrc''' to '''.xsession'''.

You must also autostart the X Window system, which differs somewhat from scenario to scenario. For most setups, all that is necessary is to edit the '''.bashrc''' file.

<pre>
nano ~/.bashrc
</pre>

Add the following as shown.

<pre>
if [[ ! $DISPLAY && $XDG_VTNR -eq 1 ]]; then
exec startx
fi
</pre>

If you wish to remain logged in after quitting X, remove the '''exec''' from the above. Other configurations can be applied, but are irrelevant to autostarting Kodi.

[https://wiki.archlinux.org/index.php/Xinit#Autostart_X_at_login Xinit Autostart X at login]

If you are using LightDM and you just want to create a new login entry for user '''kodi''', you must create a new file.

<pre>
nano /usr/share/xsessions/custom.desktop
</pre>

And insert the following text.

<pre>
[Desktop Entry]
Name=Xsession
Exec=/etc/X11/Xsession
</pre>

This will create a new login option for the custom Xsession. Only this one entry is necessary for LightDM and X11 to find the '''~/.xsession''' script in each user's home directory.

You can use any window manager or desktop enviroment with a custom Xsession script as long as it is installed.

You do this by creating '''~/.xinitrc''' script that contains the command to start the WM or DE.

For instance, if you are using FluxBox.

<pre>
#!/usr/bin/env bash
exec fluxbox &
/usr/bin/kodi -fs
</pre>

The <code>-fs</code> option is full-screen.

To run Gnome in the background, but launch Kodi in the foreground.

<pre>
#!/usr/bin/env bash
exec gnome-session &
/usr/bin/kodi -fs
</pre>

Use the '''~/.xinitrc''' file to configure '''~/.xsession''' to create a custom login for any user, not just Kodi.

<pre>
sudo -H -u [username] bash -c "ln -s ~/.xinitrc ~/.xsession"
</pre>

You must reconfigure Xserver for any user that is not a privileged user to be able to start a custom Xsession.

<pre>
dpkg-reconfigure xserver-xorg-legacy
dpkg-reconfigure xserver-xorg
</pre>

When you reconfigure X11 with these commands, choose to allow non-root users (anybody) to start an Xsession. You should see your changes take effect after rebooting.

HOW-TO:Autostart Kodi for Linux

2018-06-14T16:40:36Z

W3tech: /* Configure Kodi to autostart */

<section begin="intro" /><big>Any or all or a combination of these methods can be used to configure a Debian-based X Window System to boot directly to Kodi. This should work on any Linux using the X Window System, but these instructions are particular to Debian derivatives, such as Ubuntu. A server edition is best for running only Kodi, but this page assumes booting into a desktop OS, not a server distro. However, the instructions here can be used for a server distro with even less configuration than for a desktop. Experiment inside VirtualBox before you apply any of these to your system and make a backup.</big><section end="intro" />

__TOC__

== Installing the X11 Window System ==

Even if you are using something like [https://github.com/graysky2/kodi-standalone-service Kodi Standalone Service], you still need use a WM or a DE that installs the '''x-window-manager''' software package.

To ensure you have this installed use the '''which''' command.

<pre>
which x-window-manager
</pre>

If there is no such package, you can use '''apt''' to search your Linux distributions repository.

<pre>
apt-cache search x-window-manager
</pre>

This will general a list of packages containing '''x-window-manager''', which cannot be installed alone. If you are not using a DE, you need to use a WM. And, you can also use a compositing WM like Compiz, for fast 3D effects.

[https://wiki.archlinux.org/index.php/Compiz Compiz - ArchWiki]

A note on using Kodi Standalone Service, this package runs Kodi as a '''systemd''' service and disables the login for user '''kodi''' and will not work when autologin is enabled. In fact, it will break the login process if you autologin user '''kodi''' and run Kodi Standalone Service at the same time. This package is installed automatically with the standard Kodi package when you install Kodi on Raspbian, but must be configured manually for all other Linux distributions. You can run the '''which''' command to find this package as well.

<pre>
which kodi-standalone
</pre>

Be advised, Kodi Standalone Service still launches the Kodi GUI and still requires a WM even though it is running as a '''systemd''' service. When you install a WM such as '''xfwm4''' (the WM for XFCE4), the CLI will tell you if it provides the '''x-window-manager''' package.

<pre>
Setting up xfwm4 (4.12.4-1) ...
update-alternatives: using /usr/bin/xfwm4 to provide /usr/bin/x-window-manager (x-window-manager) in auto mode
</pre>

If you do not see this message at the end of the installation, the WM you selected does not provide this software package and may not actually be a complete WM itself but only part of a package containing a WM.

For a great example on exactly how you would do this with '''xfwm4''', see this ArchWiki entry.

[https://wiki.archlinux.org/index.php/Xfwm XFWM - ArchWiki]

Most systems utilize the client version of the X11 software an Xsession requires.

For more X11 features and functionality, you may optionally upgrade to the server software packages for the X Window System.

<pre>apt install xauth xorg xinit xserver-xorg-core xserver-xorg xserver-common</pre>

The Ubuntu wiki is usually a good source of information.

[https://wiki.ubuntu.com/CustomXSession CustomXSession - Ubuntu Wiki]

Custom user sessions can be created with the X11 Window System to run scripts, autostart apps, and launch a WM or DE.

LightDM is used for autologin.

== Customize LightDM to autologin ==

You can utilize the ability to customize LightDM data manager by changing the builtin custom configuration file '''50-myconfig.conf''' using '''nano''' or another text editor. If you have no DE or WM you can install '''lightdm''', but should make sure to do a bit of research before you do. Most versions of Linux use LightDM, but many server versions do not. For Ubuntu Server with no DE, for example, installing '''lightdm''' is okay and necessary. Changing the behavior of LightDM is done using a custom '''50-myconfig.conf''' configuration file.

To see if you have '''lightdm''' use '''which'''.

<pre>
which lightdm
</pre>

If not, install it with '''apt'''.

<pre>
apt install lightdm
</pre>

Configure LightDM for autologin to boot directly to Kodi.

<pre>
nano /etc/lightdm/lightdm.conf
</pre>

Uncomment the following line.

<pre>
#autologin-user=
</pre>

And add the user you want to autologin. The user is named '''kodi''' in this example.

<pre>
autologin-user=kodi
</pre>

And then you can create /etc/lightdm/lightdm.conf.d/50-myconfig.conf, but ensure the settings in /etc/lightdm/lightdm.conf agree.

Create a custom configuration file called '''50-myconfig.conf''' using '''nano''' or other CLI text editor.

<pre>
mkdir /etc/lightdm/lightdm.conf.d/
nano /etc/lightdm/lightdm.conf.d/50-myconfig.conf
</pre>

Inside this new file add the following text.

<pre>
[SeatDefaults]
autologin-user=kodi
</pre>

CTRL +O +Enter +X to save and exit from '''nano'''.

== Configure Kodi to autostart ==

Configure Kodi to autostart.

<pre>
mkdir -p ~/.config/autostart
ln -s /usr/bin/kodi ~/.config/autostart
</pre>

This method of autostart requires a desktop environment or DE. This is done a bit differently by each DE. Some helpful links can easily be found in today's Web search using any search engine.

[http://edoceo.com/gui/xfce-autostart-apps Autostart Apps in XFCE]

And this link shows how to autostart an app in LXDE on Raspbian.

[http://www.raspberry-projects.com/pi/pi-operating-systems/raspbian/auto-running-programs-gui Auto running programs LXDE - Raspberry Pi Projects]

The Raspberry Pi is a bit more of a tweak, but these are excellent links that will tell you how. The first link is the most helpful to making sure Kodi autostarts in Pi, and utilizes a '''crontab'''. There are many settings on the Pi that control boot, and the first link gives the best most trouble-free way to boot directly to Kodi.

[https://www.leowkahman.com/2016/03/05/lamp-stack-on-raspberry-pi-with-kodi-running-at-startup/ LAMP stack on Raspberry Pi with Kodi running at startup]

In the above link, the author describes using Crontab (short for "Cron table") to boot directly to Kodi.

<pre>
apt install cron
crontab -e
</pre>

Cron will ask you to choose a text editor from available options. I choose option 2 for '''nano'''.

In the new Crontab, enter the following text.

<pre>
@reboot kodi --standalone
</pre>

You could also consider using Crontab to run a script, much like described on this page in the section entitled "Run kodi in a window manager" if you scroll down the page.

[https://wiki.archlinux.org/index.php/Kodi Kodi - Run kodi in a window manager]

Instead your Crontab could look like this.

<pre>
@reboot startx
</pre>

And create an '''~/.xinitrc''' file.

<pre>
nano ~/.xinitrc
</pre>

The '''~/.xinitrc''' file should look like this.

<pre>
#!/bin/bash
kodi --standalone (this is proper syntax for most Kodi installs)
#kodi-standalone (this is the syntax that works on Pi)
sudo chvt 2
sleep 1
sudo chvt 1
</pre>

Make sure to make '''~/.xinitrc''' executable by running.

<pre>
chmod +x ~/.xinitrc
</pre>

To ensure no password is required by '''sudo''' for any user logging in when this script runs, you must edit /etc/sudoers or run the '''visudo''' command if it is installed to edit /etc/sudoers. You can install '''visudo''' from your Linux distributions default repository.

<pre>
apt install sudo
</pre>

For any non-root users, create an entry in this file like shown here.

<pre>
kodi ALL=NOPASSWD: /usr/bin/chvt
pi ALL=NOPASSWD: /usr/bin/chvt
</pre>

The above example is for users '''pi''' and '''kodi'''.

If you decide not use a Cron table, you can always remove it again.

<pre>
crontab -r
</pre>

This is a quick reference for Crontab.

[http://www.adminschoice.com/crontab-quick-reference Crontab Quick Reference]

These linked pages facilitate more tweaks and settings relevant to other uses of the X Window System on Pi.

[http://ozzmaker.com/enable-x-windows-on-piscreen/ Enable X Window System on PiScreen]

Other things to tweak on Raspbian.

[https://yingtongli.me/blog/2016/12/21/splash.html Raspbian splash screen guide - Clean up the boot process]

[https://scribles.net/lightning-bolt-under-voltage-warning-on-raspberry-pi/ Under voltage warning and disabling splash screen on Raspbian]

[https://raspberrypi.stackexchange.com/questions/59310/remove-boot-messages-all-text-in-jessie Remove boot messages all text in Raspbian - Raspberry Pi Stack Exchange]

And, if you would rather, it is easier to follow the process provided by this link to modify the Raspbian image before installing it onto the microSD card.

[https://wiki.debian.org/RaspberryPi/qemu-user-static Modifying Raspbian with qemu-user-static]

The above link describes removing the DE from a Raspbian image, though Raspbian Lite is a much better starting point for using Qemu for this purpose.

You can also use the X11 Window System to autostart Kodi by placing a startup script in the /etc/X11/Xsession.d/ directory.

[https://debian-administration.org/article/50/Running_applications_automatically_when_X_starts Running applications automatically when X starts]

<pre>
nano /etc/X11/Xsession.d/startup-local
</pre>

Insert this text into the new file. Use CTRL + O + Enter + X to save the file.

<pre>
#!/bin/sh
/usr/bin/kodi
</pre>

If you have a WM, such as Blackbox you can add it here as well.

<pre>
#!/bin/sh
blackbox &
/usr/bin/kodi
</pre>

Set permissions to make it executable. Use the ampersand to run an application in the background, such as a WM you only need to for the purpose of launching Kodi but not if you don't want to use the WM itself. Kodi will not launch without a DE or WM, but placing the ampersand "&" at the end of the command makes it run in the background where it can do its job out of sight. Also, make sure to start a WM or DE before running an application in the foreground. This is not necessary for apps running in the background.

<pre>
chmod 755 /etc/X11/Xsession.d/startup-local
</pre>

If Kodi is not installed at the standard path, find it using the '''which''' command.

<pre>
which kodi
</pre>

This feature is available on X Window System operating systems most Linux distributions use the X Window System.

== Create custom Xsession script ==

To create a custom Xsession script with a text editor we start with an '''xinitrc''' script. For more detail on how to create and use '''xinit''', there is a great guide available here.

[https://en.wikibooks.org/wiki/Guide_to_X11/Starting_Sessions Guide to X11 - Starting Sessions - WikiBooks]

<pre>
nano ~/.xinitrc
</pre>

To run Kodi full-screen make sure the text reads:

<pre>
#!/usr/bin/env bash
exec gnome-session
/usr/bin/kodi -fs
</pre>

Replace the '''gnome-session''' with the DE or WM command you are using. See the last section for examples.

To make '''~/.xinitrc''' executable use.

<pre>
chmod +x ~/.xinitrc
</pre>

Use '''sudo''' and the '''~/.xinitrc''' file to configure '''~/.xsession'''.

<pre>
sudo -H -u kodi bash -c "ln -s ~/.xinitrc /home/kodi/.xsession"
</pre>

Make sure the path goes to user's home directory. In this example, the user is '''kodi'''.

You need to use '''sudo''' to run this command. If you do not have '''sudo''', install it.

<pre>
apt install sudo
</pre>

If you create a symbolic link and want to remove it, simply remove the existing '''.xsession''' file you created.

<pre>
rm /home/kodi/.xsession
</pre>

On some systems using a DE such as Gnome, not all systems using Gnome, it may be necessary for '''.xsession''' to be '''.xsessionrc'''. Though this is more likely the case for organization network computers than a personal one, where configurations may vary on a diversity of machines. Most of the time, it will be '''.xsession''' rather than '''.xsessionrc''' that you want to create.

You can also create the '''.xsession''' script directly in the home directory, rather than link it from '''~/.xinitrc'''. This is necessary if you create multiple custom Xsession scripts for multiple users, and you do not in that case link '''~/.xinitrc''' to '''.xsession'''.

You must also autostart the X Window system, which differs somewhat from scenario to scenario. For most setups, all that is necessary is to edit the '''.bashrc''' file.

<pre>
nano ~/.bashrc
</pre>

Add the following as shown.

<pre>
if [[ ! $DISPLAY && $XDG_VTNR -eq 1 ]]; then
exec startx
fi
</pre>

If you wish to remain logged in after quitting X, remove the '''exec''' from the above. Other configurations can be applied, but are irrelevant to autostarting Kodi.

[https://wiki.archlinux.org/index.php/Xinit#Autostart_X_at_login Xinit Autostart X at login]

If you are using LightDM and you just want to create a new login entry for user '''kodi''', you must create a new file.

<pre>
nano /usr/share/xsessions/custom.desktop
</pre>

And insert the following text.

<pre>
[Desktop Entry]
Name=Xsession
Exec=/etc/X11/Xsession
</pre>

This will create a new login option for the custom Xsession. Only this one entry is necessary for LightDM and X11 to find the '''~/.xsession''' script in each user's home directory.

You can use any window manager or desktop enviroment with a custom Xsession script as long as it is installed.

You do this by creating '''~/.xinitrc''' script that contains the command to start the WM or DE.

For instance, if you are using FluxBox.

<pre>
#!/usr/bin/env bash
exec fluxbox &
/usr/bin/kodi -fs
</pre>

The <code>-fs</code> option is full-screen.

To run Gnome in the background, but launch Kodi in the foreground.

<pre>
#!/usr/bin/env bash
exec gnome-session &
/usr/bin/kodi -fs
</pre>

Use the '''~/.xinitrc''' file to configure '''~/.xsession''' to create a custom login for any user, not just Kodi.

<pre>
sudo -H -u [username] bash -c "ln -s ~/.xinitrc ~/.xsession"
</pre>

You must reconfigure Xserver for any user that is not a privileged user to be able to start a custom Xsession.

<pre>
dpkg-reconfigure xserver-xorg-legacy
dpkg-reconfigure xserver-xorg
</pre>

When you reconfigure X11 with these commands, choose to allow non-root users (anybody) to start an Xsession. You should see your changes take effect after rebooting.

HOW-TO:Autostart Kodi for Linux

2018-05-02T23:35:12Z

W3tech: /* Customize LightDM to autologin */

<section begin="intro" /><big>Any or all or a combination of these methods can be used to configure a Debian-based X Window System to boot directly to Kodi. This should work on any Linux using the X Window System, but these instructions are particular to Debian derivatives, such as Ubuntu. A server edition is best for running only Kodi, but this page assumes booting into a desktop OS, not a server distro. However, the instructions here can be used for a server distro with even less configuration than for a desktop. Experiment inside VirtualBox before you apply any of these to your system and make a backup.</big><section end="intro" />

__TOC__

== Installing the X11 Window System ==

Even if you are using something like [https://github.com/graysky2/kodi-standalone-service Kodi Standalone Service], you still need use a WM or a DE that installs the '''x-window-manager''' software package.

To ensure you have this installed use the '''which''' command.

<pre>
which x-window-manager
</pre>

If there is no such package, you can use '''apt''' to search your Linux distributions repository.

<pre>
apt-cache search x-window-manager
</pre>

This will general a list of packages containing '''x-window-manager''', which cannot be installed alone. If you are not using a DE, you need to use a WM. And, you can also use a compositing WM like Compiz, for fast 3D effects.

[https://wiki.archlinux.org/index.php/Compiz Compiz - ArchWiki]

A note on using Kodi Standalone Service, this package runs Kodi as a '''systemd''' service and disables the login for user '''kodi''' and will not work when autologin is enabled. In fact, it will break the login process if you autologin user '''kodi''' and run Kodi Standalone Service at the same time. This package is installed automatically with the standard Kodi package when you install Kodi on Raspbian, but must be configured manually for all other Linux distributions. You can run the '''which''' command to find this package as well.

<pre>
which kodi-standalone
</pre>

Be advised, Kodi Standalone Service still launches the Kodi GUI and still requires a WM even though it is running as a '''systemd''' service. When you install a WM such as '''xfwm4''' (the WM for XFCE4), the CLI will tell you if it provides the '''x-window-manager''' package.

<pre>
Setting up xfwm4 (4.12.4-1) ...
update-alternatives: using /usr/bin/xfwm4 to provide /usr/bin/x-window-manager (x-window-manager) in auto mode
</pre>

If you do not see this message at the end of the installation, the WM you selected does not provide this software package and may not actually be a complete WM itself but only part of a package containing a WM.

For a great example on exactly how you would do this with '''xfwm4''', see this ArchWiki entry.

[https://wiki.archlinux.org/index.php/Xfwm XFWM - ArchWiki]

Most systems utilize the client version of the X11 software an Xsession requires.

For more X11 features and functionality, you may optionally upgrade to the server software packages for the X Window System.

<pre>apt install xauth xorg xinit xserver-xorg-core xserver-xorg xserver-common</pre>

The Ubuntu wiki is usually a good source of information.

[https://wiki.ubuntu.com/CustomXSession CustomXSession - Ubuntu Wiki]

Custom user sessions can be created with the X11 Window System to run scripts, autostart apps, and launch a WM or DE.

LightDM is used for autologin.

== Customize LightDM to autologin ==

You can utilize the ability to customize LightDM data manager by changing the builtin custom configuration file '''50-myconfig.conf''' using '''nano''' or another text editor. If you have no DE or WM you can install '''lightdm''', but should make sure to do a bit of research before you do. Most versions of Linux use LightDM, but many server versions do not. For Ubuntu Server with no DE, for example, installing '''lightdm''' is okay and necessary. Changing the behavior of LightDM is done using a custom '''50-myconfig.conf''' configuration file.

To see if you have '''lightdm''' use '''which'''.

<pre>
which lightdm
</pre>

If not, install it with '''apt'''.

<pre>
apt install lightdm
</pre>

Configure LightDM for autologin to boot directly to Kodi.

<pre>
nano /etc/lightdm/lightdm.conf
</pre>

Uncomment the following line.

<pre>
#autologin-user=
</pre>

And add the user you want to autologin. The user is named '''kodi''' in this example.

<pre>
autologin-user=kodi
</pre>

And then you can create /etc/lightdm/lightdm.conf.d/50-myconfig.conf, but ensure the settings in /etc/lightdm/lightdm.conf agree.

Create a custom configuration file called '''50-myconfig.conf''' using '''nano''' or other CLI text editor.

<pre>
mkdir /etc/lightdm/lightdm.conf.d/
nano /etc/lightdm/lightdm.conf.d/50-myconfig.conf
</pre>

Inside this new file add the following text.

<pre>
[SeatDefaults]
autologin-user=kodi
</pre>

CTRL +O +Enter +X to save and exit from '''nano'''.

== Configure Kodi to autostart ==

Configure Kodi to autostart.

<pre>
mkdir -p ~/.config/autostart
ln -s /usr/bin/kodi ~/.config/autostart
</pre>

This method of autostart requires a desktop environment or DE. This is done a bit differently by each DE. Some helpful links can easily be found in today's Web search using any search engine.

[http://edoceo.com/gui/xfce-autostart-apps Autostart Apps in XFCE]

And this link shows how to autostart an app in LXDE on Raspbian.

[http://www.raspberry-projects.com/pi/pi-operating-systems/raspbian/auto-running-programs-gui Auto running programs LXDE - Raspberry Pi Projects]

The Raspberry Pi is a bit more of a tweak, but these are excellent links that will tell you how. The first link is the most helpful to making sure Kodi autostarts in Pi, and utilizes a '''crontab'''. There are many settings on the Pi that control boot, and the first link gives the best most trouble-free way to boot directly to Kodi.

[https://www.leowkahman.com/2016/03/05/lamp-stack-on-raspberry-pi-with-kodi-running-at-startup/ LAMP stack on Raspberry Pi with Kodi running at startup]

In the above link, the author describes using Crontab (short for "Cron table") to boot directly to Kodi.

<pre>
crontab -e
</pre>

Cron will ask you to choose a text editor from available options. I choose option 2 for '''nano'''.

In the new Crontab, enter the following text.

<pre>
@reboot kodi --standalone
</pre>

You could also consider using Crontab to run a script, much like described on this page in the section entitled "Run kodi in a window manager" if you scroll down the page.

[https://wiki.archlinux.org/index.php/Kodi Kodi - Run kodi in a window manager]

Instead your Crontab could look like this.

<pre>
@reboot startx
</pre>

And create an '''~/.xinitrc''' file.

<pre>
nano ~/.xinitrc
</pre>

The '''~/.xinitrc''' file should look like this.

<pre>
#!/bin/bash
kodi-standalone
sudo chvt 2
sleep 1
sudo chvt 1
</pre>

Make sure to make '''~/.xinitrc''' executable by running.

<pre>
chmod +x ~/.xinitrc
</pre>

To ensure no password is required by '''sudo''' for any user logging in when this script runs, you must edit /etc/sudoers or run the '''visudo''' command if it is installed to edit /etc/sudoers. You can install '''visudo''' from your Linux distributions default repository.

<pre>
apt install sudo
</pre>

For any non-root users, create an entry in this file like shown here.

<pre>
kodi ALL=NOPASSWD: /usr/bin/chvt
pi ALL=NOPASSWD: /usr/bin/chvt
</pre>

The above example is for users '''pi''' and '''kodi'''.

If you decide not use a Cron table, you can always remove it again.

<pre>
crontab -r
</pre>

This is a quick reference for Crontab.

[http://www.adminschoice.com/crontab-quick-reference Crontab Quick Reference]

These linked pages facilitate more tweaks and settings relevant to other uses of the X Window System on Pi.

[http://ozzmaker.com/enable-x-windows-on-piscreen/ Enable X Window System on PiScreen]

Other things to tweak on Raspbian.

[https://yingtongli.me/blog/2016/12/21/splash.html Raspbian splash screen guide - Clean up the boot process]

[https://scribles.net/lightning-bolt-under-voltage-warning-on-raspberry-pi/ Under voltage warning and disabling splash screen on Raspbian]

[https://raspberrypi.stackexchange.com/questions/59310/remove-boot-messages-all-text-in-jessie Remove boot messages all text in Raspbian - Raspberry Pi Stack Exchange]

And, if you would rather, it is easier to follow the process provided by this link to modify the Raspbian image before installing it onto the microSD card.

[https://wiki.debian.org/RaspberryPi/qemu-user-static Modifying Raspbian with qemu-user-static]

The above link describes removing the DE from a Raspbian image, though Raspbian Lite is a much better starting point for using Qemu for this purpose.

You can also use the X11 Window System to autostart Kodi by placing a startup script in the /etc/X11/Xsession.d/ directory.

[https://debian-administration.org/article/50/Running_applications_automatically_when_X_starts Running applications automatically when X starts]

<pre>
nano /etc/X11/Xsession.d/startup-local
</pre>

Insert this text into the new file. Use CTRL + O + Enter + X to save the file.

<pre>
#!/bin/sh
/usr/bin/kodi
</pre>

If you have a WM, such as Blackbox you can add it here as well.

<pre>
#!/bin/sh
blackbox &
/usr/bin/kodi
</pre>

Set permissions to make it executable. Use the ampersand to run an application in the background, such as a WM you only need to for the purpose of launching Kodi but not if you don't want to use the WM itself. Kodi will not launch without a DE or WM, but placing the ampersand "&" at the end of the command makes it run in the background where it can do its job out of sight. Also, make sure to start a WM or DE before running an application in the foreground. This is not necessary for apps running in the background.

<pre>
chmod 755 /etc/X11/Xsession.d/startup-local
</pre>

If Kodi is not installed at the standard path, find it using the '''which''' command.

<pre>
which kodi
</pre>

This feature is available on X Window System operating systems most Linux distributions use the X Window System.

== Create custom Xsession script ==

To create a custom Xsession script with a text editor we start with an '''xinitrc''' script. For more detail on how to create and use '''xinit''', there is a great guide available here.

[https://en.wikibooks.org/wiki/Guide_to_X11/Starting_Sessions Guide to X11 - Starting Sessions - WikiBooks]

<pre>
nano ~/.xinitrc
</pre>

To run Kodi full-screen make sure the text reads:

<pre>
#!/usr/bin/env bash
exec gnome-session
/usr/bin/kodi -fs
</pre>

Replace the '''gnome-session''' with the DE or WM command you are using. See the last section for examples.

To make '''~/.xinitrc''' executable use.

<pre>
chmod +x ~/.xinitrc
</pre>

Use '''sudo''' and the '''~/.xinitrc''' file to configure '''~/.xsession'''.

<pre>
sudo -H -u kodi bash -c "ln -s ~/.xinitrc /home/kodi/.xsession"
</pre>

Make sure the path goes to user's home directory. In this example, the user is '''kodi'''.

You need to use '''sudo''' to run this command. If you do not have '''sudo''', install it.

<pre>
apt install sudo
</pre>

If you create a symbolic link and want to remove it, simply remove the existing '''.xsession''' file you created.

<pre>
rm /home/kodi/.xsession
</pre>

On some systems using a DE such as Gnome, not all systems using Gnome, it may be necessary for '''.xsession''' to be '''.xsessionrc'''. Though this is more likely the case for organization network computers than a personal one, where configurations may vary on a diversity of machines. Most of the time, it will be '''.xsession''' rather than '''.xsessionrc''' that you want to create.

You can also create the '''.xsession''' script directly in the home directory, rather than link it from '''~/.xinitrc'''. This is necessary if you create multiple custom Xsession scripts for multiple users, and you do not in that case link '''~/.xinitrc''' to '''.xsession'''.

You must also autostart the X Window system, which differs somewhat from scenario to scenario. For most setups, all that is necessary is to edit the '''.bashrc''' file.

<pre>
nano ~/.bashrc
</pre>

Add the following as shown.

<pre>
if [[ ! $DISPLAY && $XDG_VTNR -eq 1 ]]; then
exec startx
fi
</pre>

If you wish to remain logged in after quitting X, remove the '''exec''' from the above. Other configurations can be applied, but are irrelevant to autostarting Kodi.

[https://wiki.archlinux.org/index.php/Xinit#Autostart_X_at_login Xinit Autostart X at login]

If you are using LightDM and you just want to create a new login entry for user '''kodi''', you must create a new file.

<pre>
nano /usr/share/xsessions/custom.desktop
</pre>

And insert the following text.

<pre>
[Desktop Entry]
Name=Xsession
Exec=/etc/X11/Xsession
</pre>

This will create a new login option for the custom Xsession. Only this one entry is necessary for LightDM and X11 to find the '''~/.xsession''' script in each user's home directory.

You can use any window manager or desktop enviroment with a custom Xsession script as long as it is installed.

You do this by creating '''~/.xinitrc''' script that contains the command to start the WM or DE.

For instance, if you are using FluxBox.

<pre>
#!/usr/bin/env bash
exec fluxbox &
/usr/bin/kodi -fs
</pre>

The <code>-fs</code> option is full-screen.

To run Gnome in the background, but launch Kodi in the foreground.

<pre>
#!/usr/bin/env bash
exec gnome-session &
/usr/bin/kodi -fs
</pre>

Use the '''~/.xinitrc''' file to configure '''~/.xsession''' to create a custom login for any user, not just Kodi.

<pre>
sudo -H -u [username] bash -c "ln -s ~/.xinitrc ~/.xsession"
</pre>

You must reconfigure Xserver for any user that is not a privileged user to be able to start a custom Xsession.

<pre>
dpkg-reconfigure xserver-xorg-legacy
dpkg-reconfigure xserver-xorg
</pre>

When you reconfigure X11 with these commands, choose to allow non-root users (anybody) to start an Xsession. You should see your changes take effect after rebooting.

HOW-TO:Autostart Kodi for Linux

2018-05-02T23:25:06Z

W3tech: /* Configure Kodi to autostart */

<section begin="intro" /><big>Any or all or a combination of these methods can be used to configure a Debian-based X Window System to boot directly to Kodi. This should work on any Linux using the X Window System, but these instructions are particular to Debian derivatives, such as Ubuntu. A server edition is best for running only Kodi, but this page assumes booting into a desktop OS, not a server distro. However, the instructions here can be used for a server distro with even less configuration than for a desktop. Experiment inside VirtualBox before you apply any of these to your system and make a backup.</big><section end="intro" />

__TOC__

== Installing the X11 Window System ==

Even if you are using something like [https://github.com/graysky2/kodi-standalone-service Kodi Standalone Service], you still need use a WM or a DE that installs the '''x-window-manager''' software package.

To ensure you have this installed use the '''which''' command.

<pre>
which x-window-manager
</pre>

If there is no such package, you can use '''apt''' to search your Linux distributions repository.

<pre>
apt-cache search x-window-manager
</pre>

This will general a list of packages containing '''x-window-manager''', which cannot be installed alone. If you are not using a DE, you need to use a WM. And, you can also use a compositing WM like Compiz, for fast 3D effects.

[https://wiki.archlinux.org/index.php/Compiz Compiz - ArchWiki]

A note on using Kodi Standalone Service, this package runs Kodi as a '''systemd''' service and disables the login for user '''kodi''' and will not work when autologin is enabled. In fact, it will break the login process if you autologin user '''kodi''' and run Kodi Standalone Service at the same time. This package is installed automatically with the standard Kodi package when you install Kodi on Raspbian, but must be configured manually for all other Linux distributions. You can run the '''which''' command to find this package as well.

<pre>
which kodi-standalone
</pre>

Be advised, Kodi Standalone Service still launches the Kodi GUI and still requires a WM even though it is running as a '''systemd''' service. When you install a WM such as '''xfwm4''' (the WM for XFCE4), the CLI will tell you if it provides the '''x-window-manager''' package.

<pre>
Setting up xfwm4 (4.12.4-1) ...
update-alternatives: using /usr/bin/xfwm4 to provide /usr/bin/x-window-manager (x-window-manager) in auto mode
</pre>

If you do not see this message at the end of the installation, the WM you selected does not provide this software package and may not actually be a complete WM itself but only part of a package containing a WM.

For a great example on exactly how you would do this with '''xfwm4''', see this ArchWiki entry.

[https://wiki.archlinux.org/index.php/Xfwm XFWM - ArchWiki]

Most systems utilize the client version of the X11 software an Xsession requires.

For more X11 features and functionality, you may optionally upgrade to the server software packages for the X Window System.

<pre>apt install xauth xorg xinit xserver-xorg-core xserver-xorg xserver-common</pre>

The Ubuntu wiki is usually a good source of information.

[https://wiki.ubuntu.com/CustomXSession CustomXSession - Ubuntu Wiki]

Custom user sessions can be created with the X11 Window System to run scripts, autostart apps, and launch a WM or DE.

LightDM is used for autologin.

== Customize LightDM to autologin ==

You can utilize the ability to customize LightDM data manager by changing the builtin custom configuration file '''50-myconfig.conf''' using '''nano''' or another text editor. If you have no DE or WM you can install '''lightdm''', but should make sure to do a bit of research before you do. Most versions of Linux use LightDM, but many server versions do not. For Ubuntu Server with no DE, for example, installing '''lightdm''' is okay and necessary. Changing the behavior of LightDM is done using a custom '''50-myconfig.conf''' configuration file.

To see if you have '''lightdm''' use '''which'''.

<pre>
which lightdm
</pre>

If not, install it with '''apt'''.

<pre>
apt install lightdm
</pre>

Create a custom configuration file called '''50-myconfig.conf''' using '''nano''' or other CLI text editor.

<pre>
mkdir /etc/lightdm/lightdm.conf.d/
nano /etc/lightdm/lightdm.conf.d/50-myconfig.conf
</pre>

Inside this new file add the following text.

<pre>
[SeatDefaults]
autologin-user=kodi
</pre>

On Raspbian, you configure LightDM differently for autologin to boot directly to Kodi.

<pre>
nano /etc/lightdm/lightdm.conf
</pre>

Uncomment the following line.

<pre>
#autologin-user=
</pre>

And add the user you want to autologin. The user is named '''kodi''' in this example.

<pre>
autologin-user=kodi
</pre>

And then you can create /etc/lightdm/lightdm.conf.d/50-myconfig.conf, but ensure the settings in /etc/lightdm/lightdm.conf agree.

== Configure Kodi to autostart ==

Configure Kodi to autostart.

<pre>
mkdir -p ~/.config/autostart
ln -s /usr/bin/kodi ~/.config/autostart
</pre>

This method of autostart requires a desktop environment or DE. This is done a bit differently by each DE. Some helpful links can easily be found in today's Web search using any search engine.

[http://edoceo.com/gui/xfce-autostart-apps Autostart Apps in XFCE]

And this link shows how to autostart an app in LXDE on Raspbian.

[http://www.raspberry-projects.com/pi/pi-operating-systems/raspbian/auto-running-programs-gui Auto running programs LXDE - Raspberry Pi Projects]

The Raspberry Pi is a bit more of a tweak, but these are excellent links that will tell you how. The first link is the most helpful to making sure Kodi autostarts in Pi, and utilizes a '''crontab'''. There are many settings on the Pi that control boot, and the first link gives the best most trouble-free way to boot directly to Kodi.

[https://www.leowkahman.com/2016/03/05/lamp-stack-on-raspberry-pi-with-kodi-running-at-startup/ LAMP stack on Raspberry Pi with Kodi running at startup]

In the above link, the author describes using Crontab (short for "Cron table") to boot directly to Kodi.

<pre>
crontab -e
</pre>

Cron will ask you to choose a text editor from available options. I choose option 2 for '''nano'''.

In the new Crontab, enter the following text.

<pre>
@reboot kodi --standalone
</pre>

You could also consider using Crontab to run a script, much like described on this page in the section entitled "Run kodi in a window manager" if you scroll down the page.

[https://wiki.archlinux.org/index.php/Kodi Kodi - Run kodi in a window manager]

Instead your Crontab could look like this.

<pre>
@reboot startx
</pre>

And create an '''~/.xinitrc''' file.

<pre>
nano ~/.xinitrc
</pre>

The '''~/.xinitrc''' file should look like this.

<pre>
#!/bin/bash
kodi-standalone
sudo chvt 2
sleep 1
sudo chvt 1
</pre>

Make sure to make '''~/.xinitrc''' executable by running.

<pre>
chmod +x ~/.xinitrc
</pre>

To ensure no password is required by '''sudo''' for any user logging in when this script runs, you must edit /etc/sudoers or run the '''visudo''' command if it is installed to edit /etc/sudoers. You can install '''visudo''' from your Linux distributions default repository.

<pre>
apt install sudo
</pre>

For any non-root users, create an entry in this file like shown here.

<pre>
kodi ALL=NOPASSWD: /usr/bin/chvt
pi ALL=NOPASSWD: /usr/bin/chvt
</pre>

The above example is for users '''pi''' and '''kodi'''.

If you decide not use a Cron table, you can always remove it again.

<pre>
crontab -r
</pre>

This is a quick reference for Crontab.

[http://www.adminschoice.com/crontab-quick-reference Crontab Quick Reference]

These linked pages facilitate more tweaks and settings relevant to other uses of the X Window System on Pi.

[http://ozzmaker.com/enable-x-windows-on-piscreen/ Enable X Window System on PiScreen]

Other things to tweak on Raspbian.

[https://yingtongli.me/blog/2016/12/21/splash.html Raspbian splash screen guide - Clean up the boot process]

[https://scribles.net/lightning-bolt-under-voltage-warning-on-raspberry-pi/ Under voltage warning and disabling splash screen on Raspbian]

[https://raspberrypi.stackexchange.com/questions/59310/remove-boot-messages-all-text-in-jessie Remove boot messages all text in Raspbian - Raspberry Pi Stack Exchange]

And, if you would rather, it is easier to follow the process provided by this link to modify the Raspbian image before installing it onto the microSD card.

[https://wiki.debian.org/RaspberryPi/qemu-user-static Modifying Raspbian with qemu-user-static]

The above link describes removing the DE from a Raspbian image, though Raspbian Lite is a much better starting point for using Qemu for this purpose.

You can also use the X11 Window System to autostart Kodi by placing a startup script in the /etc/X11/Xsession.d/ directory.

[https://debian-administration.org/article/50/Running_applications_automatically_when_X_starts Running applications automatically when X starts]

<pre>
nano /etc/X11/Xsession.d/startup-local
</pre>

Insert this text into the new file. Use CTRL + O + Enter + X to save the file.

<pre>
#!/bin/sh
/usr/bin/kodi
</pre>

If you have a WM, such as Blackbox you can add it here as well.

<pre>
#!/bin/sh
blackbox &
/usr/bin/kodi
</pre>

Set permissions to make it executable. Use the ampersand to run an application in the background, such as a WM you only need to for the purpose of launching Kodi but not if you don't want to use the WM itself. Kodi will not launch without a DE or WM, but placing the ampersand "&" at the end of the command makes it run in the background where it can do its job out of sight. Also, make sure to start a WM or DE before running an application in the foreground. This is not necessary for apps running in the background.

<pre>
chmod 755 /etc/X11/Xsession.d/startup-local
</pre>

If Kodi is not installed at the standard path, find it using the '''which''' command.

<pre>
which kodi
</pre>

This feature is available on X Window System operating systems most Linux distributions use the X Window System.

== Create custom Xsession script ==

To create a custom Xsession script with a text editor we start with an '''xinitrc''' script. For more detail on how to create and use '''xinit''', there is a great guide available here.

[https://en.wikibooks.org/wiki/Guide_to_X11/Starting_Sessions Guide to X11 - Starting Sessions - WikiBooks]

<pre>
nano ~/.xinitrc
</pre>

To run Kodi full-screen make sure the text reads:

<pre>
#!/usr/bin/env bash
exec gnome-session
/usr/bin/kodi -fs
</pre>

Replace the '''gnome-session''' with the DE or WM command you are using. See the last section for examples.

To make '''~/.xinitrc''' executable use.

<pre>
chmod +x ~/.xinitrc
</pre>

Use '''sudo''' and the '''~/.xinitrc''' file to configure '''~/.xsession'''.

<pre>
sudo -H -u kodi bash -c "ln -s ~/.xinitrc /home/kodi/.xsession"
</pre>

Make sure the path goes to user's home directory. In this example, the user is '''kodi'''.

You need to use '''sudo''' to run this command. If you do not have '''sudo''', install it.

<pre>
apt install sudo
</pre>

If you create a symbolic link and want to remove it, simply remove the existing '''.xsession''' file you created.

<pre>
rm /home/kodi/.xsession
</pre>

On some systems using a DE such as Gnome, not all systems using Gnome, it may be necessary for '''.xsession''' to be '''.xsessionrc'''. Though this is more likely the case for organization network computers than a personal one, where configurations may vary on a diversity of machines. Most of the time, it will be '''.xsession''' rather than '''.xsessionrc''' that you want to create.

You can also create the '''.xsession''' script directly in the home directory, rather than link it from '''~/.xinitrc'''. This is necessary if you create multiple custom Xsession scripts for multiple users, and you do not in that case link '''~/.xinitrc''' to '''.xsession'''.

You must also autostart the X Window system, which differs somewhat from scenario to scenario. For most setups, all that is necessary is to edit the '''.bashrc''' file.

<pre>
nano ~/.bashrc
</pre>

Add the following as shown.

<pre>
if [[ ! $DISPLAY && $XDG_VTNR -eq 1 ]]; then
exec startx
fi
</pre>

If you wish to remain logged in after quitting X, remove the '''exec''' from the above. Other configurations can be applied, but are irrelevant to autostarting Kodi.

[https://wiki.archlinux.org/index.php/Xinit#Autostart_X_at_login Xinit Autostart X at login]

If you are using LightDM and you just want to create a new login entry for user '''kodi''', you must create a new file.

<pre>
nano /usr/share/xsessions/custom.desktop
</pre>

And insert the following text.

<pre>
[Desktop Entry]
Name=Xsession
Exec=/etc/X11/Xsession
</pre>

This will create a new login option for the custom Xsession. Only this one entry is necessary for LightDM and X11 to find the '''~/.xsession''' script in each user's home directory.

You can use any window manager or desktop enviroment with a custom Xsession script as long as it is installed.

You do this by creating '''~/.xinitrc''' script that contains the command to start the WM or DE.

For instance, if you are using FluxBox.

<pre>
#!/usr/bin/env bash
exec fluxbox &
/usr/bin/kodi -fs
</pre>

The <code>-fs</code> option is full-screen.

To run Gnome in the background, but launch Kodi in the foreground.

<pre>
#!/usr/bin/env bash
exec gnome-session &
/usr/bin/kodi -fs
</pre>

Use the '''~/.xinitrc''' file to configure '''~/.xsession''' to create a custom login for any user, not just Kodi.

<pre>
sudo -H -u [username] bash -c "ln -s ~/.xinitrc ~/.xsession"
</pre>

You must reconfigure Xserver for any user that is not a privileged user to be able to start a custom Xsession.

<pre>
dpkg-reconfigure xserver-xorg-legacy
dpkg-reconfigure xserver-xorg
</pre>

When you reconfigure X11 with these commands, choose to allow non-root users (anybody) to start an Xsession. You should see your changes take effect after rebooting.

HOW-TO:Autostart Kodi for Linux

2018-04-29T18:08:10Z

W3tech: /* Customize LightDM to autologin */

<section begin="intro" /><big>Any or all or a combination of these methods can be used to configure a Debian-based X Window System to boot directly to Kodi. This should work on any Linux using the X Window System, but these instructions are particular to Debian derivatives, such as Ubuntu. A server edition is best for running only Kodi, but this page assumes booting into a desktop OS, not a server distro. However, the instructions here can be used for a server distro with even less configuration than for a desktop. Experiment inside VirtualBox before you apply any of these to your system and make a backup.</big><section end="intro" />

__TOC__

== Installing the X11 Window System ==

Even if you are using something like [https://github.com/graysky2/kodi-standalone-service Kodi Standalone Service], you still need use a WM or a DE that installs the '''x-window-manager''' software package.

To ensure you have this installed use the '''which''' command.

<pre>
which x-window-manager
</pre>

If there is no such package, you can use '''apt''' to search your Linux distributions repository.

<pre>
apt-cache search x-window-manager
</pre>

This will general a list of packages containing '''x-window-manager''', which cannot be installed alone. If you are not using a DE, you need to use a WM. And, you can also use a compositing WM like Compiz, for fast 3D effects.

[https://wiki.archlinux.org/index.php/Compiz Compiz - ArchWiki]

A note on using Kodi Standalone Service, this package runs Kodi as a '''systemd''' service and disables the login for user '''kodi''' and will not work when autologin is enabled. In fact, it will break the login process if you autologin user '''kodi''' and run Kodi Standalone Service at the same time. This package is installed automatically with the standard Kodi package when you install Kodi on Raspbian, but must be configured manually for all other Linux distributions. You can run the '''which''' command to find this package as well.

<pre>
which kodi-standalone
</pre>

Be advised, Kodi Standalone Service still launches the Kodi GUI and still requires a WM even though it is running as a '''systemd''' service. When you install a WM such as '''xfwm4''' (the WM for XFCE4), the CLI will tell you if it provides the '''x-window-manager''' package.

<pre>
Setting up xfwm4 (4.12.4-1) ...
update-alternatives: using /usr/bin/xfwm4 to provide /usr/bin/x-window-manager (x-window-manager) in auto mode
</pre>

If you do not see this message at the end of the installation, the WM you selected does not provide this software package and may not actually be a complete WM itself but only part of a package containing a WM.

For a great example on exactly how you would do this with '''xfwm4''', see this ArchWiki entry.

[https://wiki.archlinux.org/index.php/Xfwm XFWM - ArchWiki]

Most systems utilize the client version of the X11 software an Xsession requires.

For more X11 features and functionality, you may optionally upgrade to the server software packages for the X Window System.

<pre>apt install xauth xorg xinit xserver-xorg-core xserver-xorg xserver-common</pre>

The Ubuntu wiki is usually a good source of information.

[https://wiki.ubuntu.com/CustomXSession CustomXSession - Ubuntu Wiki]

Custom user sessions can be created with the X11 Window System to run scripts, autostart apps, and launch a WM or DE.

LightDM is used for autologin.

== Customize LightDM to autologin ==

You can utilize the ability to customize LightDM data manager by changing the builtin custom configuration file '''50-myconfig.conf''' using '''nano''' or another text editor. If you have no DE or WM you can install '''lightdm''', but should make sure to do a bit of research before you do. Most versions of Linux use LightDM, but many server versions do not. For Ubuntu Server with no DE, for example, installing '''lightdm''' is okay and necessary. Changing the behavior of LightDM is done using a custom '''50-myconfig.conf''' configuration file.

To see if you have '''lightdm''' use '''which'''.

<pre>
which lightdm
</pre>

If not, install it with '''apt'''.

<pre>
apt install lightdm
</pre>

Create a custom configuration file called '''50-myconfig.conf''' using '''nano''' or other CLI text editor.

<pre>
mkdir /etc/lightdm/lightdm.conf.d/
nano /etc/lightdm/lightdm.conf.d/50-myconfig.conf
</pre>

Inside this new file add the following text.

<pre>
[SeatDefaults]
autologin-user=kodi
</pre>

On Raspbian, you configure LightDM differently for autologin to boot directly to Kodi.

<pre>
nano /etc/lightdm/lightdm.conf
</pre>

Uncomment the following line.

<pre>
#autologin-user=
</pre>

And add the user you want to autologin. The user is named '''kodi''' in this example.

<pre>
autologin-user=kodi
</pre>

And then you can create /etc/lightdm/lightdm.conf.d/50-myconfig.conf, but ensure the settings in /etc/lightdm/lightdm.conf agree.

== Configure Kodi to autostart ==

Configure Kodi to autostart.

<pre>
mkdir -p ~/.config/autostart
ln -s /usr/bin/kodi ~/.config/autostart
</pre>

This method of autostart requires a desktop environment or DE. This is done a bit differently by each DE. Some helpful links can easily be found in today's Web search using any search engine.

[http://edoceo.com/gui/xfce-autostart-apps Autostart Apps in XFCE]

And this link shows how to autostart an app in LXDE on Raspbian.

[http://www.raspberry-projects.com/pi/pi-operating-systems/raspbian/auto-running-programs-gui Auto running programs LXDE - Raspberry Pi Projects]

The Raspberry Pi is a bit more of a tweak, but these are excellent links that will tell you how. The first link is the most helpful to making sure Kodi autostarts in Pi, and utilizes a '''crontab'''. There are many settings on the Pi that control boot, and the first link gives the best most trouble-free way to boot directly to Kodi.

[https://www.leowkahman.com/2016/03/05/lamp-stack-on-raspberry-pi-with-kodi-running-at-startup/ LAMP stack on Raspberry Pi with Kodi running at startup]

In the above link, the author describes using Crontab (short for "Cron table") to boot directly to Kodi.

<pre>
crontab -e
</pre>

Cron will ask you to choose a text editor from available options. I choose option 2 for '''nano'''.

In the new Crontab, enter the following text.

<pre>
@reboot kodi --standalone
</pre>

You could also consider using Crontab to run a script, much like described on this page in the section entitled "Run kodi in a window manager" if you scroll down the page.

[https://wiki.archlinux.org/index.php/Kodi Kodi - Run kodi in a window manager]

Instead your Crontab could look like this.

<pre>
@reboot startx
</pre>

And create an '''~/.xinitrc''' file.

<pre>
nano ~/.xinitrc
</pre>

The '''~/.xinitrc''' file should look like this.

<pre>
#!/bin/bash
kodi-standalone
sudo chvt 2
sleep 1
sudo chvt 1
</pre>

Make sure to make '''~/.xinitrc''' executable by running.

<pre>
chmod +x ~/.xinitrc
</pre>

To ensure no password is required by '''sudo''' for any user logging in when this script runs, you must edit /etc/sudoers or run the '''visudo''' command if it is installed to edit /etc/sudoers. You can install '''visudo''' from your Linux distributions default repository.

<pre>
apt install visudo
</pre>

For any non-root users, create an entry in this file like shown here.

<pre>
kodi ALL=NOPASSWD: /usr/bin/chvt
pi ALL=NOPASSWD: /usr/bin/chvt
</pre>

The above example is for users '''pi''' and '''kodi'''.

If you decide not use a Cron table, you can always remove it again.

<pre>
crontab -r
</pre>

This is a quick reference for Crontab.

[http://www.adminschoice.com/crontab-quick-reference Crontab Quick Reference]

These linked pages facilitate more tweaks and settings relevant to other uses of the X Window System on Pi.

[http://ozzmaker.com/enable-x-windows-on-piscreen/ Enable X Window System on PiScreen]

Other things to tweak on Raspbian.

[https://yingtongli.me/blog/2016/12/21/splash.html Raspbian splash screen guide - Clean up the boot process]

[https://scribles.net/lightning-bolt-under-voltage-warning-on-raspberry-pi/ Under voltage warning and disabling splash screen on Raspbian]

[https://raspberrypi.stackexchange.com/questions/59310/remove-boot-messages-all-text-in-jessie Remove boot messages all text in Raspbian - Raspberry Pi Stack Exchange]

And, if you would rather, it is easier to follow the process provided by this link to modify the Raspbian image before installing it onto the microSD card.

[https://wiki.debian.org/RaspberryPi/qemu-user-static Modifying Raspbian with qemu-user-static]

The above link describes removing the DE from a Raspbian image, though Raspbian Lite is a much better starting point for using Qemu for this purpose.

You can also use the X11 Window System to autostart Kodi by placing a startup script in the /etc/X11/Xsession.d/ directory.

[https://debian-administration.org/article/50/Running_applications_automatically_when_X_starts Running applications automatically when X starts]

<pre>
nano /etc/X11/Xsession.d/startup-local
</pre>

Insert this text into the new file. Use CTRL + O + Enter + X to save the file.

<pre>
#!/bin/sh
/usr/bin/kodi
</pre>

If you have a WM, such as Blackbox you can add it here as well.

<pre>
#!/bin/sh
blackbox &
/usr/bin/kodi
</pre>

Set permissions to make it executable. Use the ampersand to run an application in the background, such as a WM you only need to for the purpose of launching Kodi but not if you don't want to use the WM itself. Kodi will not launch without a DE or WM, but placing the ampersand "&" at the end of the command makes it run in the background where it can do its job out of sight. Also, make sure to start a WM or DE before running an application in the foreground. This is not necessary for apps running in the background.

<pre>
chmod 755 /etc/X11/Xsession.d/startup-local
</pre>

If Kodi is not installed at the standard path, find it using the '''which''' command.

<pre>
which kodi
</pre>

This feature is available on X Window System operating systems most Linux distributions use the X Window System.

== Create custom Xsession script ==

To create a custom Xsession script with a text editor we start with an '''xinitrc''' script. For more detail on how to create and use '''xinit''', there is a great guide available here.

[https://en.wikibooks.org/wiki/Guide_to_X11/Starting_Sessions Guide to X11 - Starting Sessions - WikiBooks]

<pre>
nano ~/.xinitrc
</pre>

To run Kodi full-screen make sure the text reads:

<pre>
#!/usr/bin/env bash
exec gnome-session
/usr/bin/kodi -fs
</pre>

Replace the '''gnome-session''' with the DE or WM command you are using. See the last section for examples.

To make '''~/.xinitrc''' executable use.

<pre>
chmod +x ~/.xinitrc
</pre>

Use '''sudo''' and the '''~/.xinitrc''' file to configure '''~/.xsession'''.

<pre>
sudo -H -u kodi bash -c "ln -s ~/.xinitrc /home/kodi/.xsession"
</pre>

Make sure the path goes to user's home directory. In this example, the user is '''kodi'''.

You need to use '''sudo''' to run this command. If you do not have '''sudo''', install it.

<pre>
apt install sudo
</pre>

If you create a symbolic link and want to remove it, simply remove the existing '''.xsession''' file you created.

<pre>
rm /home/kodi/.xsession
</pre>

On some systems using a DE such as Gnome, not all systems using Gnome, it may be necessary for '''.xsession''' to be '''.xsessionrc'''. Though this is more likely the case for organization network computers than a personal one, where configurations may vary on a diversity of machines. Most of the time, it will be '''.xsession''' rather than '''.xsessionrc''' that you want to create.

You can also create the '''.xsession''' script directly in the home directory, rather than link it from '''~/.xinitrc'''. This is necessary if you create multiple custom Xsession scripts for multiple users, and you do not in that case link '''~/.xinitrc''' to '''.xsession'''.

You must also autostart the X Window system, which differs somewhat from scenario to scenario. For most setups, all that is necessary is to edit the '''.bashrc''' file.

<pre>
nano ~/.bashrc
</pre>

Add the following as shown.

<pre>
if [[ ! $DISPLAY && $XDG_VTNR -eq 1 ]]; then
exec startx
fi
</pre>

If you wish to remain logged in after quitting X, remove the '''exec''' from the above. Other configurations can be applied, but are irrelevant to autostarting Kodi.

[https://wiki.archlinux.org/index.php/Xinit#Autostart_X_at_login Xinit Autostart X at login]

If you are using LightDM and you just want to create a new login entry for user '''kodi''', you must create a new file.

<pre>
nano /usr/share/xsessions/custom.desktop
</pre>

And insert the following text.

<pre>
[Desktop Entry]
Name=Xsession
Exec=/etc/X11/Xsession
</pre>

This will create a new login option for the custom Xsession. Only this one entry is necessary for LightDM and X11 to find the '''~/.xsession''' script in each user's home directory.

You can use any window manager or desktop enviroment with a custom Xsession script as long as it is installed.

You do this by creating '''~/.xinitrc''' script that contains the command to start the WM or DE.

For instance, if you are using FluxBox.

<pre>
#!/usr/bin/env bash
exec fluxbox &
/usr/bin/kodi -fs
</pre>

The <code>-fs</code> option is full-screen.

To run Gnome in the background, but launch Kodi in the foreground.

<pre>
#!/usr/bin/env bash
exec gnome-session &
/usr/bin/kodi -fs
</pre>

Use the '''~/.xinitrc''' file to configure '''~/.xsession''' to create a custom login for any user, not just Kodi.

<pre>
sudo -H -u [username] bash -c "ln -s ~/.xinitrc ~/.xsession"
</pre>

You must reconfigure Xserver for any user that is not a privileged user to be able to start a custom Xsession.

<pre>
dpkg-reconfigure xserver-xorg-legacy
dpkg-reconfigure xserver-xorg
</pre>

When you reconfigure X11 with these commands, choose to allow non-root users (anybody) to start an Xsession. You should see your changes take effect after rebooting.

HOW-TO:Autostart Kodi for Linux

2018-04-29T14:18:43Z

W3tech: /* Configure Kodi to autostart */

<section begin="intro" /><big>Any or all or a combination of these methods can be used to configure a Debian-based X Window System to boot directly to Kodi. This should work on any Linux using the X Window System, but these instructions are particular to Debian derivatives, such as Ubuntu. A server edition is best for running only Kodi, but this page assumes booting into a desktop OS, not a server distro. However, the instructions here can be used for a server distro with even less configuration than for a desktop. Experiment inside VirtualBox before you apply any of these to your system and make a backup.</big><section end="intro" />

__TOC__

== Installing the X11 Window System ==

Even if you are using something like [https://github.com/graysky2/kodi-standalone-service Kodi Standalone Service], you still need use a WM or a DE that installs the '''x-window-manager''' software package.

To ensure you have this installed use the '''which''' command.

<pre>
which x-window-manager
</pre>

If there is no such package, you can use '''apt''' to search your Linux distributions repository.

<pre>
apt-cache search x-window-manager
</pre>

This will general a list of packages containing '''x-window-manager''', which cannot be installed alone. If you are not using a DE, you need to use a WM. And, you can also use a compositing WM like Compiz, for fast 3D effects.

[https://wiki.archlinux.org/index.php/Compiz Compiz - ArchWiki]

A note on using Kodi Standalone Service, this package runs Kodi as a '''systemd''' service and disables the login for user '''kodi''' and will not work when autologin is enabled. In fact, it will break the login process if you autologin user '''kodi''' and run Kodi Standalone Service at the same time. This package is installed automatically with the standard Kodi package when you install Kodi on Raspbian, but must be configured manually for all other Linux distributions. You can run the '''which''' command to find this package as well.

<pre>
which kodi-standalone
</pre>

Be advised, Kodi Standalone Service still launches the Kodi GUI and still requires a WM even though it is running as a '''systemd''' service. When you install a WM such as '''xfwm4''' (the WM for XFCE4), the CLI will tell you if it provides the '''x-window-manager''' package.

<pre>
Setting up xfwm4 (4.12.4-1) ...
update-alternatives: using /usr/bin/xfwm4 to provide /usr/bin/x-window-manager (x-window-manager) in auto mode
</pre>

If you do not see this message at the end of the installation, the WM you selected does not provide this software package and may not actually be a complete WM itself but only part of a package containing a WM.

For a great example on exactly how you would do this with '''xfwm4''', see this ArchWiki entry.

[https://wiki.archlinux.org/index.php/Xfwm XFWM - ArchWiki]

Most systems utilize the client version of the X11 software an Xsession requires.

For more X11 features and functionality, you may optionally upgrade to the server software packages for the X Window System.

<pre>apt install xauth xorg xinit xserver-xorg-core xserver-xorg xserver-common</pre>

The Ubuntu wiki is usually a good source of information.

[https://wiki.ubuntu.com/CustomXSession CustomXSession - Ubuntu Wiki]

Custom user sessions can be created with the X11 Window System to run scripts, autostart apps, and launch a WM or DE.

LightDM is used for autologin.

== Customize LightDM to autologin ==

You can utilize the ability to customize LightDM data manager by changing the builtin custom configuration file '''50-myconfig.conf''' using '''nano''' or another text editor. If you have no DE or WM you can install '''lightdm''', but should make sure to do a bit of research before you do. Most versions of Linux use LightDM, but many server versions do not. For Ubuntu Server with no DE, for example, installing '''lightdm''' is okay and necessary. Changing the behavior of LightDM is done using a custom '''50-myconfig.conf''' configuration file.

To see if you have '''lightdm''' use '''which'''.

<pre>
which lightdm
</pre>

If not, install it with '''apt'''.

<pre>
apt install lightdm
</pre>

Create a custom configuration file called '''50-myconfig.conf''' using '''nano''' or other CLI text editor.

<pre>
mkdir /etc/lightdm/lightdm.conf.d/
nano /etc/lightdm/lightdm.conf.d/50-myconfig.conf
</pre>

Inside this new file add the following text.

<pre>
[SeatDefaults]
autologin-user=kodi
</pre>

On Raspbian, you can configure LightDM differently for autologin to boot directly to Kodi.

<pre>
nano /etc/lightdm/lightdm.conf
</pre>

Uncomment the following line.

<pre>
#autologin-user=
</pre>

And add the user you want to autologin and autostart Kodi. The user is named '''kodi''' in this example.

<pre>
autologin-user=kodi
</pre>

You can alternately create /etc/lightdm/lightdm.conf.d/50-myconfig.conf, but should still ensure the settings in /etc/lightdm/lightdm.conf agree.

== Configure Kodi to autostart ==

Configure Kodi to autostart.

<pre>
mkdir -p ~/.config/autostart
ln -s /usr/bin/kodi ~/.config/autostart
</pre>

This method of autostart requires a desktop environment or DE. This is done a bit differently by each DE. Some helpful links can easily be found in today's Web search using any search engine.

[http://edoceo.com/gui/xfce-autostart-apps Autostart Apps in XFCE]

And this link shows how to autostart an app in LXDE on Raspbian.

[http://www.raspberry-projects.com/pi/pi-operating-systems/raspbian/auto-running-programs-gui Auto running programs LXDE - Raspberry Pi Projects]

The Raspberry Pi is a bit more of a tweak, but these are excellent links that will tell you how. The first link is the most helpful to making sure Kodi autostarts in Pi, and utilizes a '''crontab'''. There are many settings on the Pi that control boot, and the first link gives the best most trouble-free way to boot directly to Kodi.

[https://www.leowkahman.com/2016/03/05/lamp-stack-on-raspberry-pi-with-kodi-running-at-startup/ LAMP stack on Raspberry Pi with Kodi running at startup]

In the above link, the author describes using Crontab (short for "Cron table") to boot directly to Kodi.

<pre>
crontab -e
</pre>

Cron will ask you to choose a text editor from available options. I choose option 2 for '''nano'''.

In the new Crontab, enter the following text.

<pre>
@reboot kodi --standalone
</pre>

You could also consider using Crontab to run a script, much like described on this page in the section entitled "Run kodi in a window manager" if you scroll down the page.

[https://wiki.archlinux.org/index.php/Kodi Kodi - Run kodi in a window manager]

Instead your Crontab could look like this.

<pre>
@reboot startx
</pre>

And create an '''~/.xinitrc''' file.

<pre>
nano ~/.xinitrc
</pre>

The '''~/.xinitrc''' file should look like this.

<pre>
#!/bin/bash
kodi-standalone
sudo chvt 2
sleep 1
sudo chvt 1
</pre>

Make sure to make '''~/.xinitrc''' executable by running.

<pre>
chmod +x ~/.xinitrc
</pre>

To ensure no password is required by '''sudo''' for any user logging in when this script runs, you must edit /etc/sudoers or run the '''visudo''' command if it is installed to edit /etc/sudoers. You can install '''visudo''' from your Linux distributions default repository.

<pre>
apt install visudo
</pre>

For any non-root users, create an entry in this file like shown here.

<pre>
kodi ALL=NOPASSWD: /usr/bin/chvt
pi ALL=NOPASSWD: /usr/bin/chvt
</pre>

The above example is for users '''pi''' and '''kodi'''.

If you decide not use a Cron table, you can always remove it again.

<pre>
crontab -r
</pre>

This is a quick reference for Crontab.

[http://www.adminschoice.com/crontab-quick-reference Crontab Quick Reference]

These linked pages facilitate more tweaks and settings relevant to other uses of the X Window System on Pi.

[http://ozzmaker.com/enable-x-windows-on-piscreen/ Enable X Window System on PiScreen]

Other things to tweak on Raspbian.

[https://yingtongli.me/blog/2016/12/21/splash.html Raspbian splash screen guide - Clean up the boot process]

[https://scribles.net/lightning-bolt-under-voltage-warning-on-raspberry-pi/ Under voltage warning and disabling splash screen on Raspbian]

[https://raspberrypi.stackexchange.com/questions/59310/remove-boot-messages-all-text-in-jessie Remove boot messages all text in Raspbian - Raspberry Pi Stack Exchange]

And, if you would rather, it is easier to follow the process provided by this link to modify the Raspbian image before installing it onto the microSD card.

[https://wiki.debian.org/RaspberryPi/qemu-user-static Modifying Raspbian with qemu-user-static]

The above link describes removing the DE from a Raspbian image, though Raspbian Lite is a much better starting point for using Qemu for this purpose.

You can also use the X11 Window System to autostart Kodi by placing a startup script in the /etc/X11/Xsession.d/ directory.

[https://debian-administration.org/article/50/Running_applications_automatically_when_X_starts Running applications automatically when X starts]

<pre>
nano /etc/X11/Xsession.d/startup-local
</pre>

Insert this text into the new file. Use CTRL + O + Enter + X to save the file.

<pre>
#!/bin/sh
/usr/bin/kodi
</pre>

If you have a WM, such as Blackbox you can add it here as well.

<pre>
#!/bin/sh
blackbox &
/usr/bin/kodi
</pre>

Set permissions to make it executable. Use the ampersand to run an application in the background, such as a WM you only need to for the purpose of launching Kodi but not if you don't want to use the WM itself. Kodi will not launch without a DE or WM, but placing the ampersand "&" at the end of the command makes it run in the background where it can do its job out of sight. Also, make sure to start a WM or DE before running an application in the foreground. This is not necessary for apps running in the background.

<pre>
chmod 755 /etc/X11/Xsession.d/startup-local
</pre>

If Kodi is not installed at the standard path, find it using the '''which''' command.

<pre>
which kodi
</pre>

This feature is available on X Window System operating systems most Linux distributions use the X Window System.

== Create custom Xsession script ==

To create a custom Xsession script with a text editor we start with an '''xinitrc''' script. For more detail on how to create and use '''xinit''', there is a great guide available here.

[https://en.wikibooks.org/wiki/Guide_to_X11/Starting_Sessions Guide to X11 - Starting Sessions - WikiBooks]

<pre>
nano ~/.xinitrc
</pre>

To run Kodi full-screen make sure the text reads:

<pre>
#!/usr/bin/env bash
exec gnome-session
/usr/bin/kodi -fs
</pre>

Replace the '''gnome-session''' with the DE or WM command you are using. See the last section for examples.

To make '''~/.xinitrc''' executable use.

<pre>
chmod +x ~/.xinitrc
</pre>

Use '''sudo''' and the '''~/.xinitrc''' file to configure '''~/.xsession'''.

<pre>
sudo -H -u kodi bash -c "ln -s ~/.xinitrc /home/kodi/.xsession"
</pre>

Make sure the path goes to user's home directory. In this example, the user is '''kodi'''.

You need to use '''sudo''' to run this command. If you do not have '''sudo''', install it.

<pre>
apt install sudo
</pre>

If you create a symbolic link and want to remove it, simply remove the existing '''.xsession''' file you created.

<pre>
rm /home/kodi/.xsession
</pre>

On some systems using a DE such as Gnome, not all systems using Gnome, it may be necessary for '''.xsession''' to be '''.xsessionrc'''. Though this is more likely the case for organization network computers than a personal one, where configurations may vary on a diversity of machines. Most of the time, it will be '''.xsession''' rather than '''.xsessionrc''' that you want to create.

You can also create the '''.xsession''' script directly in the home directory, rather than link it from '''~/.xinitrc'''. This is necessary if you create multiple custom Xsession scripts for multiple users, and you do not in that case link '''~/.xinitrc''' to '''.xsession'''.

You must also autostart the X Window system, which differs somewhat from scenario to scenario. For most setups, all that is necessary is to edit the '''.bashrc''' file.

<pre>
nano ~/.bashrc
</pre>

Add the following as shown.

<pre>
if [[ ! $DISPLAY && $XDG_VTNR -eq 1 ]]; then
exec startx
fi
</pre>

If you wish to remain logged in after quitting X, remove the '''exec''' from the above. Other configurations can be applied, but are irrelevant to autostarting Kodi.

[https://wiki.archlinux.org/index.php/Xinit#Autostart_X_at_login Xinit Autostart X at login]

If you are using LightDM and you just want to create a new login entry for user '''kodi''', you must create a new file.

<pre>
nano /usr/share/xsessions/custom.desktop
</pre>

And insert the following text.

<pre>
[Desktop Entry]
Name=Xsession
Exec=/etc/X11/Xsession
</pre>

This will create a new login option for the custom Xsession. Only this one entry is necessary for LightDM and X11 to find the '''~/.xsession''' script in each user's home directory.

You can use any window manager or desktop enviroment with a custom Xsession script as long as it is installed.

You do this by creating '''~/.xinitrc''' script that contains the command to start the WM or DE.

For instance, if you are using FluxBox.

<pre>
#!/usr/bin/env bash
exec fluxbox &
/usr/bin/kodi -fs
</pre>

The <code>-fs</code> option is full-screen.

To run Gnome in the background, but launch Kodi in the foreground.

<pre>
#!/usr/bin/env bash
exec gnome-session &
/usr/bin/kodi -fs
</pre>

Use the '''~/.xinitrc''' file to configure '''~/.xsession''' to create a custom login for any user, not just Kodi.

<pre>
sudo -H -u [username] bash -c "ln -s ~/.xinitrc ~/.xsession"
</pre>

You must reconfigure Xserver for any user that is not a privileged user to be able to start a custom Xsession.

<pre>
dpkg-reconfigure xserver-xorg-legacy
dpkg-reconfigure xserver-xorg
</pre>

When you reconfigure X11 with these commands, choose to allow non-root users (anybody) to start an Xsession. You should see your changes take effect after rebooting.

HOW-TO:Autostart Kodi for Linux

2018-04-29T14:17:29Z

W3tech: /* Configure Kodi to autostart */

<section begin="intro" /><big>Any or all or a combination of these methods can be used to configure a Debian-based X Window System to boot directly to Kodi. This should work on any Linux using the X Window System, but these instructions are particular to Debian derivatives, such as Ubuntu. A server edition is best for running only Kodi, but this page assumes booting into a desktop OS, not a server distro. However, the instructions here can be used for a server distro with even less configuration than for a desktop. Experiment inside VirtualBox before you apply any of these to your system and make a backup.</big><section end="intro" />

__TOC__

== Installing the X11 Window System ==

Even if you are using something like [https://github.com/graysky2/kodi-standalone-service Kodi Standalone Service], you still need use a WM or a DE that installs the '''x-window-manager''' software package.

To ensure you have this installed use the '''which''' command.

<pre>
which x-window-manager
</pre>

If there is no such package, you can use '''apt''' to search your Linux distributions repository.

<pre>
apt-cache search x-window-manager
</pre>

This will general a list of packages containing '''x-window-manager''', which cannot be installed alone. If you are not using a DE, you need to use a WM. And, you can also use a compositing WM like Compiz, for fast 3D effects.

[https://wiki.archlinux.org/index.php/Compiz Compiz - ArchWiki]

A note on using Kodi Standalone Service, this package runs Kodi as a '''systemd''' service and disables the login for user '''kodi''' and will not work when autologin is enabled. In fact, it will break the login process if you autologin user '''kodi''' and run Kodi Standalone Service at the same time. This package is installed automatically with the standard Kodi package when you install Kodi on Raspbian, but must be configured manually for all other Linux distributions. You can run the '''which''' command to find this package as well.

<pre>
which kodi-standalone
</pre>

Be advised, Kodi Standalone Service still launches the Kodi GUI and still requires a WM even though it is running as a '''systemd''' service. When you install a WM such as '''xfwm4''' (the WM for XFCE4), the CLI will tell you if it provides the '''x-window-manager''' package.

<pre>
Setting up xfwm4 (4.12.4-1) ...
update-alternatives: using /usr/bin/xfwm4 to provide /usr/bin/x-window-manager (x-window-manager) in auto mode
</pre>

If you do not see this message at the end of the installation, the WM you selected does not provide this software package and may not actually be a complete WM itself but only part of a package containing a WM.

For a great example on exactly how you would do this with '''xfwm4''', see this ArchWiki entry.

[https://wiki.archlinux.org/index.php/Xfwm XFWM - ArchWiki]

Most systems utilize the client version of the X11 software an Xsession requires.

For more X11 features and functionality, you may optionally upgrade to the server software packages for the X Window System.

<pre>apt install xauth xorg xinit xserver-xorg-core xserver-xorg xserver-common</pre>

The Ubuntu wiki is usually a good source of information.

[https://wiki.ubuntu.com/CustomXSession CustomXSession - Ubuntu Wiki]

Custom user sessions can be created with the X11 Window System to run scripts, autostart apps, and launch a WM or DE.

LightDM is used for autologin.

== Customize LightDM to autologin ==

You can utilize the ability to customize LightDM data manager by changing the builtin custom configuration file '''50-myconfig.conf''' using '''nano''' or another text editor. If you have no DE or WM you can install '''lightdm''', but should make sure to do a bit of research before you do. Most versions of Linux use LightDM, but many server versions do not. For Ubuntu Server with no DE, for example, installing '''lightdm''' is okay and necessary. Changing the behavior of LightDM is done using a custom '''50-myconfig.conf''' configuration file.

To see if you have '''lightdm''' use '''which'''.

<pre>
which lightdm
</pre>

If not, install it with '''apt'''.

<pre>
apt install lightdm
</pre>

Create a custom configuration file called '''50-myconfig.conf''' using '''nano''' or other CLI text editor.

<pre>
mkdir /etc/lightdm/lightdm.conf.d/
nano /etc/lightdm/lightdm.conf.d/50-myconfig.conf
</pre>

Inside this new file add the following text.

<pre>
[SeatDefaults]
autologin-user=kodi
</pre>

On Raspbian, you can configure LightDM differently for autologin to boot directly to Kodi.

<pre>
nano /etc/lightdm/lightdm.conf
</pre>

Uncomment the following line.

<pre>
#autologin-user=
</pre>

And add the user you want to autologin and autostart Kodi. The user is named '''kodi''' in this example.

<pre>
autologin-user=kodi
</pre>

You can alternately create /etc/lightdm/lightdm.conf.d/50-myconfig.conf, but should still ensure the settings in /etc/lightdm/lightdm.conf agree.

== Configure Kodi to autostart ==

Configure Kodi to autostart.

<pre>
mkdir -p ~/.config/autostart
ln -s /usr/bin/kodi ~/.config/autostart
</pre>

This method of autostart requires a desktop environment or DE. This is done a bit differently by each DE. Some helpful links can easily be found in today's Web search using any search engine.

[http://edoceo.com/gui/xfce-autostart-apps Autostart Apps in XFCE]

And this link shows how to autostart an app in LXDE on Raspbian.

[http://www.raspberry-projects.com/pi/pi-operating-systems/raspbian/auto-running-programs-gui Auto running programs LXDE - Raspberry Pi Projects]

The Raspberry Pi is a bit more of a tweak, but these are excellent links that will tell you how. The first link is the most helpful to making sure Kodi autostarts in Pi, and utilizes a '''crontab'''. There are many settings on the Pi that control boot, and the first link gives the best most trouble-free way to boot directly to Kodi.

[https://www.leowkahman.com/2016/03/05/lamp-stack-on-raspberry-pi-with-kodi-running-at-startup/ LAMP stack on Raspberry Pi with Kodi running at startup]

In the above link, the author describes using Crontab (short for "Cron table") to boot directly to Kodi.

<pre>
crontab -e
</pre>

Cron will ask you to choose a text editor from available options. I choose option 2 for '''nano'''.

In the new Crontab, enter the following text.

<pre>
@reboot kodi --standalone
</pre>

You could also consider using Crontab to run a script, much like described on this page in the section entitled "Run kodi in a window manager" if you scroll down the page.

[https://wiki.archlinux.org/index.php/Kodi Kodi - Run kodi in a window manager]

Instead your Crontab could look like this.

<pre>
@reboot startx
</pre>

And create an '''~/.xinitrc''' file.

<pre>
nano ~/.xinitrc
</pre>

The '''~/.xinitrc''' file should look like this.

<pre>
#!/bin/bash
kodi-standalone
sudo chvt 2
sleep 1
sudo chvt 1
</pre>

Make sure to make '''~/.xinitrc''' executable by running.

<pre>
chmod +x ~/.xinitrc
</pre>

To ensure no password is required by '''sudo''' for any user logging in when this script runs, you must edit /etc/sudoers or run the '''visudo''' command if it is installed to edit /etc/sudoers. You can install '''visudo''' from your Linux distributions default repository.

<pre>
apt install visudo
</pre>

For any non-root users, create an entry in this file like shown here.

<pre>
kodi ALL=NOPASSWD: /usr/bin/chvt
pi ALL=NOPASSWD: /usr/bin/chvt
</pre>

The above example is for users '''pi''' and '''kodi'''.

If you decide not use a Cron table, you can always remove it again.

<pre>
crontab -r
</pre>

This is a quick reference for Crontab.

[http://www.adminschoice.com/crontab-quick-reference Crontab Quick Reference]

These linked pages facilitate more tweaks and settings relevant to other uses of the X Window System on Pi.

[http://ozzmaker.com/enable-x-windows-on-piscreen/ Enable X Window System on PiScreen]

Other things to tweak on Raspbian.

[https://yingtongli.me/blog/2016/12/21/splash.html Raspbian splash screen guide - Clean up the boot process]

[https://scribles.net/lightning-bolt-under-voltage-warning-on-raspberry-pi/ Under voltage warning and disabling splash screen on Raspbian]

[https://raspberrypi.stackexchange.com/questions/59310/remove-boot-messages-all-text-in-jessie Remove boot messages all text in Raspbian - Raspberry Pi Stack Exchange]

And, if you would rather, it is easier to follow the process provided by this link to modify the Raspbian image before installing it onto the microSD card.

[https://wiki.debian.org/RaspberryPi/qemu-user-static Modifying Raspbian with qemu-user-static]

The above link describes removing the DE from a Raspbian image, though Raspbian Lite is a much better starting point for using Qemu for this purpose.

You can also use the X11 Window System to autostart Kodi by placing a statup script in the /etc/X11/Xsession.d/ directory.

[https://debian-administration.org/article/50/Running_applications_automatically_when_X_starts Running applications automatically when X starts]

<pre>
nano /etc/X11/Xsession.d/startup-local
</pre>

Insert this text into the new file. Use CTRL + O + Enter + X to save the file.

<pre>
#!/bin/sh
/usr/bin/kodi
</pre>

If you have a WM, such as Blackbox you can add it here as well.

<pre>
#!/bin/sh
blackbox &
/usr/bin/kodi
</pre>

Set permissions to make it executable. Use the ampersand to run an application in the background, such as a WM you only need to for the purpose of launching Kodi but not if you don't want to use the WM itself. Kodi will not launch without a DE or WM, but placing the ampersand "&" at the end of the command makes it run in the background where it can do its job out of sight. Also, make sure to start a WM or DE before running an application in the foreground. This is not necessary for apps running in the background.

<pre>
chmod 755 /etc/X11/Xsession.d/startup-local
</pre>

If Kodi is not installed at the standard path, find it using the '''which''' command.

<pre>
which kodi
</pre>

This feature is available on X Window System operating systems most Linux distributions use the X Window System.

== Create custom Xsession script ==

To create a custom Xsession script with a text editor we start with an '''xinitrc''' script. For more detail on how to create and use '''xinit''', there is a great guide available here.

[https://en.wikibooks.org/wiki/Guide_to_X11/Starting_Sessions Guide to X11 - Starting Sessions - WikiBooks]

<pre>
nano ~/.xinitrc
</pre>

To run Kodi full-screen make sure the text reads:

<pre>
#!/usr/bin/env bash
exec gnome-session
/usr/bin/kodi -fs
</pre>

Replace the '''gnome-session''' with the DE or WM command you are using. See the last section for examples.

To make '''~/.xinitrc''' executable use.

<pre>
chmod +x ~/.xinitrc
</pre>

Use '''sudo''' and the '''~/.xinitrc''' file to configure '''~/.xsession'''.

<pre>
sudo -H -u kodi bash -c "ln -s ~/.xinitrc /home/kodi/.xsession"
</pre>

Make sure the path goes to user's home directory. In this example, the user is '''kodi'''.

You need to use '''sudo''' to run this command. If you do not have '''sudo''', install it.

<pre>
apt install sudo
</pre>

If you create a symbolic link and want to remove it, simply remove the existing '''.xsession''' file you created.

<pre>
rm /home/kodi/.xsession
</pre>

On some systems using a DE such as Gnome, not all systems using Gnome, it may be necessary for '''.xsession''' to be '''.xsessionrc'''. Though this is more likely the case for organization network computers than a personal one, where configurations may vary on a diversity of machines. Most of the time, it will be '''.xsession''' rather than '''.xsessionrc''' that you want to create.

You can also create the '''.xsession''' script directly in the home directory, rather than link it from '''~/.xinitrc'''. This is necessary if you create multiple custom Xsession scripts for multiple users, and you do not in that case link '''~/.xinitrc''' to '''.xsession'''.

You must also autostart the X Window system, which differs somewhat from scenario to scenario. For most setups, all that is necessary is to edit the '''.bashrc''' file.

<pre>
nano ~/.bashrc
</pre>

Add the following as shown.

<pre>
if [[ ! $DISPLAY && $XDG_VTNR -eq 1 ]]; then
exec startx
fi
</pre>

If you wish to remain logged in after quitting X, remove the '''exec''' from the above. Other configurations can be applied, but are irrelevant to autostarting Kodi.

[https://wiki.archlinux.org/index.php/Xinit#Autostart_X_at_login Xinit Autostart X at login]

If you are using LightDM and you just want to create a new login entry for user '''kodi''', you must create a new file.

<pre>
nano /usr/share/xsessions/custom.desktop
</pre>

And insert the following text.

<pre>
[Desktop Entry]
Name=Xsession
Exec=/etc/X11/Xsession
</pre>

This will create a new login option for the custom Xsession. Only this one entry is necessary for LightDM and X11 to find the '''~/.xsession''' script in each user's home directory.

You can use any window manager or desktop enviroment with a custom Xsession script as long as it is installed.

You do this by creating '''~/.xinitrc''' script that contains the command to start the WM or DE.

For instance, if you are using FluxBox.

<pre>
#!/usr/bin/env bash
exec fluxbox &
/usr/bin/kodi -fs
</pre>

The <code>-fs</code> option is full-screen.

To run Gnome in the background, but launch Kodi in the foreground.

<pre>
#!/usr/bin/env bash
exec gnome-session &
/usr/bin/kodi -fs
</pre>

Use the '''~/.xinitrc''' file to configure '''~/.xsession''' to create a custom login for any user, not just Kodi.

<pre>
sudo -H -u [username] bash -c "ln -s ~/.xinitrc ~/.xsession"
</pre>

You must reconfigure Xserver for any user that is not a privileged user to be able to start a custom Xsession.

<pre>
dpkg-reconfigure xserver-xorg-legacy
dpkg-reconfigure xserver-xorg
</pre>

When you reconfigure X11 with these commands, choose to allow non-root users (anybody) to start an Xsession. You should see your changes take effect after rebooting.

HOW-TO:Autostart Kodi for Linux

2018-04-29T13:52:00Z

W3tech: /* Installing the X11 Window System */

<section begin="intro" /><big>Any or all or a combination of these methods can be used to configure a Debian-based X Window System to boot directly to Kodi. This should work on any Linux using the X Window System, but these instructions are particular to Debian derivatives, such as Ubuntu. A server edition is best for running only Kodi, but this page assumes booting into a desktop OS, not a server distro. However, the instructions here can be used for a server distro with even less configuration than for a desktop. Experiment inside VirtualBox before you apply any of these to your system and make a backup.</big><section end="intro" />

__TOC__

== Installing the X11 Window System ==

Even if you are using something like [https://github.com/graysky2/kodi-standalone-service Kodi Standalone Service], you still need use a WM or a DE that installs the '''x-window-manager''' software package.

To ensure you have this installed use the '''which''' command.

<pre>
which x-window-manager
</pre>

If there is no such package, you can use '''apt''' to search your Linux distributions repository.

<pre>
apt-cache search x-window-manager
</pre>

This will general a list of packages containing '''x-window-manager''', which cannot be installed alone. If you are not using a DE, you need to use a WM. And, you can also use a compositing WM like Compiz, for fast 3D effects.

[https://wiki.archlinux.org/index.php/Compiz Compiz - ArchWiki]

A note on using Kodi Standalone Service, this package runs Kodi as a '''systemd''' service and disables the login for user '''kodi''' and will not work when autologin is enabled. In fact, it will break the login process if you autologin user '''kodi''' and run Kodi Standalone Service at the same time. This package is installed automatically with the standard Kodi package when you install Kodi on Raspbian, but must be configured manually for all other Linux distributions. You can run the '''which''' command to find this package as well.

<pre>
which kodi-standalone
</pre>

Be advised, Kodi Standalone Service still launches the Kodi GUI and still requires a WM even though it is running as a '''systemd''' service. When you install a WM such as '''xfwm4''' (the WM for XFCE4), the CLI will tell you if it provides the '''x-window-manager''' package.

<pre>
Setting up xfwm4 (4.12.4-1) ...
update-alternatives: using /usr/bin/xfwm4 to provide /usr/bin/x-window-manager (x-window-manager) in auto mode
</pre>

If you do not see this message at the end of the installation, the WM you selected does not provide this software package and may not actually be a complete WM itself but only part of a package containing a WM.

For a great example on exactly how you would do this with '''xfwm4''', see this ArchWiki entry.

[https://wiki.archlinux.org/index.php/Xfwm XFWM - ArchWiki]

Most systems utilize the client version of the X11 software an Xsession requires.

For more X11 features and functionality, you may optionally upgrade to the server software packages for the X Window System.

<pre>apt install xauth xorg xinit xserver-xorg-core xserver-xorg xserver-common</pre>

The Ubuntu wiki is usually a good source of information.

[https://wiki.ubuntu.com/CustomXSession CustomXSession - Ubuntu Wiki]

Custom user sessions can be created with the X11 Window System to run scripts, autostart apps, and launch a WM or DE.

LightDM is used for autologin.

== Customize LightDM to autologin ==

You can utilize the ability to customize LightDM data manager by changing the builtin custom configuration file '''50-myconfig.conf''' using '''nano''' or another text editor. If you have no DE or WM you can install '''lightdm''', but should make sure to do a bit of research before you do. Most versions of Linux use LightDM, but many server versions do not. For Ubuntu Server with no DE, for example, installing '''lightdm''' is okay and necessary. Changing the behavior of LightDM is done using a custom '''50-myconfig.conf''' configuration file.

To see if you have '''lightdm''' use '''which'''.

<pre>
which lightdm
</pre>

If not, install it with '''apt'''.

<pre>
apt install lightdm
</pre>

Create a custom configuration file called '''50-myconfig.conf''' using '''nano''' or other CLI text editor.

<pre>
mkdir /etc/lightdm/lightdm.conf.d/
nano /etc/lightdm/lightdm.conf.d/50-myconfig.conf
</pre>

Inside this new file add the following text.

<pre>
[SeatDefaults]
autologin-user=kodi
</pre>

On Raspbian, you can configure LightDM differently for autologin to boot directly to Kodi.

<pre>
nano /etc/lightdm/lightdm.conf
</pre>

Uncomment the following line.

<pre>
#autologin-user=
</pre>

And add the user you want to autologin and autostart Kodi. The user is named '''kodi''' in this example.

<pre>
autologin-user=kodi
</pre>

You can alternately create /etc/lightdm/lightdm.conf.d/50-myconfig.conf, but should still ensure the settings in /etc/lightdm/lightdm.conf agree.

== Configure Kodi to autostart ==

Configure Kodi to autostart.

<pre>
mkdir -p ~/.config/autostart
ln -s /usr/bin/kodi ~/.config/autostart
</pre>

This method of autostart requires a desktop environment or DE. This is done a bit differently by each DE. Some helpful links can easily be found in today's Web search using any search engine.

[http://edoceo.com/gui/xfce-autostart-apps Autostart Apps in XFCE]

And this link shows how to autostart an app in LXDE on Raspbian.

[http://www.raspberry-projects.com/pi/pi-operating-systems/raspbian/auto-running-programs-gui Auto running programs LXDE - Raspberry Pi Projects]

The Raspberry Pi is a bit more of a tweak, but these are excellent links that will tell you how. The first link is the most helpful to making sure Kodi autostarts in Pi, and utilizes a '''crontab'''. There are many settings on the Pi that control boot, and the first link gives the best most trouble-free way to boot directly to Kodi.

[https://www.leowkahman.com/2016/03/05/lamp-stack-on-raspberry-pi-with-kodi-running-at-startup/ LAMP stack on Raspberry Pi with Kodi running at startup]

In the above link, the author describes using Crontab (short for "Cron table") to boot directly to Kodi.

<pre>
crontab -e
</pre>

Cron will ask you to choose a text editor from available options. I choose option 2 for '''nano'''.

In the new Crontab, enter the following text.

<pre>
@reboot kodi --standalone
</pre>

You could also consider using Crontab to run a script, much like described on this page in the section entitled "Run kodi in a window manager" if you scroll down the page.

[https://wiki.archlinux.org/index.php/Kodi Kodi - Run kodi in a window manager]

Instead your Crontab could look like this.

<pre>
@reboot startx
</pre>

And create an '''~/.xinitrc''' file.

<pre>
nano ~/.xinitrc
</pre>

The '''~/.xinitrc''' file should look like this.

<pre>
#!/bin/bash
kodi-standalone
sudo chvt 2
sleep 1
sudo chvt 1
</pre>

Make sure to make '''~/.xinitrc''' executable by running.

<pre>
chmod +x ~/.xinitrc
</pre>

To ensure no password is required by '''sudo''' for any user logging in when this script runs, you must edit /etc/sudoers or run the '''visudo''' command if it is installed to edit /etc/sudoers. You can install '''visudo''' from your Linux distributions default repository.

<pre>
apt install visudo
</pre>

For any non-root users, create an entry in this file like shown here.

<pre>
kodi ALL=NOPASSWD: /usr/bin/chvt
pi ALL=NOPASSWD: /usr/bin/chvt
</pre>

The above example is for users '''pi''' and '''kodi'''.

If you decide not use a Cron table, you can always remove it again.

<pre>
crontab -r
</pre>

This is a quick reference for Crontab.

[http://www.adminschoice.com/crontab-quick-reference Crontab Quick Reference]

These linked pages facilitate more tweaks and settings relevant to other uses of the X Window System on Pi.

[http://ozzmaker.com/enable-x-windows-on-piscreen/ Enable X Window System on PiScreen]

Other things to tweak on Raspbian.

[https://scribles.net/lightning-bolt-under-voltage-warning-on-raspberry-pi/ Under voltage warning and disabling splash screen on Raspbian]

[https://raspberrypi.stackexchange.com/questions/59310/remove-boot-messages-all-text-in-jessie Remove boot messages all text in Raspbian - Raspberry Pi Stack Exchange]

And, if you would rather, it is easier to follow the process provided by this link to modify the Raspbian image before installing it onto the microSD card.

[https://wiki.debian.org/RaspberryPi/qemu-user-static Modifying Raspbian with qemu-user-static]

The above link describes removing the DE from a Raspbian image, though Raspbian Lite is a much better starting point for using Qemu for this purpose.

You can also use the X11 Window System to autostart Kodi by placing a statup script in the /etc/X11/Xsession.d/ directory.

[https://debian-administration.org/article/50/Running_applications_automatically_when_X_starts Running applications automatically when X starts]

<pre>
nano /etc/X11/Xsession.d/startup-local
</pre>

Insert this text into the new file. Use CTRL + O + Enter + X to save the file.

<pre>
#!/bin/sh
/usr/bin/kodi
</pre>

If you have a WM, such as Blackbox you can add it here as well.

<pre>
#!/bin/sh
blackbox &
/usr/bin/kodi
</pre>

Set permissions to make it executable. Use the ampersand to run an application in the background, such as a WM you only need to for the purpose of launching Kodi but not if you don't want to use the WM itself. Kodi will not launch without a DE or WM, but placing the ampersand "&" at the end of the command makes it run in the background where it can do its job out of sight. Also, make sure to start a WM or DE before running an application in the foreground. This is not necessary for apps running in the background.

<pre>
chmod 755 /etc/X11/Xsession.d/startup-local
</pre>

If Kodi is not installed at the standard path, find it using the '''which''' command.

<pre>
which kodi
</pre>

This feature is available on X Window System operating systems most Linux distributions use the X Window System.

== Create custom Xsession script ==

To create a custom Xsession script with a text editor we start with an '''xinitrc''' script. For more detail on how to create and use '''xinit''', there is a great guide available here.

[https://en.wikibooks.org/wiki/Guide_to_X11/Starting_Sessions Guide to X11 - Starting Sessions - WikiBooks]

<pre>
nano ~/.xinitrc
</pre>

To run Kodi full-screen make sure the text reads:

<pre>
#!/usr/bin/env bash
exec gnome-session
/usr/bin/kodi -fs
</pre>

Replace the '''gnome-session''' with the DE or WM command you are using. See the last section for examples.

To make '''~/.xinitrc''' executable use.

<pre>
chmod +x ~/.xinitrc
</pre>

Use '''sudo''' and the '''~/.xinitrc''' file to configure '''~/.xsession'''.

<pre>
sudo -H -u kodi bash -c "ln -s ~/.xinitrc /home/kodi/.xsession"
</pre>

Make sure the path goes to user's home directory. In this example, the user is '''kodi'''.

You need to use '''sudo''' to run this command. If you do not have '''sudo''', install it.

<pre>
apt install sudo
</pre>

If you create a symbolic link and want to remove it, simply remove the existing '''.xsession''' file you created.

<pre>
rm /home/kodi/.xsession
</pre>

On some systems using a DE such as Gnome, not all systems using Gnome, it may be necessary for '''.xsession''' to be '''.xsessionrc'''. Though this is more likely the case for organization network computers than a personal one, where configurations may vary on a diversity of machines. Most of the time, it will be '''.xsession''' rather than '''.xsessionrc''' that you want to create.

You can also create the '''.xsession''' script directly in the home directory, rather than link it from '''~/.xinitrc'''. This is necessary if you create multiple custom Xsession scripts for multiple users, and you do not in that case link '''~/.xinitrc''' to '''.xsession'''.

You must also autostart the X Window system, which differs somewhat from scenario to scenario. For most setups, all that is necessary is to edit the '''.bashrc''' file.

<pre>
nano ~/.bashrc
</pre>

Add the following as shown.

<pre>
if [[ ! $DISPLAY && $XDG_VTNR -eq 1 ]]; then
exec startx
fi
</pre>

If you wish to remain logged in after quitting X, remove the '''exec''' from the above. Other configurations can be applied, but are irrelevant to autostarting Kodi.

[https://wiki.archlinux.org/index.php/Xinit#Autostart_X_at_login Xinit Autostart X at login]

If you are using LightDM and you just want to create a new login entry for user '''kodi''', you must create a new file.

<pre>
nano /usr/share/xsessions/custom.desktop
</pre>

And insert the following text.

<pre>
[Desktop Entry]
Name=Xsession
Exec=/etc/X11/Xsession
</pre>

This will create a new login option for the custom Xsession. Only this one entry is necessary for LightDM and X11 to find the '''~/.xsession''' script in each user's home directory.

You can use any window manager or desktop enviroment with a custom Xsession script as long as it is installed.

You do this by creating '''~/.xinitrc''' script that contains the command to start the WM or DE.

For instance, if you are using FluxBox.

<pre>
#!/usr/bin/env bash
exec fluxbox &
/usr/bin/kodi -fs
</pre>

The <code>-fs</code> option is full-screen.

To run Gnome in the background, but launch Kodi in the foreground.

<pre>
#!/usr/bin/env bash
exec gnome-session &
/usr/bin/kodi -fs
</pre>

Use the '''~/.xinitrc''' file to configure '''~/.xsession''' to create a custom login for any user, not just Kodi.

<pre>
sudo -H -u [username] bash -c "ln -s ~/.xinitrc ~/.xsession"
</pre>

You must reconfigure Xserver for any user that is not a privileged user to be able to start a custom Xsession.

<pre>
dpkg-reconfigure xserver-xorg-legacy
dpkg-reconfigure xserver-xorg
</pre>

When you reconfigure X11 with these commands, choose to allow non-root users (anybody) to start an Xsession. You should see your changes take effect after rebooting.

HOW-TO:Autostart Kodi for Linux

2018-04-29T13:45:07Z

W3tech: More cleaning

<section begin="intro" /><big>Any or all or a combination of these methods can be used to configure a Debian-based X Window System to boot directly to Kodi. This should work on any Linux using the X Window System, but these instructions are particular to Debian derivatives, such as Ubuntu. A server edition is best for running only Kodi, but this page assumes booting into a desktop OS, not a server distro. However, the instructions here can be used for a server distro with even less configuration than for a desktop. Experiment inside VirtualBox before you apply any of these to your system and make a backup.</big><section end="intro" />

__TOC__

== Installing the X11 Window System ==

Even if you are using something like [https://github.com/graysky2/kodi-standalone-service Kodi Standalone Service], you still need use a WM or a DE that installs the '''x-window-manager''' software package.

To ensure you have this installed use the '''which''' command.

<pre>
which x-window-manager
</pre>

If there is no such package, you can use '''apt''' to search your Linux distributions repository.

<pre>
apt-cache search x-window-manager
</pre>

This will general a list of packages containing '''x-window-manager''', which cannot be installed alone. If you are not using a DE, you need to use a WM. And, you can also use a compositing WM like Compiz, for fast 3D effects.

[https://wiki.archlinux.org/index.php/Compiz Compiz - ArchWiki]

A note on using Kodi Standalone Service, this package runs Kodi as a '''systemd''' service and disables the login for user '''kodi''' and will not work when autologin is enabled. In fact, it will break the login process if you autologin user '''kodi''' and run Kodi Standalone Service at the same time. This package is installed automatically with the standard Kodi package when you install Kodi on Raspbian, but must be configured manually for all other Linux distributions. You can run the '''which''' command to find this package as well.

<pre>
which kodi-standalone
</pre>

Be advised, Kodi Standalone Service still launches the Kodi GUI and still requires a WM even though it is running as a '''systemd''' service. When you install a WM such as '''xfwm4''' (the WM for XFCE4), the CLI will tell you if it provides the '''x-window-manager''' package.

<pre>
Setting up xfwm4 (4.12.4-1) ...
update-alternatives: using /usr/bin/xfwm4 to provide /usr/bin/x-window-manager (x-window-manager) in auto mode
</pre>

If you do not see this message at the end of the installation, the WM you selected does not provide this software package and may not actually be a complete WM itself but only part of a package containing a WM.

For a great example on exactly how you would do this with '''xfwm4''', see this ArchWiki entry.

[https://wiki.archlinux.org/index.php/Xfwm XFWM - ArchWiki]

Most systems utilize the client version of the X11 software an Xsession requires requires.

Upgrade to the server versions of the X Window System.

<pre>apt install xauth xorg xinit xserver-xorg-core xserver-xorg xserver-common</pre>

The Ubuntu wiki is usually a good source of information.

[https://wiki.ubuntu.com/CustomXSession CustomXSession - Ubuntu Wiki]

Custom user sessions can be created with the X11 Window System to run scripts, autostart apps, and launch a WM or DE.

LightDM is used for autologin.

== Customize LightDM to autologin ==

You can utilize the ability to customize LightDM data manager by changing the builtin custom configuration file '''50-myconfig.conf''' using '''nano''' or another text editor. If you have no DE or WM you can install '''lightdm''', but should make sure to do a bit of research before you do. Most versions of Linux use LightDM, but many server versions do not. For Ubuntu Server with no DE, for example, installing '''lightdm''' is okay and necessary. Changing the behavior of LightDM is done using a custom '''50-myconfig.conf''' configuration file.

To see if you have '''lightdm''' use '''which'''.

<pre>
which lightdm
</pre>

If not, install it with '''apt'''.

<pre>
apt install lightdm
</pre>

Create a custom configuration file called '''50-myconfig.conf''' using '''nano''' or other CLI text editor.

<pre>
mkdir /etc/lightdm/lightdm.conf.d/
nano /etc/lightdm/lightdm.conf.d/50-myconfig.conf
</pre>

Inside this new file add the following text.

<pre>
[SeatDefaults]
autologin-user=kodi
</pre>

On Raspbian, you can configure LightDM differently for autologin to boot directly to Kodi.

<pre>
nano /etc/lightdm/lightdm.conf
</pre>

Uncomment the following line.

<pre>
#autologin-user=
</pre>

And add the user you want to autologin and autostart Kodi. The user is named '''kodi''' in this example.

<pre>
autologin-user=kodi
</pre>

You can alternately create /etc/lightdm/lightdm.conf.d/50-myconfig.conf, but should still ensure the settings in /etc/lightdm/lightdm.conf agree.

== Configure Kodi to autostart ==

Configure Kodi to autostart.

<pre>
mkdir -p ~/.config/autostart
ln -s /usr/bin/kodi ~/.config/autostart
</pre>

This method of autostart requires a desktop environment or DE. This is done a bit differently by each DE. Some helpful links can easily be found in today's Web search using any search engine.

[http://edoceo.com/gui/xfce-autostart-apps Autostart Apps in XFCE]

And this link shows how to autostart an app in LXDE on Raspbian.

[http://www.raspberry-projects.com/pi/pi-operating-systems/raspbian/auto-running-programs-gui Auto running programs LXDE - Raspberry Pi Projects]

The Raspberry Pi is a bit more of a tweak, but these are excellent links that will tell you how. The first link is the most helpful to making sure Kodi autostarts in Pi, and utilizes a '''crontab'''. There are many settings on the Pi that control boot, and the first link gives the best most trouble-free way to boot directly to Kodi.

[https://www.leowkahman.com/2016/03/05/lamp-stack-on-raspberry-pi-with-kodi-running-at-startup/ LAMP stack on Raspberry Pi with Kodi running at startup]

In the above link, the author describes using Crontab (short for "Cron table") to boot directly to Kodi.

<pre>
crontab -e
</pre>

Cron will ask you to choose a text editor from available options. I choose option 2 for '''nano'''.

In the new Crontab, enter the following text.

<pre>
@reboot kodi --standalone
</pre>

You could also consider using Crontab to run a script, much like described on this page in the section entitled "Run kodi in a window manager" if you scroll down the page.

[https://wiki.archlinux.org/index.php/Kodi Kodi - Run kodi in a window manager]

Instead your Crontab could look like this.

<pre>
@reboot startx
</pre>

And create an '''~/.xinitrc''' file.

<pre>
nano ~/.xinitrc
</pre>

The '''~/.xinitrc''' file should look like this.

<pre>
#!/bin/bash
kodi-standalone
sudo chvt 2
sleep 1
sudo chvt 1
</pre>

Make sure to make '''~/.xinitrc''' executable by running.

<pre>
chmod +x ~/.xinitrc
</pre>

To ensure no password is required by '''sudo''' for any user logging in when this script runs, you must edit /etc/sudoers or run the '''visudo''' command if it is installed to edit /etc/sudoers. You can install '''visudo''' from your Linux distributions default repository.

<pre>
apt install visudo
</pre>

For any non-root users, create an entry in this file like shown here.

<pre>
kodi ALL=NOPASSWD: /usr/bin/chvt
pi ALL=NOPASSWD: /usr/bin/chvt
</pre>

The above example is for users '''pi''' and '''kodi'''.

If you decide not use a Cron table, you can always remove it again.

<pre>
crontab -r
</pre>

This is a quick reference for Crontab.

[http://www.adminschoice.com/crontab-quick-reference Crontab Quick Reference]

These linked pages facilitate more tweaks and settings relevant to other uses of the X Window System on Pi.

[http://ozzmaker.com/enable-x-windows-on-piscreen/ Enable X Window System on PiScreen]

Other things to tweak on Raspbian.

[https://scribles.net/lightning-bolt-under-voltage-warning-on-raspberry-pi/ Under voltage warning and disabling splash screen on Raspbian]

[https://raspberrypi.stackexchange.com/questions/59310/remove-boot-messages-all-text-in-jessie Remove boot messages all text in Raspbian - Raspberry Pi Stack Exchange]

And, if you would rather, it is easier to follow the process provided by this link to modify the Raspbian image before installing it onto the microSD card.

[https://wiki.debian.org/RaspberryPi/qemu-user-static Modifying Raspbian with qemu-user-static]

The above link describes removing the DE from a Raspbian image, though Raspbian Lite is a much better starting point for using Qemu for this purpose.

You can also use the X11 Window System to autostart Kodi by placing a statup script in the /etc/X11/Xsession.d/ directory.

[https://debian-administration.org/article/50/Running_applications_automatically_when_X_starts Running applications automatically when X starts]

<pre>
nano /etc/X11/Xsession.d/startup-local
</pre>

Insert this text into the new file. Use CTRL + O + Enter + X to save the file.

<pre>
#!/bin/sh
/usr/bin/kodi
</pre>

If you have a WM, such as Blackbox you can add it here as well.

<pre>
#!/bin/sh
blackbox &
/usr/bin/kodi
</pre>

Set permissions to make it executable. Use the ampersand to run an application in the background, such as a WM you only need to for the purpose of launching Kodi but not if you don't want to use the WM itself. Kodi will not launch without a DE or WM, but placing the ampersand "&" at the end of the command makes it run in the background where it can do its job out of sight. Also, make sure to start a WM or DE before running an application in the foreground. This is not necessary for apps running in the background.

<pre>
chmod 755 /etc/X11/Xsession.d/startup-local
</pre>

If Kodi is not installed at the standard path, find it using the '''which''' command.

<pre>
which kodi
</pre>

This feature is available on X Window System operating systems most Linux distributions use the X Window System.

== Create custom Xsession script ==

To create a custom Xsession script with a text editor we start with an '''xinitrc''' script. For more detail on how to create and use '''xinit''', there is a great guide available here.

[https://en.wikibooks.org/wiki/Guide_to_X11/Starting_Sessions Guide to X11 - Starting Sessions - WikiBooks]

<pre>
nano ~/.xinitrc
</pre>

To run Kodi full-screen make sure the text reads:

<pre>
#!/usr/bin/env bash
exec gnome-session
/usr/bin/kodi -fs
</pre>

Replace the '''gnome-session''' with the DE or WM command you are using. See the last section for examples.

To make '''~/.xinitrc''' executable use.

<pre>
chmod +x ~/.xinitrc
</pre>

Use '''sudo''' and the '''~/.xinitrc''' file to configure '''~/.xsession'''.

<pre>
sudo -H -u kodi bash -c "ln -s ~/.xinitrc /home/kodi/.xsession"
</pre>

Make sure the path goes to user's home directory. In this example, the user is '''kodi'''.

You need to use '''sudo''' to run this command. If you do not have '''sudo''', install it.

<pre>
apt install sudo
</pre>

If you create a symbolic link and want to remove it, simply remove the existing '''.xsession''' file you created.

<pre>
rm /home/kodi/.xsession
</pre>

On some systems using a DE such as Gnome, not all systems using Gnome, it may be necessary for '''.xsession''' to be '''.xsessionrc'''. Though this is more likely the case for organization network computers than a personal one, where configurations may vary on a diversity of machines. Most of the time, it will be '''.xsession''' rather than '''.xsessionrc''' that you want to create.

You can also create the '''.xsession''' script directly in the home directory, rather than link it from '''~/.xinitrc'''. This is necessary if you create multiple custom Xsession scripts for multiple users, and you do not in that case link '''~/.xinitrc''' to '''.xsession'''.

You must also autostart the X Window system, which differs somewhat from scenario to scenario. For most setups, all that is necessary is to edit the '''.bashrc''' file.

<pre>
nano ~/.bashrc
</pre>

Add the following as shown.

<pre>
if [[ ! $DISPLAY && $XDG_VTNR -eq 1 ]]; then
exec startx
fi
</pre>

If you wish to remain logged in after quitting X, remove the '''exec''' from the above. Other configurations can be applied, but are irrelevant to autostarting Kodi.

[https://wiki.archlinux.org/index.php/Xinit#Autostart_X_at_login Xinit Autostart X at login]

If you are using LightDM and you just want to create a new login entry for user '''kodi''', you must create a new file.

<pre>
nano /usr/share/xsessions/custom.desktop
</pre>

And insert the following text.

<pre>
[Desktop Entry]
Name=Xsession
Exec=/etc/X11/Xsession
</pre>

This will create a new login option for the custom Xsession. Only this one entry is necessary for LightDM and X11 to find the '''~/.xsession''' script in each user's home directory.

You can use any window manager or desktop enviroment with a custom Xsession script as long as it is installed.

You do this by creating '''~/.xinitrc''' script that contains the command to start the WM or DE.

For instance, if you are using FluxBox.

<pre>
#!/usr/bin/env bash
exec fluxbox &
/usr/bin/kodi -fs
</pre>

The <code>-fs</code> option is full-screen.

To run Gnome in the background, but launch Kodi in the foreground.

<pre>
#!/usr/bin/env bash
exec gnome-session &
/usr/bin/kodi -fs
</pre>

Use the '''~/.xinitrc''' file to configure '''~/.xsession''' to create a custom login for any user, not just Kodi.

<pre>
sudo -H -u [username] bash -c "ln -s ~/.xinitrc ~/.xsession"
</pre>

You must reconfigure Xserver for any user that is not a privileged user to be able to start a custom Xsession.

<pre>
dpkg-reconfigure xserver-xorg-legacy
dpkg-reconfigure xserver-xorg
</pre>

When you reconfigure X11 with these commands, choose to allow non-root users (anybody) to start an Xsession. You should see your changes take effect after rebooting.

HOW-TO:Autostart Kodi for Linux

2018-04-29T13:10:04Z

W3tech: /* Configure Kodi to autostart */

<section begin="intro" /><big>Any or all or a combination of these methods can be used to configure a Debian-based X Window System to boot directly to Kodi. This should work on any Linux using the X Window System, but these instructions are particular to Debian derivatives, such as Ubuntu. A server edition is best for running only Kodi, but this page assumes booting into a desktop OS, not a server distro. However, the instructions here can be used for a server distro with even less configuration than for a desktop. Experiment inside VirtualBox before you apply any of these to your system and make a backup.</big><section end="intro" />

__TOC__

== Installing the X11 Window System ==

Even if you are using something like [https://github.com/graysky2/kodi-standalone-service Kodi Standalone Service], you still need use a WM or a DE that installs the '''x-window-manager''' software package.

To ensure you have this installed use the '''which''' command.

<pre>
which x-window-manager
</pre>

If there is no such package, you can use '''apt''' to search your Linux distributions repository.

<pre>
apt-cache search x-window-manager
</pre>

This will general a list of packages containing '''x-window-manager''', which cannot be installed alone. If you are not using a DE, you need to use a WM. And, you can also use a compositing WM like Compiz, for fast 3D effects.

[https://wiki.archlinux.org/index.php/Compiz Compiz - ArchWiki]

A note on using Kodi Standalone Service, this package runs Kodi as a '''systemd''' service and disables the login for user '''kodi''' and will not work when autologin is enabled. In fact, it will break the login process if you autologin user '''kodi''' and run Kodi Standalone Service at the same time. This package is installed automatically with the standard Kodi package when you install Kodi on Raspbian, but must be configured manually for all other Linux distributions. You can run the '''which''' command to find this package as well.

<pre>
which kodi-standalone
</pre>

Be advised, Kodi Standalone Service still launches the Kodi GUI and still requires a WM even though it is running as a '''systemd''' service. When you install a WM such as '''xfwm4''' (the WM for XFCE4), the CLI will tell you if it provides the '''x-window-manager''' package.

<pre>
Setting up xfwm4 (4.12.4-1) ...
update-alternatives: using /usr/bin/xfwm4 to provide /usr/bin/x-window-manager (x-window-manager) in auto mode
</pre>

If you do not see this message at the end of the installation, the WM you selected does not provide this software package and may not actually be a complete WM itself but only part of a package containing a WM.

For a great example on exactly how you would do this with '''xfwm4''', see this ArchWiki entry.

[https://wiki.archlinux.org/index.php/Xfwm XFWM - ArchWiki]

Most systems utilize the client version of the X11 software an Xsession requires requires.

Upgrade to the server versions of the X Window System.

<pre>apt install xauth xorg xinit xserver-xorg-core xserver-xorg xserver-common</pre>

The Ubuntu wiki is usually a good source of information.

[https://wiki.ubuntu.com/CustomXSession CustomXSession - Ubuntu Wiki]

Custom user sessions can be created with the X11 Window System to run scripts, autostart apps, and launch a WM or DE.

LightDM is used for autologin.

== Customize LightDM to autologin ==

You can utilize the ability to customize LightDM data manager by changing the builtin custom configuration file '''50-myconfig.conf''' using '''nano''' or another text editor. If you have no DE or WM you can install '''lightdm''', but should make sure to do a bit of research before you do. Most versions of Linux use LightDM, but many server versions do not. For Ubuntu Server with no DE, for example, installing '''lightdm''' is okay and necessary. Changing the behavior of LightDM is done using a custom '''50-myconfig.conf''' configuration file.

To see if you have '''lightdm''' use '''which'''.

<pre>
which lightdm
</pre>

If not, install it with '''apt'''.

<pre>
apt install lightdm
</pre>

Create a custom configuration file called '''50-myconfig.conf''' using '''nano''' or other CLI text editor.

<pre>
mkdir /etc/lightdm/lightdm.conf.d/
nano /etc/lightdm/lightdm.conf.d/50-myconfig.conf
</pre>

Inside this new file add the following text.

<pre>
[SeatDefaults]
autologin-user=kodi
</pre>

On Raspbian, you can configure LightDM differently for autologin to boot directly to Kodi.

<pre>
nano /etc/lightdm/lightdm.conf
</pre>

Uncomment the following line.

<pre>
#autologin-user=
</pre>

And add the user you want to autologin and autostart Kodi. The user is named '''kodi''' in this example.

<pre>
autologin-user=kodi
</pre>

You can alternately create /etc/lightdm/lightdm.conf.d/50-myconfig.conf, but should still ensure the settings in /etc/lightdm/lightdm.conf agree.

== Configure Kodi to autostart ==

Configure Kodi to autostart.

<pre>
mkdir -p ~/.config/autostart
ln -s /usr/bin/kodi ~/.config/autostart
</pre>

This method of autostart requires a desktop environment or DE. This is done a bit differently by each DE. Some helpful links can easily be found in today's Web search using any search engine.

[http://edoceo.com/gui/xfce-autostart-apps Autostart Apps in XFCE]

And this link shows how to autostart an app in LXDE on Raspbian.

[http://www.raspberry-projects.com/pi/pi-operating-systems/raspbian/auto-running-programs-gui Auto running programs LXDE - Raspberry Pi Projects]

The Raspberry Pi is a bit more of a tweak, but these are excellent links that will tell you how. The first link is the most helpful to making sure Kodi autostarts in Pi, and utilizes a '''crontab'''. There are many settings on the Pi that control boot, and the first link gives the best most trouble-free way to boot directly to Kodi.

[https://www.leowkahman.com/2016/03/05/lamp-stack-on-raspberry-pi-with-kodi-running-at-startup/ LAMP stack on Raspberry Pi with Kodi running at startup]

In the above link, the author describes using Crontab (short for "Cron table") to boot directly to Kodi.

<pre>
crontab -e
</pre>

Cron will ask you to choose a text editor from available options. I choose option 2 for '''nano'''.

In the new Crontab, enter the following text.

<pre>
@reboot kodi --standalone
</pre>

You could also consider using Crontab to run a script, much like described on this page in the section entitled "Run kodi in a window manager" if you scroll down the page.

[https://wiki.archlinux.org/index.php/Kodi Kodi - Run kodi in a window manager]

Instead your Crontab could look like this.

<pre>
@reboot startx
</pre>

And create an '''~/.xinitrc''' file.

<pre>
nano ~/.xinitrc
</pre>

The '''~/.xinitrc''' file should look like this.

<pre>
#!/bin/bash
kodi-standalone
sudo chvt 2
sleep 1
sudo chvt 1
</pre>

Make sure to make '''~/.xinitrc''' executable by running.

<pre>
chmod +x ~/.xinitrc
</pre>

To ensure no password is required by '''sudo''' for any user logging in when this script runs, you must edit /etc/sudoers or run the '''visudo''' command if it is installed to edit /etc/sudoers. You can install '''visudo''' from your Linux distributions default repository.

<pre>
apt install visudo
</pre>

For any non-root users, create an entry in this file like shown here.

<pre>
kodi ALL=NOPASSWD: /usr/bin/chvt
pi ALL=NOPASSWD: /usr/bin/chvt
</pre>

The above example is for users '''pi''' and '''kodi'''.

If you decide not use a Cron table, you can always remove it again.

<pre>
crontab -r
</pre>

This is a quick reference for Crontab.

[http://www.adminschoice.com/crontab-quick-reference Crontab Quick Reference]

These linked pages facilitate more tweaks and settings relevant to other uses of the X Window System on Pi.

[http://ozzmaker.com/enable-x-windows-on-piscreen/ Enable X Window System on PiScreen]

Other things to tweak on Raspbian.

[https://scribles.net/lightning-bolt-under-voltage-warning-on-raspberry-pi/ Under voltage warning and disabling splash screen on Raspbian]

[https://raspberrypi.stackexchange.com/questions/59310/remove-boot-messages-all-text-in-jessie Remove boot messages all text in Raspbian - Raspberry Pi Stack Exchange]

And, if you would rather, it is easier to follow the process provided by this link to modify the Raspbian image before installing it onto the microSD card.

[https://wiki.debian.org/RaspberryPi/qemu-user-static Modifying Raspbian with qemu-user-static]

The above link describes removing the DE from a Raspbian image, though Raspbian Lite is a much better starting point for using Qemu for this purpose.

You can also use the X11 Window System to autostart Kodi by placing a statup script in the /etc/X11/Xsession.d/ directory.

[https://debian-administration.org/article/50/Running_applications_automatically_when_X_starts Running applications automatically when X starts]

<pre>
nano /etc/X11/Xsession.d/startup-local
</pre>

Insert this text into the new file. Use CTRL + O + Enter + X to save the file.

<pre>
#!/bin/sh
/usr/bin/kodi
</pre>

If you have a WM, such as Blackbox you can add it here as well.

<pre>
#!/bin/sh
blackbox &
/usr/bin/kodi
</pre>

Set permissions to make it executable. Use the ampersand to run an application in the background, such as a WM you only need to for the purpose of launching Kodi but not if you don't want to use the WM itself. Kodi will not launch without a DE or WM, but placing the ampersand "&" at the end of the command makes it run in the background where it can do its job out of sight. Also, make sure to start a WM or DE before running an application in the foreground. This is not necessary for apps running in the background.

<pre>
chmod 755 /etc/X11/Xsession.d/startup-local
</pre>

If Kodi is not installed at the standard path, find it using the '''which''' command.

<pre>
which kodi
</pre>

This feature is available on X Window System operating systems most Linux distributions use the X Window System.

== Create custom Xsession script ==

To create a custom Xsession script with a text editor we start with an '''xinitrc''' script. For more detail on how to create and use '''xinit''', there is a great guide available here.

[https://en.wikibooks.org/wiki/Guide_to_X11/Starting_Sessions Guide to X11 - Starting Sessions - WikiBooks]

<pre>
nano ~/.xinitrc
</pre>

To run Kodi full-screen make sure the text reads:

<pre>
#!/usr/bin/env bash
exec gnome-session
/usr/bin/kodi -fs
</pre>

Replace the '''gnome-session''' with the DE or WM command you are using. See the last section for examples.

To make '''~/.xinitrc''' executable use.

<pre>
chmod +x ~/.xinitrc
</pre>

Use '''sudo''' and the '''~/.xinitrc''' file to configure '''~/.xsession'''.

<pre>
sudo -H -u kodi bash -c "ln -s ~/.xinitrc /home/kodi/.xsession"
</pre>

Make sure the path goes to user's home directory. In this example, the user is '''kodi'''.

You need to use '''sudo''' to run this command. If you do not have '''sudo''', install it.

<pre>
apt install sudo
</pre>

If you create a symbolic link and want to remove it, simply remove the existing '''.xsession''' file you created.

<pre>
rm /home/kodi/.xsession
</pre>

On some systems using a DE such as Gnome, not all systems using Gnome, it may be necessary for '''.xsession''' to be '''.xsessionrc'''. Though this is more likely the case for organization network computers than a personal one, where configurations may vary on a diversity of machines. Most of the time, it will be '''.xsession''' rather than '''.xsessionrc''' that you want to create.

You can also create the '''.xsession''' script directly in the home directory, rather than link it from '''~/.xinitrc'''. This is necessary if you create multiple custom Xsession scripts for multiple users, and you do not in that case link '''~/.xinitrc''' to '''.xsession'''.

You must also autostart the X Window system, which differs somewhat from scenario to scenario. For most setups, all that is necessary is to edit the '''.bashrc''' file.

<pre>
nano ~/.bashrc
</pre>

Add the following as shown.

<pre>
if [[ ! $DISPLAY && $XDG_VTNR -eq 1 ]]; then
exec startx
fi
</pre>

If you wish to remain logged in after quitting X, remove the '''exec''' from the above. Other configurations can be applied, but are irrelevant to autostarting Kodi.

[https://wiki.archlinux.org/index.php/Xinit#Autostart_X_at_login Xinit Autostart X at login]

If you are using LightDM and you just want to create a new login entry for user '''kodi''', you must create a new file.

<pre>
nano /usr/share/xsessions/custom.desktop
</pre>

And insert the following text.

<pre>
[Desktop Entry]
Name=Xsession
Exec=/etc/X11/Xsession
</pre>

This will create a new login option for the custom Xsession. Only this one entry is necessary for LightDM and X11 to find the '''~/.xsession''' script in each user's home directory.

== Xsession to boot to app / WM / DE ==

You can use any window manager or desktop enviroment with a custom Xsession script as long as it is intalled.

You do this by creating '''~/.xinitrc''' script that contains the command to start the WM or DE.

For instance, if you are using FluxBox.

<pre>
#!/usr/bin/env bash
exec fluxbox &
/usr/bin/kodi -fs
</pre>

The <code>-fs</code> option is full-screen.

To run Gnome in the background, but launch Kodi in the foreground.

<pre>
#!/usr/bin/env bash
exec gnome-session &
/usr/bin/kodi -fs
</pre>

Use the '''~/.xinitrc''' file to configure '''~/.xsession''' to create a custom login for any user, not just Kodi.

<pre>
sudo -H -u [username] bash -c "ln -s ~/.xinitrc ~/.xsession"
</pre>

You must reconfigure Xserver for any user that is not a privileged user to be able to start a custom Xsession.

<pre>
dpkg-reconfigure xserver-xorg-legacy
dpkg-reconfigure xserver-xorg
</pre>

When you reconfigure X11 with these commands, choose to allow non-root users (anybody) to start an Xsession. You should see your changes take effect after rebooting.

HOW-TO:Autostart Kodi for Linux

2018-04-29T13:07:42Z

W3tech: /* Configure Kodi to autostart */ Cleaning up.

<section begin="intro" /><big>Any or all or a combination of these methods can be used to configure a Debian-based X Window System to boot directly to Kodi. This should work on any Linux using the X Window System, but these instructions are particular to Debian derivatives, such as Ubuntu. A server edition is best for running only Kodi, but this page assumes booting into a desktop OS, not a server distro. However, the instructions here can be used for a server distro with even less configuration than for a desktop. Experiment inside VirtualBox before you apply any of these to your system and make a backup.</big><section end="intro" />

__TOC__

== Installing the X11 Window System ==

Even if you are using something like [https://github.com/graysky2/kodi-standalone-service Kodi Standalone Service], you still need use a WM or a DE that installs the '''x-window-manager''' software package.

To ensure you have this installed use the '''which''' command.

<pre>
which x-window-manager
</pre>

If there is no such package, you can use '''apt''' to search your Linux distributions repository.

<pre>
apt-cache search x-window-manager
</pre>

This will general a list of packages containing '''x-window-manager''', which cannot be installed alone. If you are not using a DE, you need to use a WM. And, you can also use a compositing WM like Compiz, for fast 3D effects.

[https://wiki.archlinux.org/index.php/Compiz Compiz - ArchWiki]

A note on using Kodi Standalone Service, this package runs Kodi as a '''systemd''' service and disables the login for user '''kodi''' and will not work when autologin is enabled. In fact, it will break the login process if you autologin user '''kodi''' and run Kodi Standalone Service at the same time. This package is installed automatically with the standard Kodi package when you install Kodi on Raspbian, but must be configured manually for all other Linux distributions. You can run the '''which''' command to find this package as well.

<pre>
which kodi-standalone
</pre>

Be advised, Kodi Standalone Service still launches the Kodi GUI and still requires a WM even though it is running as a '''systemd''' service. When you install a WM such as '''xfwm4''' (the WM for XFCE4), the CLI will tell you if it provides the '''x-window-manager''' package.

<pre>
Setting up xfwm4 (4.12.4-1) ...
update-alternatives: using /usr/bin/xfwm4 to provide /usr/bin/x-window-manager (x-window-manager) in auto mode
</pre>

If you do not see this message at the end of the installation, the WM you selected does not provide this software package and may not actually be a complete WM itself but only part of a package containing a WM.

For a great example on exactly how you would do this with '''xfwm4''', see this ArchWiki entry.

[https://wiki.archlinux.org/index.php/Xfwm XFWM - ArchWiki]

Most systems utilize the client version of the X11 software an Xsession requires requires.

Upgrade to the server versions of the X Window System.

<pre>apt install xauth xorg xinit xserver-xorg-core xserver-xorg xserver-common</pre>

The Ubuntu wiki is usually a good source of information.

[https://wiki.ubuntu.com/CustomXSession CustomXSession - Ubuntu Wiki]

Custom user sessions can be created with the X11 Window System to run scripts, autostart apps, and launch a WM or DE.

LightDM is used for autologin.

== Customize LightDM to autologin ==

You can utilize the ability to customize LightDM data manager by changing the builtin custom configuration file '''50-myconfig.conf''' using '''nano''' or another text editor. If you have no DE or WM you can install '''lightdm''', but should make sure to do a bit of research before you do. Most versions of Linux use LightDM, but many server versions do not. For Ubuntu Server with no DE, for example, installing '''lightdm''' is okay and necessary. Changing the behavior of LightDM is done using a custom '''50-myconfig.conf''' configuration file.

To see if you have '''lightdm''' use '''which'''.

<pre>
which lightdm
</pre>

If not, install it with '''apt'''.

<pre>
apt install lightdm
</pre>

Create a custom configuration file called '''50-myconfig.conf''' using '''nano''' or other CLI text editor.

<pre>
mkdir /etc/lightdm/lightdm.conf.d/
nano /etc/lightdm/lightdm.conf.d/50-myconfig.conf
</pre>

Inside this new file add the following text.

<pre>
[SeatDefaults]
autologin-user=kodi
</pre>

On Raspbian, you can configure LightDM differently for autologin to boot directly to Kodi.

<pre>
nano /etc/lightdm/lightdm.conf
</pre>

Uncomment the following line.

<pre>
#autologin-user=
</pre>

And add the user you want to autologin and autostart Kodi. The user is named '''kodi''' in this example.

<pre>
autologin-user=kodi
</pre>

You can alternately create /etc/lightdm/lightdm.conf.d/50-myconfig.conf, but should still ensure the settings in /etc/lightdm/lightdm.conf agree.

== Configure Kodi to autostart ==

Configure Kodi to autostart.

<pre>
mkdir -p ~/.config/autostart
ln -s /usr/bin/kodi ~/.config/autostart
</pre>

This method of autostart requires a desktop environment or DE. This is done a bit differently by each DE. Some helpful links can easily be found in today's Web search using any search engine.

[http://edoceo.com/gui/xfce-autostart-apps Autostart Apps in XFCE]

The Raspberry Pi is a bit more of a tweak, but these are excellent links that will tell you how. The first link is the most helpful to making sure Kodi autostarts in Pi, and utilizes a '''crontab'''. There are many settings on the Pi that control boot, and the first link gives the best most trouble-free way to boot directly to Kodi.

[https://www.leowkahman.com/2016/03/05/lamp-stack-on-raspberry-pi-with-kodi-running-at-startup/ LAMP stack on Raspberry Pi with Kodi running at startup]

In the above link, the author describes using Crontab (short for "Cron table") to boot directly to Kodi.

<pre>
crontab -e
</pre>

Cron will ask you to choose a text editor from available options. I choose option 2 for '''nano'''.

In the new Crontab, enter the following text.

<pre>
@reboot kodi --standalone
</pre>

You could also consider using Crontab to run a script, much like described on this page in the section entitled "Run kodi in a window manager" if you scroll down the page.

[https://wiki.archlinux.org/index.php/Kodi Kodi - Run kodi in a window manager]

Instead your Crontab could look like this.

<pre>
@reboot startx
</pre>

And create an '''~/.xinitrc''' file.

<pre>
nano ~/.xinitrc
</pre>

The '''~/.xinitrc''' file should look like this.

<pre>
#!/bin/bash
kodi-standalone
sudo chvt 2
sleep 1
sudo chvt 1
</pre>

Make sure to make '''~/.xinitrc''' executable by running.

<pre>
chmod +x ~/.xinitrc
</pre>

To ensure no password is required by '''sudo''' for any user logging in when this script runs, you must edit /etc/sudoers or run the '''visudo''' command if it is installed to edit /etc/sudoers. You can install '''visudo''' from your Linux distributions default repository.

<pre>
apt install visudo
</pre>

For any non-root users, create an entry in this file like shown here.

<pre>
kodi ALL=NOPASSWD: /usr/bin/chvt
pi ALL=NOPASSWD: /usr/bin/chvt
</pre>

The above example is for users '''pi''' and '''kodi'''.

If you decide not use a Cron table, you can always remove it again.

<pre>
crontab -r
</pre>

This is a quick reference for Crontab.

[http://www.adminschoice.com/crontab-quick-reference Crontab Quick Reference]

These linked pages facilitate more tweaks and settings relevant to other uses of the X Window System on Pi.

[http://ozzmaker.com/enable-x-windows-on-piscreen/ Enable X Window System on PiScreen]

Autostarting apps on Raspbian is possible using the DE, as well.

[http://www.raspberry-projects.com/pi/pi-operating-systems/raspbian/auto-running-programs-gui Auto running programs LXDE - Raspberry Pi Projects]

Other things to tweak on Raspbian.

[https://scribles.net/lightning-bolt-under-voltage-warning-on-raspberry-pi/ Under voltage warning and disabling splash screen on Raspbian]

[https://raspberrypi.stackexchange.com/questions/59310/remove-boot-messages-all-text-in-jessie Remove boot messages all text in Raspbian - Raspberry Pi Stack Exchange]

And, if you would rather, it is easier to follow the process provided by this link to modify the Raspbian image before installing it onto the microSD card.

[https://wiki.debian.org/RaspberryPi/qemu-user-static Modifying Raspbian with qemu-user-static]

The above link describes removing the DE from a Raspbian image, though Raspbian Lite is a much better starting point for using Qemu for this purpose.

You can also use the X11 Window System to autostart Kodi by placing a statup script in the /etc/X11/Xsession.d/ directory.

[https://debian-administration.org/article/50/Running_applications_automatically_when_X_starts Running applications automatically when X starts]

<pre>
nano /etc/X11/Xsession.d/startup-local
</pre>

Insert this text into the new file. Use CTRL + O + Enter + X to save the file.

<pre>
#!/bin/sh
/usr/bin/kodi
</pre>

If you have a WM, such as Blackbox you can add it here as well.

<pre>
#!/bin/sh
blackbox &
/usr/bin/kodi
</pre>

Set permissions to make it executable. Use the ampersand to run an application in the background, such as a WM you only need to for the purpose of launching Kodi but not if you don't want to use the WM itself. Kodi will not launch without a DE or WM, but placing the ampersand "&" at the end of the command makes it run in the background where it can do its job out of sight. Also, make sure to start a WM or DE before running an application in the foreground. This is not necessary for apps running in the background.

<pre>
chmod 755 /etc/X11/Xsession.d/startup-local
</pre>

If Kodi is not installed at the standard path, find it using the '''which''' command.

<pre>
which kodi
</pre>

This feature is available on X Window System operating systems most Linux distributions use the X Window System.

== Create custom Xsession script ==

To create a custom Xsession script with a text editor we start with an '''xinitrc''' script. For more detail on how to create and use '''xinit''', there is a great guide available here.

[https://en.wikibooks.org/wiki/Guide_to_X11/Starting_Sessions Guide to X11 - Starting Sessions - WikiBooks]

<pre>
nano ~/.xinitrc
</pre>

To run Kodi full-screen make sure the text reads:

<pre>
#!/usr/bin/env bash
exec gnome-session
/usr/bin/kodi -fs
</pre>

Replace the '''gnome-session''' with the DE or WM command you are using. See the last section for examples.

To make '''~/.xinitrc''' executable use.

<pre>
chmod +x ~/.xinitrc
</pre>

Use '''sudo''' and the '''~/.xinitrc''' file to configure '''~/.xsession'''.

<pre>
sudo -H -u kodi bash -c "ln -s ~/.xinitrc /home/kodi/.xsession"
</pre>

Make sure the path goes to user's home directory. In this example, the user is '''kodi'''.

You need to use '''sudo''' to run this command. If you do not have '''sudo''', install it.

<pre>
apt install sudo
</pre>

If you create a symbolic link and want to remove it, simply remove the existing '''.xsession''' file you created.

<pre>
rm /home/kodi/.xsession
</pre>

On some systems using a DE such as Gnome, not all systems using Gnome, it may be necessary for '''.xsession''' to be '''.xsessionrc'''. Though this is more likely the case for organization network computers than a personal one, where configurations may vary on a diversity of machines. Most of the time, it will be '''.xsession''' rather than '''.xsessionrc''' that you want to create.

You can also create the '''.xsession''' script directly in the home directory, rather than link it from '''~/.xinitrc'''. This is necessary if you create multiple custom Xsession scripts for multiple users, and you do not in that case link '''~/.xinitrc''' to '''.xsession'''.

You must also autostart the X Window system, which differs somewhat from scenario to scenario. For most setups, all that is necessary is to edit the '''.bashrc''' file.

<pre>
nano ~/.bashrc
</pre>

Add the following as shown.

<pre>
if [[ ! $DISPLAY && $XDG_VTNR -eq 1 ]]; then
exec startx
fi
</pre>

If you wish to remain logged in after quitting X, remove the '''exec''' from the above. Other configurations can be applied, but are irrelevant to autostarting Kodi.

[https://wiki.archlinux.org/index.php/Xinit#Autostart_X_at_login Xinit Autostart X at login]

If you are using LightDM and you just want to create a new login entry for user '''kodi''', you must create a new file.

<pre>
nano /usr/share/xsessions/custom.desktop
</pre>

And insert the following text.

<pre>
[Desktop Entry]
Name=Xsession
Exec=/etc/X11/Xsession
</pre>

This will create a new login option for the custom Xsession. Only this one entry is necessary for LightDM and X11 to find the '''~/.xsession''' script in each user's home directory.

== Xsession to boot to app / WM / DE ==

You can use any window manager or desktop enviroment with a custom Xsession script as long as it is intalled.

You do this by creating '''~/.xinitrc''' script that contains the command to start the WM or DE.

For instance, if you are using FluxBox.

<pre>
#!/usr/bin/env bash
exec fluxbox &
/usr/bin/kodi -fs
</pre>

The <code>-fs</code> option is full-screen.

To run Gnome in the background, but launch Kodi in the foreground.

<pre>
#!/usr/bin/env bash
exec gnome-session &
/usr/bin/kodi -fs
</pre>

Use the '''~/.xinitrc''' file to configure '''~/.xsession''' to create a custom login for any user, not just Kodi.

<pre>
sudo -H -u [username] bash -c "ln -s ~/.xinitrc ~/.xsession"
</pre>

You must reconfigure Xserver for any user that is not a privileged user to be able to start a custom Xsession.

<pre>
dpkg-reconfigure xserver-xorg-legacy
dpkg-reconfigure xserver-xorg
</pre>

When you reconfigure X11 with these commands, choose to allow non-root users (anybody) to start an Xsession. You should see your changes take effect after rebooting.

HOW-TO:Autostart Kodi for Linux

2018-04-29T12:44:37Z

W3tech: Taking out the unnecessary Grub entry section

<section begin="intro" /><big>Any or all or a combination of these methods can be used to configure a Debian-based X Window System to boot directly to Kodi. This should work on any Linux using the X Window System, but these instructions are particular to Debian derivatives, such as Ubuntu. A server edition is best for running only Kodi, but this page assumes booting into a desktop OS, not a server distro. However, the instructions here can be used for a server distro with even less configuration than for a desktop. Experiment inside VirtualBox before you apply any of these to your system and make a backup.</big><section end="intro" />

__TOC__

== Installing the X11 Window System ==

Even if you are using something like [https://github.com/graysky2/kodi-standalone-service Kodi Standalone Service], you still need use a WM or a DE that installs the '''x-window-manager''' software package.

To ensure you have this installed use the '''which''' command.

<pre>
which x-window-manager
</pre>

If there is no such package, you can use '''apt''' to search your Linux distributions repository.

<pre>
apt-cache search x-window-manager
</pre>

This will general a list of packages containing '''x-window-manager''', which cannot be installed alone. If you are not using a DE, you need to use a WM. And, you can also use a compositing WM like Compiz, for fast 3D effects.

[https://wiki.archlinux.org/index.php/Compiz Compiz - ArchWiki]

A note on using Kodi Standalone Service, this package runs Kodi as a '''systemd''' service and disables the login for user '''kodi''' and will not work when autologin is enabled. In fact, it will break the login process if you autologin user '''kodi''' and run Kodi Standalone Service at the same time. This package is installed automatically with the standard Kodi package when you install Kodi on Raspbian, but must be configured manually for all other Linux distributions. You can run the '''which''' command to find this package as well.

<pre>
which kodi-standalone
</pre>

Be advised, Kodi Standalone Service still launches the Kodi GUI and still requires a WM even though it is running as a '''systemd''' service. When you install a WM such as '''xfwm4''' (the WM for XFCE4), the CLI will tell you if it provides the '''x-window-manager''' package.

<pre>
Setting up xfwm4 (4.12.4-1) ...
update-alternatives: using /usr/bin/xfwm4 to provide /usr/bin/x-window-manager (x-window-manager) in auto mode
</pre>

If you do not see this message at the end of the installation, the WM you selected does not provide this software package and may not actually be a complete WM itself but only part of a package containing a WM.

For a great example on exactly how you would do this with '''xfwm4''', see this ArchWiki entry.

[https://wiki.archlinux.org/index.php/Xfwm XFWM - ArchWiki]

Most systems utilize the client version of the X11 software an Xsession requires requires.

Upgrade to the server versions of the X Window System.

<pre>apt install xauth xorg xinit xserver-xorg-core xserver-xorg xserver-common</pre>

The Ubuntu wiki is usually a good source of information.

[https://wiki.ubuntu.com/CustomXSession CustomXSession - Ubuntu Wiki]

Custom user sessions can be created with the X11 Window System to run scripts, autostart apps, and launch a WM or DE.

LightDM is used for autologin.

== Customize LightDM to autologin ==

You can utilize the ability to customize LightDM data manager by changing the builtin custom configuration file '''50-myconfig.conf''' using '''nano''' or another text editor. If you have no DE or WM you can install '''lightdm''', but should make sure to do a bit of research before you do. Most versions of Linux use LightDM, but many server versions do not. For Ubuntu Server with no DE, for example, installing '''lightdm''' is okay and necessary. Changing the behavior of LightDM is done using a custom '''50-myconfig.conf''' configuration file.

To see if you have '''lightdm''' use '''which'''.

<pre>
which lightdm
</pre>

If not, install it with '''apt'''.

<pre>
apt install lightdm
</pre>

Create a custom configuration file called '''50-myconfig.conf''' using '''nano''' or other CLI text editor.

<pre>
mkdir /etc/lightdm/lightdm.conf.d/
nano /etc/lightdm/lightdm.conf.d/50-myconfig.conf
</pre>

Inside this new file add the following text.

<pre>
[SeatDefaults]
autologin-user=kodi
</pre>

On Raspbian, you can configure LightDM differently for autologin to boot directly to Kodi.

<pre>
nano /etc/lightdm/lightdm.conf
</pre>

Uncomment the following line.

<pre>
#autologin-user=
</pre>

And add the user you want to autologin and autostart Kodi. The user is named '''kodi''' in this example.

<pre>
autologin-user=kodi
</pre>

You can alternately create /etc/lightdm/lightdm.conf.d/50-myconfig.conf, but should still ensure the settings in /etc/lightdm/lightdm.conf agree.

== Configure Kodi to autostart ==

Configure Kodi to autostart.

<pre>
mkdir -p ~/.config/autostart
ln -s /usr/bin/kodi ~/.config/autostart
</pre>

This method of autostart requires a desktop environment or DE. This is done a bit differently by each DE. Some helpful links can easily be found in today's Web search using any search engine.

[http://edoceo.com/gui/xfce-autostart-apps Autostart Apps in XFCE]

The Raspberry Pi is a bit more of a tweak, but these are excellent links that will tell you how. The first link is the most helpful to making sure Kodi autostarts in Pi, and utilizes a '''crontab'''. There are many settings on the Pi that control boot, and the first link gives the best most trouble-free way to boot directly to Kodi.

[https://www.leowkahman.com/2016/03/05/lamp-stack-on-raspberry-pi-with-kodi-running-at-startup/ LAMP stack on Raspberry Pi with Kodi running at startup]

In the above link, the author describes using Crontab (short for "Cron table") to boot directly to Kodi.

<pre>
crontab -e
</pre>

Cron will ask you to choose a text editor from available options. I choose option 2 for '''nano'''.

In the new Crontab, enter the following text.

<pre>
@reboot kodi --standalone
</pre>

You could also consider using Crontab to run a script, much like described on this page in the section entitled "Run kodi in a window manager" if you scroll down the page.

[https://wiki.archlinux.org/index.php/Kodi Kodi - Run kodi in a window manager]

Instead your Crontab could look like this.

<pre>
@reboot startx
</pre>

And create an '''~/.xinitrc''' file.

<pre>
nano ~/.xinitrc
</pre>

The '''~/.xinitrc''' file should look like this.

<pre>
#!/bin/bash
kodi-standalone
sudo chvt 2
sleep 1
sudo chvt 1
</pre>

Make sure to make '''~/.xinitrc''' executable by running.

<pre>
chmod +x ~/.xinitrc
</pre>

To ensure no password is required by '''sudo''' for any user logging in when this script runs, you must edit /etc/sudoers or run the '''visudo''' command if it is installed to edit /etc/sudoers. You can install '''visudo''' from your Linux distributions default repository.

<pre>
apt install visudo
</pre>

For any non-root users, create an entry in this file like shown here.

<pre>
kodi ALL=NOPASSWD: /usr/bin/chvt
pi ALL=NOPASSWD: /usr/bin/chvt
</pre>

The above example is for users '''pi''' and '''kodi'''.

If you decide not use a Cron table, you can always remove it again.

<pre>
crontab -r
</pre>

This is a quick reference for Crontab.

[http://www.adminschoice.com/crontab-quick-reference Crontab Quick Reference]

These linked pages facilitate more tweaks and settings relevant to other uses of the X Window System on Pi.

[http://ozzmaker.com/enable-x-windows-on-piscreen/ Enable X Window System on PiScreen]

[https://raspberrypi.stackexchange.com/questions/59310/remove-boot-messages-all-text-in-jessie Remove boot messages all text in Raspbian - Raspberry Pi Stack Exchange]

[https://raspberrypi.stackexchange.com/questions/47823/how-to-prevent-autologin-of-gui How to prevent or allow autologin of GUI - Raspberry Pi Stack Exchange]

[http://www.raspberry-projects.com/pi/pi-operating-systems/raspbian/auto-running-programs-gui Auto running programs LXDE - Raspberry Pi Projects]

And, if you would rather, it is easier to follow the process provided by this link to modify the Raspbian image before installing it onto the microSD card.

[https://wiki.debian.org/RaspberryPi/qemu-user-static Modifying Raspbian with qemu-user-static]

The above link describes removing the DE from a Raspbian image, though Raspbian Lite is a much better starting point for using Qemu for this purpose.

You can also use the X11 Window System to autostart Kodi by placing a statup script in the /etc/X11/Xsession.d/ directory.

[https://debian-administration.org/article/50/Running_applications_automatically_when_X_starts Running applications automatically when X starts]

<pre>
nano /etc/X11/Xsession.d/startup-local
</pre>

Insert this text into the new file. Use CTRL + O + Enter + X to save the file.

<pre>
#!/bin/sh
/usr/bin/kodi
</pre>

If you have a WM, such as Blackbox you can add it here as well.

<pre>
#!/bin/sh
blackbox &
/usr/bin/kodi
</pre>

Set permissions to make it executable. Use the ampersand to run an application in the background, such as a WM you only need to for the purpose of launching Kodi but not if you don't want to use the WM itself. Kodi will not launch without a DE or WM, but placing the ampersand "&" at the end of the command makes it run in the background where it can do its job out of sight. Also, make sure to start a WM or DE before running an application in the foreground. This is not necessary for apps running in the background.

<pre>
chmod 755 /etc/X11/Xsession.d/startup-local
</pre>

If Kodi is not installed at the standard path, find it using the '''which''' command.

<pre>
which kodi
</pre>

This feature is available on X Window System operating systems most Linux distributions use the X Window System.

== Create custom Xsession script ==

To create a custom Xsession script with a text editor we start with an '''xinitrc''' script. For more detail on how to create and use '''xinit''', there is a great guide available here.

[https://en.wikibooks.org/wiki/Guide_to_X11/Starting_Sessions Guide to X11 - Starting Sessions - WikiBooks]

<pre>
nano ~/.xinitrc
</pre>

To run Kodi full-screen make sure the text reads:

<pre>
#!/usr/bin/env bash
exec gnome-session
/usr/bin/kodi -fs
</pre>

Replace the '''gnome-session''' with the DE or WM command you are using. See the last section for examples.

To make '''~/.xinitrc''' executable use.

<pre>
chmod +x ~/.xinitrc
</pre>

Use '''sudo''' and the '''~/.xinitrc''' file to configure '''~/.xsession'''.

<pre>
sudo -H -u kodi bash -c "ln -s ~/.xinitrc /home/kodi/.xsession"
</pre>

Make sure the path goes to user's home directory. In this example, the user is '''kodi'''.

You need to use '''sudo''' to run this command. If you do not have '''sudo''', install it.

<pre>
apt install sudo
</pre>

If you create a symbolic link and want to remove it, simply remove the existing '''.xsession''' file you created.

<pre>
rm /home/kodi/.xsession
</pre>

On some systems using a DE such as Gnome, not all systems using Gnome, it may be necessary for '''.xsession''' to be '''.xsessionrc'''. Though this is more likely the case for organization network computers than a personal one, where configurations may vary on a diversity of machines. Most of the time, it will be '''.xsession''' rather than '''.xsessionrc''' that you want to create.

You can also create the '''.xsession''' script directly in the home directory, rather than link it from '''~/.xinitrc'''. This is necessary if you create multiple custom Xsession scripts for multiple users, and you do not in that case link '''~/.xinitrc''' to '''.xsession'''.

You must also autostart the X Window system, which differs somewhat from scenario to scenario. For most setups, all that is necessary is to edit the '''.bashrc''' file.

<pre>
nano ~/.bashrc
</pre>

Add the following as shown.

<pre>
if [[ ! $DISPLAY && $XDG_VTNR -eq 1 ]]; then
exec startx
fi
</pre>

If you wish to remain logged in after quitting X, remove the '''exec''' from the above. Other configurations can be applied, but are irrelevant to autostarting Kodi.

[https://wiki.archlinux.org/index.php/Xinit#Autostart_X_at_login Xinit Autostart X at login]

If you are using LightDM and you just want to create a new login entry for user '''kodi''', you must create a new file.

<pre>
nano /usr/share/xsessions/custom.desktop
</pre>

And insert the following text.

<pre>
[Desktop Entry]
Name=Xsession
Exec=/etc/X11/Xsession
</pre>

This will create a new login option for the custom Xsession. Only this one entry is necessary for LightDM and X11 to find the '''~/.xsession''' script in each user's home directory.

== Xsession to boot to app / WM / DE ==

You can use any window manager or desktop enviroment with a custom Xsession script as long as it is intalled.

You do this by creating '''~/.xinitrc''' script that contains the command to start the WM or DE.

For instance, if you are using FluxBox.

<pre>
#!/usr/bin/env bash
exec fluxbox &
/usr/bin/kodi -fs
</pre>

The <code>-fs</code> option is full-screen.

To run Gnome in the background, but launch Kodi in the foreground.

<pre>
#!/usr/bin/env bash
exec gnome-session &
/usr/bin/kodi -fs
</pre>

Use the '''~/.xinitrc''' file to configure '''~/.xsession''' to create a custom login for any user, not just Kodi.

<pre>
sudo -H -u [username] bash -c "ln -s ~/.xinitrc ~/.xsession"
</pre>

You must reconfigure Xserver for any user that is not a privileged user to be able to start a custom Xsession.

<pre>
dpkg-reconfigure xserver-xorg-legacy
dpkg-reconfigure xserver-xorg
</pre>

When you reconfigure X11 with these commands, choose to allow non-root users (anybody) to start an Xsession. You should see your changes take effect after rebooting.

HOW-TO:Autostart Kodi for Linux

2018-04-29T12:33:27Z

W3tech: Making it more tidy and presentable.

<section begin="intro" /><big>Any or all or a combination of these methods can be used to configure a Debian-based X Window System to boot directly to Kodi. This should work on any Linux using the X Window System, but these instructions are particular to Debian derivatives, such as Ubuntu. A server edition is best for running only Kodi, but this page assumes booting into a desktop OS, not a server distro. However, the instructions here can be used for a server distro with even less configuration than for a desktop. Experiment inside VirtualBox before you apply any of these to your system and make a backup.</big><section end="intro" />

__TOC__

== Installing the X11 Window System ==

Even if you are using something like [https://github.com/graysky2/kodi-standalone-service Kodi Standalone Service], you still need use a WM or a DE that installs the '''x-window-manager''' software package.

To ensure you have this installed use the '''which''' command.

<pre>
which x-window-manager
</pre>

If there is no such package, you can use '''apt''' to search your Linux distributions repository.

<pre>
apt-cache search x-window-manager
</pre>

This will general a list of packages containing '''x-window-manager''', which cannot be installed alone. If you are not using a DE, you need to use a WM. And, you can also use a compositing WM like Compiz, for fast 3D effects.

[https://wiki.archlinux.org/index.php/Compiz Compiz - ArchWiki]

A note on using Kodi Standalone Service, this package runs Kodi as a '''systemd''' service and disables the login for user '''kodi''' and will not work when autologin is enabled. In fact, it will break the login process if you autologin user '''kodi''' and run Kodi Standalone Service at the same time. This package is installed automatically with the standard Kodi package when you install Kodi on Raspbian, but must be configured manually for all other Linux distributions. You can run the '''which''' command to find this package as well.

<pre>
which kodi-standalone
</pre>

Be advised, Kodi Standalone Service still launches the Kodi GUI and still requires a WM even though it is running as a '''systemd''' service. When you install a WM such as '''xfwm4''' (the WM for XFCE4), the CLI will tell you if it provides the '''x-window-manager''' package.

<pre>
Setting up xfwm4 (4.12.4-1) ...
update-alternatives: using /usr/bin/xfwm4 to provide /usr/bin/x-window-manager (x-window-manager) in auto mode
</pre>

If you do not see this message at the end of the installation, the WM you selected does not provide this software package and may not actually be a complete WM itself but only part of a package containing a WM.

For a great example on exactly how you would do this with '''xfwm4''', see this ArchWiki entry.

[https://wiki.archlinux.org/index.php/Xfwm XFWM - ArchWiki]

Most systems utilize the client version of the X11 software an Xsession requires requires.

Upgrade to the server versions of the X Window System.

<pre>apt install xauth xorg xinit xserver-xorg-core xserver-xorg xserver-common</pre>

The Ubuntu wiki is usually a good source of information.

[https://wiki.ubuntu.com/CustomXSession CustomXSession - Ubuntu Wiki]

Custom user sessions can be created with the X11 Window System to run scripts, autostart apps, and launch a WM or DE.

LightDM is used for autologin.

== Customize LightDM to autologin ==

You can utilize the ability to customize LightDM data manager by changing the builtin custom configuration file '''50-myconfig.conf''' using '''nano''' or another text editor. If you have no DE or WM you can install '''lightdm''', but should make sure to do a bit of research before you do. Most versions of Linux use LightDM, but many server versions do not. For Ubuntu Server with no DE, for example, installing '''lightdm''' is okay and necessary. Changing the behavior of LightDM is done using a custom '''50-myconfig.conf''' configuration file.

To see if you have '''lightdm''' use '''which'''.

<pre>
which lightdm
</pre>

If not, install it with '''apt'''.

<pre>
apt install lightdm
</pre>

Create a custom configuration file called '''50-myconfig.conf''' using '''nano''' or other CLI text editor.

<pre>
mkdir /etc/lightdm/lightdm.conf.d/
nano /etc/lightdm/lightdm.conf.d/50-myconfig.conf
</pre>

Inside this new file add the following text.

<pre>
[SeatDefaults]
autologin-user=kodi
</pre>

On Raspbian, you can configure LightDM differently for autologin to boot directly to Kodi.

<pre>
nano /etc/lightdm/lightdm.conf
</pre>

Uncomment the following line.

<pre>
#autologin-user=
</pre>

And add the user you want to autologin and autostart Kodi. The user is named '''kodi''' in this example.

<pre>
autologin-user=kodi
</pre>

You can alternately create /etc/lightdm/lightdm.conf.d/50-myconfig.conf, but should still ensure the settings in /etc/lightdm/lightdm.conf agree.

== Configure Kodi to autostart ==

Configure Kodi to autostart.

<pre>
mkdir -p ~/.config/autostart
ln -s /usr/bin/kodi ~/.config/autostart
</pre>

This method of autostart requires a desktop environment or DE. This is done a bit differently by each DE. Some helpful links can easily be found in today's Web search using any search engine.

[http://edoceo.com/gui/xfce-autostart-apps Autostart Apps in XFCE]

The Raspberry Pi is a bit more of a tweak, but these are excellent links that will tell you how. The first link is the most helpful to making sure Kodi autostarts in Pi, and utilizes a '''crontab'''. There are many settings on the Pi that control boot, and the first link gives the best most trouble-free way to boot directly to Kodi.

[https://www.leowkahman.com/2016/03/05/lamp-stack-on-raspberry-pi-with-kodi-running-at-startup/ LAMP stack on Raspberry Pi with Kodi running at startup]

In the above link, the author describes using Crontab (short for "Cron table") to boot directly to Kodi.

<pre>
crontab -e
</pre>

Cron will ask you to choose a text editor from available options. I choose option 2 for '''nano'''.

In the new Crontab, enter the following text.

<pre>
@reboot kodi --standalone
</pre>

You could also consider using Crontab to run a script, much like described on this page in the section entitled "Run kodi in a window manager" if you scroll down the page.

[https://wiki.archlinux.org/index.php/Kodi Kodi - Run kodi in a window manager]

Instead your Crontab could look like this.

<pre>
@reboot startx
</pre>

And create an '''~/.xinitrc''' file.

<pre>
nano ~/.xinitrc
</pre>

The '''~/.xinitrc''' file should look like this.

<pre>
#!/bin/bash
kodi-standalone
sudo chvt 2
sleep 1
sudo chvt 1
</pre>

Make sure to make '''~/.xinitrc''' executable by running.

<pre>
chmod +x ~/.xinitrc
</pre>

To ensure no password is required by '''sudo''' for any user logging in when this script runs, you must edit /etc/sudoers or run the '''visudo''' command if it is installed to edit /etc/sudoers. You can install '''visudo''' from your Linux distributions default repository.

<pre>
apt install visudo
</pre>

For any non-root users, create an entry in this file like shown here.

<pre>
kodi ALL=NOPASSWD: /usr/bin/chvt
pi ALL=NOPASSWD: /usr/bin/chvt
</pre>

The above example is for users '''pi''' and '''kodi'''.

If you decide not use a Cron table, you can always remove it again.

<pre>
crontab -r
</pre>

This is a quick reference for Crontab.

[http://www.adminschoice.com/crontab-quick-reference Crontab Quick Reference]

These linked pages facilitate more tweaks and settings relevant to other uses of the X Window System on Pi.

[http://ozzmaker.com/enable-x-windows-on-piscreen/ Enable X Window System on PiScreen]

[https://raspberrypi.stackexchange.com/questions/59310/remove-boot-messages-all-text-in-jessie Remove boot messages all text in Raspbian - Raspberry Pi Stack Exchange]

[https://raspberrypi.stackexchange.com/questions/47823/how-to-prevent-autologin-of-gui How to prevent or allow autologin of GUI - Raspberry Pi Stack Exchange]

[http://www.raspberry-projects.com/pi/pi-operating-systems/raspbian/auto-running-programs-gui Auto running programs LXDE - Raspberry Pi Projects]

And, if you would rather, it is easier to follow the process provided by this link to modify the Raspbian image before installing it onto the microSD card.

[https://wiki.debian.org/RaspberryPi/qemu-user-static Modifying Raspbian with qemu-user-static]

The above link describes removing the DE from a Raspbian image, though Raspbian Lite is a much better starting point for using Qemu for this purpose.

You can also use the X11 Window System to autostart Kodi by placing a statup script in the /etc/X11/Xsession.d/ directory.

[https://debian-administration.org/article/50/Running_applications_automatically_when_X_starts Running applications automatically when X starts]

<pre>
nano /etc/X11/Xsession.d/startup-local
</pre>

Insert this text into the new file. Use CTRL + O + Enter + X to save the file.

<pre>
#!/bin/sh
/usr/bin/kodi
</pre>

If you have a WM, such as Blackbox you can add it here as well.

<pre>
#!/bin/sh
blackbox &
/usr/bin/kodi
</pre>

Set permissions to make it executable. Use the ampersand to run an application in the background, such as a WM you only need to for the purpose of launching Kodi but not if you don't want to use the WM itself. Kodi will not launch without a DE or WM, but placing the ampersand "&" at the end of the command makes it run in the background where it can do its job out of sight. Also, make sure to start a WM or DE before running an application in the foreground. This is not necessary for apps running in the background.

<pre>
chmod 755 /etc/X11/Xsession.d/startup-local
</pre>

If Kodi is not installed at the standard path, find it using the '''which''' command.

<pre>
which kodi
</pre>

This feature is available on X Window System operating systems most Linux distributions use the X Window System.

== Create custom Xsession script ==

To create a custom Xsession script with a text editor we start with an '''xinitrc''' script. For more detail on how to create and use '''xinit''', there is a great guide available here.

[https://en.wikibooks.org/wiki/Guide_to_X11/Starting_Sessions Guide to X11 - Starting Sessions - WikiBooks]

<pre>
nano ~/.xinitrc
</pre>

To run Kodi full-screen make sure the text reads:

<pre>
#!/usr/bin/env bash
exec gnome-session
/usr/bin/kodi -fs
</pre>

Replace the '''gnome-session''' with the DE or WM command you are using. See the last section for examples.

To make '''~/.xinitrc''' executable use.

<pre>
chmod +x ~/.xinitrc
</pre>

Use '''sudo''' and the '''~/.xinitrc''' file to configure '''~/.xsession'''.

<pre>
sudo -H -u kodi bash -c "ln -s ~/.xinitrc /home/kodi/.xsession"
</pre>

Make sure the path goes to user's home directory. In this example, the user is '''kodi'''.

You need to use '''sudo''' to run this command. If you do not have '''sudo''', install it.

<pre>
apt install sudo
</pre>

If you create a symbolic link and want to remove it, simply remove the existing '''.xsession''' file you created.

<pre>
rm /home/kodi/.xsession
</pre>

On some systems using a DE such as Gnome, not all systems using Gnome, it may be necessary for '''.xsession''' to be '''.xsessionrc'''. Though this is more likely the case for organization network computers than a personal one, where configurations may vary on a diversity of machines. Most of the time, it will be '''.xsession''' rather than '''.xsessionrc''' that you want to create.

You can also create the '''.xsession''' script directly in the home directory, rather than link it from '''~/.xinitrc'''. This is necessary if you create multiple custom Xsession scripts for multiple users, and you do not in that case link '''~/.xinitrc''' to '''.xsession'''.

You must also autostart the X Window system, which differs somewhat from scenario to scenario. For most setups, all that is necessary is to edit the '''.bashrc''' file.

<pre>
nano ~/.bashrc
</pre>

Add the following as shown.

<pre>
if [[ ! $DISPLAY && $XDG_VTNR -eq 1 ]]; then
exec startx
fi
</pre>

If you wish to remain logged in after quitting X, remove the '''exec''' from the above. Other configurations can be applied, but are irrelevant to autostarting Kodi.

[https://wiki.archlinux.org/index.php/Xinit#Autostart_X_at_login Xinit Autostart X at login]

If you are using LightDM and you just want to create a new login entry for user '''kodi''', you must create a new file.

<pre>
nano /usr/share/xsessions/custom.desktop
</pre>

And insert the following text.

<pre>
[Desktop Entry]
Name=Xsession
Exec=/etc/X11/Xsession
</pre>

This will create a new login option for the custom Xsession. Only this one entry is necessary for LightDM and X11 to find the '''~/.xsession''' script in each user's home directory.

== Xsession to boot to app / WM / DE ==

You can use any window manager or desktop enviroment with a custom Xsession script as long as it is intalled.

You do this by creating '''~/.xinitrc''' script that contains the command to start the WM or DE.

For instance, if you are using FluxBox.

<pre>
#!/usr/bin/env bash
exec fluxbox &
/usr/bin/kodi -fs
</pre>

The <code>-fs</code> option is full-screen.

To run Gnome in the background, but launch Kodi in the foreground.

<pre>
#!/usr/bin/env bash
exec gnome-session &
/usr/bin/kodi -fs
</pre>

Use the '''~/.xinitrc''' file to configure '''~/.xsession''' to create a custom login for any user, not just Kodi.

<pre>
sudo -H -u [username] bash -c "ln -s ~/.xinitrc ~/.xsession"
</pre>

You must reconfigure Xserver for any user that is not a privileged user to be able to start a custom Xsession.

<pre>
dpkg-reconfigure xserver-xorg-legacy
</pre>

And / or...

<pre>
dpkg-reconfigure xserver-xorg
</pre>

If both packages are installed, you must reconfigure both. Not all systems will use or require the legacy package to allow non-root users to start X.

== Add a custom Grub entry ==

If you want to boot to the CLI and manually launch an app or boot directly to Kodi without a DE or WM, add a custom grub entry.

The right way to add a custom grub entry is to copy the menu entry you want to change or duplicate.

Copy the default Grub configuration file and open it with a text editor on your desktop. If you use a text editor on the CLI, the text will be cut off by the window when copying and pasting.

<pre>
cp /boot/grub/grub.cfg grub.cfg
gedit grub.cfg
</pre>

Copy the menu entry and paste it into '''40_custom''' with a text editor in the CLI.

<pre>
nano /etc/grub.d/40_custom
</pre>

Where the menu entry contains '''quiet splash''' change it to '''text''' instead.

You should also change the name of the entry!

I just appended mine with “CLI” for command line interface.

To update Grub:

<pre>
update-grub
</pre>

To launch a WM you can type its name. I use Enlightment 17 or Fluxbox. It must be installed.

<pre>
fluxbox
</pre>

You must have FluxBox installed. There are countless other window managers.

To launch a DE you enter the appropriate command. For Gnome desktop:

<pre>
gnome-session
</pre>

For KDE:

<pre>
startkde
</pre>

or

<pre>
plasma-desktop
</pre>

For XFCE:

<pre>
startxfce4
</pre>

For Mate:

<pre>
mate-session
</pre>

For LXDE:

<pre>
startlxde
</pre>

You can either manually launch your apps, boot right into them, or create an Xsession for each user. This is great when you want to create a Kodi user for running Kodi only, and for making sure you can still login to your DE with your regular user account. You can boot to any app full-screen this way, not just Kodi. You can create a custom Xsession script for any user, configured with any startup applications running in full-screen mode or normally.

By optionally creating a Grub menu entry, you can create a different Grub menu selection to boot only to the CLI and start an Xsession with a script or run commands manually.

HOW-TO:Autostart Kodi for Linux

2018-04-29T11:52:48Z

W3tech: /* Configure Kodi to autostart */

<section begin="intro" /><big>Any or all or any combination of these methods can be used to configure a Debian-based X Window System to boot directly to Kodi. This should work on any Linux using the X Window System, but these instructions are particular to Debian derivatives, such as Ubuntu. A server edition is best for running only Kodi, but this page assumes booting into a desktop OS, not a server distro. However, the instructions here can be used for a server distro with even less configuration than for a desktop. Experiment inside VirtualBox before you apply any of these to your system and make a backup.</big><section end="intro" />

__TOC__

== Switch to root ==

<pre>
su
</pre>

or

<pre>
sudo su
</pre>

== Create a Kodi user ==

To use Kodi full-screen, you only have to create a standard user.

<pre>
adduser kodi
</pre>

To remove the password use:

<pre>
passwd -d kodi
</pre>

== Customize LightDM to autologin ==

You can utilize the ability to customize LightDM data manager by changing the builtin custom configuration file '''50-myconfig.conf''' using '''nano''' or another text editor. If you have no DE or WM you can install '''lightdm''', but should make sure to do a bit of research before you do. Most versions of Linux use LightDM, but many server versions do not. For Ubuntu Server with no DE, for example, installing '''lightdm''' is okay and necessary. Changing the behavior of LightDM is done using a custom '''50-myconfig.conf''' configuration file.

To see if you have '''lightdm''' use '''which'''.

<pre>
which lightdm
</pre>

If not, install it with '''apt'''.

<pre>
apt install lightdm
</pre>

Create a custom configuration file called '''50-myconfig.conf''' using '''nano''' or other CLI text editor.

<pre>
mkdir /etc/lightdm/lightdm.conf.d/
nano /etc/lightdm/lightdm.conf.d/50-myconfig.conf
</pre>

Inside this new file add the following text.

<pre>
[SeatDefaults]
autologin-user=kodi
</pre>

On Raspbian, you can configure LightDM differently for autologin to boot directly to Kodi.

<pre>
nano /etc/lightdm/lightdm.conf
</pre>

Uncomment the following line.

<pre>
#autologin-user=
</pre>

And add the user you want to autologin and autostart Kodi. The user is named '''kodi''' in this example.

<pre>
autologin-user=kodi
</pre>

You can alternately create /etc/lightdm/lightdm.conf.d/50-myconfig.conf, but should still ensure the settings in /etc/lightdm/lightdm.conf agree.

== Configure Kodi to autostart ==

Configure Kodi to autostart.

<pre>
mkdir -p ~/.config/autostart
ln -s /usr/bin/kodi ~/.config/autostart
</pre>

This method of autostart requires a desktop environment or DE. This is done a bit differently by each DE. Some helpful links can easily be found in today's Web search using any search engine.

[http://edoceo.com/gui/xfce-autostart-apps Autostart Apps in XFCE]

The Raspberry Pi is a bit more of a tweak, but these are excellent links that will tell you how. The first link is the most helpful to making sure Kodi autostarts in Pi, and utilizes a '''crontab'''. There are many settings on the Pi that control boot, and the first link gives the best most trouble-free way to boot directly to Kodi.

[https://www.leowkahman.com/2016/03/05/lamp-stack-on-raspberry-pi-with-kodi-running-at-startup/ LAMP stack on Raspberry Pi with Kodi running at startup]

In the above link, the author describes using Crontab (short for "Cron table") to boot directly to Kodi.

<pre>
crontab -e
</pre>

Cron will ask you to choose a text editor from available options. I choose option 2 for '''nano'''.

In the new Crontab, enter the following text.

<pre>
@reboot kodi --standalone
</pre>

You could also consider using Crontab to run a script, much like described on this page in the section entitled "Run kodi in a window manager" if you scroll down the page.

[https://wiki.archlinux.org/index.php/Kodi Kodi - Run kodi in a window manager]

Instead your Crontab could look like this.

<pre>
@reboot startx
</pre>

And create an '''~/.xinitrc''' file.

<pre>
nano ~/.xinitrc
</pre>

The '''~/.xinitrc''' file should look like this.

<pre>
#!/bin/bash
kodi-standalone
sudo chvt 2
sleep 1
sudo chvt 1
</pre>

Make sure to make '''~/.xinitrc''' executable by running.

<pre>
chmod +x ~/.xinitrc
</pre>

To ensure no password is required by '''sudo''' for any user logging in when this script runs, you must edit /etc/sudoers or run the '''visudo''' command if it is installed to edit /etc/sudoers. You can install '''visudo''' from your Linux distributions default repository.

<pre>
apt install visudo
</pre>

For any non-root users, create an entry in this file like shown here.

<pre>
kodi ALL=NOPASSWD: /usr/bin/chvt
pi ALL=NOPASSWD: /usr/bin/chvt
</pre>

The above example is for users '''pi''' and '''kodi'''.

If you decide not use a Cron table, you can always remove it again.

<pre>
crontab -r
</pre>

This is a quick reference for Crontab.

[http://www.adminschoice.com/crontab-quick-reference Crontab Quick Reference]

These linked pages facilitate more tweaks and settings relevant to other uses of the X Window System on Pi.

[http://ozzmaker.com/enable-x-windows-on-piscreen/ Enable X Window System on PiScreen]

[https://raspberrypi.stackexchange.com/questions/59310/remove-boot-messages-all-text-in-jessie Remove boot messages all text in Raspbian - Raspberry Pi Stack Exchange]

[https://raspberrypi.stackexchange.com/questions/47823/how-to-prevent-autologin-of-gui How to prevent or allow autologin of GUI - Raspberry Pi Stack Exchange]

[http://www.raspberry-projects.com/pi/pi-operating-systems/raspbian/auto-running-programs-gui Auto running programs LXDE - Raspberry Pi Projects]

And, if you would rather, it is easier to follow the process provided by this link to modify the Raspbian image before installing it onto the microSD card.

[https://wiki.debian.org/RaspberryPi/qemu-user-static Modifying Raspbian with qemu-user-static]

The above link describes removing the DE from a Raspbian image, though Raspbian Lite is a much better starting point for using Qemu for this purpose.

You can also use the X11 Window System to autostart Kodi by placing a statup script in the /etc/X11/Xsession.d/ directory.

[https://debian-administration.org/article/50/Running_applications_automatically_when_X_starts Running applications automatically when X starts]

<pre>
nano /etc/X11/Xsession.d/startup-local
</pre>

Insert this text into the new file. Use CTRL + O + Enter + X to save the file.

<pre>
#!/bin/sh
/usr/bin/kodi
</pre>

If you have a WM, such as Blackbox you can add it here as well.

<pre>
#!/bin/sh
blackbox &
/usr/bin/kodi
</pre>

Set permissions to make it executable. Use the ampersand to run an application in the background, such as a WM you only need to for the purpose of launching Kodi but not if you don't want to use the WM itself. Kodi will not launch without a DE or WM, but placing the ampersand "&" at the end of the command makes it run in the background where it can do its job out of sight. Also, make sure to start a WM or DE before running an application in the foreground. This is not necessary for apps running in the background.

<pre>
chmod 755 /etc/X11/Xsession.d/startup-local
</pre>

If Kodi is not installed at the standard path, find it using the '''which''' command.

<pre>
which kodi
</pre>

This feature is available on X Window System operating systems most Linux distributions use the X Window System.

== Disable / enable the login prompt ==

You can disable the graphical login prompt.

<pre>
systemctl set-default multi-user.target
</pre>

To enable it again use.

<pre>
systemctl set-default graphical.target
</pre>

If you are using an autologin method associated with your DE or WM, you '''do not''' want to disable the graphical login.

Even if you are using something like [https://github.com/graysky2/kodi-standalone-service Kodi Standalone Service], you still need use a WM or a DE that installs the '''x-window-manager''' software package.

To ensure you have this installed use the '''which''' command.

<pre>
which x-window-manager
</pre>

If there is no such package, you can use '''apt''' to search your Linux distributions repository.

<pre>
apt-cache search x-window-manager
</pre>

This will general a list of packages containing '''x-window-manager''', which cannot be installed alone. If you are not using a DE, you need to use a WM. And, you can also use a compositing WM like Compiz, for fast 3D effects.

[https://wiki.archlinux.org/index.php/Compiz Compiz - ArchWiki]

A note on using Kodi Standalone Service, this package runs Kodi as a '''systemd''' service and disables the login for user '''kodi''' and will not work when autologin is enabled. In fact, it will break the login process if you autologin user '''kodi''' and run Kodi Standalone Service at the same time. This package is installed automatically with the standard Kodi package when you install Kodi on Raspbian, but must be configured manually for all other Linux distributions. You can run the '''which''' command to find this package as well.

<pre>
which kodi-standalone
</pre>

Be advised, Kodi Standalone Service still launches the Kodi GUI and still requires a WM even though it is running as a '''systemd''' service. When you install a WM such as '''xfwm4''' (the WM for XFCE4), the CLI will tell you if it provides the '''x-window-manager''' package.

<pre>
Setting up xfwm4 (4.12.4-1) ...
update-alternatives: using /usr/bin/xfwm4 to provide /usr/bin/x-window-manager (x-window-manager) in auto mode
</pre>

If you do not see this message at the end of the installation, the WM you selected does not provide this software package and may not actually be a complete WM itself but only part of a package containing a WM.

For a great example on exactly how you would do this with '''xfwm4''', see this ArchWiki entry.

[https://wiki.archlinux.org/index.php/Xfwm XFWM - ArchWiki]

== Create custom Xsession script ==

Most systems utilize the client version of the X11 software an Xsession requires requires.

Upgrade to the server versions of the X Window System, if you want to utilize all the greatness of the X Window System.

Because of the lack of documentation, it is probably better to find tweaks and hacks on wikis and support pages rather than forums. For instance, the Ubuntu wiki is usually a good source of information.

[https://wiki.ubuntu.com/CustomXSession CustomXSession - Ubuntu Wiki]

<pre>apt install xauth xorg xinit xserver-xorg-core xserver-xorg xserver-common</pre>

To create a custom Xsession script with a text editor we start with an '''xinitrc''' script. For more detail on how to create and use '''xinit''', there is a great guide available here.

[https://en.wikibooks.org/wiki/Guide_to_X11/Starting_Sessions Guide to X11 - Starting Sessions - WikiBooks]

<pre>
nano ~/.xinitrc
</pre>

To run Kodi full-screen make sure the text reads:

<pre>
#!/usr/bin/env bash
exec gnome-session
/usr/bin/kodi -fs
</pre>

Replace the '''gnome-session''' with the DE or WM command you are using. See the last section for examples.

To make '''~/.xinitrc''' executable use.

<pre>
chmod +x ~/.xinitrc
</pre>

Use '''sudo''' and the '''~/.xinitrc''' file to configure '''~/.xsession'''.

<pre>
sudo -H -u kodi bash -c "ln -s ~/.xinitrc /home/kodi/.xsession"
</pre>

Make sure the path goes to user's home directory. In this example, the user is '''kodi'''.

You need to use '''sudo''' to run this command. If you do not have '''sudo''', install it.

<pre>
apt install sudo
</pre>

If you create a symbolic link and want to remove it, simply remove the existing '''.xsession''' file you created.

<pre>
rm /home/kodi/.xsession
</pre>

On some systems using a DE such as Gnome, not all systems using Gnome, it may be necessary for '''.xsession''' to be '''.xsessionrc'''. Though this is more likely the case for organization network computers than a personal one, where configurations may vary on a diversity of machines. Most of the time, it will be '''.xsession''' rather than '''.xsessionrc''' that you want to create.

You can also create the '''.xsession''' script directly in the home directory, rather than link it from '''~/.xinitrc'''. This is necessary if you create multiple custom Xsession scripts for multiple users, and you do not in that case link '''~/.xinitrc''' to '''.xsession'''.

You must also autostart the X Window system, which differs somewhat from scenario to scenario. For most setups, all that is necessary is to edit the '''.bashrc''' file.

<pre>
nano ~/.bashrc
</pre>

Add the following as shown.

<pre>
if [[ ! $DISPLAY && $XDG_VTNR -eq 1 ]]; then
exec startx
fi
</pre>

If you wish to remain logged in after quitting X, remove the '''exec''' from the above. Other configurations can be applied, but are irrelevant to autostarting Kodi.

[https://wiki.archlinux.org/index.php/Xinit#Autostart_X_at_login Xinit Autostart X at login]

If you are using LightDM and you just want to create a new login entry for user '''kodi''', you must create a new file.

<pre>
nano /usr/share/xsessions/custom.desktop
</pre>

And insert the following text.

<pre>
[Desktop Entry]
Name=Xsession
Exec=/etc/X11/Xsession
</pre>

This will create a new login option for the custom Xsession. Only this one entry is necessary for LightDM and X11 to find the '''~/.xsession''' script in each user's home directory.

== Xsession to boot to app / WM / DE ==

You can use any window manager or desktop enviroment with a custom Xsession script as long as it is intalled.

You do this by creating '''~/.xinitrc''' script that contains the command to start the WM or DE.

For instance, if you are using FluxBox.

<pre>
#!/usr/bin/env bash
exec fluxbox &
/usr/bin/kodi -fs
</pre>

The <code>-fs</code> option is full-screen.

To run Gnome in the background, but launch Kodi in the foreground.

<pre>
#!/usr/bin/env bash
exec gnome-session &
/usr/bin/kodi -fs
</pre>

Use the '''~/.xinitrc''' file to configure '''~/.xsession''' to create a custom login for any user, not just Kodi.

<pre>
sudo -H -u [username] bash -c "ln -s ~/.xinitrc ~/.xsession"
</pre>

You must reconfigure Xserver for any user that is not a privileged user to be able to start a custom Xsession.

<pre>
dpkg-reconfigure xserver-xorg-legacy
</pre>

And / or...

<pre>
dpkg-reconfigure xserver-xorg
</pre>

If both packages are installed, you must reconfigure both. Not all systems will use or require the legacy package to allow non-root users to start X.

== Add a custom Grub entry ==

If you want to boot to the CLI and manually launch an app or boot directly to Kodi without a DE or WM, add a custom grub entry.

The right way to add a custom grub entry is to copy the menu entry you want to change or duplicate.

Copy the default Grub configuration file and open it with a text editor on your desktop. If you use a text editor on the CLI, the text will be cut off by the window when copying and pasting.

<pre>
cp /boot/grub/grub.cfg grub.cfg
gedit grub.cfg
</pre>

Copy the menu entry and paste it into '''40_custom''' with a text editor in the CLI.

<pre>
nano /etc/grub.d/40_custom
</pre>

Where the menu entry contains '''quiet splash''' change it to '''text''' instead.

You should also change the name of the entry!

I just appended mine with “CLI” for command line interface.

To update Grub:

<pre>
update-grub
</pre>

To launch a WM you can type its name. I use Enlightment 17 or Fluxbox. It must be installed.

<pre>
fluxbox
</pre>

You must have FluxBox installed. There are countless other window managers.

To launch a DE you enter the appropriate command. For Gnome desktop:

<pre>
gnome-session
</pre>

For KDE:

<pre>
startkde
</pre>

or

<pre>
plasma-desktop
</pre>

For XFCE:

<pre>
startxfce4
</pre>

For Mate:

<pre>
mate-session
</pre>

For LXDE:

<pre>
startlxde
</pre>

You can either manually launch your apps, boot right into them, or create an Xsession for each user. This is great when you want to create a Kodi user for running Kodi only, and for making sure you can still login to your DE with your regular user account. You can boot to any app full-screen this way, not just Kodi. You can create a custom Xsession script for any user, configured with any startup applications running in full-screen mode or normally.

By optionally creating a Grub menu entry, you can create a different Grub menu selection to boot only to the CLI and start an Xsession with a script or run commands manually.

HOW-TO:Autostart Kodi for Linux

2018-04-29T11:45:58Z

W3tech: /* Configure Kodi to autostart */ More how-to clarification

<section begin="intro" /><big>Any or all or any combination of these methods can be used to configure a Debian-based X Window System to boot directly to Kodi. This should work on any Linux using the X Window System, but these instructions are particular to Debian derivatives, such as Ubuntu. A server edition is best for running only Kodi, but this page assumes booting into a desktop OS, not a server distro. However, the instructions here can be used for a server distro with even less configuration than for a desktop. Experiment inside VirtualBox before you apply any of these to your system and make a backup.</big><section end="intro" />

__TOC__

== Switch to root ==

<pre>
su
</pre>

or

<pre>
sudo su
</pre>

== Create a Kodi user ==

To use Kodi full-screen, you only have to create a standard user.

<pre>
adduser kodi
</pre>

To remove the password use:

<pre>
passwd -d kodi
</pre>

== Customize LightDM to autologin ==

You can utilize the ability to customize LightDM data manager by changing the builtin custom configuration file '''50-myconfig.conf''' using '''nano''' or another text editor. If you have no DE or WM you can install '''lightdm''', but should make sure to do a bit of research before you do. Most versions of Linux use LightDM, but many server versions do not. For Ubuntu Server with no DE, for example, installing '''lightdm''' is okay and necessary. Changing the behavior of LightDM is done using a custom '''50-myconfig.conf''' configuration file.

To see if you have '''lightdm''' use '''which'''.

<pre>
which lightdm
</pre>

If not, install it with '''apt'''.

<pre>
apt install lightdm
</pre>

Create a custom configuration file called '''50-myconfig.conf''' using '''nano''' or other CLI text editor.

<pre>
mkdir /etc/lightdm/lightdm.conf.d/
nano /etc/lightdm/lightdm.conf.d/50-myconfig.conf
</pre>

Inside this new file add the following text.

<pre>
[SeatDefaults]
autologin-user=kodi
</pre>

On Raspbian, you can configure LightDM differently for autologin to boot directly to Kodi.

<pre>
nano /etc/lightdm/lightdm.conf
</pre>

Uncomment the following line.

<pre>
#autologin-user=
</pre>

And add the user you want to autologin and autostart Kodi. The user is named '''kodi''' in this example.

<pre>
autologin-user=kodi
</pre>

You can alternately create /etc/lightdm/lightdm.conf.d/50-myconfig.conf, but should still ensure the settings in /etc/lightdm/lightdm.conf agree.

== Configure Kodi to autostart ==

Configure Kodi to autostart.

<pre>
mkdir -p ~/.config/autostart
ln -s /usr/bin/kodi ~/.config/autostart
</pre>

This method of autostart requires a desktop environment or DE. This is done a bit differently by each DE. Some helpful links can easily be found in today's Web search using any search engine.

[http://edoceo.com/gui/xfce-autostart-apps Autostart Apps in XFCE]

The Raspberry Pi is a bit more of a tweak, but these are excellent links that will tell you how. The first link is the most helpful to making sure Kodi autostarts in Pi, and utilizes a '''crontab'''. There are many settings on the Pi that control boot, and the first link gives the best most trouble-free way to boot directly to Kodi.

[https://www.leowkahman.com/2016/03/05/lamp-stack-on-raspberry-pi-with-kodi-running-at-startup/ LAMP stack on Raspberry Pi with Kodi running at startup]

In the above link, the author describes using Crontab (short for "Cron table") to boot directly to Kodi.

<pre>
crontab -e
</pre>

Cron will ask you to choose a text editor from available options. I choose option 2 for '''nano'''.

In the new Crontab, enter the following text.

<pre>
@reboot kodi --standalone
</pre>

You could also consider using Crontab to run a script, much like described on this page in the section entitled "Run kodi in a window manager" if you scroll down the page.

[https://wiki.archlinux.org/index.php/Kodi Kodi - Run kodi in a window manager]

Instead your Crontab could look like this.

<pre>
@reboot startx
</pre>

And your '''.xinitrc''' should look like this.

<pre>
#!/bin/bash
kodi-standalone
sudo chvt 2
sleep 1
sudo chvt 1
</pre>

To ensure no password is required by '''sudo''' for any user logging in when this script runs, you must edit /etc/sudoers or run the '''visudo''' command if it is installed to edit /etc/sudoers. You can install '''visudo''' from your Linux distributions default repository.

<pre>
apt install visudo
</pre>

For any non-root users, create an entry in this file like shown here.

<pre>
kodi ALL=NOPASSWD: /usr/bin/chvt
pi ALL=NOPASSWD: /usr/bin/chvt
</pre>

The above example is for users '''pi''' and '''kodi'''.

If you decide not use a Cron table, you can always remove it again.

<pre>
crontab -r
</pre>

This is a quick reference for Crontab.

[http://www.adminschoice.com/crontab-quick-reference Crontab Quick Reference]

These linked pages facilitate more tweaks and settings relevant to other uses of the X Window System on Pi.

[http://ozzmaker.com/enable-x-windows-on-piscreen/ Enable X Window System on PiScreen]

[https://raspberrypi.stackexchange.com/questions/59310/remove-boot-messages-all-text-in-jessie Remove boot messages all text in Raspbian - Raspberry Pi Stack Exchange]

[https://raspberrypi.stackexchange.com/questions/47823/how-to-prevent-autologin-of-gui How to prevent or allow autologin of GUI - Raspberry Pi Stack Exchange]

[http://www.raspberry-projects.com/pi/pi-operating-systems/raspbian/auto-running-programs-gui Auto running programs LXDE - Raspberry Pi Projects]

And, if you would rather, it is easier to follow the process provided by this link to modify the Raspbian image before installing it onto the microSD card.

[https://wiki.debian.org/RaspberryPi/qemu-user-static Modifying Raspbian with qemu-user-static]

The above link describes removing the DE from a Raspbian image, though Raspbian Lite is a much better starting point for using Qemu for this purpose.

You can also use the X11 Window System to autostart Kodi by placing a statup script in the /etc/X11/Xsession.d/ directory.

[https://debian-administration.org/article/50/Running_applications_automatically_when_X_starts Running applications automatically when X starts]

<pre>
nano /etc/X11/Xsession.d/startup-local
</pre>

Insert this text into the new file. Use CTRL + O + Enter + X to save the file.

<pre>
#!/bin/sh
/usr/bin/kodi
</pre>

If you have a WM, such as Blackbox you can add it here as well.

<pre>
#!/bin/sh
blackbox &
/usr/bin/kodi
</pre>

Set permissions to make it executable. Use the ampersand to run an application in the background, such as a WM you only need to for the purpose of launching Kodi but not if you don't want to use the WM itself. Kodi will not launch without a DE or WM, but placing the ampersand "&" at the end of the command makes it run in the background where it can do its job out of sight. Also, make sure to start a WM or DE before running an application in the foreground. This is not necessary for apps running in the background.

<pre>
chmod 755 /etc/X11/Xsession.d/startup-local
</pre>

If Kodi is not installed at the standard path, find it using the '''which''' command.

<pre>
which kodi
</pre>

This feature is available on X Window System operating systems most Linux distributions use the X Window System.

== Disable / enable the login prompt ==

You can disable the graphical login prompt.

<pre>
systemctl set-default multi-user.target
</pre>

To enable it again use.

<pre>
systemctl set-default graphical.target
</pre>

If you are using an autologin method associated with your DE or WM, you '''do not''' want to disable the graphical login.

Even if you are using something like [https://github.com/graysky2/kodi-standalone-service Kodi Standalone Service], you still need use a WM or a DE that installs the '''x-window-manager''' software package.

To ensure you have this installed use the '''which''' command.

<pre>
which x-window-manager
</pre>

If there is no such package, you can use '''apt''' to search your Linux distributions repository.

<pre>
apt-cache search x-window-manager
</pre>

This will general a list of packages containing '''x-window-manager''', which cannot be installed alone. If you are not using a DE, you need to use a WM. And, you can also use a compositing WM like Compiz, for fast 3D effects.

[https://wiki.archlinux.org/index.php/Compiz Compiz - ArchWiki]

A note on using Kodi Standalone Service, this package runs Kodi as a '''systemd''' service and disables the login for user '''kodi''' and will not work when autologin is enabled. In fact, it will break the login process if you autologin user '''kodi''' and run Kodi Standalone Service at the same time. This package is installed automatically with the standard Kodi package when you install Kodi on Raspbian, but must be configured manually for all other Linux distributions. You can run the '''which''' command to find this package as well.

<pre>
which kodi-standalone
</pre>

Be advised, Kodi Standalone Service still launches the Kodi GUI and still requires a WM even though it is running as a '''systemd''' service. When you install a WM such as '''xfwm4''' (the WM for XFCE4), the CLI will tell you if it provides the '''x-window-manager''' package.

<pre>
Setting up xfwm4 (4.12.4-1) ...
update-alternatives: using /usr/bin/xfwm4 to provide /usr/bin/x-window-manager (x-window-manager) in auto mode
</pre>

If you do not see this message at the end of the installation, the WM you selected does not provide this software package and may not actually be a complete WM itself but only part of a package containing a WM.

For a great example on exactly how you would do this with '''xfwm4''', see this ArchWiki entry.

[https://wiki.archlinux.org/index.php/Xfwm XFWM - ArchWiki]

== Create custom Xsession script ==

Most systems utilize the client version of the X11 software an Xsession requires requires.

Upgrade to the server versions of the X Window System, if you want to utilize all the greatness of the X Window System.

Because of the lack of documentation, it is probably better to find tweaks and hacks on wikis and support pages rather than forums. For instance, the Ubuntu wiki is usually a good source of information.

[https://wiki.ubuntu.com/CustomXSession CustomXSession - Ubuntu Wiki]

<pre>apt install xauth xorg xinit xserver-xorg-core xserver-xorg xserver-common</pre>

To create a custom Xsession script with a text editor we start with an '''xinitrc''' script. For more detail on how to create and use '''xinit''', there is a great guide available here.

[https://en.wikibooks.org/wiki/Guide_to_X11/Starting_Sessions Guide to X11 - Starting Sessions - WikiBooks]

<pre>
nano ~/.xinitrc
</pre>

To run Kodi full-screen make sure the text reads:

<pre>
#!/usr/bin/env bash
exec gnome-session
/usr/bin/kodi -fs
</pre>

Replace the '''gnome-session''' with the DE or WM command you are using. See the last section for examples.

To make '''~/.xinitrc''' executable use.

<pre>
chmod +x ~/.xinitrc
</pre>

Use '''sudo''' and the '''~/.xinitrc''' file to configure '''~/.xsession'''.

<pre>
sudo -H -u kodi bash -c "ln -s ~/.xinitrc /home/kodi/.xsession"
</pre>

Make sure the path goes to user's home directory. In this example, the user is '''kodi'''.

You need to use '''sudo''' to run this command. If you do not have '''sudo''', install it.

<pre>
apt install sudo
</pre>

If you create a symbolic link and want to remove it, simply remove the existing '''.xsession''' file you created.

<pre>
rm /home/kodi/.xsession
</pre>

On some systems using a DE such as Gnome, not all systems using Gnome, it may be necessary for '''.xsession''' to be '''.xsessionrc'''. Though this is more likely the case for organization network computers than a personal one, where configurations may vary on a diversity of machines. Most of the time, it will be '''.xsession''' rather than '''.xsessionrc''' that you want to create.

You can also create the '''.xsession''' script directly in the home directory, rather than link it from '''~/.xinitrc'''. This is necessary if you create multiple custom Xsession scripts for multiple users, and you do not in that case link '''~/.xinitrc''' to '''.xsession'''.

You must also autostart the X Window system, which differs somewhat from scenario to scenario. For most setups, all that is necessary is to edit the '''.bashrc''' file.

<pre>
nano ~/.bashrc
</pre>

Add the following as shown.

<pre>
if [[ ! $DISPLAY && $XDG_VTNR -eq 1 ]]; then
exec startx
fi
</pre>

If you wish to remain logged in after quitting X, remove the '''exec''' from the above. Other configurations can be applied, but are irrelevant to autostarting Kodi.

[https://wiki.archlinux.org/index.php/Xinit#Autostart_X_at_login Xinit Autostart X at login]

If you are using LightDM and you just want to create a new login entry for user '''kodi''', you must create a new file.

<pre>
nano /usr/share/xsessions/custom.desktop
</pre>

And insert the following text.

<pre>
[Desktop Entry]
Name=Xsession
Exec=/etc/X11/Xsession
</pre>

This will create a new login option for the custom Xsession. Only this one entry is necessary for LightDM and X11 to find the '''~/.xsession''' script in each user's home directory.

== Xsession to boot to app / WM / DE ==

You can use any window manager or desktop enviroment with a custom Xsession script as long as it is intalled.

You do this by creating '''~/.xinitrc''' script that contains the command to start the WM or DE.

For instance, if you are using FluxBox.

<pre>
#!/usr/bin/env bash
exec fluxbox &
/usr/bin/kodi -fs
</pre>

The <code>-fs</code> option is full-screen.

To run Gnome in the background, but launch Kodi in the foreground.

<pre>
#!/usr/bin/env bash
exec gnome-session &
/usr/bin/kodi -fs
</pre>

Use the '''~/.xinitrc''' file to configure '''~/.xsession''' to create a custom login for any user, not just Kodi.

<pre>
sudo -H -u [username] bash -c "ln -s ~/.xinitrc ~/.xsession"
</pre>

You must reconfigure Xserver for any user that is not a privileged user to be able to start a custom Xsession.

<pre>
dpkg-reconfigure xserver-xorg-legacy
</pre>

And / or...

<pre>
dpkg-reconfigure xserver-xorg
</pre>

If both packages are installed, you must reconfigure both. Not all systems will use or require the legacy package to allow non-root users to start X.

== Add a custom Grub entry ==

If you want to boot to the CLI and manually launch an app or boot directly to Kodi without a DE or WM, add a custom grub entry.

The right way to add a custom grub entry is to copy the menu entry you want to change or duplicate.

Copy the default Grub configuration file and open it with a text editor on your desktop. If you use a text editor on the CLI, the text will be cut off by the window when copying and pasting.

<pre>
cp /boot/grub/grub.cfg grub.cfg
gedit grub.cfg
</pre>

Copy the menu entry and paste it into '''40_custom''' with a text editor in the CLI.

<pre>
nano /etc/grub.d/40_custom
</pre>

Where the menu entry contains '''quiet splash''' change it to '''text''' instead.

You should also change the name of the entry!

I just appended mine with “CLI” for command line interface.

To update Grub:

<pre>
update-grub
</pre>

To launch a WM you can type its name. I use Enlightment 17 or Fluxbox. It must be installed.

<pre>
fluxbox
</pre>

You must have FluxBox installed. There are countless other window managers.

To launch a DE you enter the appropriate command. For Gnome desktop:

<pre>
gnome-session
</pre>

For KDE:

<pre>
startkde
</pre>

or

<pre>
plasma-desktop
</pre>

For XFCE:

<pre>
startxfce4
</pre>

For Mate:

<pre>
mate-session
</pre>

For LXDE:

<pre>
startlxde
</pre>

You can either manually launch your apps, boot right into them, or create an Xsession for each user. This is great when you want to create a Kodi user for running Kodi only, and for making sure you can still login to your DE with your regular user account. You can boot to any app full-screen this way, not just Kodi. You can create a custom Xsession script for any user, configured with any startup applications running in full-screen mode or normally.

By optionally creating a Grub menu entry, you can create a different Grub menu selection to boot only to the CLI and start an Xsession with a script or run commands manually.

HOW-TO:Autostart Kodi for Linux

2018-04-29T10:54:29Z

W3tech: /* Configure Kodi to autostart */

<section begin="intro" /><big>Any or all or any combination of these methods can be used to configure a Debian-based X Window System to boot directly to Kodi. This should work on any Linux using the X Window System, but these instructions are particular to Debian derivatives, such as Ubuntu. A server edition is best for running only Kodi, but this page assumes booting into a desktop OS, not a server distro. However, the instructions here can be used for a server distro with even less configuration than for a desktop. Experiment inside VirtualBox before you apply any of these to your system and make a backup.</big><section end="intro" />

__TOC__

== Switch to root ==

<pre>
su
</pre>

or

<pre>
sudo su
</pre>

== Create a Kodi user ==

To use Kodi full-screen, you only have to create a standard user.

<pre>
adduser kodi
</pre>

To remove the password use:

<pre>
passwd -d kodi
</pre>

== Customize LightDM to autologin ==

You can utilize the ability to customize LightDM data manager by changing the builtin custom configuration file '''50-myconfig.conf''' using '''nano''' or another text editor. If you have no DE or WM you can install '''lightdm''', but should make sure to do a bit of research before you do. Most versions of Linux use LightDM, but many server versions do not. For Ubuntu Server with no DE, for example, installing '''lightdm''' is okay and necessary. Changing the behavior of LightDM is done using a custom '''50-myconfig.conf''' configuration file.

To see if you have '''lightdm''' use '''which'''.

<pre>
which lightdm
</pre>

If not, install it with '''apt'''.

<pre>
apt install lightdm
</pre>

Create a custom configuration file called '''50-myconfig.conf''' using '''nano''' or other CLI text editor.

<pre>
mkdir /etc/lightdm/lightdm.conf.d/
nano /etc/lightdm/lightdm.conf.d/50-myconfig.conf
</pre>

Inside this new file add the following text.

<pre>
[SeatDefaults]
autologin-user=kodi
</pre>

On Raspbian, you can configure LightDM differently for autologin to boot directly to Kodi.

<pre>
nano /etc/lightdm/lightdm.conf
</pre>

Uncomment the following line.

<pre>
#autologin-user=
</pre>

And add the user you want to autologin and autostart Kodi. The user is named '''kodi''' in this example.

<pre>
autologin-user=kodi
</pre>

You can alternately create /etc/lightdm/lightdm.conf.d/50-myconfig.conf, but should still ensure the settings in /etc/lightdm/lightdm.conf agree.

== Configure Kodi to autostart ==

Configure Kodi to autostart.

<pre>
mkdir -p ~/.config/autostart
ln -s /usr/bin/kodi ~/.config/autostart
</pre>

This method of autostart requires a desktop environment or DE. This is done a bit differently by each DE. Some helpful links can easily be found in today's Web search using any search engine.

[http://edoceo.com/gui/xfce-autostart-apps Autostart Apps in XFCE]

The Raspberry Pi is a bit more of a tweak, but these are excellent links that will tell you how. The first link is the most helpful to making sure Kodi autostarts in Pi, and utilizes a '''crontab'''. There are many settings on the Pi that control boot, and the first link gives the best most trouble-free way to boot directly to Kodi.

[https://www.leowkahman.com/2016/03/05/lamp-stack-on-raspberry-pi-with-kodi-running-at-startup/ LAMP stack on Raspberry Pi with Kodi running at startup]

In the above link, the author describes using Crontab (short for "Cron table") to boot directly to Kodi.

<pre>
crontab -e
</pre>

Cron will ask you to choose a text editor from available options. I choose option 2 for '''nano'''.

In the new Crontab, enter the following text.

<pre>
@reboot kodi --standalone
</pre>

You should also consider adding a shutdown script, much like described on this page.

[https://www.vdr-portal.de/forum/index.php?thread/128602-kodi-vdr-shutdown-handling/&pageNo=1 Kodi VDR shutdown handling]

If you decide not use a Cron table, you can always remove it again.

<pre>
crontab -r
</pre>

This is a quick reference for Crontab.

[http://www.adminschoice.com/crontab-quick-reference Crontab Quick Reference]

These linked pages facilitate more tweaks and settings relevant to other uses of the X Window System on Pi.

[http://ozzmaker.com/enable-x-windows-on-piscreen/ Enable X Window System on PiScreen]

[https://raspberrypi.stackexchange.com/questions/59310/remove-boot-messages-all-text-in-jessie Remove boot messages all text in Raspbian - Raspberry Pi Stack Exchange]

[https://raspberrypi.stackexchange.com/questions/47823/how-to-prevent-autologin-of-gui How to prevent or allow autologin of GUI - Raspberry Pi Stack Exchange]

[http://www.raspberry-projects.com/pi/pi-operating-systems/raspbian/auto-running-programs-gui Auto running programs LXDE - Raspberry Pi Projects]

And, if you would rather, it is easier to follow the process provided by this link to modify the Raspbian image before installing it onto the microSD card.

[https://wiki.debian.org/RaspberryPi/qemu-user-static Modifying Raspbian with qemu-user-static]

The above link describes removing the DE from a Raspbian image, though Raspbian Lite is a much better starting point for using Qemu for this purpose.

You can also use the X11 Window System to autostart Kodi by placing a statup script in the /etc/X11/Xsession.d/ directory.

[https://debian-administration.org/article/50/Running_applications_automatically_when_X_starts Running applications automatically when X starts]

<pre>
nano /etc/X11/Xsession.d/startup-local
</pre>

Insert this text into the new file. Use CTRL + O + Enter + X to save the file.

<pre>
#!/bin/sh
/usr/bin/kodi
</pre>

If you have a WM, such as Blackbox you can add it here as well.

<pre>
#!/bin/sh
blackbox &
/usr/bin/kodi
</pre>

Set permissions to make it executable. Use the ampersand to run an application in the background, such as a WM you only need to for the purpose of launching Kodi but not if you don't want to use the WM itself. Kodi will not launch without a DE or WM, but placing the ampersand "&" at the end of the command makes it run in the background where it can do its job out of sight. Also, make sure to start a WM or DE before running an application in the foreground. This is not necessary for apps running in the background.

<pre>
chmod 755 /etc/X11/Xsession.d/startup-local
</pre>

If Kodi is not installed at the standard path, find it using the '''which''' command.

<pre>
which kodi
</pre>

This feature is available on X Window System operating systems most Linux distributions use the X Window System.

== Disable / enable the login prompt ==

You can disable the graphical login prompt.

<pre>
systemctl set-default multi-user.target
</pre>

To enable it again use.

<pre>
systemctl set-default graphical.target
</pre>

If you are using an autologin method associated with your DE or WM, you '''do not''' want to disable the graphical login.

Even if you are using something like [https://github.com/graysky2/kodi-standalone-service Kodi Standalone Service], you still need use a WM or a DE that installs the '''x-window-manager''' software package.

To ensure you have this installed use the '''which''' command.

<pre>
which x-window-manager
</pre>

If there is no such package, you can use '''apt''' to search your Linux distributions repository.

<pre>
apt-cache search x-window-manager
</pre>

This will general a list of packages containing '''x-window-manager''', which cannot be installed alone. If you are not using a DE, you need to use a WM. And, you can also use a compositing WM like Compiz, for fast 3D effects.

[https://wiki.archlinux.org/index.php/Compiz Compiz - ArchWiki]

A note on using Kodi Standalone Service, this package runs Kodi as a '''systemd''' service and disables the login for user '''kodi''' and will not work when autologin is enabled. In fact, it will break the login process if you autologin user '''kodi''' and run Kodi Standalone Service at the same time. This package is installed automatically with the standard Kodi package when you install Kodi on Raspbian, but must be configured manually for all other Linux distributions. You can run the '''which''' command to find this package as well.

<pre>
which kodi-standalone
</pre>

Be advised, Kodi Standalone Service still launches the Kodi GUI and still requires a WM even though it is running as a '''systemd''' service. When you install a WM such as '''xfwm4''' (the WM for XFCE4), the CLI will tell you if it provides the '''x-window-manager''' package.

<pre>
Setting up xfwm4 (4.12.4-1) ...
update-alternatives: using /usr/bin/xfwm4 to provide /usr/bin/x-window-manager (x-window-manager) in auto mode
</pre>

If you do not see this message at the end of the installation, the WM you selected does not provide this software package and may not actually be a complete WM itself but only part of a package containing a WM.

For a great example on exactly how you would do this with '''xfwm4''', see this ArchWiki entry.

[https://wiki.archlinux.org/index.php/Xfwm XFWM - ArchWiki]

== Create custom Xsession script ==

Most systems utilize the client version of the X11 software an Xsession requires requires.

Upgrade to the server versions of the X Window System, if you want to utilize all the greatness of the X Window System.

Because of the lack of documentation, it is probably better to find tweaks and hacks on wikis and support pages rather than forums. For instance, the Ubuntu wiki is usually a good source of information.

[https://wiki.ubuntu.com/CustomXSession CustomXSession - Ubuntu Wiki]

<pre>apt install xauth xorg xinit xserver-xorg-core xserver-xorg xserver-common</pre>

To create a custom Xsession script with a text editor we start with an '''xinitrc''' script. For more detail on how to create and use '''xinit''', there is a great guide available here.

[https://en.wikibooks.org/wiki/Guide_to_X11/Starting_Sessions Guide to X11 - Starting Sessions - WikiBooks]

<pre>
nano ~/.xinitrc
</pre>

To run Kodi full-screen make sure the text reads:

<pre>
#!/usr/bin/env bash
exec gnome-session
/usr/bin/kodi -fs
</pre>

Replace the '''gnome-session''' with the DE or WM command you are using. See the last section for examples.

To make '''~/.xinitrc''' executable use.

<pre>
chmod +x ~/.xinitrc
</pre>

Use '''sudo''' and the '''~/.xinitrc''' file to configure '''~/.xsession'''.

<pre>
sudo -H -u kodi bash -c "ln -s ~/.xinitrc /home/kodi/.xsession"
</pre>

Make sure the path goes to user's home directory. In this example, the user is '''kodi'''.

You need to use '''sudo''' to run this command. If you do not have '''sudo''', install it.

<pre>
apt install sudo
</pre>

If you create a symbolic link and want to remove it, simply remove the existing '''.xsession''' file you created.

<pre>
rm /home/kodi/.xsession
</pre>

On some systems using a DE such as Gnome, not all systems using Gnome, it may be necessary for '''.xsession''' to be '''.xsessionrc'''. Though this is more likely the case for organization network computers than a personal one, where configurations may vary on a diversity of machines. Most of the time, it will be '''.xsession''' rather than '''.xsessionrc''' that you want to create.

You can also create the '''.xsession''' script directly in the home directory, rather than link it from '''~/.xinitrc'''. This is necessary if you create multiple custom Xsession scripts for multiple users, and you do not in that case link '''~/.xinitrc''' to '''.xsession'''.

You must also autostart the X Window system, which differs somewhat from scenario to scenario. For most setups, all that is necessary is to edit the '''.bashrc''' file.

<pre>
nano ~/.bashrc
</pre>

Add the following as shown.

<pre>
if [[ ! $DISPLAY && $XDG_VTNR -eq 1 ]]; then
exec startx
fi
</pre>

If you wish to remain logged in after quitting X, remove the '''exec''' from the above. Other configurations can be applied, but are irrelevant to autostarting Kodi.

[https://wiki.archlinux.org/index.php/Xinit#Autostart_X_at_login Xinit Autostart X at login]

If you are using LightDM and you just want to create a new login entry for user '''kodi''', you must create a new file.

<pre>
nano /usr/share/xsessions/custom.desktop
</pre>

And insert the following text.

<pre>
[Desktop Entry]
Name=Xsession
Exec=/etc/X11/Xsession
</pre>

This will create a new login option for the custom Xsession. Only this one entry is necessary for LightDM and X11 to find the '''~/.xsession''' script in each user's home directory.

== Xsession to boot to app / WM / DE ==

You can use any window manager or desktop enviroment with a custom Xsession script as long as it is intalled.

You do this by creating '''~/.xinitrc''' script that contains the command to start the WM or DE.

For instance, if you are using FluxBox.

<pre>
#!/usr/bin/env bash
exec fluxbox &
/usr/bin/kodi -fs
</pre>

The <code>-fs</code> option is full-screen.

To run Gnome in the background, but launch Kodi in the foreground.

<pre>
#!/usr/bin/env bash
exec gnome-session &
/usr/bin/kodi -fs
</pre>

Use the '''~/.xinitrc''' file to configure '''~/.xsession''' to create a custom login for any user, not just Kodi.

<pre>
sudo -H -u [username] bash -c "ln -s ~/.xinitrc ~/.xsession"
</pre>

You must reconfigure Xserver for any user that is not a privileged user to be able to start a custom Xsession.

<pre>
dpkg-reconfigure xserver-xorg-legacy
</pre>

And / or...

<pre>
dpkg-reconfigure xserver-xorg
</pre>

If both packages are installed, you must reconfigure both. Not all systems will use or require the legacy package to allow non-root users to start X.

== Add a custom Grub entry ==

If you want to boot to the CLI and manually launch an app or boot directly to Kodi without a DE or WM, add a custom grub entry.

The right way to add a custom grub entry is to copy the menu entry you want to change or duplicate.

Copy the default Grub configuration file and open it with a text editor on your desktop. If you use a text editor on the CLI, the text will be cut off by the window when copying and pasting.

<pre>
cp /boot/grub/grub.cfg grub.cfg
gedit grub.cfg
</pre>

Copy the menu entry and paste it into '''40_custom''' with a text editor in the CLI.

<pre>
nano /etc/grub.d/40_custom
</pre>

Where the menu entry contains '''quiet splash''' change it to '''text''' instead.

You should also change the name of the entry!

I just appended mine with “CLI” for command line interface.

To update Grub:

<pre>
update-grub
</pre>

To launch a WM you can type its name. I use Enlightment 17 or Fluxbox. It must be installed.

<pre>
fluxbox
</pre>

You must have FluxBox installed. There are countless other window managers.

To launch a DE you enter the appropriate command. For Gnome desktop:

<pre>
gnome-session
</pre>

For KDE:

<pre>
startkde
</pre>

or

<pre>
plasma-desktop
</pre>

For XFCE:

<pre>
startxfce4
</pre>

For Mate:

<pre>
mate-session
</pre>

For LXDE:

<pre>
startlxde
</pre>

You can either manually launch your apps, boot right into them, or create an Xsession for each user. This is great when you want to create a Kodi user for running Kodi only, and for making sure you can still login to your DE with your regular user account. You can boot to any app full-screen this way, not just Kodi. You can create a custom Xsession script for any user, configured with any startup applications running in full-screen mode or normally.

By optionally creating a Grub menu entry, you can create a different Grub menu selection to boot only to the CLI and start an Xsession with a script or run commands manually.

HOW-TO:Autostart Kodi for Linux

2018-04-29T09:45:22Z

W3tech: /* Create custom Xsession script */ More clarification. X11 Guide linked.

<section begin="intro" /><big>Any or all or any combination of these methods can be used to configure a Debian-based X Window System to boot directly to Kodi. This should work on any Linux using the X Window System, but these instructions are particular to Debian derivatives, such as Ubuntu. A server edition is best for running only Kodi, but this page assumes booting into a desktop OS, not a server distro. However, the instructions here can be used for a server distro with even less configuration than for a desktop. Experiment inside VirtualBox before you apply any of these to your system and make a backup.</big><section end="intro" />

__TOC__

== Switch to root ==

<pre>
su
</pre>

or

<pre>
sudo su
</pre>

== Create a Kodi user ==

To use Kodi full-screen, you only have to create a standard user.

<pre>
adduser kodi
</pre>

To remove the password use:

<pre>
passwd -d kodi
</pre>

== Customize LightDM to autologin ==

You can utilize the ability to customize LightDM data manager by changing the builtin custom configuration file '''50-myconfig.conf''' using '''nano''' or another text editor. If you have no DE or WM you can install '''lightdm''', but should make sure to do a bit of research before you do. Most versions of Linux use LightDM, but many server versions do not. For Ubuntu Server with no DE, for example, installing '''lightdm''' is okay and necessary. Changing the behavior of LightDM is done using a custom '''50-myconfig.conf''' configuration file.

To see if you have '''lightdm''' use '''which'''.

<pre>
which lightdm
</pre>

If not, install it with '''apt'''.

<pre>
apt install lightdm
</pre>

Create a custom configuration file called '''50-myconfig.conf''' using '''nano''' or other CLI text editor.

<pre>
mkdir /etc/lightdm/lightdm.conf.d/
nano /etc/lightdm/lightdm.conf.d/50-myconfig.conf
</pre>

Inside this new file add the following text.

<pre>
[SeatDefaults]
autologin-user=kodi
</pre>

On Raspbian, you can configure LightDM differently for autologin to boot directly to Kodi.

<pre>
nano /etc/lightdm/lightdm.conf
</pre>

Uncomment the following line.

<pre>
#autologin-user=
</pre>

And add the user you want to autologin and autostart Kodi. The user is named '''kodi''' in this example.

<pre>
autologin-user=kodi
</pre>

You can alternately create /etc/lightdm/lightdm.conf.d/50-myconfig.conf, but should still ensure the settings in /etc/lightdm/lightdm.conf agree.

== Configure Kodi to autostart ==

Configure Kodi to autostart.

<pre>
mkdir -p ~/.config/autostart
ln -s /usr/bin/kodi ~/.config/autostart
</pre>

This method of autostart requires a desktop environment or DE. This is done a bit differently by each DE. Some helpful links can easily be found in today's Web search using any search engine.

[http://edoceo.com/gui/xfce-autostart-apps Autostart Apps in XFCE]

The Raspberry Pi is a bit more of a tweak, but these are excellent links that will tell you how. The first link is the most helpful to making sure Kodi autostarts in Pi, and utilizes a '''crontab'''. There are many settings on the Pi that control boot, and the first link gives the best most trouble-free way to boot directly to Kodi.

[https://www.leowkahman.com/2016/03/05/lamp-stack-on-raspberry-pi-with-kodi-running-at-startup/ LAMP stack on Raspberry Pi with Kodi running at startup]

This is a quick reference for Crontab.

[http://www.adminschoice.com/crontab-quick-reference Crontab Quick Reference]

These linked pages facilitate more tweaks and settings relevant to other uses of the X Window System on Pi.

[http://ozzmaker.com/enable-x-windows-on-piscreen/ Enable X Window System on PiScreen]

[https://raspberrypi.stackexchange.com/questions/59310/remove-boot-messages-all-text-in-jessie Remove boot messages all text in Raspbian - Raspberry Pi Stack Exchange]

[https://raspberrypi.stackexchange.com/questions/47823/how-to-prevent-autologin-of-gui How to prevent or allow autologin of GUI - Raspberry Pi Stack Exchange]

[http://www.raspberry-projects.com/pi/pi-operating-systems/raspbian/auto-running-programs-gui Auto running programs LXDE - Raspberry Pi Projects]

And, if you would rather, it is easier to follow the process provided by this link to modify the Raspbian image before installing it onto the microSD card.

[https://wiki.debian.org/RaspberryPi/qemu-user-static Modifying Raspbian with qemu-user-static]

The above link describes removing the DE from a Raspbian image, though Raspbian Lite is a much better starting point for using Qemu for this purpose.

You can also use the X11 Window System to autostart Kodi by placing a statup script in the /etc/X11/Xsession.d/ directory.

[https://debian-administration.org/article/50/Running_applications_automatically_when_X_starts Running applications automatically when X starts]

<pre>
nano /etc/X11/Xsession.d/startup-local
</pre>

Insert this text into the new file. Use CTRL + O + Enter + X to save the file.

<pre>
#!/bin/sh
/usr/bin/kodi
</pre>

If you have a WM, such as Blackbox you can add it here as well.

<pre>
#!/bin/sh
blackbox &
/usr/bin/kodi
</pre>

Set permissions to make it executable. Use the ampersand to run an application in the background, such as a WM you only need to for the purpose of launching Kodi but not if you don't want to use the WM itself. Kodi will not launch without a DE or WM, but placing the ampersand "&" at the end of the command makes it run in the background where it can do its job out of sight. Also, make sure to start a WM or DE before running an application in the foreground. This is not necessary for apps running in the background.

<pre>
chmod 755 /etc/X11/Xsession.d/startup-local
</pre>

If Kodi is not installed at the standard path, find it using the '''which''' command.

<pre>
which kodi
</pre>

This feature is available on X Window System operating systems most Linux distributions use the X Window System.

== Disable / enable the login prompt ==

You can disable the graphical login prompt.

<pre>
systemctl set-default multi-user.target
</pre>

To enable it again use.

<pre>
systemctl set-default graphical.target
</pre>

If you are using an autologin method associated with your DE or WM, you '''do not''' want to disable the graphical login.

Even if you are using something like [https://github.com/graysky2/kodi-standalone-service Kodi Standalone Service], you still need use a WM or a DE that installs the '''x-window-manager''' software package.

To ensure you have this installed use the '''which''' command.

<pre>
which x-window-manager
</pre>

If there is no such package, you can use '''apt''' to search your Linux distributions repository.

<pre>
apt-cache search x-window-manager
</pre>

This will general a list of packages containing '''x-window-manager''', which cannot be installed alone. If you are not using a DE, you need to use a WM. And, you can also use a compositing WM like Compiz, for fast 3D effects.

[https://wiki.archlinux.org/index.php/Compiz Compiz - ArchWiki]

A note on using Kodi Standalone Service, this package runs Kodi as a '''systemd''' service and disables the login for user '''kodi''' and will not work when autologin is enabled. In fact, it will break the login process if you autologin user '''kodi''' and run Kodi Standalone Service at the same time. This package is installed automatically with the standard Kodi package when you install Kodi on Raspbian, but must be configured manually for all other Linux distributions. You can run the '''which''' command to find this package as well.

<pre>
which kodi-standalone
</pre>

Be advised, Kodi Standalone Service still launches the Kodi GUI and still requires a WM even though it is running as a '''systemd''' service. When you install a WM such as '''xfwm4''' (the WM for XFCE4), the CLI will tell you if it provides the '''x-window-manager''' package.

<pre>
Setting up xfwm4 (4.12.4-1) ...
update-alternatives: using /usr/bin/xfwm4 to provide /usr/bin/x-window-manager (x-window-manager) in auto mode
</pre>

If you do not see this message at the end of the installation, the WM you selected does not provide this software package and may not actually be a complete WM itself but only part of a package containing a WM.

For a great example on exactly how you would do this with '''xfwm4''', see this ArchWiki entry.

[https://wiki.archlinux.org/index.php/Xfwm XFWM - ArchWiki]

== Create custom Xsession script ==

Most systems utilize the client version of the X11 software an Xsession requires requires.

Upgrade to the server versions of the X Window System, if you want to utilize all the greatness of the X Window System.

Because of the lack of documentation, it is probably better to find tweaks and hacks on wikis and support pages rather than forums. For instance, the Ubuntu wiki is usually a good source of information.

[https://wiki.ubuntu.com/CustomXSession CustomXSession - Ubuntu Wiki]

<pre>apt install xauth xorg xinit xserver-xorg-core xserver-xorg xserver-common</pre>

To create a custom Xsession script with a text editor we start with an '''xinitrc''' script. For more detail on how to create and use '''xinit''', there is a great guide available here.

[https://en.wikibooks.org/wiki/Guide_to_X11/Starting_Sessions Guide to X11 - Starting Sessions - WikiBooks]

<pre>
nano ~/.xinitrc
</pre>

To run Kodi full-screen make sure the text reads:

<pre>
#!/usr/bin/env bash
exec gnome-session
/usr/bin/kodi -fs
</pre>

Replace the '''gnome-session''' with the DE or WM command you are using. See the last section for examples.

To make '''~/.xinitrc''' executable use.

<pre>
chmod +x ~/.xinitrc
</pre>

Use '''sudo''' and the '''~/.xinitrc''' file to configure '''~/.xsession'''.

<pre>
sudo -H -u kodi bash -c "ln -s ~/.xinitrc /home/kodi/.xsession"
</pre>

Make sure the path goes to user's home directory. In this example, the user is '''kodi'''.

You need to use '''sudo''' to run this command. If you do not have '''sudo''', install it.

<pre>
apt install sudo
</pre>

If you create a symbolic link and want to remove it, simply remove the existing '''.xsession''' file you created.

<pre>
rm /home/kodi/.xsession
</pre>

On some systems using a DE such as Gnome, not all systems using Gnome, it may be necessary for '''.xsession''' to be '''.xsessionrc'''. Though this is more likely the case for organization network computers than a personal one, where configurations may vary on a diversity of machines. Most of the time, it will be '''.xsession''' rather than '''.xsessionrc''' that you want to create.

You can also create the '''.xsession''' script directly in the home directory, rather than link it from '''~/.xinitrc'''. This is necessary if you create multiple custom Xsession scripts for multiple users, and you do not in that case link '''~/.xinitrc''' to '''.xsession'''.

You must also autostart the X Window system, which differs somewhat from scenario to scenario. For most setups, all that is necessary is to edit the '''.bashrc''' file.

<pre>
nano ~/.bashrc
</pre>

Add the following as shown.

<pre>
if [[ ! $DISPLAY && $XDG_VTNR -eq 1 ]]; then
exec startx
fi
</pre>

If you wish to remain logged in after quitting X, remove the '''exec''' from the above. Other configurations can be applied, but are irrelevant to autostarting Kodi.

[https://wiki.archlinux.org/index.php/Xinit#Autostart_X_at_login Xinit Autostart X at login]

If you are using LightDM and you just want to create a new login entry for user '''kodi''', you must create a new file.

<pre>
nano /usr/share/xsessions/custom.desktop
</pre>

And insert the following text.

<pre>
[Desktop Entry]
Name=Xsession
Exec=/etc/X11/Xsession
</pre>

This will create a new login option for the custom Xsession. Only this one entry is necessary for LightDM and X11 to find the '''~/.xsession''' script in each user's home directory.

== Xsession to boot to app / WM / DE ==

You can use any window manager or desktop enviroment with a custom Xsession script as long as it is intalled.

You do this by creating '''~/.xinitrc''' script that contains the command to start the WM or DE.

For instance, if you are using FluxBox.

<pre>
#!/usr/bin/env bash
exec fluxbox &
/usr/bin/kodi -fs
</pre>

The <code>-fs</code> option is full-screen.

To run Gnome in the background, but launch Kodi in the foreground.

<pre>
#!/usr/bin/env bash
exec gnome-session &
/usr/bin/kodi -fs
</pre>

Use the '''~/.xinitrc''' file to configure '''~/.xsession''' to create a custom login for any user, not just Kodi.

<pre>
sudo -H -u [username] bash -c "ln -s ~/.xinitrc ~/.xsession"
</pre>

You must reconfigure Xserver for any user that is not a privileged user to be able to start a custom Xsession.

<pre>
dpkg-reconfigure xserver-xorg-legacy
</pre>

And / or...

<pre>
dpkg-reconfigure xserver-xorg
</pre>

If both packages are installed, you must reconfigure both. Not all systems will use or require the legacy package to allow non-root users to start X.

== Add a custom Grub entry ==

If you want to boot to the CLI and manually launch an app or boot directly to Kodi without a DE or WM, add a custom grub entry.

The right way to add a custom grub entry is to copy the menu entry you want to change or duplicate.

Copy the default Grub configuration file and open it with a text editor on your desktop. If you use a text editor on the CLI, the text will be cut off by the window when copying and pasting.

<pre>
cp /boot/grub/grub.cfg grub.cfg
gedit grub.cfg
</pre>

Copy the menu entry and paste it into '''40_custom''' with a text editor in the CLI.

<pre>
nano /etc/grub.d/40_custom
</pre>

Where the menu entry contains '''quiet splash''' change it to '''text''' instead.

You should also change the name of the entry!

I just appended mine with “CLI” for command line interface.

To update Grub:

<pre>
update-grub
</pre>

To launch a WM you can type its name. I use Enlightment 17 or Fluxbox. It must be installed.

<pre>
fluxbox
</pre>

You must have FluxBox installed. There are countless other window managers.

To launch a DE you enter the appropriate command. For Gnome desktop:

<pre>
gnome-session
</pre>

For KDE:

<pre>
startkde
</pre>

or

<pre>
plasma-desktop
</pre>

For XFCE:

<pre>
startxfce4
</pre>

For Mate:

<pre>
mate-session
</pre>

For LXDE:

<pre>
startlxde
</pre>

You can either manually launch your apps, boot right into them, or create an Xsession for each user. This is great when you want to create a Kodi user for running Kodi only, and for making sure you can still login to your DE with your regular user account. You can boot to any app full-screen this way, not just Kodi. You can create a custom Xsession script for any user, configured with any startup applications running in full-screen mode or normally.

By optionally creating a Grub menu entry, you can create a different Grub menu selection to boot only to the CLI and start an Xsession with a script or run commands manually.

HOW-TO talk:Autostart Kodi for Linux

2018-04-28T19:04:29Z

W3tech:

I think it's worth adding an edit here to the effect that - to my knowledge - there's no way of enabling an ubuntu account to auto-login, and so to autostart Kodi, if the installation uses encrypted home directories. I had this issue and have posted [http://askubuntu.com/questions/209650/autostart-xbmc-at-boot/715976#715976 on the Ask Ubuntu site] to this effect.

May I add a subsection outlining how to remove encrypted home directories per the linked answer above?

[[User:Nmg20|Nmg20]] ([[User talk:Nmg20|talk]]) 17:28, 3 January 2016 (EST)

:Go for it. -- [[User:Ned Scott|Ned Scott]] ([[User talk:Ned Scott|talk]]) 02:02, 4 January 2016 (EST)

I updated this old page. I think it could be a lot better. It needs instructions for RPM-based commands and commands on systems like Manjaro which use a different command set. I could do this in time. Anyone who knows how to easily convert the commands can as well. It is very basic stuff. I am surprised no one has written about writing an Xsession script before. Kodi standalone service is new software. It was in the Arch Linux repo, but it got moved. This page could use some screenshots, and I think could be a How-To for any Linux. I cannot seem to get the human verification box for external links, but it prompts me to enter two words. Only there is nowhere to see these words or put them into a box. I am not sure if external links are disabled on this page. [[User:W3tech|W3tech]] ([[User talk:W3tech|talk]]) 05:27, 2 February 2018 (EST) w3tech

So the code is much tighter after testing on more Ubuntu derivatives. It also needed put into better order. I am not finished with it yet. Working on screenshots and multimedia and expanding command sets for using other Linux distros. It is really more appropriately a guide for configuring an X Window System with autologin and autostart options. It can be used with any app or media player, not exclusively Kodi. [[User:W3tech|W3tech]] ([[User talk:W3tech|talk]]) 14:01, 19 February 2018 (EST)

I am testing various Kodi-embedded and other Linux-embedded Linux, and will be updating this page periodically and accordingly. I plan to provide screenshots and commands for other distros like Manjaro and Fedora in a classic tutorial-style manner. Fedora or OpenSUSE have proved to me the best distros for running Kodi and other media software. Now the wiki lets me insert links after the upgrade. A much nicer theme and layout too! [[User:W3tech|W3tech]] ([[User talk:W3tech|talk]]) 13:20, 27 April 2018 (UTC)w3tech

Cleaned up some errors in syntax and added some information for running Xsession scripts. [[User:W3tech|W3tech]] ([[User talk:W3tech|talk]]) 09:07, 28 April 2018 (UTC)w3tech

More clarification may be necessary. It is more important to state how to do it than exactly what to do on this page.

HOW-TO:Autostart Kodi for Linux

2018-04-28T19:01:42Z

W3tech: /* Create custom Xsession script */

<section begin="intro" /><big>Any or all or any combination of these methods can be used to configure a Debian-based X Window System to boot directly to Kodi. This should work on any Linux using the X Window System, but these instructions are particular to Debian derivatives, such as Ubuntu. A server edition is best for running only Kodi, but this page assumes booting into a desktop OS, not a server distro. However, the instructions here can be used for a server distro with even less configuration than for a desktop. Experiment inside VirtualBox before you apply any of these to your system and make a backup.</big><section end="intro" />

__TOC__

== Switch to root ==

<pre>
su
</pre>

or

<pre>
sudo su
</pre>

== Create a Kodi user ==

To use Kodi full-screen, you only have to create a standard user.

<pre>
adduser kodi
</pre>

To remove the password use:

<pre>
passwd -d kodi
</pre>

== Customize LightDM to autologin ==

You can utilize the ability to customize LightDM data manager by changing the builtin custom configuration file '''50-myconfig.conf''' using '''nano''' or another text editor. If you have no DE or WM you can install '''lightdm''', but should make sure to do a bit of research before you do. Most versions of Linux use LightDM, but many server versions do not. For Ubuntu Server with no DE, for example, installing '''lightdm''' is okay and necessary. Changing the behavior of LightDM is done using a custom '''50-myconfig.conf''' configuration file.

To see if you have '''lightdm''' use '''which'''.

<pre>
which lightdm
</pre>

If not, install it with '''apt'''.

<pre>
apt install lightdm
</pre>

Create a custom configuration file called '''50-myconfig.conf''' using '''nano''' or other CLI text editor.

<pre>
mkdir /etc/lightdm/lightdm.conf.d/
nano /etc/lightdm/lightdm.conf.d/50-myconfig.conf
</pre>

Inside this new file add the following text.

<pre>
[SeatDefaults]
autologin-user=kodi
</pre>

On Raspbian, you can configure LightDM differently for autologin to boot directly to Kodi.

<pre>
nano /etc/lightdm/lightdm.conf
</pre>

Uncomment the following line.

<pre>
#autologin-user=
</pre>

And add the user you want to autologin and autostart Kodi. The user is named '''kodi''' in this example.

<pre>
autologin-user=kodi
</pre>

You can alternately create /etc/lightdm/lightdm.conf.d/50-myconfig.conf, but should still ensure the settings in /etc/lightdm/lightdm.conf agree.

== Configure Kodi to autostart ==

Configure Kodi to autostart.

<pre>
mkdir -p ~/.config/autostart
ln -s /usr/bin/kodi ~/.config/autostart
</pre>

This method of autostart requires a desktop environment or DE. This is done a bit differently by each DE. Some helpful links can easily be found in today's Web search using any search engine.

[http://edoceo.com/gui/xfce-autostart-apps Autostart Apps in XFCE]

The Raspberry Pi is a bit more of a tweak, but these are excellent links that will tell you how. The first link is the most helpful to making sure Kodi autostarts in Pi, and utilizes a '''crontab'''. There are many settings on the Pi that control boot, and the first link gives the best most trouble-free way to boot directly to Kodi.

[https://www.leowkahman.com/2016/03/05/lamp-stack-on-raspberry-pi-with-kodi-running-at-startup/ LAMP stack on Raspberry Pi with Kodi running at startup]

This is a quick reference for Crontab.

[http://www.adminschoice.com/crontab-quick-reference Crontab Quick Reference]

These linked pages facilitate more tweaks and settings relevant to other uses of the X Window System on Pi.

[http://ozzmaker.com/enable-x-windows-on-piscreen/ Enable X Window System on PiScreen]

[https://raspberrypi.stackexchange.com/questions/59310/remove-boot-messages-all-text-in-jessie Remove boot messages all text in Raspbian - Raspberry Pi Stack Exchange]

[https://raspberrypi.stackexchange.com/questions/47823/how-to-prevent-autologin-of-gui How to prevent or allow autologin of GUI - Raspberry Pi Stack Exchange]

[http://www.raspberry-projects.com/pi/pi-operating-systems/raspbian/auto-running-programs-gui Auto running programs LXDE - Raspberry Pi Projects]

And, if you would rather, it is easier to follow the process provided by this link to modify the Raspbian image before installing it onto the microSD card.

[https://wiki.debian.org/RaspberryPi/qemu-user-static Modifying Raspbian with qemu-user-static]

The above link describes removing the DE from a Raspbian image, though Raspbian Lite is a much better starting point for using Qemu for this purpose.

You can also use the X11 Window System to autostart Kodi by placing a statup script in the /etc/X11/Xsession.d/ directory.

[https://debian-administration.org/article/50/Running_applications_automatically_when_X_starts Running applications automatically when X starts]

<pre>
nano /etc/X11/Xsession.d/startup-local
</pre>

Insert this text into the new file. Use CTRL + O + Enter + X to save the file.

<pre>
#!/bin/sh
/usr/bin/kodi
</pre>

If you have a WM, such as Blackbox you can add it here as well.

<pre>
#!/bin/sh
blackbox &
/usr/bin/kodi
</pre>

Set permissions to make it executable. Use the ampersand to run an application in the background, such as a WM you only need to for the purpose of launching Kodi but not if you don't want to use the WM itself. Kodi will not launch without a DE or WM, but placing the ampersand "&" at the end of the command makes it run in the background where it can do its job out of sight. Also, make sure to start a WM or DE before running an application in the foreground. This is not necessary for apps running in the background.

<pre>
chmod 755 /etc/X11/Xsession.d/startup-local
</pre>

If Kodi is not installed at the standard path, find it using the '''which''' command.

<pre>
which kodi
</pre>

This feature is available on X Window System operating systems most Linux distributions use the X Window System.

== Disable / enable the login prompt ==

You can disable the graphical login prompt.

<pre>
systemctl set-default multi-user.target
</pre>

To enable it again use.

<pre>
systemctl set-default graphical.target
</pre>

If you are using an autologin method associated with your DE or WM, you '''do not''' want to disable the graphical login.

Even if you are using something like [https://github.com/graysky2/kodi-standalone-service Kodi Standalone Service], you still need use a WM or a DE that installs the '''x-window-manager''' software package.

To ensure you have this installed use the '''which''' command.

<pre>
which x-window-manager
</pre>

If there is no such package, you can use '''apt''' to search your Linux distributions repository.

<pre>
apt-cache search x-window-manager
</pre>

This will general a list of packages containing '''x-window-manager''', which cannot be installed alone. If you are not using a DE, you need to use a WM. And, you can also use a compositing WM like Compiz, for fast 3D effects.

[https://wiki.archlinux.org/index.php/Compiz Compiz - ArchWiki]

A note on using Kodi Standalone Service, this package runs Kodi as a '''systemd''' service and disables the login for user '''kodi''' and will not work when autologin is enabled. In fact, it will break the login process if you autologin user '''kodi''' and run Kodi Standalone Service at the same time. This package is installed automatically with the standard Kodi package when you install Kodi on Raspbian, but must be configured manually for all other Linux distributions. You can run the '''which''' command to find this package as well.

<pre>
which kodi-standalone
</pre>

Be advised, Kodi Standalone Service still launches the Kodi GUI and still requires a WM even though it is running as a '''systemd''' service. When you install a WM such as '''xfwm4''' (the WM for XFCE4), the CLI will tell you if it provides the '''x-window-manager''' package.

<pre>
Setting up xfwm4 (4.12.4-1) ...
update-alternatives: using /usr/bin/xfwm4 to provide /usr/bin/x-window-manager (x-window-manager) in auto mode
</pre>

If you do not see this message at the end of the installation, the WM you selected does not provide this software package and may not actually be a complete WM itself but only part of a package containing a WM.

For a great example on exactly how you would do this with '''xfwm4''', see this ArchWiki entry.

[https://wiki.archlinux.org/index.php/Xfwm XFWM - ArchWiki]

== Create custom Xsession script ==

Most systems utilize the client version of the X11 software an Xsession requires requires.

Upgrade to the server versions of the X Window System, if you want to utilize all the greatness of the X Window System.

Because of the lack of documentation, it is probably better to find tweaks and hacks on wikis and support pages rather than forums. For instance, the Ubuntu wiki is usually a good source of information.

[https://wiki.ubuntu.com/CustomXSession CustomXSession - Ubuntu Wiki]

<pre>apt install xauth xorg xinit xserver-xorg-core xserver-xorg xserver-common</pre>

Create a custom Xsession script with a text editor.

<pre>
nano ~/.xinitrc
</pre>

To run Kodi full-screen make sure the text reads:

<pre>
#!/usr/bin/env bash
exec gnome-session
/usr/bin/kodi -fs
</pre>

Replace the '''gnome-session''' with the DE or WM command you are using. See the last section for examples.

To make '''~/.xinitrc''' executable use.

<pre>
chmod +x ~/.xinitrc
</pre>

Use '''sudo''' and the '''~/.xinitrc''' file to configure '''~/.xsession'''.

<pre>
sudo -H -u kodi bash -c "ln -s ~/.xinitrc /home/kodi/.xsession"
</pre>

Make sure the path goes to user's home directory. In this example, the user is '''kodi'''.

You need to use '''sudo''' to run this command. If you do not have '''sudo''', install it.

<pre>
apt install sudo
</pre>

If you create a symbolic link and want to remove it, simply remove the existing '''.xsession''' file you created.

<pre>
rm /home/kodi/.xsession
</pre>

Remember you can modify use and reuse the '''~/.xinitrc''' file to configure '''~/.xsession''' as often as you want. That is the purpose of the file. It does nothing on its own until you associate it with a user. On some systems using a DE such as Gnome, not all systems using Gnome, it may be necessary for '''.xsession''' to be '''.xsessionrc'''. Though this is more likely the case for organization network computers than a personal one, where configurations may vary on a diversity of machines. Most of the time, it will be '''.xsession''' rather than '''.xsessionrc''' that you want to create.

You can also create the '''.xsession''' script directly in the home directory, rather than link it from '''~/.xinitrc'''. This is necessary if you create multiple custom Xsession scripts for multiple users, and you do not in that case link '''~/.xinitrc''' to '''.xsession'''.

You must also autostart the X Window system, which differs somewhat from scenario to scenario. For most setups, all that is necessary is to edit the '''.bashrc''' file.

<pre>
nano ~/.bashrc
</pre>

Add the following as shown.

<pre>
if [[ ! $DISPLAY && $XDG_VTNR -eq 1 ]]; then
exec startx
fi
</pre>

If you wish to remain logged in after quitting X, remove the '''exec''' from the above. Other configurations can be applied, but are irrelevant to autostarting Kodi.

[https://wiki.archlinux.org/index.php/Xinit#Autostart_X_at_login Xinit Autostart X at login]

If you are using LightDM and you just want to create a new login entry for user '''kodi''', you must create a new file.

<pre>
nano /usr/share/xsessions/custom.desktop
</pre>

And insert the following text.

<pre>
[Desktop Entry]
Name=Xsession
Exec=/etc/X11/Xsession
</pre>

This will create a new login option for the custom Xsession. Only this one entry is necessary for LightDM and X11 to find the '''~/.xsession''' script in each user's home directory.

== Xsession to boot to app / WM / DE ==

You can use any window manager or desktop enviroment with a custom Xsession script as long as it is intalled.

You do this by creating '''~/.xinitrc''' script that contains the command to start the WM or DE.

For instance, if you are using FluxBox.

<pre>
#!/usr/bin/env bash
exec fluxbox &
/usr/bin/kodi -fs
</pre>

The <code>-fs</code> option is full-screen.

To run Gnome in the background, but launch Kodi in the foreground.

<pre>
#!/usr/bin/env bash
exec gnome-session &
/usr/bin/kodi -fs
</pre>

Use the '''~/.xinitrc''' file to configure '''~/.xsession''' to create a custom login for any user, not just Kodi.

<pre>
sudo -H -u [username] bash -c "ln -s ~/.xinitrc ~/.xsession"
</pre>

You must reconfigure Xserver for any user that is not a privileged user to be able to start a custom Xsession.

<pre>
dpkg-reconfigure xserver-xorg-legacy
</pre>

And / or...

<pre>
dpkg-reconfigure xserver-xorg
</pre>

If both packages are installed, you must reconfigure both. Not all systems will use or require the legacy package to allow non-root users to start X.

== Add a custom Grub entry ==

If you want to boot to the CLI and manually launch an app or boot directly to Kodi without a DE or WM, add a custom grub entry.

The right way to add a custom grub entry is to copy the menu entry you want to change or duplicate.

Copy the default Grub configuration file and open it with a text editor on your desktop. If you use a text editor on the CLI, the text will be cut off by the window when copying and pasting.

<pre>
cp /boot/grub/grub.cfg grub.cfg
gedit grub.cfg
</pre>

Copy the menu entry and paste it into '''40_custom''' with a text editor in the CLI.

<pre>
nano /etc/grub.d/40_custom
</pre>

Where the menu entry contains '''quiet splash''' change it to '''text''' instead.

You should also change the name of the entry!

I just appended mine with “CLI” for command line interface.

To update Grub:

<pre>
update-grub
</pre>

To launch a WM you can type its name. I use Enlightment 17 or Fluxbox. It must be installed.

<pre>
fluxbox
</pre>

You must have FluxBox installed. There are countless other window managers.

To launch a DE you enter the appropriate command. For Gnome desktop:

<pre>
gnome-session
</pre>

For KDE:

<pre>
startkde
</pre>

or

<pre>
plasma-desktop
</pre>

For XFCE:

<pre>
startxfce4
</pre>

For Mate:

<pre>
mate-session
</pre>

For LXDE:

<pre>
startlxde
</pre>

You can either manually launch your apps, boot right into them, or create an Xsession for each user. This is great when you want to create a Kodi user for running Kodi only, and for making sure you can still login to your DE with your regular user account. You can boot to any app full-screen this way, not just Kodi. You can create a custom Xsession script for any user, configured with any startup applications running in full-screen mode or normally.

By optionally creating a Grub menu entry, you can create a different Grub menu selection to boot only to the CLI and start an Xsession with a script or run commands manually.

HOW-TO:Autostart Kodi for Linux

2018-04-28T16:59:31Z

W3tech: /* Configure Kodi to autostart */

<section begin="intro" /><big>Any or all or any combination of these methods can be used to configure a Debian-based X Window System to boot directly to Kodi. This should work on any Linux using the X Window System, but these instructions are particular to Debian derivatives, such as Ubuntu. A server edition is best for running only Kodi, but this page assumes booting into a desktop OS, not a server distro. However, the instructions here can be used for a server distro with even less configuration than for a desktop. Experiment inside VirtualBox before you apply any of these to your system and make a backup.</big><section end="intro" />

__TOC__

== Switch to root ==

<pre>
su
</pre>

or

<pre>
sudo su
</pre>

== Create a Kodi user ==

To use Kodi full-screen, you only have to create a standard user.

<pre>
adduser kodi
</pre>

To remove the password use:

<pre>
passwd -d kodi
</pre>

== Customize LightDM to autologin ==

You can utilize the ability to customize LightDM data manager by changing the builtin custom configuration file '''50-myconfig.conf''' using '''nano''' or another text editor. If you have no DE or WM you can install '''lightdm''', but should make sure to do a bit of research before you do. Most versions of Linux use LightDM, but many server versions do not. For Ubuntu Server with no DE, for example, installing '''lightdm''' is okay and necessary. Changing the behavior of LightDM is done using a custom '''50-myconfig.conf''' configuration file.

To see if you have '''lightdm''' use '''which'''.

<pre>
which lightdm
</pre>

If not, install it with '''apt'''.

<pre>
apt install lightdm
</pre>

Create a custom configuration file called '''50-myconfig.conf''' using '''nano''' or other CLI text editor.

<pre>
mkdir /etc/lightdm/lightdm.conf.d/
nano /etc/lightdm/lightdm.conf.d/50-myconfig.conf
</pre>

Inside this new file add the following text.

<pre>
[SeatDefaults]
autologin-user=kodi
</pre>

On Raspbian, you can configure LightDM differently for autologin to boot directly to Kodi.

<pre>
nano /etc/lightdm/lightdm.conf
</pre>

Uncomment the following line.

<pre>
#autologin-user=
</pre>

And add the user you want to autologin and autostart Kodi. The user is named '''kodi''' in this example.

<pre>
autologin-user=kodi
</pre>

You can alternately create /etc/lightdm/lightdm.conf.d/50-myconfig.conf, but should still ensure the settings in /etc/lightdm/lightdm.conf agree.

== Configure Kodi to autostart ==

Configure Kodi to autostart.

<pre>
mkdir -p ~/.config/autostart
ln -s /usr/bin/kodi ~/.config/autostart
</pre>

This method of autostart requires a desktop environment or DE. This is done a bit differently by each DE. Some helpful links can easily be found in today's Web search using any search engine.

[http://edoceo.com/gui/xfce-autostart-apps Autostart Apps in XFCE]

The Raspberry Pi is a bit more of a tweak, but these are excellent links that will tell you how. The first link is the most helpful to making sure Kodi autostarts in Pi, and utilizes a '''crontab'''. There are many settings on the Pi that control boot, and the first link gives the best most trouble-free way to boot directly to Kodi.

[https://www.leowkahman.com/2016/03/05/lamp-stack-on-raspberry-pi-with-kodi-running-at-startup/ LAMP stack on Raspberry Pi with Kodi running at startup]

This is a quick reference for Crontab.

[http://www.adminschoice.com/crontab-quick-reference Crontab Quick Reference]

These linked pages facilitate more tweaks and settings relevant to other uses of the X Window System on Pi.

[http://ozzmaker.com/enable-x-windows-on-piscreen/ Enable X Window System on PiScreen]

[https://raspberrypi.stackexchange.com/questions/59310/remove-boot-messages-all-text-in-jessie Remove boot messages all text in Raspbian - Raspberry Pi Stack Exchange]

[https://raspberrypi.stackexchange.com/questions/47823/how-to-prevent-autologin-of-gui How to prevent or allow autologin of GUI - Raspberry Pi Stack Exchange]

[http://www.raspberry-projects.com/pi/pi-operating-systems/raspbian/auto-running-programs-gui Auto running programs LXDE - Raspberry Pi Projects]

And, if you would rather, it is easier to follow the process provided by this link to modify the Raspbian image before installing it onto the microSD card.

[https://wiki.debian.org/RaspberryPi/qemu-user-static Modifying Raspbian with qemu-user-static]

The above link describes removing the DE from a Raspbian image, though Raspbian Lite is a much better starting point for using Qemu for this purpose.

You can also use the X11 Window System to autostart Kodi by placing a statup script in the /etc/X11/Xsession.d/ directory.

[https://debian-administration.org/article/50/Running_applications_automatically_when_X_starts Running applications automatically when X starts]

<pre>
nano /etc/X11/Xsession.d/startup-local
</pre>

Insert this text into the new file. Use CTRL + O + Enter + X to save the file.

<pre>
#!/bin/sh
/usr/bin/kodi
</pre>

If you have a WM, such as Blackbox you can add it here as well.

<pre>
#!/bin/sh
blackbox &
/usr/bin/kodi
</pre>

Set permissions to make it executable. Use the ampersand to run an application in the background, such as a WM you only need to for the purpose of launching Kodi but not if you don't want to use the WM itself. Kodi will not launch without a DE or WM, but placing the ampersand "&" at the end of the command makes it run in the background where it can do its job out of sight. Also, make sure to start a WM or DE before running an application in the foreground. This is not necessary for apps running in the background.

<pre>
chmod 755 /etc/X11/Xsession.d/startup-local
</pre>

If Kodi is not installed at the standard path, find it using the '''which''' command.

<pre>
which kodi
</pre>

This feature is available on X Window System operating systems most Linux distributions use the X Window System.

== Disable / enable the login prompt ==

You can disable the graphical login prompt.

<pre>
systemctl set-default multi-user.target
</pre>

To enable it again use.

<pre>
systemctl set-default graphical.target
</pre>

If you are using an autologin method associated with your DE or WM, you '''do not''' want to disable the graphical login.

Even if you are using something like [https://github.com/graysky2/kodi-standalone-service Kodi Standalone Service], you still need use a WM or a DE that installs the '''x-window-manager''' software package.

To ensure you have this installed use the '''which''' command.

<pre>
which x-window-manager
</pre>

If there is no such package, you can use '''apt''' to search your Linux distributions repository.

<pre>
apt-cache search x-window-manager
</pre>

This will general a list of packages containing '''x-window-manager''', which cannot be installed alone. If you are not using a DE, you need to use a WM. And, you can also use a compositing WM like Compiz, for fast 3D effects.

[https://wiki.archlinux.org/index.php/Compiz Compiz - ArchWiki]

A note on using Kodi Standalone Service, this package runs Kodi as a '''systemd''' service and disables the login for user '''kodi''' and will not work when autologin is enabled. In fact, it will break the login process if you autologin user '''kodi''' and run Kodi Standalone Service at the same time. This package is installed automatically with the standard Kodi package when you install Kodi on Raspbian, but must be configured manually for all other Linux distributions. You can run the '''which''' command to find this package as well.

<pre>
which kodi-standalone
</pre>

Be advised, Kodi Standalone Service still launches the Kodi GUI and still requires a WM even though it is running as a '''systemd''' service. When you install a WM such as '''xfwm4''' (the WM for XFCE4), the CLI will tell you if it provides the '''x-window-manager''' package.

<pre>
Setting up xfwm4 (4.12.4-1) ...
update-alternatives: using /usr/bin/xfwm4 to provide /usr/bin/x-window-manager (x-window-manager) in auto mode
</pre>

If you do not see this message at the end of the installation, the WM you selected does not provide this software package and may not actually be a complete WM itself but only part of a package containing a WM.

For a great example on exactly how you would do this with '''xfwm4''', see this ArchWiki entry.

[https://wiki.archlinux.org/index.php/Xfwm XFWM - ArchWiki]

== Create custom Xsession script ==

Most systems utilize the client version of the X11 software an Xsession requires requires.

Upgrade to the server versions of the X Window System, if you want to utilize all the greatness of the X Window System.

Because of the lack of documentation, it is probably better to find tweaks and hacks on wikis and support pages rather than forums. For instance, the Ubuntu wiki is usually a good source of information.

[https://wiki.ubuntu.com/CustomXSession CustomXSession - Ubuntu Wiki]

<pre>apt install xauth xorg xinit xserver-xorg-core xserver-xorg xserver-common</pre>

Create a custom Xsession script with a text editor.

<pre>
nano ~/.xinitrc
</pre>

To run Kodi full-screen make sure the text reads:

<pre>
#!/usr/bin/env bash
exec gnome-session
/usr/bin/kodi -fs
</pre>

Replace the '''gnome-session''' with the DE or WM command you are using. See the last section for examples.

To make '''~/.xinitrc''' executable use.

<pre>
chmod +x ~/.xinitrc
</pre>

Use '''sudo''' and the '''~/.xinitrc''' file to configure '''~/.xsession'''.

<pre>
sudo -H -u kodi bash -c "ln -s ~/.xinitrc ~/.xsession"
</pre>

You need to use '''sudo''' to run this command. If you do not have '''sudo''', install it.

<pre>
apt install sudo
</pre>

If you create a symbolic link and want to remove it, simply remove the existing '''.xsession''' file you created.

<pre>
rm /home/kodi/.xsession
</pre>

Remember you can modify use and reuse the '''~/.xinitrc''' file to configure '''~/.xsession''' as often as you want. That is the purpose of the file. It does nothing on its own until you associate it with a user. On some systems using a DE such as Gnome, not all systems using Gnome, it may be necessary for '''.xsession''' to be '''.xsessionrc'''. Though this is more likely the case for organization network computers than a personal one, where configurations may vary on a diversity of machines. Most of the time, it will be '''.xsession''' rather than '''.xsessionrc''' that you want to create.

You must also autostart the X Window system, which differs somewhat from scenario to scenario. For most setups, all that is necessary is to edit the '''.bashrc''' file.

<pre>
nano ~/.bashrc
</pre>

Add the following as shown.

<pre>
if [[ ! $DISPLAY && $XDG_VTNR -eq 1 ]]; then
exec startx
fi
</pre>

If you wish to remain logged in after quitting X, remove the '''exec''' from the above. Other configurations can be applied, but are irrelevant to autostarting Kodi.

[https://wiki.archlinux.org/index.php/Xinit#Autostart_X_at_login Xinit Autostart X at login]

If you are using LightDM and you just want to create a new login entry for user '''kodi''', you must create a new file.

<pre>
nano /usr/share/xsessions/custom.desktop
</pre>

And insert the following text.

<pre>
[Desktop Entry]
Name=Xsession
Exec=/etc/X11/Xsession
</pre>

This will create a new login option for the custom Xsession. Only this one entry is necessary for LightDM and X11 to find the '''~/.xsession''' script in each user's home directory.

== Xsession to boot to app / WM / DE ==

You can use any window manager or desktop enviroment with a custom Xsession script as long as it is intalled.

You do this by creating '''~/.xinitrc''' script that contains the command to start the WM or DE.

For instance, if you are using FluxBox.

<pre>
#!/usr/bin/env bash
exec fluxbox &
/usr/bin/kodi -fs
</pre>

The <code>-fs</code> option is full-screen.

To run Gnome in the background, but launch Kodi in the foreground.

<pre>
#!/usr/bin/env bash
exec gnome-session &
/usr/bin/kodi -fs
</pre>

Use the '''~/.xinitrc''' file to configure '''~/.xsession''' to create a custom login for any user, not just Kodi.

<pre>
sudo -H -u [username] bash -c "ln -s ~/.xinitrc ~/.xsession"
</pre>

You must reconfigure Xserver for any user that is not a privileged user to be able to start a custom Xsession.

<pre>
dpkg-reconfigure xserver-xorg-legacy
</pre>

And / or...

<pre>
dpkg-reconfigure xserver-xorg
</pre>

If both packages are installed, you must reconfigure both. Not all systems will use or require the legacy package to allow non-root users to start X.

== Add a custom Grub entry ==

If you want to boot to the CLI and manually launch an app or boot directly to Kodi without a DE or WM, add a custom grub entry.

The right way to add a custom grub entry is to copy the menu entry you want to change or duplicate.

Copy the default Grub configuration file and open it with a text editor on your desktop. If you use a text editor on the CLI, the text will be cut off by the window when copying and pasting.

<pre>
cp /boot/grub/grub.cfg grub.cfg
gedit grub.cfg
</pre>

Copy the menu entry and paste it into '''40_custom''' with a text editor in the CLI.

<pre>
nano /etc/grub.d/40_custom
</pre>

Where the menu entry contains '''quiet splash''' change it to '''text''' instead.

You should also change the name of the entry!

I just appended mine with “CLI” for command line interface.

To update Grub:

<pre>
update-grub
</pre>

To launch a WM you can type its name. I use Enlightment 17 or Fluxbox. It must be installed.

<pre>
fluxbox
</pre>

You must have FluxBox installed. There are countless other window managers.

To launch a DE you enter the appropriate command. For Gnome desktop:

<pre>
gnome-session
</pre>

For KDE:

<pre>
startkde
</pre>

or

<pre>
plasma-desktop
</pre>

For XFCE:

<pre>
startxfce4
</pre>

For Mate:

<pre>
mate-session
</pre>

For LXDE:

<pre>
startlxde
</pre>

You can either manually launch your apps, boot right into them, or create an Xsession for each user. This is great when you want to create a Kodi user for running Kodi only, and for making sure you can still login to your DE with your regular user account. You can boot to any app full-screen this way, not just Kodi. You can create a custom Xsession script for any user, configured with any startup applications running in full-screen mode or normally.

By optionally creating a Grub menu entry, you can create a different Grub menu selection to boot only to the CLI and start an Xsession with a script or run commands manually.

HOW-TO:Autostart Kodi for Linux

2018-04-28T15:27:11Z

W3tech: /* Customize LightDM to autologin */

<section begin="intro" /><big>Any or all or any combination of these methods can be used to configure a Debian-based X Window System to boot directly to Kodi. This should work on any Linux using the X Window System, but these instructions are particular to Debian derivatives, such as Ubuntu. A server edition is best for running only Kodi, but this page assumes booting into a desktop OS, not a server distro. However, the instructions here can be used for a server distro with even less configuration than for a desktop. Experiment inside VirtualBox before you apply any of these to your system and make a backup.</big><section end="intro" />

__TOC__

== Switch to root ==

<pre>
su
</pre>

or

<pre>
sudo su
</pre>

== Create a Kodi user ==

To use Kodi full-screen, you only have to create a standard user.

<pre>
adduser kodi
</pre>

To remove the password use:

<pre>
passwd -d kodi
</pre>

== Customize LightDM to autologin ==

You can utilize the ability to customize LightDM data manager by changing the builtin custom configuration file '''50-myconfig.conf''' using '''nano''' or another text editor. If you have no DE or WM you can install '''lightdm''', but should make sure to do a bit of research before you do. Most versions of Linux use LightDM, but many server versions do not. For Ubuntu Server with no DE, for example, installing '''lightdm''' is okay and necessary. Changing the behavior of LightDM is done using a custom '''50-myconfig.conf''' configuration file.

To see if you have '''lightdm''' use '''which'''.

<pre>
which lightdm
</pre>

If not, install it with '''apt'''.

<pre>
apt install lightdm
</pre>

Create a custom configuration file called '''50-myconfig.conf''' using '''nano''' or other CLI text editor.

<pre>
mkdir /etc/lightdm/lightdm.conf.d/
nano /etc/lightdm/lightdm.conf.d/50-myconfig.conf
</pre>

Inside this new file add the following text.

<pre>
[SeatDefaults]
autologin-user=kodi
</pre>

On Raspbian, you can configure LightDM differently for autologin to boot directly to Kodi.

<pre>
nano /etc/lightdm/lightdm.conf
</pre>

Uncomment the following line.

<pre>
#autologin-user=
</pre>

And add the user you want to autologin and autostart Kodi. The user is named '''kodi''' in this example.

<pre>
autologin-user=kodi
</pre>

You can alternately create /etc/lightdm/lightdm.conf.d/50-myconfig.conf, but should still ensure the settings in /etc/lightdm/lightdm.conf agree.

== Configure Kodi to autostart ==

Configure Kodi to autostart.

<pre>
mkdir -p ~/.config/autostart
ln -s /usr/bin/kodi ~/.config/autostart
</pre>

This method of autostart requires a desktop environment or DE. This is done a bit differently by each DE. Some helpful links can easily be found in today's Web search using any search engine.

[http://edoceo.com/gui/xfce-autostart-apps Autostart Apps in XFCE]

The Raspberry Pi is a bit more of a tweak, but these are excellent links that will tell you how. The first link is the most helpful to making sure Kodi autostarts in Pi. There are many settings on the Pi that control boot, and the first link gives the best most trouble-free way to boot directly to Kodi. The others facilitate more tweaks and settings relevant to other uses of the X Window System.

[https://www.leowkahman.com/2016/03/05/lamp-stack-on-raspberry-pi-with-kodi-running-at-startup/ LAMP stack on Raspberry Pi with Kodi running at startup]

[http://ozzmaker.com/enable-x-windows-on-piscreen/ Enable X Window System on PiScreen]

[https://raspberrypi.stackexchange.com/questions/59310/remove-boot-messages-all-text-in-jessie Remove boot messages all text in Raspbian - Raspberry Pi Stack Exchange]

[https://raspberrypi.stackexchange.com/questions/47823/how-to-prevent-autologin-of-gui How to prevent or allow autologin of GUI - Raspberry Pi Stack Exchange]

[http://www.raspberry-projects.com/pi/pi-operating-systems/raspbian/auto-running-programs-gui Auto running programs LXDE - Raspberry Pi Projects]

And, if you would rather, it is easier to follow the process provided by this link to modify the Raspbian image before installing it onto the microSD card.

[https://wiki.debian.org/RaspberryPi/qemu-user-static Modifying Raspbian with qemu-user-static]

The above link describes removing the DE from a Raspbian image, though Raspbian Lite is a much better starting point for using Qemu for this purpose.

You can also use the X11 Window System to autostart Kodi by placing a statup script in the /etc/X11/Xsession.d/ directory.

[https://debian-administration.org/article/50/Running_applications_automatically_when_X_starts Running applications automatically when X starts]

<pre>
nano /etc/X11/Xsession.d/startup-local
</pre>

Insert this text into the new file. Use CTRL + O + Enter + X to save the file.

<pre>
#!/bin/sh
/usr/bin/kodi
</pre>

If you have a WM, such as Blackbox you can add it here as well.

<pre>
#!/bin/sh
blackbox &
/usr/bin/kodi
</pre>

Set permissions to make it executable. Use the ampersand to run an application in the background, such as a WM you only need to for the purpose of launching Kodi but not if you don't want to use the WM itself. Kodi will not launch without a DE or WM, but placing the ampersand "&" at the end of the command makes it run in the background where it can do its job out of sight. Also, make sure to start a WM or DE before running an application in the foreground. This is not necessary for apps running in the background.

<pre>
chmod 755 /etc/X11/Xsession.d/startup-local
</pre>

If Kodi is not installed at the standard path, find it using the '''which''' command.

<pre>
which kodi
</pre>

This feature is available on X Window System operating systems most Linux distributions use the X Window System.

== Disable / enable the login prompt ==

You can disable the graphical login prompt.

<pre>
systemctl set-default multi-user.target
</pre>

To enable it again use.

<pre>
systemctl set-default graphical.target
</pre>

If you are using an autologin method associated with your DE or WM, you '''do not''' want to disable the graphical login.

Even if you are using something like [https://github.com/graysky2/kodi-standalone-service Kodi Standalone Service], you still need use a WM or a DE that installs the '''x-window-manager''' software package.

To ensure you have this installed use the '''which''' command.

<pre>
which x-window-manager
</pre>

If there is no such package, you can use '''apt''' to search your Linux distributions repository.

<pre>
apt-cache search x-window-manager
</pre>

This will general a list of packages containing '''x-window-manager''', which cannot be installed alone. If you are not using a DE, you need to use a WM. And, you can also use a compositing WM like Compiz, for fast 3D effects.

[https://wiki.archlinux.org/index.php/Compiz Compiz - ArchWiki]

A note on using Kodi Standalone Service, this package runs Kodi as a '''systemd''' service and disables the login for user '''kodi''' and will not work when autologin is enabled. In fact, it will break the login process if you autologin user '''kodi''' and run Kodi Standalone Service at the same time. This package is installed automatically with the standard Kodi package when you install Kodi on Raspbian, but must be configured manually for all other Linux distributions. You can run the '''which''' command to find this package as well.

<pre>
which kodi-standalone
</pre>

Be advised, Kodi Standalone Service still launches the Kodi GUI and still requires a WM even though it is running as a '''systemd''' service. When you install a WM such as '''xfwm4''' (the WM for XFCE4), the CLI will tell you if it provides the '''x-window-manager''' package.

<pre>
Setting up xfwm4 (4.12.4-1) ...
update-alternatives: using /usr/bin/xfwm4 to provide /usr/bin/x-window-manager (x-window-manager) in auto mode
</pre>

If you do not see this message at the end of the installation, the WM you selected does not provide this software package and may not actually be a complete WM itself but only part of a package containing a WM.

For a great example on exactly how you would do this with '''xfwm4''', see this ArchWiki entry.

[https://wiki.archlinux.org/index.php/Xfwm XFWM - ArchWiki]

== Create custom Xsession script ==

Most systems utilize the client version of the X11 software an Xsession requires requires.

Upgrade to the server versions of the X Window System, if you want to utilize all the greatness of the X Window System.

Because of the lack of documentation, it is probably better to find tweaks and hacks on wikis and support pages rather than forums. For instance, the Ubuntu wiki is usually a good source of information.

[https://wiki.ubuntu.com/CustomXSession CustomXSession - Ubuntu Wiki]

<pre>apt install xauth xorg xinit xserver-xorg-core xserver-xorg xserver-common</pre>

Create a custom Xsession script with a text editor.

<pre>
nano ~/.xinitrc
</pre>

To run Kodi full-screen make sure the text reads:

<pre>
#!/usr/bin/env bash
exec gnome-session
/usr/bin/kodi -fs
</pre>

Replace the '''gnome-session''' with the DE or WM command you are using. See the last section for examples.

To make '''~/.xinitrc''' executable use.

<pre>
chmod +x ~/.xinitrc
</pre>

Use '''sudo''' and the '''~/.xinitrc''' file to configure '''~/.xsession'''.

<pre>
sudo -H -u kodi bash -c "ln -s ~/.xinitrc ~/.xsession"
</pre>

You need to use '''sudo''' to run this command. If you do not have '''sudo''', install it.

<pre>
apt install sudo
</pre>

If you create a symbolic link and want to remove it, simply remove the existing '''.xsession''' file you created.

<pre>
rm /home/kodi/.xsession
</pre>

Remember you can modify use and reuse the '''~/.xinitrc''' file to configure '''~/.xsession''' as often as you want. That is the purpose of the file. It does nothing on its own until you associate it with a user. On some systems using a DE such as Gnome, not all systems using Gnome, it may be necessary for '''.xsession''' to be '''.xsessionrc'''. Though this is more likely the case for organization network computers than a personal one, where configurations may vary on a diversity of machines. Most of the time, it will be '''.xsession''' rather than '''.xsessionrc''' that you want to create.

You must also autostart the X Window system, which differs somewhat from scenario to scenario. For most setups, all that is necessary is to edit the '''.bashrc''' file.

<pre>
nano ~/.bashrc
</pre>

Add the following as shown.

<pre>
if [[ ! $DISPLAY && $XDG_VTNR -eq 1 ]]; then
exec startx
fi
</pre>

If you wish to remain logged in after quitting X, remove the '''exec''' from the above. Other configurations can be applied, but are irrelevant to autostarting Kodi.

[https://wiki.archlinux.org/index.php/Xinit#Autostart_X_at_login Xinit Autostart X at login]

If you are using LightDM and you just want to create a new login entry for user '''kodi''', you must create a new file.

<pre>
nano /usr/share/xsessions/custom.desktop
</pre>

And insert the following text.

<pre>
[Desktop Entry]
Name=Xsession
Exec=/etc/X11/Xsession
</pre>

This will create a new login option for the custom Xsession. Only this one entry is necessary for LightDM and X11 to find the '''~/.xsession''' script in each user's home directory.

== Xsession to boot to app / WM / DE ==

You can use any window manager or desktop enviroment with a custom Xsession script as long as it is intalled.

You do this by creating '''~/.xinitrc''' script that contains the command to start the WM or DE.

For instance, if you are using FluxBox.

<pre>
#!/usr/bin/env bash
exec fluxbox &
/usr/bin/kodi -fs
</pre>

The <code>-fs</code> option is full-screen.

To run Gnome in the background, but launch Kodi in the foreground.

<pre>
#!/usr/bin/env bash
exec gnome-session &
/usr/bin/kodi -fs
</pre>

Use the '''~/.xinitrc''' file to configure '''~/.xsession''' to create a custom login for any user, not just Kodi.

<pre>
sudo -H -u [username] bash -c "ln -s ~/.xinitrc ~/.xsession"
</pre>

You must reconfigure Xserver for any user that is not a privileged user to be able to start a custom Xsession.

<pre>
dpkg-reconfigure xserver-xorg-legacy
</pre>

And / or...

<pre>
dpkg-reconfigure xserver-xorg
</pre>

If both packages are installed, you must reconfigure both. Not all systems will use or require the legacy package to allow non-root users to start X.

== Add a custom Grub entry ==

If you want to boot to the CLI and manually launch an app or boot directly to Kodi without a DE or WM, add a custom grub entry.

The right way to add a custom grub entry is to copy the menu entry you want to change or duplicate.

Copy the default Grub configuration file and open it with a text editor on your desktop. If you use a text editor on the CLI, the text will be cut off by the window when copying and pasting.

<pre>
cp /boot/grub/grub.cfg grub.cfg
gedit grub.cfg
</pre>

Copy the menu entry and paste it into '''40_custom''' with a text editor in the CLI.

<pre>
nano /etc/grub.d/40_custom
</pre>

Where the menu entry contains '''quiet splash''' change it to '''text''' instead.

You should also change the name of the entry!

I just appended mine with “CLI” for command line interface.

To update Grub:

<pre>
update-grub
</pre>

To launch a WM you can type its name. I use Enlightment 17 or Fluxbox. It must be installed.

<pre>
fluxbox
</pre>

You must have FluxBox installed. There are countless other window managers.

To launch a DE you enter the appropriate command. For Gnome desktop:

<pre>
gnome-session
</pre>

For KDE:

<pre>
startkde
</pre>

or

<pre>
plasma-desktop
</pre>

For XFCE:

<pre>
startxfce4
</pre>

For Mate:

<pre>
mate-session
</pre>

For LXDE:

<pre>
startlxde
</pre>

You can either manually launch your apps, boot right into them, or create an Xsession for each user. This is great when you want to create a Kodi user for running Kodi only, and for making sure you can still login to your DE with your regular user account. You can boot to any app full-screen this way, not just Kodi. You can create a custom Xsession script for any user, configured with any startup applications running in full-screen mode or normally.

By optionally creating a Grub menu entry, you can create a different Grub menu selection to boot only to the CLI and start an Xsession with a script or run commands manually.

HOW-TO:Autostart Kodi for Linux

2018-04-28T15:25:13Z

W3tech: /* Configure Kodi to autostart */

<section begin="intro" /><big>Any or all or any combination of these methods can be used to configure a Debian-based X Window System to boot directly to Kodi. This should work on any Linux using the X Window System, but these instructions are particular to Debian derivatives, such as Ubuntu. A server edition is best for running only Kodi, but this page assumes booting into a desktop OS, not a server distro. However, the instructions here can be used for a server distro with even less configuration than for a desktop. Experiment inside VirtualBox before you apply any of these to your system and make a backup.</big><section end="intro" />

__TOC__

== Switch to root ==

<pre>
su
</pre>

or

<pre>
sudo su
</pre>

== Create a Kodi user ==

To use Kodi full-screen, you only have to create a standard user.

<pre>
adduser kodi
</pre>

To remove the password use:

<pre>
passwd -d kodi
</pre>

== Customize LightDM to autologin ==

You can utilize the ability to customize LightDM data manager by changing the builtin custom configuration file '''50-myconfig.conf''' using '''nano''' or another text editor. If you have no DE or WM you can install '''lightdm''', but should make sure to do a bit of research before you do. Most versions of Linux use LightDM, but many server versions do not. For Ubuntu Server with no DE, for example, installing '''lightdm''' is okay and necessary. Changing the behavior of LightDM is done using a custom '''50-myconfig.conf''' configuration file.

To see if you have '''lightdm''' use '''which'''.

<pre>
which lightdm
</pre>

If not, install it with '''apt'''.

<pre>
apt install lightdm
</pre>

Create a custom configuration file called '''50-myconfig.conf''' using '''nano''' or other CLI text editor.

<pre>
mkdir /etc/lightdm/lightdm.conf.d/
nano /etc/lightdm/lightdm.conf.d/50-myconfig.conf
</pre>

Inside this new file add the following text.

<pre>
[SeatDefaults]
autologin-user=kodi
</pre>

== Configure Kodi to autostart ==

Configure Kodi to autostart.

<pre>
mkdir -p ~/.config/autostart
ln -s /usr/bin/kodi ~/.config/autostart
</pre>

This method of autostart requires a desktop environment or DE. This is done a bit differently by each DE. Some helpful links can easily be found in today's Web search using any search engine.

[http://edoceo.com/gui/xfce-autostart-apps Autostart Apps in XFCE]

The Raspberry Pi is a bit more of a tweak, but these are excellent links that will tell you how. The first link is the most helpful to making sure Kodi autostarts in Pi. There are many settings on the Pi that control boot, and the first link gives the best most trouble-free way to boot directly to Kodi. The others facilitate more tweaks and settings relevant to other uses of the X Window System.

[https://www.leowkahman.com/2016/03/05/lamp-stack-on-raspberry-pi-with-kodi-running-at-startup/ LAMP stack on Raspberry Pi with Kodi running at startup]

[http://ozzmaker.com/enable-x-windows-on-piscreen/ Enable X Window System on PiScreen]

[https://raspberrypi.stackexchange.com/questions/59310/remove-boot-messages-all-text-in-jessie Remove boot messages all text in Raspbian - Raspberry Pi Stack Exchange]

[https://raspberrypi.stackexchange.com/questions/47823/how-to-prevent-autologin-of-gui How to prevent or allow autologin of GUI - Raspberry Pi Stack Exchange]

[http://www.raspberry-projects.com/pi/pi-operating-systems/raspbian/auto-running-programs-gui Auto running programs LXDE - Raspberry Pi Projects]

And, if you would rather, it is easier to follow the process provided by this link to modify the Raspbian image before installing it onto the microSD card.

[https://wiki.debian.org/RaspberryPi/qemu-user-static Modifying Raspbian with qemu-user-static]

The above link describes removing the DE from a Raspbian image, though Raspbian Lite is a much better starting point for using Qemu for this purpose.

You can also use the X11 Window System to autostart Kodi by placing a statup script in the /etc/X11/Xsession.d/ directory.

[https://debian-administration.org/article/50/Running_applications_automatically_when_X_starts Running applications automatically when X starts]

<pre>
nano /etc/X11/Xsession.d/startup-local
</pre>

Insert this text into the new file. Use CTRL + O + Enter + X to save the file.

<pre>
#!/bin/sh
/usr/bin/kodi
</pre>

If you have a WM, such as Blackbox you can add it here as well.

<pre>
#!/bin/sh
blackbox &
/usr/bin/kodi
</pre>

Set permissions to make it executable. Use the ampersand to run an application in the background, such as a WM you only need to for the purpose of launching Kodi but not if you don't want to use the WM itself. Kodi will not launch without a DE or WM, but placing the ampersand "&" at the end of the command makes it run in the background where it can do its job out of sight. Also, make sure to start a WM or DE before running an application in the foreground. This is not necessary for apps running in the background.

<pre>
chmod 755 /etc/X11/Xsession.d/startup-local
</pre>

If Kodi is not installed at the standard path, find it using the '''which''' command.

<pre>
which kodi
</pre>

This feature is available on X Window System operating systems most Linux distributions use the X Window System.

== Disable / enable the login prompt ==

You can disable the graphical login prompt.

<pre>
systemctl set-default multi-user.target
</pre>

To enable it again use.

<pre>
systemctl set-default graphical.target
</pre>

If you are using an autologin method associated with your DE or WM, you '''do not''' want to disable the graphical login.

Even if you are using something like [https://github.com/graysky2/kodi-standalone-service Kodi Standalone Service], you still need use a WM or a DE that installs the '''x-window-manager''' software package.

To ensure you have this installed use the '''which''' command.

<pre>
which x-window-manager
</pre>

If there is no such package, you can use '''apt''' to search your Linux distributions repository.

<pre>
apt-cache search x-window-manager
</pre>

This will general a list of packages containing '''x-window-manager''', which cannot be installed alone. If you are not using a DE, you need to use a WM. And, you can also use a compositing WM like Compiz, for fast 3D effects.

[https://wiki.archlinux.org/index.php/Compiz Compiz - ArchWiki]

A note on using Kodi Standalone Service, this package runs Kodi as a '''systemd''' service and disables the login for user '''kodi''' and will not work when autologin is enabled. In fact, it will break the login process if you autologin user '''kodi''' and run Kodi Standalone Service at the same time. This package is installed automatically with the standard Kodi package when you install Kodi on Raspbian, but must be configured manually for all other Linux distributions. You can run the '''which''' command to find this package as well.

<pre>
which kodi-standalone
</pre>

Be advised, Kodi Standalone Service still launches the Kodi GUI and still requires a WM even though it is running as a '''systemd''' service. When you install a WM such as '''xfwm4''' (the WM for XFCE4), the CLI will tell you if it provides the '''x-window-manager''' package.

<pre>
Setting up xfwm4 (4.12.4-1) ...
update-alternatives: using /usr/bin/xfwm4 to provide /usr/bin/x-window-manager (x-window-manager) in auto mode
</pre>

If you do not see this message at the end of the installation, the WM you selected does not provide this software package and may not actually be a complete WM itself but only part of a package containing a WM.

For a great example on exactly how you would do this with '''xfwm4''', see this ArchWiki entry.

[https://wiki.archlinux.org/index.php/Xfwm XFWM - ArchWiki]

== Create custom Xsession script ==

Most systems utilize the client version of the X11 software an Xsession requires requires.

Upgrade to the server versions of the X Window System, if you want to utilize all the greatness of the X Window System.

Because of the lack of documentation, it is probably better to find tweaks and hacks on wikis and support pages rather than forums. For instance, the Ubuntu wiki is usually a good source of information.

[https://wiki.ubuntu.com/CustomXSession CustomXSession - Ubuntu Wiki]

<pre>apt install xauth xorg xinit xserver-xorg-core xserver-xorg xserver-common</pre>

Create a custom Xsession script with a text editor.

<pre>
nano ~/.xinitrc
</pre>

To run Kodi full-screen make sure the text reads:

<pre>
#!/usr/bin/env bash
exec gnome-session
/usr/bin/kodi -fs
</pre>

Replace the '''gnome-session''' with the DE or WM command you are using. See the last section for examples.

To make '''~/.xinitrc''' executable use.

<pre>
chmod +x ~/.xinitrc
</pre>

Use '''sudo''' and the '''~/.xinitrc''' file to configure '''~/.xsession'''.

<pre>
sudo -H -u kodi bash -c "ln -s ~/.xinitrc ~/.xsession"
</pre>

You need to use '''sudo''' to run this command. If you do not have '''sudo''', install it.

<pre>
apt install sudo
</pre>

If you create a symbolic link and want to remove it, simply remove the existing '''.xsession''' file you created.

<pre>
rm /home/kodi/.xsession
</pre>

Remember you can modify use and reuse the '''~/.xinitrc''' file to configure '''~/.xsession''' as often as you want. That is the purpose of the file. It does nothing on its own until you associate it with a user. On some systems using a DE such as Gnome, not all systems using Gnome, it may be necessary for '''.xsession''' to be '''.xsessionrc'''. Though this is more likely the case for organization network computers than a personal one, where configurations may vary on a diversity of machines. Most of the time, it will be '''.xsession''' rather than '''.xsessionrc''' that you want to create.

You must also autostart the X Window system, which differs somewhat from scenario to scenario. For most setups, all that is necessary is to edit the '''.bashrc''' file.

<pre>
nano ~/.bashrc
</pre>

Add the following as shown.

<pre>
if [[ ! $DISPLAY && $XDG_VTNR -eq 1 ]]; then
exec startx
fi
</pre>

If you wish to remain logged in after quitting X, remove the '''exec''' from the above. Other configurations can be applied, but are irrelevant to autostarting Kodi.

[https://wiki.archlinux.org/index.php/Xinit#Autostart_X_at_login Xinit Autostart X at login]

If you are using LightDM and you just want to create a new login entry for user '''kodi''', you must create a new file.

<pre>
nano /usr/share/xsessions/custom.desktop
</pre>

And insert the following text.

<pre>
[Desktop Entry]
Name=Xsession
Exec=/etc/X11/Xsession
</pre>

This will create a new login option for the custom Xsession. Only this one entry is necessary for LightDM and X11 to find the '''~/.xsession''' script in each user's home directory.

== Xsession to boot to app / WM / DE ==

You can use any window manager or desktop enviroment with a custom Xsession script as long as it is intalled.

You do this by creating '''~/.xinitrc''' script that contains the command to start the WM or DE.

For instance, if you are using FluxBox.

<pre>
#!/usr/bin/env bash
exec fluxbox &
/usr/bin/kodi -fs
</pre>

The <code>-fs</code> option is full-screen.

To run Gnome in the background, but launch Kodi in the foreground.

<pre>
#!/usr/bin/env bash
exec gnome-session &
/usr/bin/kodi -fs
</pre>

Use the '''~/.xinitrc''' file to configure '''~/.xsession''' to create a custom login for any user, not just Kodi.

<pre>
sudo -H -u [username] bash -c "ln -s ~/.xinitrc ~/.xsession"
</pre>

You must reconfigure Xserver for any user that is not a privileged user to be able to start a custom Xsession.

<pre>
dpkg-reconfigure xserver-xorg-legacy
</pre>

And / or...

<pre>
dpkg-reconfigure xserver-xorg
</pre>

If both packages are installed, you must reconfigure both. Not all systems will use or require the legacy package to allow non-root users to start X.

== Add a custom Grub entry ==

If you want to boot to the CLI and manually launch an app or boot directly to Kodi without a DE or WM, add a custom grub entry.

The right way to add a custom grub entry is to copy the menu entry you want to change or duplicate.

Copy the default Grub configuration file and open it with a text editor on your desktop. If you use a text editor on the CLI, the text will be cut off by the window when copying and pasting.

<pre>
cp /boot/grub/grub.cfg grub.cfg
gedit grub.cfg
</pre>

Copy the menu entry and paste it into '''40_custom''' with a text editor in the CLI.

<pre>
nano /etc/grub.d/40_custom
</pre>

Where the menu entry contains '''quiet splash''' change it to '''text''' instead.

You should also change the name of the entry!

I just appended mine with “CLI” for command line interface.

To update Grub:

<pre>
update-grub
</pre>

To launch a WM you can type its name. I use Enlightment 17 or Fluxbox. It must be installed.

<pre>
fluxbox
</pre>

You must have FluxBox installed. There are countless other window managers.

To launch a DE you enter the appropriate command. For Gnome desktop:

<pre>
gnome-session
</pre>

For KDE:

<pre>
startkde
</pre>

or

<pre>
plasma-desktop
</pre>

For XFCE:

<pre>
startxfce4
</pre>

For Mate:

<pre>
mate-session
</pre>

For LXDE:

<pre>
startlxde
</pre>

You can either manually launch your apps, boot right into them, or create an Xsession for each user. This is great when you want to create a Kodi user for running Kodi only, and for making sure you can still login to your DE with your regular user account. You can boot to any app full-screen this way, not just Kodi. You can create a custom Xsession script for any user, configured with any startup applications running in full-screen mode or normally.

By optionally creating a Grub menu entry, you can create a different Grub menu selection to boot only to the CLI and start an Xsession with a script or run commands manually.

HOW-TO:Autostart Kodi for Linux

2018-04-28T14:53:06Z

W3tech: /* Configure Kodi to autostart */

<section begin="intro" /><big>Any or all or any combination of these methods can be used to configure a Debian-based X Window System to boot directly to Kodi. This should work on any Linux using the X Window System, but these instructions are particular to Debian derivatives, such as Ubuntu. A server edition is best for running only Kodi, but this page assumes booting into a desktop OS, not a server distro. However, the instructions here can be used for a server distro with even less configuration than for a desktop. Experiment inside VirtualBox before you apply any of these to your system and make a backup.</big><section end="intro" />

__TOC__

== Switch to root ==

<pre>
su
</pre>

or

<pre>
sudo su
</pre>

== Create a Kodi user ==

To use Kodi full-screen, you only have to create a standard user.

<pre>
adduser kodi
</pre>

To remove the password use:

<pre>
passwd -d kodi
</pre>

== Customize LightDM to autologin ==

You can utilize the ability to customize LightDM data manager by changing the builtin custom configuration file '''50-myconfig.conf''' using '''nano''' or another text editor. If you have no DE or WM you can install '''lightdm''', but should make sure to do a bit of research before you do. Most versions of Linux use LightDM, but many server versions do not. For Ubuntu Server with no DE, for example, installing '''lightdm''' is okay and necessary. Changing the behavior of LightDM is done using a custom '''50-myconfig.conf''' configuration file.

To see if you have '''lightdm''' use '''which'''.

<pre>
which lightdm
</pre>

If not, install it with '''apt'''.

<pre>
apt install lightdm
</pre>

Create a custom configuration file called '''50-myconfig.conf''' using '''nano''' or other CLI text editor.

<pre>
mkdir /etc/lightdm/lightdm.conf.d/
nano /etc/lightdm/lightdm.conf.d/50-myconfig.conf
</pre>

Inside this new file add the following text.

<pre>
[SeatDefaults]
autologin-user=kodi
</pre>

== Configure Kodi to autostart ==

Configure Kodi to autostart.

<pre>
mkdir -p ~/.config/autostart
ln -s /usr/bin/kodi ~/.config/autostart
</pre>

This method of autostart requires a desktop environment or DE. This is done a bit differently by each DE. Some helpful links can easily be found in today's Web search using any search engine.

[http://edoceo.com/gui/xfce-autostart-apps Autostart Apps in XFCE]

The Raspberry Pi is a bit more of a tweak, but these are excellent links that will tell you how. The first link is the most helpful to making sure Kodi autostarts in Pi. There are many settings on the Pi that control boot, and the first link gives the best most trouble-free way to boot directly to Kodi. The others facilitate more tweaks and settings relevant to other uses of the X Window System.

[https://www.leowkahman.com/2016/03/05/lamp-stack-on-raspberry-pi-with-kodi-running-at-startup/ LAMP stack on Raspberry Pi with Kodi running at startup]

[http://ozzmaker.com/enable-x-windows-on-piscreen/ Enable X Window System on PiScreen]

[https://raspberrypi.stackexchange.com/questions/59310/remove-boot-messages-all-text-in-jessie Remove boot messages all text in Raspbian - Raspberry Pi Stack Exchange]

[https://raspberrypi.stackexchange.com/questions/47823/how-to-prevent-autologin-of-gui How to prevent or allow autologin of GUI - Raspberry Pi Stack Exchange]

[http://www.raspberry-projects.com/pi/pi-operating-systems/raspbian/auto-running-programs-gui Auto running programs LXDE - Raspberry Pi Projects]

And, if you would rather, it is easier to follow the process provided by this link to modify the Raspbian image before installing it onto the microSD card.

[https://wiki.debian.org/RaspberryPi/qemu-user-static Modifying Raspbian with qemu-user-static]

The above link describes removing the DE from a Raspbian image, though Raspbian Lite is a much better starting point for using Qemu for this purpose.

On Raspbian, you configure LightDM differently for autologin, which is necessary to boot directly to Kodi.

<pre>
nano /etc/lightdm/lightdm.conf
</pre>

Uncomment the following line.

<pre>
#autologin-user=
</pre>

And add the user you want to autologin and autostart Kodi. The user is named '''kodi''' in this example.

<pre>
autologin-user=kodi
</pre>

If Kodi is not installed at the standard path, find it using the '''which''' command.

<pre>
which kodi
</pre>

You can also use the X11 Window System to autostart Kodi by placing a statup script in the /etc/X11/Xsession.d/ directory.

[https://debian-administration.org/article/50/Running_applications_automatically_when_X_starts Running applications automatically when X starts]

<pre>
nano /etc/X11/Xsession.d/startup-local
</pre>

Insert this text into the new file. Use CTRL + O + Enter + X to save the file.

<pre>
#!/bin/sh
/usr/bin/kodi
</pre>

If you have a WM, such as Blackbox you can add it here as well.

<pre>
#!/bin/sh
blackbox &
/usr/bin/kodi
</pre>

Set permissions to make it executable. Use the ampersand to run an application in the background, such as a WM you only need to for the purpose of launching Kodi but not if you don't want to use the WM itself. Kodi will not launch without a DE or WM, but placing the ampersand "&" at the end of the command makes it run in the background where it can do its job out of sight. Also, make sure to start a WM or DE before running an application in the foreground. This is not necessary for apps running in the background.

<pre>
chmod 755 /etc/X11/Xsession.d/startup-local
</pre>

This feature is available on X Window System operating systems without upgrading to Xserver. Most Linux distributions use the X Window System.

== Disable / enable the login prompt ==

You can disable the graphical login prompt.

<pre>
systemctl set-default multi-user.target
</pre>

To enable it again use.

<pre>
systemctl set-default graphical.target
</pre>

If you are using an autologin method associated with your DE or WM, you '''do not''' want to disable the graphical login.

Even if you are using something like [https://github.com/graysky2/kodi-standalone-service Kodi Standalone Service], you still need use a WM or a DE that installs the '''x-window-manager''' software package.

To ensure you have this installed use the '''which''' command.

<pre>
which x-window-manager
</pre>

If there is no such package, you can use '''apt''' to search your Linux distributions repository.

<pre>
apt-cache search x-window-manager
</pre>

This will general a list of packages containing '''x-window-manager''', which cannot be installed alone. If you are not using a DE, you need to use a WM. And, you can also use a compositing WM like Compiz, for fast 3D effects.

[https://wiki.archlinux.org/index.php/Compiz Compiz - ArchWiki]

A note on using Kodi Standalone Service, this package runs Kodi as a '''systemd''' service and disables the login for user '''kodi''' and will not work when autologin is enabled. In fact, it will break the login process if you autologin user '''kodi''' and run Kodi Standalone Service at the same time. This package is installed automatically with the standard Kodi package when you install Kodi on Raspbian, but must be configured manually for all other Linux distributions. You can run the '''which''' command to find this package as well.

<pre>
which kodi-standalone
</pre>

Be advised, Kodi Standalone Service still launches the Kodi GUI and still requires a WM even though it is running as a '''systemd''' service. When you install a WM such as '''xfwm4''' (the WM for XFCE4), the CLI will tell you if it provides the '''x-window-manager''' package.

<pre>
Setting up xfwm4 (4.12.4-1) ...
update-alternatives: using /usr/bin/xfwm4 to provide /usr/bin/x-window-manager (x-window-manager) in auto mode
</pre>

If you do not see this message at the end of the installation, the WM you selected does not provide this software package and may not actually be a complete WM itself but only part of a package containing a WM.

For a great example on exactly how you would do this with '''xfwm4''', see this ArchWiki entry.

[https://wiki.archlinux.org/index.php/Xfwm XFWM - ArchWiki]

== Create custom Xsession script ==

Most systems utilize the client version of the X11 software an Xsession requires requires.

Upgrade to the server versions of the X Window System, if you want to utilize all the greatness of the X Window System.

Because of the lack of documentation, it is probably better to find tweaks and hacks on wikis and support pages rather than forums. For instance, the Ubuntu wiki is usually a good source of information.

[https://wiki.ubuntu.com/CustomXSession CustomXSession - Ubuntu Wiki]

<pre>apt install xauth xorg xinit xserver-xorg-core xserver-xorg xserver-common</pre>

Create a custom Xsession script with a text editor.

<pre>
nano ~/.xinitrc
</pre>

To run Kodi full-screen make sure the text reads:

<pre>
#!/usr/bin/env bash
exec gnome-session
/usr/bin/kodi -fs
</pre>

Replace the '''gnome-session''' with the DE or WM command you are using. See the last section for examples.

To make '''~/.xinitrc''' executable use.

<pre>
chmod +x ~/.xinitrc
</pre>

Use '''sudo''' and the '''~/.xinitrc''' file to configure '''~/.xsession'''.

<pre>
sudo -H -u kodi bash -c "ln -s ~/.xinitrc ~/.xsession"
</pre>

You need to use '''sudo''' to run this command. If you do not have '''sudo''', install it.

<pre>
apt install sudo
</pre>

If you create a symbolic link and want to remove it, simply remove the existing '''.xsession''' file you created.

<pre>
rm /home/kodi/.xsession
</pre>

Remember you can modify use and reuse the '''~/.xinitrc''' file to configure '''~/.xsession''' as often as you want. That is the purpose of the file. It does nothing on its own until you associate it with a user. On some systems using a DE such as Gnome, not all systems using Gnome, it may be necessary for '''.xsession''' to be '''.xsessionrc'''. Though this is more likely the case for organization network computers than a personal one, where configurations may vary on a diversity of machines. Most of the time, it will be '''.xsession''' rather than '''.xsessionrc''' that you want to create.

You must also autostart the X Window system, which differs somewhat from scenario to scenario. For most setups, all that is necessary is to edit the '''.bashrc''' file.

<pre>
nano ~/.bashrc
</pre>

Add the following as shown.

<pre>
if [[ ! $DISPLAY && $XDG_VTNR -eq 1 ]]; then
exec startx
fi
</pre>

If you wish to remain logged in after quitting X, remove the '''exec''' from the above. Other configurations can be applied, but are irrelevant to autostarting Kodi.

[https://wiki.archlinux.org/index.php/Xinit#Autostart_X_at_login Xinit Autostart X at login]

If you are using LightDM and you just want to create a new login entry for user '''kodi''', you must create a new file.

<pre>
nano /usr/share/xsessions/custom.desktop
</pre>

And insert the following text.

<pre>
[Desktop Entry]
Name=Xsession
Exec=/etc/X11/Xsession
</pre>

This will create a new login option for the custom Xsession. Only this one entry is necessary for LightDM and X11 to find the '''~/.xsession''' script in each user's home directory.

== Xsession to boot to app / WM / DE ==

You can use any window manager or desktop enviroment with a custom Xsession script as long as it is intalled.

You do this by creating '''~/.xinitrc''' script that contains the command to start the WM or DE.

For instance, if you are using FluxBox.

<pre>
#!/usr/bin/env bash
exec fluxbox &
/usr/bin/kodi -fs
</pre>

The <code>-fs</code> option is full-screen.

To run Gnome in the background, but launch Kodi in the foreground.

<pre>
#!/usr/bin/env bash
exec gnome-session &
/usr/bin/kodi -fs
</pre>

Use the '''~/.xinitrc''' file to configure '''~/.xsession''' to create a custom login for any user, not just Kodi.

<pre>
sudo -H -u [username] bash -c "ln -s ~/.xinitrc ~/.xsession"
</pre>

You must reconfigure Xserver for any user that is not a privileged user to be able to start a custom Xsession.

<pre>
dpkg-reconfigure xserver-xorg-legacy
</pre>

And / or...

<pre>
dpkg-reconfigure xserver-xorg
</pre>

If both packages are installed, you must reconfigure both. Not all systems will use or require the legacy package to allow non-root users to start X.

== Add a custom Grub entry ==

If you want to boot to the CLI and manually launch an app or boot directly to Kodi without a DE or WM, add a custom grub entry.

The right way to add a custom grub entry is to copy the menu entry you want to change or duplicate.

Copy the default Grub configuration file and open it with a text editor on your desktop. If you use a text editor on the CLI, the text will be cut off by the window when copying and pasting.

<pre>
cp /boot/grub/grub.cfg grub.cfg
gedit grub.cfg
</pre>

Copy the menu entry and paste it into '''40_custom''' with a text editor in the CLI.

<pre>
nano /etc/grub.d/40_custom
</pre>

Where the menu entry contains '''quiet splash''' change it to '''text''' instead.

You should also change the name of the entry!

I just appended mine with “CLI” for command line interface.

To update Grub:

<pre>
update-grub
</pre>

To launch a WM you can type its name. I use Enlightment 17 or Fluxbox. It must be installed.

<pre>
fluxbox
</pre>

You must have FluxBox installed. There are countless other window managers.

To launch a DE you enter the appropriate command. For Gnome desktop:

<pre>
gnome-session
</pre>

For KDE:

<pre>
startkde
</pre>

or

<pre>
plasma-desktop
</pre>

For XFCE:

<pre>
startxfce4
</pre>

For Mate:

<pre>
mate-session
</pre>

For LXDE:

<pre>
startlxde
</pre>

You can either manually launch your apps, boot right into them, or create an Xsession for each user. This is great when you want to create a Kodi user for running Kodi only, and for making sure you can still login to your DE with your regular user account. You can boot to any app full-screen this way, not just Kodi. You can create a custom Xsession script for any user, configured with any startup applications running in full-screen mode or normally.

By optionally creating a Grub menu entry, you can create a different Grub menu selection to boot only to the CLI and start an Xsession with a script or run commands manually.

HOW-TO:Autostart Kodi for Linux

2018-04-28T09:40:49Z

W3tech: /* Create custom Xsession script */

<section begin="intro" /><big>Any or all or any combination of these methods can be used to configure a Debian-based X Window System to boot directly to Kodi. This should work on any Linux using the X Window System, but these instructions are particular to Debian derivatives, such as Ubuntu. A server edition is best for running only Kodi, but this page assumes booting into a desktop OS, not a server distro. However, the instructions here can be used for a server distro with even less configuration than for a desktop. Experiment inside VirtualBox before you apply any of these to your system and make a backup.</big><section end="intro" />

__TOC__

== Switch to root ==

<pre>
su
</pre>

or

<pre>
sudo su
</pre>

== Create a Kodi user ==

To use Kodi full-screen, you only have to create a standard user.

<pre>
adduser kodi
</pre>

To remove the password use:

<pre>
passwd -d kodi
</pre>

== Customize LightDM to autologin ==

You can utilize the ability to customize LightDM data manager by changing the builtin custom configuration file '''50-myconfig.conf''' using '''nano''' or another text editor. If you have no DE or WM you can install '''lightdm''', but should make sure to do a bit of research before you do. Most versions of Linux use LightDM, but many server versions do not. For Ubuntu Server with no DE, for example, installing '''lightdm''' is okay and necessary. Changing the behavior of LightDM is done using a custom '''50-myconfig.conf''' configuration file.

To see if you have '''lightdm''' use '''which'''.

<pre>
which lightdm
</pre>

If not, install it with '''apt'''.

<pre>
apt install lightdm
</pre>

Create a custom configuration file called '''50-myconfig.conf''' using '''nano''' or other CLI text editor.

<pre>
mkdir /etc/lightdm/lightdm.conf.d/
nano /etc/lightdm/lightdm.conf.d/50-myconfig.conf
</pre>

Inside this new file add the following text.

<pre>
[SeatDefaults]
autologin-user=kodi
</pre>

== Configure Kodi to autostart ==

Configure Kodi to autostart.

<pre>
mkdir -p ~/.config/autostart
ln -s /usr/bin/kodi ~/.config/autostart
</pre>

This method of autostart requires a desktop environment or DE. This is done a bit differently by each DE. Some helpful links can easily be found in today's Web search using any search engine.

[http://edoceo.com/gui/xfce-autostart-apps Autostart Apps in XFCE]

The Raspberry Pi is a bit more of a tweak, but these are excellent links that will tell you how. The first link is the most helpful to making sure Kodi autostarts in Pi. There are many settings on the Pi that control boot, and the first link gives the best most trouble-free way to boot directly to Kodi. The others facilitate more tweaks and settings relevant to other uses of the X Window System.

[https://www.leowkahman.com/2016/03/05/lamp-stack-on-raspberry-pi-with-kodi-running-at-startup/ LAMP stack on Raspberry Pi with Kodi running at startup]

[http://ozzmaker.com/enable-x-windows-on-piscreen/ Enable X Window System on PiScreen]

[https://raspberrypi.stackexchange.com/questions/59310/remove-boot-messages-all-text-in-jessie Remove boot messages all text in Raspbian - Raspberry Pi Stack Exchange]

[https://raspberrypi.stackexchange.com/questions/47823/how-to-prevent-autologin-of-gui How to prevent or allow autologin of GUI - Raspberry Pi Stack Exchange]

[http://www.raspberry-projects.com/pi/pi-operating-systems/raspbian/auto-running-programs-gui Auto running programs LXDE - Raspberry Pi Projects]

And, if you would rather, it is easier to follow the process provided by this link to modify the Raspbian image before installing it onto the microSD card.

[https://wiki.debian.org/RaspberryPi/qemu-user-static Modifying Raspbian with qemu-user-static]

The above link describes removing the DE from a Raspbian image, though Raspbian Lite is a much better starting point for using Qemu for this purpose.

On Raspbian, you configure LightDM differently for autologin, which is necessary to boot directly to Kodi.

<pre>
nano /etc/lightdm/lightdm.conf
</pre>

Uncomment the following line.

<pre>
#autologin-user=
</pre>

And add the user you want to autologin and autostart Kodi. The user is named '''kodi''' in this example.

<pre>
autologin-user=kodi
</pre>

If Kodi is not installed at the standard path, find it using the '''which''' command.

<pre>
which kodi
</pre>

You can also use the X11 Window System to autostart Kodi.

<pre>
nano /etc/X11/Xsession.d/startup-local
</pre>

Insert this text into the new file. Use CTRL + O + Enter + X to save the file.

<pre>
#!/bin/sh
/usr/bin/kodi
</pre>

If you have a WM, such as Blackbox you can add it here as well.

<pre>
#!/bin/sh
blackbox &
/usr/bin/kodi
</pre>

Set permissions to make it executable. Use the ampersand to run an application in the background, such as a WM you only need to for the purpose of launching Kodi but not if you don't want to use the WM itself. Kodi will not launch without a DE or WM, but placing the ampersand "&" at the end of the command makes it run in the background where it can do its job out of sight. Also, make sure to start a WM or DE before running an application in the foreground. This is not necessary for apps running in the background.

<pre>
chmod 755 /etc/X11/Xsession.d/startup-local
</pre>

This feature is available on X Window System operating systems without upgrading to Xserver. Most Linux distributions use the X Window System.

== Disable / enable the login prompt ==

You can disable the graphical login prompt.

<pre>
systemctl set-default multi-user.target
</pre>

To enable it again use.

<pre>
systemctl set-default graphical.target
</pre>

If you are using an autologin method associated with your DE or WM, you '''do not''' want to disable the graphical login.

Even if you are using something like [https://github.com/graysky2/kodi-standalone-service Kodi Standalone Service], you still need use a WM or a DE that installs the '''x-window-manager''' software package.

To ensure you have this installed use the '''which''' command.

<pre>
which x-window-manager
</pre>

If there is no such package, you can use '''apt''' to search your Linux distributions repository.

<pre>
apt-cache search x-window-manager
</pre>

This will general a list of packages containing '''x-window-manager''', which cannot be installed alone. If you are not using a DE, you need to use a WM. And, you can also use a compositing WM like Compiz, for fast 3D effects.

[https://wiki.archlinux.org/index.php/Compiz Compiz - ArchWiki]

A note on using Kodi Standalone Service, this package runs Kodi as a '''systemd''' service and disables the login for user '''kodi''' and will not work when autologin is enabled. In fact, it will break the login process if you autologin user '''kodi''' and run Kodi Standalone Service at the same time. This package is installed automatically with the standard Kodi package when you install Kodi on Raspbian, but must be configured manually for all other Linux distributions. You can run the '''which''' command to find this package as well.

<pre>
which kodi-standalone
</pre>

Be advised, Kodi Standalone Service still launches the Kodi GUI and still requires a WM even though it is running as a '''systemd''' service. When you install a WM such as '''xfwm4''' (the WM for XFCE4), the CLI will tell you if it provides the '''x-window-manager''' package.

<pre>
Setting up xfwm4 (4.12.4-1) ...
update-alternatives: using /usr/bin/xfwm4 to provide /usr/bin/x-window-manager (x-window-manager) in auto mode
</pre>

If you do not see this message at the end of the installation, the WM you selected does not provide this software package and may not actually be a complete WM itself but only part of a package containing a WM.

For a great example on exactly how you would do this with '''xfwm4''', see this ArchWiki entry.

[https://wiki.archlinux.org/index.php/Xfwm XFWM - ArchWiki]

== Create custom Xsession script ==

Most systems utilize the client version of the X11 software an Xsession requires requires.

Upgrade to the server versions of the X Window System, if you want to utilize all the greatness of the X Window System.

Because of the lack of documentation, it is probably better to find tweaks and hacks on wikis and support pages rather than forums. For instance, the Ubuntu wiki is usually a good source of information.

[https://wiki.ubuntu.com/CustomXSession CustomXSession - Ubuntu Wiki]

<pre>apt install xauth xorg xinit xserver-xorg-core xserver-xorg xserver-common</pre>

Create a custom Xsession script with a text editor.

<pre>
nano ~/.xinitrc
</pre>

To run Kodi full-screen make sure the text reads:

<pre>
#!/usr/bin/env bash
exec gnome-session
/usr/bin/kodi -fs
</pre>

Replace the '''gnome-session''' with the DE or WM command you are using. See the last section for examples.

To make '''~/.xinitrc''' executable use.

<pre>
chmod +x ~/.xinitrc
</pre>

Use '''sudo''' and the '''~/.xinitrc''' file to configure '''~/.xsession'''.

<pre>
sudo -H -u kodi bash -c "ln -s ~/.xinitrc ~/.xsession"
</pre>

You need to use '''sudo''' to run this command. If you do not have '''sudo''', install it.

<pre>
apt install sudo
</pre>

If you create a symbolic link and want to remove it, simply remove the existing '''.xsession''' file you created.

<pre>
rm /home/kodi/.xsession
</pre>

Remember you can modify use and reuse the '''~/.xinitrc''' file to configure '''~/.xsession''' as often as you want. That is the purpose of the file. It does nothing on its own until you associate it with a user. On some systems using a DE such as Gnome, not all systems using Gnome, it may be necessary for '''.xsession''' to be '''.xsessionrc'''. Though this is more likely the case for organization network computers than a personal one, where configurations may vary on a diversity of machines. Most of the time, it will be '''.xsession''' rather than '''.xsessionrc''' that you want to create.

You must also autostart the X Window system, which differs somewhat from scenario to scenario. For most setups, all that is necessary is to edit the '''.bashrc''' file.

<pre>
nano ~/.bashrc
</pre>

Add the following as shown.

<pre>
if [[ ! $DISPLAY && $XDG_VTNR -eq 1 ]]; then
exec startx
fi
</pre>

If you wish to remain logged in after quitting X, remove the '''exec''' from the above. Other configurations can be applied, but are irrelevant to autostarting Kodi.

[https://wiki.archlinux.org/index.php/Xinit#Autostart_X_at_login Xinit Autostart X at login]

If you are using LightDM and you just want to create a new login entry for user '''kodi''', you must create a new file.

<pre>
nano /usr/share/xsessions/custom.desktop
</pre>

And insert the following text.

<pre>
[Desktop Entry]
Name=Xsession
Exec=/etc/X11/Xsession
</pre>

This will create a new login option for the custom Xsession. Only this one entry is necessary for LightDM and X11 to find the '''~/.xsession''' script in each user's home directory.

== Xsession to boot to app / WM / DE ==

You can use any window manager or desktop enviroment with a custom Xsession script as long as it is intalled.

You do this by creating '''~/.xinitrc''' script that contains the command to start the WM or DE.

For instance, if you are using FluxBox.

<pre>
#!/usr/bin/env bash
exec fluxbox &
/usr/bin/kodi -fs
</pre>

The <code>-fs</code> option is full-screen.

To run Gnome in the background, but launch Kodi in the foreground.

<pre>
#!/usr/bin/env bash
exec gnome-session &
/usr/bin/kodi -fs
</pre>

Use the '''~/.xinitrc''' file to configure '''~/.xsession''' to create a custom login for any user, not just Kodi.

<pre>
sudo -H -u [username] bash -c "ln -s ~/.xinitrc ~/.xsession"
</pre>

You must reconfigure Xserver for any user that is not a privileged user to be able to start a custom Xsession.

<pre>
dpkg-reconfigure xserver-xorg-legacy
</pre>

And / or...

<pre>
dpkg-reconfigure xserver-xorg
</pre>

If both packages are installed, you must reconfigure both. Not all systems will use or require the legacy package to allow non-root users to start X.

== Add a custom Grub entry ==

If you want to boot to the CLI and manually launch an app or boot directly to Kodi without a DE or WM, add a custom grub entry.

The right way to add a custom grub entry is to copy the menu entry you want to change or duplicate.

Copy the default Grub configuration file and open it with a text editor on your desktop. If you use a text editor on the CLI, the text will be cut off by the window when copying and pasting.

<pre>
cp /boot/grub/grub.cfg grub.cfg
gedit grub.cfg
</pre>

Copy the menu entry and paste it into '''40_custom''' with a text editor in the CLI.

<pre>
nano /etc/grub.d/40_custom
</pre>

Where the menu entry contains '''quiet splash''' change it to '''text''' instead.

You should also change the name of the entry!

I just appended mine with “CLI” for command line interface.

To update Grub:

<pre>
update-grub
</pre>

To launch a WM you can type its name. I use Enlightment 17 or Fluxbox. It must be installed.

<pre>
fluxbox
</pre>

You must have FluxBox installed. There are countless other window managers.

To launch a DE you enter the appropriate command. For Gnome desktop:

<pre>
gnome-session
</pre>

For KDE:

<pre>
startkde
</pre>

or

<pre>
plasma-desktop
</pre>

For XFCE:

<pre>
startxfce4
</pre>

For Mate:

<pre>
mate-session
</pre>

For LXDE:

<pre>
startlxde
</pre>

You can either manually launch your apps, boot right into them, or create an Xsession for each user. This is great when you want to create a Kodi user for running Kodi only, and for making sure you can still login to your DE with your regular user account. You can boot to any app full-screen this way, not just Kodi. You can create a custom Xsession script for any user, configured with any startup applications running in full-screen mode or normally.

By optionally creating a Grub menu entry, you can create a different Grub menu selection to boot only to the CLI and start an Xsession with a script or run commands manually.

HOW-TO talk:Autostart Kodi for Linux

2018-04-28T09:07:30Z

W3tech:

HOW-TO:Autostart Kodi for Linux

2018-04-28T09:05:21Z

W3tech: /* Xsession to boot to app / WM / DE */

<section begin="intro" /><big>Any or all or any combination of these methods can be used to configure a Debian-based X Window System to boot directly to Kodi. This should work on any Linux using the X Window System, but these instructions are particular to Debian derivatives, such as Ubuntu. A server edition is best for running only Kodi, but this page assumes booting into a desktop OS, not a server distro. However, the instructions here can be used for a server distro with even less configuration than for a desktop. Experiment inside VirtualBox before you apply any of these to your system and make a backup.</big><section end="intro" />

__TOC__

== Switch to root ==

<pre>
su
</pre>

or

<pre>
sudo su
</pre>

== Create a Kodi user ==

To use Kodi full-screen, you only have to create a standard user.

<pre>
adduser kodi
</pre>

To remove the password use:

<pre>
passwd -d kodi
</pre>

== Customize LightDM to autologin ==

You can utilize the ability to customize LightDM data manager by changing the builtin custom configuration file '''50-myconfig.conf''' using '''nano''' or another text editor. If you have no DE or WM you can install '''lightdm''', but should make sure to do a bit of research before you do. Most versions of Linux use LightDM, but many server versions do not. For Ubuntu Server with no DE, for example, installing '''lightdm''' is okay and necessary. Changing the behavior of LightDM is done using a custom '''50-myconfig.conf''' configuration file.

To see if you have '''lightdm''' use '''which'''.

<pre>
which lightdm
</pre>

If not, install it with '''apt'''.

<pre>
apt install lightdm
</pre>

Create a custom configuration file called '''50-myconfig.conf''' using '''nano''' or other CLI text editor.

<pre>
mkdir /etc/lightdm/lightdm.conf.d/
nano /etc/lightdm/lightdm.conf.d/50-myconfig.conf
</pre>

Inside this new file add the following text.

<pre>
[SeatDefaults]
autologin-user=kodi
</pre>

== Configure Kodi to autostart ==

Configure Kodi to autostart.

<pre>
mkdir -p ~/.config/autostart
ln -s /usr/bin/kodi ~/.config/autostart
</pre>

This method of autostart requires a desktop environment or DE. This is done a bit differently by each DE. Some helpful links can easily be found in today's Web search using any search engine.

[http://edoceo.com/gui/xfce-autostart-apps Autostart Apps in XFCE]

The Raspberry Pi is a bit more of a tweak, but these are excellent links that will tell you how. The first link is the most helpful to making sure Kodi autostarts in Pi. There are many settings on the Pi that control boot, and the first link gives the best most trouble-free way to boot directly to Kodi. The others facilitate more tweaks and settings relevant to other uses of the X Window System.

[https://www.leowkahman.com/2016/03/05/lamp-stack-on-raspberry-pi-with-kodi-running-at-startup/ LAMP stack on Raspberry Pi with Kodi running at startup]

[http://ozzmaker.com/enable-x-windows-on-piscreen/ Enable X Window System on PiScreen]

[https://raspberrypi.stackexchange.com/questions/59310/remove-boot-messages-all-text-in-jessie Remove boot messages all text in Raspbian - Raspberry Pi Stack Exchange]

[https://raspberrypi.stackexchange.com/questions/47823/how-to-prevent-autologin-of-gui How to prevent or allow autologin of GUI - Raspberry Pi Stack Exchange]

[http://www.raspberry-projects.com/pi/pi-operating-systems/raspbian/auto-running-programs-gui Auto running programs LXDE - Raspberry Pi Projects]

And, if you would rather, it is easier to follow the process provided by this link to modify the Raspbian image before installing it onto the microSD card.

[https://wiki.debian.org/RaspberryPi/qemu-user-static Modifying Raspbian with qemu-user-static]

The above link describes removing the DE from a Raspbian image, though Raspbian Lite is a much better starting point for using Qemu for this purpose.

On Raspbian, you configure LightDM differently for autologin, which is necessary to boot directly to Kodi.

<pre>
nano /etc/lightdm/lightdm.conf
</pre>

Uncomment the following line.

<pre>
#autologin-user=
</pre>

And add the user you want to autologin and autostart Kodi. The user is named '''kodi''' in this example.

<pre>
autologin-user=kodi
</pre>

If Kodi is not installed at the standard path, find it using the '''which''' command.

<pre>
which kodi
</pre>

You can also use the X11 Window System to autostart Kodi.

<pre>
nano /etc/X11/Xsession.d/startup-local
</pre>

Insert this text into the new file. Use CTRL + O + Enter + X to save the file.

<pre>
#!/bin/sh
/usr/bin/kodi
</pre>

If you have a WM, such as Blackbox you can add it here as well.

<pre>
#!/bin/sh
blackbox &
/usr/bin/kodi
</pre>

Set permissions to make it executable. Use the ampersand to run an application in the background, such as a WM you only need to for the purpose of launching Kodi but not if you don't want to use the WM itself. Kodi will not launch without a DE or WM, but placing the ampersand "&" at the end of the command makes it run in the background where it can do its job out of sight. Also, make sure to start a WM or DE before running an application in the foreground. This is not necessary for apps running in the background.

<pre>
chmod 755 /etc/X11/Xsession.d/startup-local
</pre>

This feature is available on X Window System operating systems without upgrading to Xserver. Most Linux distributions use the X Window System.

== Disable / enable the login prompt ==

You can disable the graphical login prompt.

<pre>
systemctl set-default multi-user.target
</pre>

To enable it again use.

<pre>
systemctl set-default graphical.target
</pre>

If you are using an autologin method associated with your DE or WM, you '''do not''' want to disable the graphical login.

Even if you are using something like [https://github.com/graysky2/kodi-standalone-service Kodi Standalone Service], you still need use a WM or a DE that installs the '''x-window-manager''' software package.

To ensure you have this installed use the '''which''' command.

<pre>
which x-window-manager
</pre>

If there is no such package, you can use '''apt''' to search your Linux distributions repository.

<pre>
apt-cache search x-window-manager
</pre>

This will general a list of packages containing '''x-window-manager''', which cannot be installed alone. If you are not using a DE, you need to use a WM. And, you can also use a compositing WM like Compiz, for fast 3D effects.

[https://wiki.archlinux.org/index.php/Compiz Compiz - ArchWiki]

A note on using Kodi Standalone Service, this package runs Kodi as a '''systemd''' service and disables the login for user '''kodi''' and will not work when autologin is enabled. In fact, it will break the login process if you autologin user '''kodi''' and run Kodi Standalone Service at the same time. This package is installed automatically with the standard Kodi package when you install Kodi on Raspbian, but must be configured manually for all other Linux distributions. You can run the '''which''' command to find this package as well.

<pre>
which kodi-standalone
</pre>

Be advised, Kodi Standalone Service still launches the Kodi GUI and still requires a WM even though it is running as a '''systemd''' service. When you install a WM such as '''xfwm4''' (the WM for XFCE4), the CLI will tell you if it provides the '''x-window-manager''' package.

<pre>
Setting up xfwm4 (4.12.4-1) ...
update-alternatives: using /usr/bin/xfwm4 to provide /usr/bin/x-window-manager (x-window-manager) in auto mode
</pre>

If you do not see this message at the end of the installation, the WM you selected does not provide this software package and may not actually be a complete WM itself but only part of a package containing a WM.

For a great example on exactly how you would do this with '''xfwm4''', see this ArchWiki entry.

[https://wiki.archlinux.org/index.php/Xfwm XFWM - ArchWiki]

== Create custom Xsession script ==

Most systems utilize the client version of the X11 software an Xsession requires requires.

Upgrade to the server versions of the X Window System, if you want to utilize all the greatness of the X Window System.

Because of the lack of documentation, it is probably better to find tweaks and hacks on wikis and support pages rather than forums. For instance, the Ubuntu wiki is usually a good source of information.

[https://wiki.ubuntu.com/CustomXSession CustomXSession - Ubuntu Wiki]

<pre>apt install xauth xorg xinit xserver-xorg-core xserver-xorg xserver-common</pre>

Create a custom Xsession script with a text editor.

<pre>
nano ~/.xinitrc
</pre>

To run Kodi full-screen make sure the text reads:

<pre>
#!/usr/bin/env bash
exec gnome-session
/usr/bin/kodi -fs
</pre>

Replace the '''gnome-session''' with the DE or WM command you are using. See the last section for examples.

To make '''~/.xinitrc''' executable use.

<pre>
chmod +x ~/.xinitrc
</pre>

Use '''sudo''' and the '''~/.xinitrc''' file to configure '''~/.xsession'''.

<pre>
sudo -H -u kodi bash -c "ln -s ~/.xinitrc ~/.xsession"
</pre>

You need to use '''sudo''' to run this command. If you do not have '''sudo''', install it.

<pre>
apt install sudo
</pre>

If you create a symbolic link and want to remove it, simply remove the existing '''.xsession''' file you created.

<pre>
rm /home/kodi/.xsession
</pre>

Remember you can modify use and reuse the '''~/.xinitrc''' file to configure '''~/.xsession''' as often as you want. That is the purpose of the file. It does nothing on its own until you associate it with a user. On some systems using a DE such as Gnome, not all systems using Gnome, it may be necessary for '''.xsession''' to be '''.xsessionrc'''. Though this is more likely the case for organization network computers than a personal one, where configurations may vary on a diversity of machines. Most of the time, it will be '''.xsession''' rather than '''.xsessionrc''' that you want to create.

You must also autostart the X Window system, which differs somewhat from scenario to scenario. For most setups, all that is necessary is to edit the '''.bashrc''' file.

<pre>
nano ~/.bashrc
</pre>

Add the following as shown.

<pre>
if [[ ! $DISPLAY && $XDG_VTNR -eq 1 ]]; then
exec startx
fi
</pre>

If you wish to remain logged in after quitting X, remove the '''exec''' from the above. Other configurations can be applied, but are irrelevant to autostarting Kodi.

[https://wiki.archlinux.org/index.php/Xinit#Autostart_X_at_login Xinit Autostart X at login]

If you are using LightDM and you just want to create a new login entry for user '''kodi''', you must create a new file.

<pre>
nano /usr/share/xsessions/custom.desktop
</pre>

And insert the following text.

[Desktop Entry]
Name=Xsession
Exec=/etc/X11/Xsession

This will create a new login option for the custom Xsession. Only this one entry is necessary for LightDM and X11 to find the '''~/.xsession''' script in each user's home directory.

== Xsession to boot to app / WM / DE ==

You can use any window manager or desktop enviroment with a custom Xsession script as long as it is intalled.

You do this by creating '''~/.xinitrc''' script that contains the command to start the WM or DE.

For instance, if you are using FluxBox.

<pre>
#!/usr/bin/env bash
exec fluxbox &
/usr/bin/kodi -fs
</pre>

The <code>-fs</code> option is full-screen.

To run Gnome in the background, but launch Kodi in the foreground.

<pre>
#!/usr/bin/env bash
exec gnome-session &
/usr/bin/kodi -fs
</pre>

Use the '''~/.xinitrc''' file to configure '''~/.xsession''' to create a custom login for any user, not just Kodi.

<pre>
sudo -H -u [username] bash -c "ln -s ~/.xinitrc ~/.xsession"
</pre>

You must reconfigure Xserver for any user that is not a privileged user to be able to start a custom Xsession.

<pre>
dpkg-reconfigure xserver-xorg-legacy
</pre>

And / or...

<pre>
dpkg-reconfigure xserver-xorg
</pre>

If both packages are installed, you must reconfigure both. Not all systems will use or require the legacy package to allow non-root users to start X.

== Add a custom Grub entry ==

If you want to boot to the CLI and manually launch an app or boot directly to Kodi without a DE or WM, add a custom grub entry.

The right way to add a custom grub entry is to copy the menu entry you want to change or duplicate.

Copy the default Grub configuration file and open it with a text editor on your desktop. If you use a text editor on the CLI, the text will be cut off by the window when copying and pasting.

<pre>
cp /boot/grub/grub.cfg grub.cfg
gedit grub.cfg
</pre>

Copy the menu entry and paste it into '''40_custom''' with a text editor in the CLI.

<pre>
nano /etc/grub.d/40_custom
</pre>

Where the menu entry contains '''quiet splash''' change it to '''text''' instead.

You should also change the name of the entry!

I just appended mine with “CLI” for command line interface.

To update Grub:

<pre>
update-grub
</pre>

To launch a WM you can type its name. I use Enlightment 17 or Fluxbox. It must be installed.

<pre>
fluxbox
</pre>

You must have FluxBox installed. There are countless other window managers.

To launch a DE you enter the appropriate command. For Gnome desktop:

<pre>
gnome-session
</pre>

For KDE:

<pre>
startkde
</pre>

or

<pre>
plasma-desktop
</pre>

For XFCE:

<pre>
startxfce4
</pre>

For Mate:

<pre>
mate-session
</pre>

For LXDE:

<pre>
startlxde
</pre>

You can either manually launch your apps, boot right into them, or create an Xsession for each user. This is great when you want to create a Kodi user for running Kodi only, and for making sure you can still login to your DE with your regular user account. You can boot to any app full-screen this way, not just Kodi. You can create a custom Xsession script for any user, configured with any startup applications running in full-screen mode or normally.

By optionally creating a Grub menu entry, you can create a different Grub menu selection to boot only to the CLI and start an Xsession with a script or run commands manually.

HOW-TO:Autostart Kodi for Linux

2018-04-28T09:01:07Z

W3tech: /* Create custom Xsession script */

<section begin="intro" /><big>Any or all or any combination of these methods can be used to configure a Debian-based X Window System to boot directly to Kodi. This should work on any Linux using the X Window System, but these instructions are particular to Debian derivatives, such as Ubuntu. A server edition is best for running only Kodi, but this page assumes booting into a desktop OS, not a server distro. However, the instructions here can be used for a server distro with even less configuration than for a desktop. Experiment inside VirtualBox before you apply any of these to your system and make a backup.</big><section end="intro" />

__TOC__

== Switch to root ==

<pre>
su
</pre>

or

<pre>
sudo su
</pre>

== Create a Kodi user ==

To use Kodi full-screen, you only have to create a standard user.

<pre>
adduser kodi
</pre>

To remove the password use:

<pre>
passwd -d kodi
</pre>

== Customize LightDM to autologin ==

You can utilize the ability to customize LightDM data manager by changing the builtin custom configuration file '''50-myconfig.conf''' using '''nano''' or another text editor. If you have no DE or WM you can install '''lightdm''', but should make sure to do a bit of research before you do. Most versions of Linux use LightDM, but many server versions do not. For Ubuntu Server with no DE, for example, installing '''lightdm''' is okay and necessary. Changing the behavior of LightDM is done using a custom '''50-myconfig.conf''' configuration file.

To see if you have '''lightdm''' use '''which'''.

<pre>
which lightdm
</pre>

If not, install it with '''apt'''.

<pre>
apt install lightdm
</pre>

Create a custom configuration file called '''50-myconfig.conf''' using '''nano''' or other CLI text editor.

<pre>
mkdir /etc/lightdm/lightdm.conf.d/
nano /etc/lightdm/lightdm.conf.d/50-myconfig.conf
</pre>

Inside this new file add the following text.

<pre>
[SeatDefaults]
autologin-user=kodi
</pre>

== Configure Kodi to autostart ==

Configure Kodi to autostart.

<pre>
mkdir -p ~/.config/autostart
ln -s /usr/bin/kodi ~/.config/autostart
</pre>

This method of autostart requires a desktop environment or DE. This is done a bit differently by each DE. Some helpful links can easily be found in today's Web search using any search engine.

[http://edoceo.com/gui/xfce-autostart-apps Autostart Apps in XFCE]

The Raspberry Pi is a bit more of a tweak, but these are excellent links that will tell you how. The first link is the most helpful to making sure Kodi autostarts in Pi. There are many settings on the Pi that control boot, and the first link gives the best most trouble-free way to boot directly to Kodi. The others facilitate more tweaks and settings relevant to other uses of the X Window System.

[https://www.leowkahman.com/2016/03/05/lamp-stack-on-raspberry-pi-with-kodi-running-at-startup/ LAMP stack on Raspberry Pi with Kodi running at startup]

[http://ozzmaker.com/enable-x-windows-on-piscreen/ Enable X Window System on PiScreen]

[https://raspberrypi.stackexchange.com/questions/59310/remove-boot-messages-all-text-in-jessie Remove boot messages all text in Raspbian - Raspberry Pi Stack Exchange]

[https://raspberrypi.stackexchange.com/questions/47823/how-to-prevent-autologin-of-gui How to prevent or allow autologin of GUI - Raspberry Pi Stack Exchange]

[http://www.raspberry-projects.com/pi/pi-operating-systems/raspbian/auto-running-programs-gui Auto running programs LXDE - Raspberry Pi Projects]

And, if you would rather, it is easier to follow the process provided by this link to modify the Raspbian image before installing it onto the microSD card.

[https://wiki.debian.org/RaspberryPi/qemu-user-static Modifying Raspbian with qemu-user-static]

The above link describes removing the DE from a Raspbian image, though Raspbian Lite is a much better starting point for using Qemu for this purpose.

On Raspbian, you configure LightDM differently for autologin, which is necessary to boot directly to Kodi.

<pre>
nano /etc/lightdm/lightdm.conf
</pre>

Uncomment the following line.

<pre>
#autologin-user=
</pre>

And add the user you want to autologin and autostart Kodi. The user is named '''kodi''' in this example.

<pre>
autologin-user=kodi
</pre>

If Kodi is not installed at the standard path, find it using the '''which''' command.

<pre>
which kodi
</pre>

You can also use the X11 Window System to autostart Kodi.

<pre>
nano /etc/X11/Xsession.d/startup-local
</pre>

Insert this text into the new file. Use CTRL + O + Enter + X to save the file.

<pre>
#!/bin/sh
/usr/bin/kodi
</pre>

If you have a WM, such as Blackbox you can add it here as well.

<pre>
#!/bin/sh
blackbox &
/usr/bin/kodi
</pre>

Set permissions to make it executable. Use the ampersand to run an application in the background, such as a WM you only need to for the purpose of launching Kodi but not if you don't want to use the WM itself. Kodi will not launch without a DE or WM, but placing the ampersand "&" at the end of the command makes it run in the background where it can do its job out of sight. Also, make sure to start a WM or DE before running an application in the foreground. This is not necessary for apps running in the background.

<pre>
chmod 755 /etc/X11/Xsession.d/startup-local
</pre>

This feature is available on X Window System operating systems without upgrading to Xserver. Most Linux distributions use the X Window System.

== Disable / enable the login prompt ==

You can disable the graphical login prompt.

<pre>
systemctl set-default multi-user.target
</pre>

To enable it again use.

<pre>
systemctl set-default graphical.target
</pre>

If you are using an autologin method associated with your DE or WM, you '''do not''' want to disable the graphical login.

Even if you are using something like [https://github.com/graysky2/kodi-standalone-service Kodi Standalone Service], you still need use a WM or a DE that installs the '''x-window-manager''' software package.

To ensure you have this installed use the '''which''' command.

<pre>
which x-window-manager
</pre>

If there is no such package, you can use '''apt''' to search your Linux distributions repository.

<pre>
apt-cache search x-window-manager
</pre>

This will general a list of packages containing '''x-window-manager''', which cannot be installed alone. If you are not using a DE, you need to use a WM. And, you can also use a compositing WM like Compiz, for fast 3D effects.

[https://wiki.archlinux.org/index.php/Compiz Compiz - ArchWiki]

A note on using Kodi Standalone Service, this package runs Kodi as a '''systemd''' service and disables the login for user '''kodi''' and will not work when autologin is enabled. In fact, it will break the login process if you autologin user '''kodi''' and run Kodi Standalone Service at the same time. This package is installed automatically with the standard Kodi package when you install Kodi on Raspbian, but must be configured manually for all other Linux distributions. You can run the '''which''' command to find this package as well.

<pre>
which kodi-standalone
</pre>

Be advised, Kodi Standalone Service still launches the Kodi GUI and still requires a WM even though it is running as a '''systemd''' service. When you install a WM such as '''xfwm4''' (the WM for XFCE4), the CLI will tell you if it provides the '''x-window-manager''' package.

<pre>
Setting up xfwm4 (4.12.4-1) ...
update-alternatives: using /usr/bin/xfwm4 to provide /usr/bin/x-window-manager (x-window-manager) in auto mode
</pre>

If you do not see this message at the end of the installation, the WM you selected does not provide this software package and may not actually be a complete WM itself but only part of a package containing a WM.

For a great example on exactly how you would do this with '''xfwm4''', see this ArchWiki entry.

[https://wiki.archlinux.org/index.php/Xfwm XFWM - ArchWiki]

== Create custom Xsession script ==

Most systems utilize the client version of the X11 software an Xsession requires requires.

Upgrade to the server versions of the X Window System, if you want to utilize all the greatness of the X Window System.

Because of the lack of documentation, it is probably better to find tweaks and hacks on wikis and support pages rather than forums. For instance, the Ubuntu wiki is usually a good source of information.

[https://wiki.ubuntu.com/CustomXSession CustomXSession - Ubuntu Wiki]

<pre>apt install xauth xorg xinit xserver-xorg-core xserver-xorg xserver-common</pre>

Create a custom Xsession script with a text editor.

<pre>
nano ~/.xinitrc
</pre>

To run Kodi full-screen make sure the text reads:

<pre>
#!/usr/bin/env bash
exec gnome-session
/usr/bin/kodi -fs
</pre>

Replace the '''gnome-session''' with the DE or WM command you are using. See the last section for examples.

To make '''~/.xinitrc''' executable use.

<pre>
chmod +x ~/.xinitrc
</pre>

Use '''sudo''' and the '''~/.xinitrc''' file to configure '''~/.xsession'''.

<pre>
sudo -H -u kodi bash -c "ln -s ~/.xinitrc ~/.xsession"
</pre>

You need to use '''sudo''' to run this command. If you do not have '''sudo''', install it.

<pre>
apt install sudo
</pre>

If you create a symbolic link and want to remove it, simply remove the existing '''.xsession''' file you created.

<pre>
rm /home/kodi/.xsession
</pre>

Remember you can modify use and reuse the '''~/.xinitrc''' file to configure '''~/.xsession''' as often as you want. That is the purpose of the file. It does nothing on its own until you associate it with a user. On some systems using a DE such as Gnome, not all systems using Gnome, it may be necessary for '''.xsession''' to be '''.xsessionrc'''. Though this is more likely the case for organization network computers than a personal one, where configurations may vary on a diversity of machines. Most of the time, it will be '''.xsession''' rather than '''.xsessionrc''' that you want to create.

You must also autostart the X Window system, which differs somewhat from scenario to scenario. For most setups, all that is necessary is to edit the '''.bashrc''' file.

<pre>
nano ~/.bashrc
</pre>

Add the following as shown.

<pre>
if [[ ! $DISPLAY && $XDG_VTNR -eq 1 ]]; then
exec startx
fi
</pre>

If you wish to remain logged in after quitting X, remove the '''exec''' from the above. Other configurations can be applied, but are irrelevant to autostarting Kodi.

[https://wiki.archlinux.org/index.php/Xinit#Autostart_X_at_login Xinit Autostart X at login]

If you are using LightDM and you just want to create a new login entry for user '''kodi''', you must create a new file.

<pre>
nano /usr/share/xsessions/custom.desktop
</pre>

And insert the following text.

[Desktop Entry]
Name=Xsession
Exec=/etc/X11/Xsession

This will create a new login option for the custom Xsession. Only this one entry is necessary for LightDM and X11 to find the '''~/.xsession''' script in each user's home directory.

== Xsession to boot to app / WM / DE ==

You can use any window manager or desktop enviroment with a custom Xsession script as long as it is intalled.

You do this by creating '''~/.xinitrc''' script that contains the command to start the WM or DE.

For instance, if you are using FluxBox?

<pre>
#!/usr/bin/env bash
exec fluxbox &
/usr/bin/kodi -fs
</pre>

The <code>-fs</code> option is full-screen.

To start Gnome with Kodi full-screen:

<pre>
#!/usr/bin/env bash
exec gnome-session
/usr/bin/kodi -fs
</pre>

To run Gnome in the background, but launch Kodi in the foreground.

<pre>
#!/usr/bin/env bash
exec gnome-session &
/usr/bin/kodi -fs
</pre>

Use the '''~/.xinitrc''' file to configure '''~/.xsession''' to create a custom login for any user, not just Kodi.

<pre>
sudo -H -u [username] bash -c "ln -s ~/.xinitrc ~/.xsession"
</pre>

You must reconfigure Xserver for any user that is not a privileged user to be able to start a custom Xsession.

<pre>
dpkg-reconfigure xserver-xorg-legacy
</pre>

And / or...

<pre>
dpkg-reconfigure xserver-xorg
</pre>

If both packages are installed, you must reconfigure both. Not all systems will use or require the legacy package to allow non-root users to start X.

== Add a custom Grub entry ==

If you want to boot to the CLI and manually launch an app or boot directly to Kodi without a DE or WM, add a custom grub entry.

The right way to add a custom grub entry is to copy the menu entry you want to change or duplicate.

Copy the default Grub configuration file and open it with a text editor on your desktop. If you use a text editor on the CLI, the text will be cut off by the window when copying and pasting.

<pre>
cp /boot/grub/grub.cfg grub.cfg
gedit grub.cfg
</pre>

Copy the menu entry and paste it into '''40_custom''' with a text editor in the CLI.

<pre>
nano /etc/grub.d/40_custom
</pre>

Where the menu entry contains '''quiet splash''' change it to '''text''' instead.

You should also change the name of the entry!

I just appended mine with “CLI” for command line interface.

To update Grub:

<pre>
update-grub
</pre>

To launch a WM you can type its name. I use Enlightment 17 or Fluxbox. It must be installed.

<pre>
fluxbox
</pre>

You must have FluxBox installed. There are countless other window managers.

To launch a DE you enter the appropriate command. For Gnome desktop:

<pre>
gnome-session
</pre>

For KDE:

<pre>
startkde
</pre>

or

<pre>
plasma-desktop
</pre>

For XFCE:

<pre>
startxfce4
</pre>

For Mate:

<pre>
mate-session
</pre>

For LXDE:

<pre>
startlxde
</pre>

You can either manually launch your apps, boot right into them, or create an Xsession for each user. This is great when you want to create a Kodi user for running Kodi only, and for making sure you can still login to your DE with your regular user account. You can boot to any app full-screen this way, not just Kodi. You can create a custom Xsession script for any user, configured with any startup applications running in full-screen mode or normally.

By optionally creating a Grub menu entry, you can create a different Grub menu selection to boot only to the CLI and start an Xsession with a script or run commands manually.

HOW-TO:Autostart Kodi for Linux

2018-04-28T08:41:12Z

W3tech: /* Xsession to boot to app / WM / DE */

<section begin="intro" /><big>Any or all or any combination of these methods can be used to configure a Debian-based X Window System to boot directly to Kodi. This should work on any Linux using the X Window System, but these instructions are particular to Debian derivatives, such as Ubuntu. A server edition is best for running only Kodi, but this page assumes booting into a desktop OS, not a server distro. However, the instructions here can be used for a server distro with even less configuration than for a desktop. Experiment inside VirtualBox before you apply any of these to your system and make a backup.</big><section end="intro" />

__TOC__

== Switch to root ==

<pre>
su
</pre>

or

<pre>
sudo su
</pre>

== Create a Kodi user ==

To use Kodi full-screen, you only have to create a standard user.

<pre>
adduser kodi
</pre>

To remove the password use:

<pre>
passwd -d kodi
</pre>

== Customize LightDM to autologin ==

You can utilize the ability to customize LightDM data manager by changing the builtin custom configuration file '''50-myconfig.conf''' using '''nano''' or another text editor. If you have no DE or WM you can install '''lightdm''', but should make sure to do a bit of research before you do. Most versions of Linux use LightDM, but many server versions do not. For Ubuntu Server with no DE, for example, installing '''lightdm''' is okay and necessary. Changing the behavior of LightDM is done using a custom '''50-myconfig.conf''' configuration file.

To see if you have '''lightdm''' use '''which'''.

<pre>
which lightdm
</pre>

If not, install it with '''apt'''.

<pre>
apt install lightdm
</pre>

Create a custom configuration file called '''50-myconfig.conf''' using '''nano''' or other CLI text editor.

<pre>
mkdir /etc/lightdm/lightdm.conf.d/
nano /etc/lightdm/lightdm.conf.d/50-myconfig.conf
</pre>

Inside this new file add the following text.

<pre>
[SeatDefaults]
autologin-user=kodi
</pre>

== Configure Kodi to autostart ==

Configure Kodi to autostart.

<pre>
mkdir -p ~/.config/autostart
ln -s /usr/bin/kodi ~/.config/autostart
</pre>

This method of autostart requires a desktop environment or DE. This is done a bit differently by each DE. Some helpful links can easily be found in today's Web search using any search engine.

[http://edoceo.com/gui/xfce-autostart-apps Autostart Apps in XFCE]

The Raspberry Pi is a bit more of a tweak, but these are excellent links that will tell you how. The first link is the most helpful to making sure Kodi autostarts in Pi. There are many settings on the Pi that control boot, and the first link gives the best most trouble-free way to boot directly to Kodi. The others facilitate more tweaks and settings relevant to other uses of the X Window System.

[https://www.leowkahman.com/2016/03/05/lamp-stack-on-raspberry-pi-with-kodi-running-at-startup/ LAMP stack on Raspberry Pi with Kodi running at startup]

[http://ozzmaker.com/enable-x-windows-on-piscreen/ Enable X Window System on PiScreen]

[https://raspberrypi.stackexchange.com/questions/59310/remove-boot-messages-all-text-in-jessie Remove boot messages all text in Raspbian - Raspberry Pi Stack Exchange]

[https://raspberrypi.stackexchange.com/questions/47823/how-to-prevent-autologin-of-gui How to prevent or allow autologin of GUI - Raspberry Pi Stack Exchange]

[http://www.raspberry-projects.com/pi/pi-operating-systems/raspbian/auto-running-programs-gui Auto running programs LXDE - Raspberry Pi Projects]

And, if you would rather, it is easier to follow the process provided by this link to modify the Raspbian image before installing it onto the microSD card.

[https://wiki.debian.org/RaspberryPi/qemu-user-static Modifying Raspbian with qemu-user-static]

The above link describes removing the DE from a Raspbian image, though Raspbian Lite is a much better starting point for using Qemu for this purpose.

On Raspbian, you configure LightDM differently for autologin, which is necessary to boot directly to Kodi.

<pre>
nano /etc/lightdm/lightdm.conf
</pre>

Uncomment the following line.

<pre>
#autologin-user=
</pre>

And add the user you want to autologin and autostart Kodi. The user is named '''kodi''' in this example.

<pre>
autologin-user=kodi
</pre>

If Kodi is not installed at the standard path, find it using the '''which''' command.

<pre>
which kodi
</pre>

You can also use the X11 Window System to autostart Kodi.

<pre>
nano /etc/X11/Xsession.d/startup-local
</pre>

Insert this text into the new file. Use CTRL + O + Enter + X to save the file.

<pre>
#!/bin/sh
/usr/bin/kodi
</pre>

If you have a WM, such as Blackbox you can add it here as well.

<pre>
#!/bin/sh
blackbox &
/usr/bin/kodi
</pre>

Set permissions to make it executable. Use the ampersand to run an application in the background, such as a WM you only need to for the purpose of launching Kodi but not if you don't want to use the WM itself. Kodi will not launch without a DE or WM, but placing the ampersand "&" at the end of the command makes it run in the background where it can do its job out of sight. Also, make sure to start a WM or DE before running an application in the foreground. This is not necessary for apps running in the background.

<pre>
chmod 755 /etc/X11/Xsession.d/startup-local
</pre>

This feature is available on X Window System operating systems without upgrading to Xserver. Most Linux distributions use the X Window System.

== Disable / enable the login prompt ==

You can disable the graphical login prompt.

<pre>
systemctl set-default multi-user.target
</pre>

To enable it again use.

<pre>
systemctl set-default graphical.target
</pre>

If you are using an autologin method associated with your DE or WM, you '''do not''' want to disable the graphical login.

Even if you are using something like [https://github.com/graysky2/kodi-standalone-service Kodi Standalone Service], you still need use a WM or a DE that installs the '''x-window-manager''' software package.

To ensure you have this installed use the '''which''' command.

<pre>
which x-window-manager
</pre>

If there is no such package, you can use '''apt''' to search your Linux distributions repository.

<pre>
apt-cache search x-window-manager
</pre>

This will general a list of packages containing '''x-window-manager''', which cannot be installed alone. If you are not using a DE, you need to use a WM. And, you can also use a compositing WM like Compiz, for fast 3D effects.

[https://wiki.archlinux.org/index.php/Compiz Compiz - ArchWiki]

A note on using Kodi Standalone Service, this package runs Kodi as a '''systemd''' service and disables the login for user '''kodi''' and will not work when autologin is enabled. In fact, it will break the login process if you autologin user '''kodi''' and run Kodi Standalone Service at the same time. This package is installed automatically with the standard Kodi package when you install Kodi on Raspbian, but must be configured manually for all other Linux distributions. You can run the '''which''' command to find this package as well.

<pre>
which kodi-standalone
</pre>

Be advised, Kodi Standalone Service still launches the Kodi GUI and still requires a WM even though it is running as a '''systemd''' service. When you install a WM such as '''xfwm4''' (the WM for XFCE4), the CLI will tell you if it provides the '''x-window-manager''' package.

<pre>
Setting up xfwm4 (4.12.4-1) ...
update-alternatives: using /usr/bin/xfwm4 to provide /usr/bin/x-window-manager (x-window-manager) in auto mode
</pre>

If you do not see this message at the end of the installation, the WM you selected does not provide this software package and may not actually be a complete WM itself but only part of a package containing a WM.

For a great example on exactly how you would do this with '''xfwm4''', see this ArchWiki entry.

[https://wiki.archlinux.org/index.php/Xfwm XFWM - ArchWiki]

== Create custom Xsession script ==

Most systems utilize the client version of the X11 software Kodi standalone service requires.

Upgrade to the server versions of the X Window System.

<pre>apt install xauth xorg xinit xserver-xorg-core xserver-xorg xserver-common</pre>

Create a custom Xsession script with a text editor.

<pre>
nano ~/.xinitrc
</pre>

To run Kodi full-screen make sure the text reads:

<pre>
#!/usr/bin/env bash
exec gnome-session
/usr/bin/kodi -fs
</pre>

Replace the '''gnome-session''' with the DE or WM command you are using. See the last section for examples.

To make '''~/.xinitrc''' executable use.

<pre>
chmod +x ~/.xinitrc
</pre>

Use '''sudo''' and the '''~/.xinitrc''' file to configure '''~/.xsession'''.

<pre>
sudo -H -u kodi bash -c "ln -s ~/.xinitrc ~/.xsession"
</pre>

You need to use '''sudo''' to run this command. If you do not have '''sudo''', install it.

<pre>
apt install sudo
</pre>

If you create a symbolic link and want to remove it, simply remove the existing '''.xsession''' file you created.

<pre>
rm /home/kodi/.xsession
</pre>

Remember you can modify use and reuse the '''~/.xinitrc''' file to configure '''~/.xsession''' as often as you want. That is the purpose of the file. It does nothing on its own until you associate it with a user. On some systems using a DE such as Gnome, not all systems using Gnome, it may be necessary for '''.xsession''' to be '''.xsessionrc'''. Though this is more likely the case for organization network computers than a personal one, where configurations may vary on a diversity of machines. Most of the time, it will be '''.xsession''' rather than '''.xsessionrc''' that you want to create.

You must also autostart the X Window system, which differs somewhat from scenario to scenario. For most setups, all that is necessary is to edit the '''.bashrc''' file.

<pre>
nano ~/.bashrc
</pre>

Add the following as shown.

<pre>
if [[ ! $DISPLAY && $XDG_VTNR -eq 1 ]]; then
exec startx
fi
</pre>

If you wish to remain logged in after quitting X, remove the '''exec''' from the above. Other configurations can be applied, but are irrelevant to autostarting Kodi.

[https://wiki.archlinux.org/index.php/Xinit#Autostart_X_at_login Xinit Autostart X at login]

== Xsession to boot to app / WM / DE ==

You can use any window manager or desktop enviroment with a custom Xsession script as long as it is intalled.

You do this by creating '''~/.xinitrc''' script that contains the command to start the WM or DE.

For instance, if you are using FluxBox?

<pre>
#!/usr/bin/env bash
exec fluxbox &
/usr/bin/kodi -fs
</pre>

The <code>-fs</code> option is full-screen.

To start Gnome with Kodi full-screen:

<pre>
#!/usr/bin/env bash
exec gnome-session
/usr/bin/kodi -fs
</pre>

To run Gnome in the background, but launch Kodi in the foreground.

<pre>
#!/usr/bin/env bash
exec gnome-session &
/usr/bin/kodi -fs
</pre>

Use the '''~/.xinitrc''' file to configure '''~/.xsession''' to create a custom login for any user, not just Kodi.

<pre>
sudo -H -u [username] bash -c "ln -s ~/.xinitrc ~/.xsession"
</pre>

You must reconfigure Xserver for any user that is not a privileged user to be able to start a custom Xsession.

<pre>
dpkg-reconfigure xserver-xorg-legacy
</pre>

And / or...

<pre>
dpkg-reconfigure xserver-xorg
</pre>

If both packages are installed, you must reconfigure both. Not all systems will use or require the legacy package to allow non-root users to start X.

== Add a custom Grub entry ==

If you want to boot to the CLI and manually launch an app or boot directly to Kodi without a DE or WM, add a custom grub entry.

The right way to add a custom grub entry is to copy the menu entry you want to change or duplicate.

Copy the default Grub configuration file and open it with a text editor on your desktop. If you use a text editor on the CLI, the text will be cut off by the window when copying and pasting.

<pre>
cp /boot/grub/grub.cfg grub.cfg
gedit grub.cfg
</pre>

Copy the menu entry and paste it into '''40_custom''' with a text editor in the CLI.

<pre>
nano /etc/grub.d/40_custom
</pre>

Where the menu entry contains '''quiet splash''' change it to '''text''' instead.

You should also change the name of the entry!

I just appended mine with “CLI” for command line interface.

To update Grub:

<pre>
update-grub
</pre>

To launch a WM you can type its name. I use Enlightment 17 or Fluxbox. It must be installed.

<pre>
fluxbox
</pre>

You must have FluxBox installed. There are countless other window managers.

To launch a DE you enter the appropriate command. For Gnome desktop:

<pre>
gnome-session
</pre>

For KDE:

<pre>
startkde
</pre>

or

<pre>
plasma-desktop
</pre>

For XFCE:

<pre>
startxfce4
</pre>

For Mate:

<pre>
mate-session
</pre>

For LXDE:

<pre>
startlxde
</pre>

You can either manually launch your apps, boot right into them, or create an Xsession for each user. This is great when you want to create a Kodi user for running Kodi only, and for making sure you can still login to your DE with your regular user account. You can boot to any app full-screen this way, not just Kodi. You can create a custom Xsession script for any user, configured with any startup applications running in full-screen mode or normally.

By optionally creating a Grub menu entry, you can create a different Grub menu selection to boot only to the CLI and start an Xsession with a script or run commands manually.

HOW-TO:Autostart Kodi for Linux

2018-04-28T08:39:49Z

W3tech: /* Xsession to boot to app / WM / DE */

<section begin="intro" /><big>Any or all or any combination of these methods can be used to configure a Debian-based X Window System to boot directly to Kodi. This should work on any Linux using the X Window System, but these instructions are particular to Debian derivatives, such as Ubuntu. A server edition is best for running only Kodi, but this page assumes booting into a desktop OS, not a server distro. However, the instructions here can be used for a server distro with even less configuration than for a desktop. Experiment inside VirtualBox before you apply any of these to your system and make a backup.</big><section end="intro" />

__TOC__

== Switch to root ==

<pre>
su
</pre>

or

<pre>
sudo su
</pre>

== Create a Kodi user ==

To use Kodi full-screen, you only have to create a standard user.

<pre>
adduser kodi
</pre>

To remove the password use:

<pre>
passwd -d kodi
</pre>

== Customize LightDM to autologin ==

You can utilize the ability to customize LightDM data manager by changing the builtin custom configuration file '''50-myconfig.conf''' using '''nano''' or another text editor. If you have no DE or WM you can install '''lightdm''', but should make sure to do a bit of research before you do. Most versions of Linux use LightDM, but many server versions do not. For Ubuntu Server with no DE, for example, installing '''lightdm''' is okay and necessary. Changing the behavior of LightDM is done using a custom '''50-myconfig.conf''' configuration file.

To see if you have '''lightdm''' use '''which'''.

<pre>
which lightdm
</pre>

If not, install it with '''apt'''.

<pre>
apt install lightdm
</pre>

Create a custom configuration file called '''50-myconfig.conf''' using '''nano''' or other CLI text editor.

<pre>
mkdir /etc/lightdm/lightdm.conf.d/
nano /etc/lightdm/lightdm.conf.d/50-myconfig.conf
</pre>

Inside this new file add the following text.

<pre>
[SeatDefaults]
autologin-user=kodi
</pre>

== Configure Kodi to autostart ==

Configure Kodi to autostart.

<pre>
mkdir -p ~/.config/autostart
ln -s /usr/bin/kodi ~/.config/autostart
</pre>

This method of autostart requires a desktop environment or DE. This is done a bit differently by each DE. Some helpful links can easily be found in today's Web search using any search engine.

[http://edoceo.com/gui/xfce-autostart-apps Autostart Apps in XFCE]

The Raspberry Pi is a bit more of a tweak, but these are excellent links that will tell you how. The first link is the most helpful to making sure Kodi autostarts in Pi. There are many settings on the Pi that control boot, and the first link gives the best most trouble-free way to boot directly to Kodi. The others facilitate more tweaks and settings relevant to other uses of the X Window System.

[https://www.leowkahman.com/2016/03/05/lamp-stack-on-raspberry-pi-with-kodi-running-at-startup/ LAMP stack on Raspberry Pi with Kodi running at startup]

[http://ozzmaker.com/enable-x-windows-on-piscreen/ Enable X Window System on PiScreen]

[https://raspberrypi.stackexchange.com/questions/59310/remove-boot-messages-all-text-in-jessie Remove boot messages all text in Raspbian - Raspberry Pi Stack Exchange]

[https://raspberrypi.stackexchange.com/questions/47823/how-to-prevent-autologin-of-gui How to prevent or allow autologin of GUI - Raspberry Pi Stack Exchange]

[http://www.raspberry-projects.com/pi/pi-operating-systems/raspbian/auto-running-programs-gui Auto running programs LXDE - Raspberry Pi Projects]

And, if you would rather, it is easier to follow the process provided by this link to modify the Raspbian image before installing it onto the microSD card.

[https://wiki.debian.org/RaspberryPi/qemu-user-static Modifying Raspbian with qemu-user-static]

The above link describes removing the DE from a Raspbian image, though Raspbian Lite is a much better starting point for using Qemu for this purpose.

On Raspbian, you configure LightDM differently for autologin, which is necessary to boot directly to Kodi.

<pre>
nano /etc/lightdm/lightdm.conf
</pre>

Uncomment the following line.

<pre>
#autologin-user=
</pre>

And add the user you want to autologin and autostart Kodi. The user is named '''kodi''' in this example.

<pre>
autologin-user=kodi
</pre>

If Kodi is not installed at the standard path, find it using the '''which''' command.

<pre>
which kodi
</pre>

You can also use the X11 Window System to autostart Kodi.

<pre>
nano /etc/X11/Xsession.d/startup-local
</pre>

Insert this text into the new file. Use CTRL + O + Enter + X to save the file.

<pre>
#!/bin/sh
/usr/bin/kodi
</pre>

If you have a WM, such as Blackbox you can add it here as well.

<pre>
#!/bin/sh
blackbox &
/usr/bin/kodi
</pre>

Set permissions to make it executable. Use the ampersand to run an application in the background, such as a WM you only need to for the purpose of launching Kodi but not if you don't want to use the WM itself. Kodi will not launch without a DE or WM, but placing the ampersand "&" at the end of the command makes it run in the background where it can do its job out of sight. Also, make sure to start a WM or DE before running an application in the foreground. This is not necessary for apps running in the background.

<pre>
chmod 755 /etc/X11/Xsession.d/startup-local
</pre>

This feature is available on X Window System operating systems without upgrading to Xserver. Most Linux distributions use the X Window System.

== Disable / enable the login prompt ==

You can disable the graphical login prompt.

<pre>
systemctl set-default multi-user.target
</pre>

To enable it again use.

<pre>
systemctl set-default graphical.target
</pre>

If you are using an autologin method associated with your DE or WM, you '''do not''' want to disable the graphical login.

Even if you are using something like [https://github.com/graysky2/kodi-standalone-service Kodi Standalone Service], you still need use a WM or a DE that installs the '''x-window-manager''' software package.

To ensure you have this installed use the '''which''' command.

<pre>
which x-window-manager
</pre>

If there is no such package, you can use '''apt''' to search your Linux distributions repository.

<pre>
apt-cache search x-window-manager
</pre>

This will general a list of packages containing '''x-window-manager''', which cannot be installed alone. If you are not using a DE, you need to use a WM. And, you can also use a compositing WM like Compiz, for fast 3D effects.

[https://wiki.archlinux.org/index.php/Compiz Compiz - ArchWiki]

A note on using Kodi Standalone Service, this package runs Kodi as a '''systemd''' service and disables the login for user '''kodi''' and will not work when autologin is enabled. In fact, it will break the login process if you autologin user '''kodi''' and run Kodi Standalone Service at the same time. This package is installed automatically with the standard Kodi package when you install Kodi on Raspbian, but must be configured manually for all other Linux distributions. You can run the '''which''' command to find this package as well.

<pre>
which kodi-standalone
</pre>

Be advised, Kodi Standalone Service still launches the Kodi GUI and still requires a WM even though it is running as a '''systemd''' service. When you install a WM such as '''xfwm4''' (the WM for XFCE4), the CLI will tell you if it provides the '''x-window-manager''' package.

<pre>
Setting up xfwm4 (4.12.4-1) ...
update-alternatives: using /usr/bin/xfwm4 to provide /usr/bin/x-window-manager (x-window-manager) in auto mode
</pre>

If you do not see this message at the end of the installation, the WM you selected does not provide this software package and may not actually be a complete WM itself but only part of a package containing a WM.

For a great example on exactly how you would do this with '''xfwm4''', see this ArchWiki entry.

[https://wiki.archlinux.org/index.php/Xfwm XFWM - ArchWiki]

== Create custom Xsession script ==

Most systems utilize the client version of the X11 software Kodi standalone service requires.

Upgrade to the server versions of the X Window System.

<pre>apt install xauth xorg xinit xserver-xorg-core xserver-xorg xserver-common</pre>

Create a custom Xsession script with a text editor.

<pre>
nano ~/.xinitrc
</pre>

To run Kodi full-screen make sure the text reads:

<pre>
#!/usr/bin/env bash
exec gnome-session
/usr/bin/kodi -fs
</pre>

Replace the '''gnome-session''' with the DE or WM command you are using. See the last section for examples.

To make '''~/.xinitrc''' executable use.

<pre>
chmod +x ~/.xinitrc
</pre>

Use '''sudo''' and the '''~/.xinitrc''' file to configure '''~/.xsession'''.

<pre>
sudo -H -u kodi bash -c "ln -s ~/.xinitrc ~/.xsession"
</pre>

You need to use '''sudo''' to run this command. If you do not have '''sudo''', install it.

<pre>
apt install sudo
</pre>

If you create a symbolic link and want to remove it, simply remove the existing '''.xsession''' file you created.

<pre>
rm /home/kodi/.xsession
</pre>

Remember you can modify use and reuse the '''~/.xinitrc''' file to configure '''~/.xsession''' as often as you want. That is the purpose of the file. It does nothing on its own until you associate it with a user. On some systems using a DE such as Gnome, not all systems using Gnome, it may be necessary for '''.xsession''' to be '''.xsessionrc'''. Though this is more likely the case for organization network computers than a personal one, where configurations may vary on a diversity of machines. Most of the time, it will be '''.xsession''' rather than '''.xsessionrc''' that you want to create.

You must also autostart the X Window system, which differs somewhat from scenario to scenario. For most setups, all that is necessary is to edit the '''.bashrc''' file.

<pre>
nano ~/.bashrc
</pre>

Add the following as shown.

<pre>
if [[ ! $DISPLAY && $XDG_VTNR -eq 1 ]]; then
exec startx
fi
</pre>

If you wish to remain logged in after quitting X, remove the '''exec''' from the above. Other configurations can be applied, but are irrelevant to autostarting Kodi.

[https://wiki.archlinux.org/index.php/Xinit#Autostart_X_at_login Xinit Autostart X at login]

== Xsession to boot to app / WM / DE ==

You can use any window manager or desktop enviroment with a custom Xsession script as long as it is intalled.

You do this by creating '''~/.xinitrc''' script that contains the command to start the WM or DE.

For instance, if you are using FluxBox?

<pre>
#!/usr/bin/env bash
exec fluxbox &
/usr/bin/kodi -fs
</pre>

The <code>-fs</code> option is full-screen.

To start Gnome with Kodi full-screen:

<pre>
#!/usr/bin/env bash
exec gnome-session &
/usr/bin/kodi -fs
</pre>

Use the '''~/.xinitrc''' file to configure '''~/.xsession''' to create a custom login for any user, not just Kodi.

<pre>
sudo -H -u [username] bash -c "ln -s ~/.xinitrc ~/.xsession"
</pre>

You must reconfigure Xserver for any user that is not a privileged user to be able to start a custom Xsession.

<pre>
dpkg-reconfigure xserver-xorg-legacy
</pre>

And / or...

<pre>
dpkg-reconfigure xserver-xorg
</pre>

If both packages are installed, you must reconfigure both. Not all systems will use or require the legacy package to allow non-root users to start X.

== Add a custom Grub entry ==

If you want to boot to the CLI and manually launch an app or boot directly to Kodi without a DE or WM, add a custom grub entry.

The right way to add a custom grub entry is to copy the menu entry you want to change or duplicate.

Copy the default Grub configuration file and open it with a text editor on your desktop. If you use a text editor on the CLI, the text will be cut off by the window when copying and pasting.

<pre>
cp /boot/grub/grub.cfg grub.cfg
gedit grub.cfg
</pre>

Copy the menu entry and paste it into '''40_custom''' with a text editor in the CLI.

<pre>
nano /etc/grub.d/40_custom
</pre>

Where the menu entry contains '''quiet splash''' change it to '''text''' instead.

You should also change the name of the entry!

I just appended mine with “CLI” for command line interface.

To update Grub:

<pre>
update-grub
</pre>

To launch a WM you can type its name. I use Enlightment 17 or Fluxbox. It must be installed.

<pre>
fluxbox
</pre>

You must have FluxBox installed. There are countless other window managers.

To launch a DE you enter the appropriate command. For Gnome desktop:

<pre>
gnome-session
</pre>

For KDE:

<pre>
startkde
</pre>

or

<pre>
plasma-desktop
</pre>

For XFCE:

<pre>
startxfce4
</pre>

For Mate:

<pre>
mate-session
</pre>

For LXDE:

<pre>
startlxde
</pre>

You can either manually launch your apps, boot right into them, or create an Xsession for each user. This is great when you want to create a Kodi user for running Kodi only, and for making sure you can still login to your DE with your regular user account. You can boot to any app full-screen this way, not just Kodi. You can create a custom Xsession script for any user, configured with any startup applications running in full-screen mode or normally.

By optionally creating a Grub menu entry, you can create a different Grub menu selection to boot only to the CLI and start an Xsession with a script or run commands manually.

HOW-TO:Autostart Kodi for Linux

2018-04-28T08:38:25Z

W3tech: /* Create custom Xsession script */

<section begin="intro" /><big>Any or all or any combination of these methods can be used to configure a Debian-based X Window System to boot directly to Kodi. This should work on any Linux using the X Window System, but these instructions are particular to Debian derivatives, such as Ubuntu. A server edition is best for running only Kodi, but this page assumes booting into a desktop OS, not a server distro. However, the instructions here can be used for a server distro with even less configuration than for a desktop. Experiment inside VirtualBox before you apply any of these to your system and make a backup.</big><section end="intro" />

__TOC__

== Switch to root ==

<pre>
su
</pre>

or

<pre>
sudo su
</pre>

== Create a Kodi user ==

To use Kodi full-screen, you only have to create a standard user.

<pre>
adduser kodi
</pre>

To remove the password use:

<pre>
passwd -d kodi
</pre>

== Customize LightDM to autologin ==

You can utilize the ability to customize LightDM data manager by changing the builtin custom configuration file '''50-myconfig.conf''' using '''nano''' or another text editor. If you have no DE or WM you can install '''lightdm''', but should make sure to do a bit of research before you do. Most versions of Linux use LightDM, but many server versions do not. For Ubuntu Server with no DE, for example, installing '''lightdm''' is okay and necessary. Changing the behavior of LightDM is done using a custom '''50-myconfig.conf''' configuration file.

To see if you have '''lightdm''' use '''which'''.

<pre>
which lightdm
</pre>

If not, install it with '''apt'''.

<pre>
apt install lightdm
</pre>

Create a custom configuration file called '''50-myconfig.conf''' using '''nano''' or other CLI text editor.

<pre>
mkdir /etc/lightdm/lightdm.conf.d/
nano /etc/lightdm/lightdm.conf.d/50-myconfig.conf
</pre>

Inside this new file add the following text.

<pre>
[SeatDefaults]
autologin-user=kodi
</pre>

== Configure Kodi to autostart ==

Configure Kodi to autostart.

<pre>
mkdir -p ~/.config/autostart
ln -s /usr/bin/kodi ~/.config/autostart
</pre>

This method of autostart requires a desktop environment or DE. This is done a bit differently by each DE. Some helpful links can easily be found in today's Web search using any search engine.

[http://edoceo.com/gui/xfce-autostart-apps Autostart Apps in XFCE]

The Raspberry Pi is a bit more of a tweak, but these are excellent links that will tell you how. The first link is the most helpful to making sure Kodi autostarts in Pi. There are many settings on the Pi that control boot, and the first link gives the best most trouble-free way to boot directly to Kodi. The others facilitate more tweaks and settings relevant to other uses of the X Window System.

[https://www.leowkahman.com/2016/03/05/lamp-stack-on-raspberry-pi-with-kodi-running-at-startup/ LAMP stack on Raspberry Pi with Kodi running at startup]

[http://ozzmaker.com/enable-x-windows-on-piscreen/ Enable X Window System on PiScreen]

[https://raspberrypi.stackexchange.com/questions/59310/remove-boot-messages-all-text-in-jessie Remove boot messages all text in Raspbian - Raspberry Pi Stack Exchange]

[https://raspberrypi.stackexchange.com/questions/47823/how-to-prevent-autologin-of-gui How to prevent or allow autologin of GUI - Raspberry Pi Stack Exchange]

[http://www.raspberry-projects.com/pi/pi-operating-systems/raspbian/auto-running-programs-gui Auto running programs LXDE - Raspberry Pi Projects]

And, if you would rather, it is easier to follow the process provided by this link to modify the Raspbian image before installing it onto the microSD card.

[https://wiki.debian.org/RaspberryPi/qemu-user-static Modifying Raspbian with qemu-user-static]

The above link describes removing the DE from a Raspbian image, though Raspbian Lite is a much better starting point for using Qemu for this purpose.

On Raspbian, you configure LightDM differently for autologin, which is necessary to boot directly to Kodi.

<pre>
nano /etc/lightdm/lightdm.conf
</pre>

Uncomment the following line.

<pre>
#autologin-user=
</pre>

And add the user you want to autologin and autostart Kodi. The user is named '''kodi''' in this example.

<pre>
autologin-user=kodi
</pre>

If Kodi is not installed at the standard path, find it using the '''which''' command.

<pre>
which kodi
</pre>

You can also use the X11 Window System to autostart Kodi.

<pre>
nano /etc/X11/Xsession.d/startup-local
</pre>

Insert this text into the new file. Use CTRL + O + Enter + X to save the file.

<pre>
#!/bin/sh
/usr/bin/kodi
</pre>

If you have a WM, such as Blackbox you can add it here as well.

<pre>
#!/bin/sh
blackbox &
/usr/bin/kodi
</pre>

Set permissions to make it executable. Use the ampersand to run an application in the background, such as a WM you only need to for the purpose of launching Kodi but not if you don't want to use the WM itself. Kodi will not launch without a DE or WM, but placing the ampersand "&" at the end of the command makes it run in the background where it can do its job out of sight. Also, make sure to start a WM or DE before running an application in the foreground. This is not necessary for apps running in the background.

<pre>
chmod 755 /etc/X11/Xsession.d/startup-local
</pre>

This feature is available on X Window System operating systems without upgrading to Xserver. Most Linux distributions use the X Window System.

== Disable / enable the login prompt ==

You can disable the graphical login prompt.

<pre>
systemctl set-default multi-user.target
</pre>

To enable it again use.

<pre>
systemctl set-default graphical.target
</pre>

If you are using an autologin method associated with your DE or WM, you '''do not''' want to disable the graphical login.

Even if you are using something like [https://github.com/graysky2/kodi-standalone-service Kodi Standalone Service], you still need use a WM or a DE that installs the '''x-window-manager''' software package.

To ensure you have this installed use the '''which''' command.

<pre>
which x-window-manager
</pre>

If there is no such package, you can use '''apt''' to search your Linux distributions repository.

<pre>
apt-cache search x-window-manager
</pre>

This will general a list of packages containing '''x-window-manager''', which cannot be installed alone. If you are not using a DE, you need to use a WM. And, you can also use a compositing WM like Compiz, for fast 3D effects.

[https://wiki.archlinux.org/index.php/Compiz Compiz - ArchWiki]

A note on using Kodi Standalone Service, this package runs Kodi as a '''systemd''' service and disables the login for user '''kodi''' and will not work when autologin is enabled. In fact, it will break the login process if you autologin user '''kodi''' and run Kodi Standalone Service at the same time. This package is installed automatically with the standard Kodi package when you install Kodi on Raspbian, but must be configured manually for all other Linux distributions. You can run the '''which''' command to find this package as well.

<pre>
which kodi-standalone
</pre>

Be advised, Kodi Standalone Service still launches the Kodi GUI and still requires a WM even though it is running as a '''systemd''' service. When you install a WM such as '''xfwm4''' (the WM for XFCE4), the CLI will tell you if it provides the '''x-window-manager''' package.

<pre>
Setting up xfwm4 (4.12.4-1) ...
update-alternatives: using /usr/bin/xfwm4 to provide /usr/bin/x-window-manager (x-window-manager) in auto mode
</pre>

If you do not see this message at the end of the installation, the WM you selected does not provide this software package and may not actually be a complete WM itself but only part of a package containing a WM.

For a great example on exactly how you would do this with '''xfwm4''', see this ArchWiki entry.

[https://wiki.archlinux.org/index.php/Xfwm XFWM - ArchWiki]

== Create custom Xsession script ==

Most systems utilize the client version of the X11 software Kodi standalone service requires.

Upgrade to the server versions of the X Window System.

<pre>apt install xauth xorg xinit xserver-xorg-core xserver-xorg xserver-common</pre>

Create a custom Xsession script with a text editor.

<pre>
nano ~/.xinitrc
</pre>

To run Kodi full-screen make sure the text reads:

<pre>
#!/usr/bin/env bash
exec gnome-session
/usr/bin/kodi -fs
</pre>

Replace the '''gnome-session''' with the DE or WM command you are using. See the last section for examples.

To make '''~/.xinitrc''' executable use.

<pre>
chmod +x ~/.xinitrc
</pre>

Use '''sudo''' and the '''~/.xinitrc''' file to configure '''~/.xsession'''.

<pre>
sudo -H -u kodi bash -c "ln -s ~/.xinitrc ~/.xsession"
</pre>

You need to use '''sudo''' to run this command. If you do not have '''sudo''', install it.

<pre>
apt install sudo
</pre>

If you create a symbolic link and want to remove it, simply remove the existing '''.xsession''' file you created.

<pre>
rm /home/kodi/.xsession
</pre>

Remember you can modify use and reuse the '''~/.xinitrc''' file to configure '''~/.xsession''' as often as you want. That is the purpose of the file. It does nothing on its own until you associate it with a user. On some systems using a DE such as Gnome, not all systems using Gnome, it may be necessary for '''.xsession''' to be '''.xsessionrc'''. Though this is more likely the case for organization network computers than a personal one, where configurations may vary on a diversity of machines. Most of the time, it will be '''.xsession''' rather than '''.xsessionrc''' that you want to create.

You must also autostart the X Window system, which differs somewhat from scenario to scenario. For most setups, all that is necessary is to edit the '''.bashrc''' file.

<pre>
nano ~/.bashrc
</pre>

Add the following as shown.

<pre>
if [[ ! $DISPLAY && $XDG_VTNR -eq 1 ]]; then
exec startx
fi
</pre>

If you wish to remain logged in after quitting X, remove the '''exec''' from the above. Other configurations can be applied, but are irrelevant to autostarting Kodi.

[https://wiki.archlinux.org/index.php/Xinit#Autostart_X_at_login Xinit Autostart X at login]

== Xsession to boot to app / WM / DE ==

You can use any window manager or desktop enviroment with a custom Xsession script as long as it is intalled.

You do this by creating '''~/.xinitrc''' script that contains the command to start the WM or DE.

For instance, if you are using FluxBox?

<pre>
#!/usr/bin/env bash
/usr/bin/kodi -fs &
exec fluxbox &
</pre>

The <code>-fs</code> option is full-screen.

To start Gnome with Kodi full-screen:

<pre>
#!/usr/bin/env bash
/usr/bin/kodi -fs &
exec gnome-session &
</pre>

Use the '''~/.xinitrc''' file to configure '''~/.xsession''' to create a custom login for any user, not just Kodi.

<pre>
sudo -H -u [username] bash -c "ln -s ~/.xinitrc ~/.xsession"
</pre>

You must reconfigure Xserver for any user that is not a privileged user to be able to start a custom Xsession.

<pre>
dpkg-reconfigure xserver-xorg-legacy
</pre>

And / or...

<pre>
dpkg-reconfigure xserver-xorg
</pre>

If both packages are installed, you must reconfigure both. Not all systems will use or require the legacy package to allow non-root users to start X.

== Add a custom Grub entry ==

If you want to boot to the CLI and manually launch an app or boot directly to Kodi without a DE or WM, add a custom grub entry.

The right way to add a custom grub entry is to copy the menu entry you want to change or duplicate.

Copy the default Grub configuration file and open it with a text editor on your desktop. If you use a text editor on the CLI, the text will be cut off by the window when copying and pasting.

<pre>
cp /boot/grub/grub.cfg grub.cfg
gedit grub.cfg
</pre>

Copy the menu entry and paste it into '''40_custom''' with a text editor in the CLI.

<pre>
nano /etc/grub.d/40_custom
</pre>

Where the menu entry contains '''quiet splash''' change it to '''text''' instead.

You should also change the name of the entry!

I just appended mine with “CLI” for command line interface.

To update Grub:

<pre>
update-grub
</pre>

To launch a WM you can type its name. I use Enlightment 17 or Fluxbox. It must be installed.

<pre>
fluxbox
</pre>

You must have FluxBox installed. There are countless other window managers.

To launch a DE you enter the appropriate command. For Gnome desktop:

<pre>
gnome-session
</pre>

For KDE:

<pre>
startkde
</pre>

or

<pre>
plasma-desktop
</pre>

For XFCE:

<pre>
startxfce4
</pre>

For Mate:

<pre>
mate-session
</pre>

For LXDE:

<pre>
startlxde
</pre>

You can either manually launch your apps, boot right into them, or create an Xsession for each user. This is great when you want to create a Kodi user for running Kodi only, and for making sure you can still login to your DE with your regular user account. You can boot to any app full-screen this way, not just Kodi. You can create a custom Xsession script for any user, configured with any startup applications running in full-screen mode or normally.

By optionally creating a Grub menu entry, you can create a different Grub menu selection to boot only to the CLI and start an Xsession with a script or run commands manually.

HOW-TO:Autostart Kodi for Linux

2018-04-28T08:37:19Z

W3tech: /* Configure Kodi to autostart */

<section begin="intro" /><big>Any or all or any combination of these methods can be used to configure a Debian-based X Window System to boot directly to Kodi. This should work on any Linux using the X Window System, but these instructions are particular to Debian derivatives, such as Ubuntu. A server edition is best for running only Kodi, but this page assumes booting into a desktop OS, not a server distro. However, the instructions here can be used for a server distro with even less configuration than for a desktop. Experiment inside VirtualBox before you apply any of these to your system and make a backup.</big><section end="intro" />

__TOC__

== Switch to root ==

<pre>
su
</pre>

or

<pre>
sudo su
</pre>

== Create a Kodi user ==

To use Kodi full-screen, you only have to create a standard user.

<pre>
adduser kodi
</pre>

To remove the password use:

<pre>
passwd -d kodi
</pre>

== Customize LightDM to autologin ==

You can utilize the ability to customize LightDM data manager by changing the builtin custom configuration file '''50-myconfig.conf''' using '''nano''' or another text editor. If you have no DE or WM you can install '''lightdm''', but should make sure to do a bit of research before you do. Most versions of Linux use LightDM, but many server versions do not. For Ubuntu Server with no DE, for example, installing '''lightdm''' is okay and necessary. Changing the behavior of LightDM is done using a custom '''50-myconfig.conf''' configuration file.

To see if you have '''lightdm''' use '''which'''.

<pre>
which lightdm
</pre>

If not, install it with '''apt'''.

<pre>
apt install lightdm
</pre>

Create a custom configuration file called '''50-myconfig.conf''' using '''nano''' or other CLI text editor.

<pre>
mkdir /etc/lightdm/lightdm.conf.d/
nano /etc/lightdm/lightdm.conf.d/50-myconfig.conf
</pre>

Inside this new file add the following text.

<pre>
[SeatDefaults]
autologin-user=kodi
</pre>

== Configure Kodi to autostart ==

Configure Kodi to autostart.

<pre>
mkdir -p ~/.config/autostart
ln -s /usr/bin/kodi ~/.config/autostart
</pre>

This method of autostart requires a desktop environment or DE. This is done a bit differently by each DE. Some helpful links can easily be found in today's Web search using any search engine.

[http://edoceo.com/gui/xfce-autostart-apps Autostart Apps in XFCE]

The Raspberry Pi is a bit more of a tweak, but these are excellent links that will tell you how. The first link is the most helpful to making sure Kodi autostarts in Pi. There are many settings on the Pi that control boot, and the first link gives the best most trouble-free way to boot directly to Kodi. The others facilitate more tweaks and settings relevant to other uses of the X Window System.

[https://www.leowkahman.com/2016/03/05/lamp-stack-on-raspberry-pi-with-kodi-running-at-startup/ LAMP stack on Raspberry Pi with Kodi running at startup]

[http://ozzmaker.com/enable-x-windows-on-piscreen/ Enable X Window System on PiScreen]

[https://raspberrypi.stackexchange.com/questions/59310/remove-boot-messages-all-text-in-jessie Remove boot messages all text in Raspbian - Raspberry Pi Stack Exchange]

[https://raspberrypi.stackexchange.com/questions/47823/how-to-prevent-autologin-of-gui How to prevent or allow autologin of GUI - Raspberry Pi Stack Exchange]

[http://www.raspberry-projects.com/pi/pi-operating-systems/raspbian/auto-running-programs-gui Auto running programs LXDE - Raspberry Pi Projects]

And, if you would rather, it is easier to follow the process provided by this link to modify the Raspbian image before installing it onto the microSD card.

[https://wiki.debian.org/RaspberryPi/qemu-user-static Modifying Raspbian with qemu-user-static]

The above link describes removing the DE from a Raspbian image, though Raspbian Lite is a much better starting point for using Qemu for this purpose.

On Raspbian, you configure LightDM differently for autologin, which is necessary to boot directly to Kodi.

<pre>
nano /etc/lightdm/lightdm.conf
</pre>

Uncomment the following line.

<pre>
#autologin-user=
</pre>

And add the user you want to autologin and autostart Kodi. The user is named '''kodi''' in this example.

<pre>
autologin-user=kodi
</pre>

If Kodi is not installed at the standard path, find it using the '''which''' command.

<pre>
which kodi
</pre>

You can also use the X11 Window System to autostart Kodi.

<pre>
nano /etc/X11/Xsession.d/startup-local
</pre>

Insert this text into the new file. Use CTRL + O + Enter + X to save the file.

<pre>
#!/bin/sh
/usr/bin/kodi
</pre>

If you have a WM, such as Blackbox you can add it here as well.

<pre>
#!/bin/sh
blackbox &
/usr/bin/kodi
</pre>

Set permissions to make it executable. Use the ampersand to run an application in the background, such as a WM you only need to for the purpose of launching Kodi but not if you don't want to use the WM itself. Kodi will not launch without a DE or WM, but placing the ampersand "&" at the end of the command makes it run in the background where it can do its job out of sight. Also, make sure to start a WM or DE before running an application in the foreground. This is not necessary for apps running in the background.

<pre>
chmod 755 /etc/X11/Xsession.d/startup-local
</pre>

This feature is available on X Window System operating systems without upgrading to Xserver. Most Linux distributions use the X Window System.

== Disable / enable the login prompt ==

You can disable the graphical login prompt.

<pre>
systemctl set-default multi-user.target
</pre>

To enable it again use.

<pre>
systemctl set-default graphical.target
</pre>

If you are using an autologin method associated with your DE or WM, you '''do not''' want to disable the graphical login.

Even if you are using something like [https://github.com/graysky2/kodi-standalone-service Kodi Standalone Service], you still need use a WM or a DE that installs the '''x-window-manager''' software package.

To ensure you have this installed use the '''which''' command.

<pre>
which x-window-manager
</pre>

If there is no such package, you can use '''apt''' to search your Linux distributions repository.

<pre>
apt-cache search x-window-manager
</pre>

This will general a list of packages containing '''x-window-manager''', which cannot be installed alone. If you are not using a DE, you need to use a WM. And, you can also use a compositing WM like Compiz, for fast 3D effects.

[https://wiki.archlinux.org/index.php/Compiz Compiz - ArchWiki]

A note on using Kodi Standalone Service, this package runs Kodi as a '''systemd''' service and disables the login for user '''kodi''' and will not work when autologin is enabled. In fact, it will break the login process if you autologin user '''kodi''' and run Kodi Standalone Service at the same time. This package is installed automatically with the standard Kodi package when you install Kodi on Raspbian, but must be configured manually for all other Linux distributions. You can run the '''which''' command to find this package as well.

<pre>
which kodi-standalone
</pre>

Be advised, Kodi Standalone Service still launches the Kodi GUI and still requires a WM even though it is running as a '''systemd''' service. When you install a WM such as '''xfwm4''' (the WM for XFCE4), the CLI will tell you if it provides the '''x-window-manager''' package.

<pre>
Setting up xfwm4 (4.12.4-1) ...
update-alternatives: using /usr/bin/xfwm4 to provide /usr/bin/x-window-manager (x-window-manager) in auto mode
</pre>

If you do not see this message at the end of the installation, the WM you selected does not provide this software package and may not actually be a complete WM itself but only part of a package containing a WM.

For a great example on exactly how you would do this with '''xfwm4''', see this ArchWiki entry.

[https://wiki.archlinux.org/index.php/Xfwm XFWM - ArchWiki]

== Create custom Xsession script ==

Most systems utilize the client version of the X11 software Kodi standalone service requires.

Upgrade to the server versions of the X Window System.

<pre>apt install xauth xorg xinit xserver-xorg-core xserver-xorg xserver-common</pre>

Create a custom Xsession script with a text editor.

<pre>
nano ~/.xinitrc
</pre>

To run Kodi full-screen make sure the text reads:

<pre>
#!/usr/bin/env bash
/usr/bin/kodi -fs &
exec gnome-session
</pre>

Replace the '''gnome-session''' with the DE or WM command you are using. See the last section for examples.

To make '''~/.xinitrc''' executable use.

<pre>
chmod +x ~/.xinitrc
</pre>

Use '''sudo''' and the '''~/.xinitrc''' file to configure '''~/.xsession'''.

<pre>
sudo -H -u kodi bash -c "ln -s ~/.xinitrc ~/.xsession"
</pre>

You need to use '''sudo''' to run this command. If you do not have '''sudo''', install it.

<pre>
apt install sudo
</pre>

If you create a symbolic link and want to remove it, simply remove the existing '''.xsession''' file you created.

<pre>
rm /home/kodi/.xsession
</pre>

Remember you can modify use and reuse the '''~/.xinitrc''' file to configure '''~/.xsession''' as often as you want. That is the purpose of the file. It does nothing on its own until you associate it with a user. On some systems using a DE such as Gnome, not all systems using Gnome, it may be necessary for '''.xsession''' to be '''.xsessionrc'''. Though this is more likely the case for organization network computers than a personal one, where configurations may vary on a diversity of machines. Most of the time, it will be '''.xsession''' rather than '''.xsessionrc''' that you want to create.

You must also autostart the X Window system, which differs somewhat from scenario to scenario. For most setups, all that is necessary is to edit the '''.bashrc''' file.

<pre>
nano ~/.bashrc
</pre>

Add the following as shown.

<pre>
if [[ ! $DISPLAY && $XDG_VTNR -eq 1 ]]; then
exec startx
fi
</pre>

If you wish to remain logged in after quitting X, remove the '''exec''' from the above. Other configurations can be applied, but are irrelevant to autostarting Kodi.

[https://wiki.archlinux.org/index.php/Xinit#Autostart_X_at_login Xinit Autostart X at login]

== Xsession to boot to app / WM / DE ==

You can use any window manager or desktop enviroment with a custom Xsession script as long as it is intalled.

You do this by creating '''~/.xinitrc''' script that contains the command to start the WM or DE.

For instance, if you are using FluxBox?

<pre>
#!/usr/bin/env bash
/usr/bin/kodi -fs &
exec fluxbox &
</pre>

The <code>-fs</code> option is full-screen.

To start Gnome with Kodi full-screen:

<pre>
#!/usr/bin/env bash
/usr/bin/kodi -fs &
exec gnome-session &
</pre>

Use the '''~/.xinitrc''' file to configure '''~/.xsession''' to create a custom login for any user, not just Kodi.

<pre>
sudo -H -u [username] bash -c "ln -s ~/.xinitrc ~/.xsession"
</pre>

You must reconfigure Xserver for any user that is not a privileged user to be able to start a custom Xsession.

<pre>
dpkg-reconfigure xserver-xorg-legacy
</pre>

And / or...

<pre>
dpkg-reconfigure xserver-xorg
</pre>

If both packages are installed, you must reconfigure both. Not all systems will use or require the legacy package to allow non-root users to start X.

== Add a custom Grub entry ==

If you want to boot to the CLI and manually launch an app or boot directly to Kodi without a DE or WM, add a custom grub entry.

The right way to add a custom grub entry is to copy the menu entry you want to change or duplicate.

Copy the default Grub configuration file and open it with a text editor on your desktop. If you use a text editor on the CLI, the text will be cut off by the window when copying and pasting.

<pre>
cp /boot/grub/grub.cfg grub.cfg
gedit grub.cfg
</pre>

Copy the menu entry and paste it into '''40_custom''' with a text editor in the CLI.

<pre>
nano /etc/grub.d/40_custom
</pre>

Where the menu entry contains '''quiet splash''' change it to '''text''' instead.

You should also change the name of the entry!

I just appended mine with “CLI” for command line interface.

To update Grub:

<pre>
update-grub
</pre>

To launch a WM you can type its name. I use Enlightment 17 or Fluxbox. It must be installed.

<pre>
fluxbox
</pre>

You must have FluxBox installed. There are countless other window managers.

To launch a DE you enter the appropriate command. For Gnome desktop:

<pre>
gnome-session
</pre>

For KDE:

<pre>
startkde
</pre>

or

<pre>
plasma-desktop
</pre>

For XFCE:

<pre>
startxfce4
</pre>

For Mate:

<pre>
mate-session
</pre>

For LXDE:

<pre>
startlxde
</pre>

You can either manually launch your apps, boot right into them, or create an Xsession for each user. This is great when you want to create a Kodi user for running Kodi only, and for making sure you can still login to your DE with your regular user account. You can boot to any app full-screen this way, not just Kodi. You can create a custom Xsession script for any user, configured with any startup applications running in full-screen mode or normally.

By optionally creating a Grub menu entry, you can create a different Grub menu selection to boot only to the CLI and start an Xsession with a script or run commands manually.

HOW-TO:Autostart Kodi for Linux

2018-04-27T14:10:55Z

W3tech: /* Add a custom Grub entry */

<section begin="intro" /><big>Any or all or any combination of these methods can be used to configure a Debian-based X Window System to boot directly to Kodi. This should work on any Linux using the X Window System, but these instructions are particular to Debian derivatives, such as Ubuntu. A server edition is best for running only Kodi, but this page assumes booting into a desktop OS, not a server distro. However, the instructions here can be used for a server distro with even less configuration than for a desktop. Experiment inside VirtualBox before you apply any of these to your system and make a backup.</big><section end="intro" />

__TOC__

== Switch to root ==

<pre>
su
</pre>

or

<pre>
sudo su
</pre>

== Create a Kodi user ==

To use Kodi full-screen, you only have to create a standard user.

<pre>
adduser kodi
</pre>

To remove the password use:

<pre>
passwd -d kodi
</pre>

== Customize LightDM to autologin ==

You can utilize the ability to customize LightDM data manager by changing the builtin custom configuration file '''50-myconfig.conf''' using '''nano''' or another text editor. If you have no DE or WM you can install '''lightdm''', but should make sure to do a bit of research before you do. Most versions of Linux use LightDM, but many server versions do not. For Ubuntu Server with no DE, for example, installing '''lightdm''' is okay and necessary. Changing the behavior of LightDM is done using a custom '''50-myconfig.conf''' configuration file.

To see if you have '''lightdm''' use '''which'''.

<pre>
which lightdm
</pre>

If not, install it with '''apt'''.

<pre>
apt install lightdm
</pre>

Create a custom configuration file called '''50-myconfig.conf''' using '''nano''' or other CLI text editor.

<pre>
mkdir /etc/lightdm/lightdm.conf.d/
nano /etc/lightdm/lightdm.conf.d/50-myconfig.conf
</pre>

Inside this new file add the following text.

<pre>
[SeatDefaults]
autologin-user=kodi
</pre>

== Configure Kodi to autostart ==

Configure Kodi to autostart.

<pre>
mkdir -p ~/.config/autostart
ln -s /usr/bin/kodi ~/.config/autostart
</pre>

This method of autostart requires a desktop environment or DE. This is done a bit differently by each DE. Some helpful links can easily be found in today's Web search using any search engine.

[http://edoceo.com/gui/xfce-autostart-apps Autostart Apps in XFCE]

The Raspberry Pi is a bit more of a tweak, but these are excellent links that will tell you how. The first link is the most helpful to making sure Kodi autostarts in Pi. There are many settings on the Pi that control boot, and the first link gives the best most trouble-free way to boot directly to Kodi. The others facilitate more tweaks and settings relevant to other uses of the X Window System.

[https://www.leowkahman.com/2016/03/05/lamp-stack-on-raspberry-pi-with-kodi-running-at-startup/ LAMP stack on Raspberry Pi with Kodi running at startup]

[http://ozzmaker.com/enable-x-windows-on-piscreen/ Enable X Window System on PiScreen]

[https://raspberrypi.stackexchange.com/questions/59310/remove-boot-messages-all-text-in-jessie Remove boot messages all text in Raspbian - Raspberry Pi Stack Exchange]

[https://raspberrypi.stackexchange.com/questions/47823/how-to-prevent-autologin-of-gui How to prevent or allow autologin of GUI - Raspberry Pi Stack Exchange]

[http://www.raspberry-projects.com/pi/pi-operating-systems/raspbian/auto-running-programs-gui Auto running programs LXDE - Raspberry Pi Projects]

And, if you would rather, it is easier to follow the process provided by this link to modify the Raspbian image before installing it onto the microSD card.

[https://wiki.debian.org/RaspberryPi/qemu-user-static Modifying Raspbian with qemu-user-static]

The above link describes removing the DE from a Raspbian image, though Raspbian Lite is a much better starting point for using Qemu for this purpose.

On Raspbian, you configure LightDM differently for autologin, which is necessary to boot directly to Kodi.

<pre>
nano /etc/lightdm/lightdm.conf
</pre>

Uncomment the following line.

<pre>
#autologin-user=
</pre>

And add the user you want to autologin and autostart Kodi. The user is named '''kodi''' in this example.

<pre>
autologin-user=kodi
</pre>

If Kodi is not installed at the standard path, find it using the '''which''' command.

<pre>
which kodi
</pre>

You can also use the X11 Window System to autostart Kodi.

<pre>
nano /etc/X11/Xsession.d/startup-local
</pre>

Insert this text into the new file. Use CTRL + O + Enter + X to save the file.

<pre>
#!/bin/sh
/usr/bin/kodi &
</pre>

If you have a WM, such as Blackbox you can add it here as well.

<pre>
#!/bin/sh
/usr/bin/kodi &
blackbox &
</pre>

Set permissions to make it executable.

<pre>
chmod 755 /etc/X11/Xsession.d/startup-local
</pre>

This feature is available on X Window System operating systems without upgrading to Xserver. Most Linux distributions use the X Window System.

== Disable / enable the login prompt ==

You can disable the graphical login prompt.

<pre>
systemctl set-default multi-user.target
</pre>

To enable it again use.

<pre>
systemctl set-default graphical.target
</pre>

If you are using an autologin method associated with your DE or WM, you '''do not''' want to disable the graphical login.

Even if you are using something like [https://github.com/graysky2/kodi-standalone-service Kodi Standalone Service], you still need use a WM or a DE that installs the '''x-window-manager''' software package.

To ensure you have this installed use the '''which''' command.

<pre>
which x-window-manager
</pre>

If there is no such package, you can use '''apt''' to search your Linux distributions repository.

<pre>
apt-cache search x-window-manager
</pre>

This will general a list of packages containing '''x-window-manager''', which cannot be installed alone. If you are not using a DE, you need to use a WM. And, you can also use a compositing WM like Compiz, for fast 3D effects.

[https://wiki.archlinux.org/index.php/Compiz Compiz - ArchWiki]

A note on using Kodi Standalone Service, this package runs Kodi as a '''systemd''' service and disables the login for user '''kodi''' and will not work when autologin is enabled. In fact, it will break the login process if you autologin user '''kodi''' and run Kodi Standalone Service at the same time. This package is installed automatically with the standard Kodi package when you install Kodi on Raspbian, but must be configured manually for all other Linux distributions. You can run the '''which''' command to find this package as well.

<pre>
which kodi-standalone
</pre>

Be advised, Kodi Standalone Service still launches the Kodi GUI and still requires a WM even though it is running as a '''systemd''' service. When you install a WM such as '''xfwm4''' (the WM for XFCE4), the CLI will tell you if it provides the '''x-window-manager''' package.

<pre>
Setting up xfwm4 (4.12.4-1) ...
update-alternatives: using /usr/bin/xfwm4 to provide /usr/bin/x-window-manager (x-window-manager) in auto mode
</pre>

If you do not see this message at the end of the installation, the WM you selected does not provide this software package and may not actually be a complete WM itself but only part of a package containing a WM.

For a great example on exactly how you would do this with '''xfwm4''', see this ArchWiki entry.

[https://wiki.archlinux.org/index.php/Xfwm XFWM - ArchWiki]

== Create custom Xsession script ==

Most systems utilize the client version of the X11 software Kodi standalone service requires.

Upgrade to the server versions of the X Window System.

<pre>apt install xauth xorg xinit xserver-xorg-core xserver-xorg xserver-common</pre>

Create a custom Xsession script with a text editor.

<pre>
nano ~/.xinitrc
</pre>

To run Kodi full-screen make sure the text reads:

<pre>
#!/usr/bin/env bash
/usr/bin/kodi -fs &
exec gnome-session
</pre>

Replace the '''gnome-session''' with the DE or WM command you are using. See the last section for examples.

To make '''~/.xinitrc''' executable use.

<pre>
chmod +x ~/.xinitrc
</pre>

Use '''sudo''' and the '''~/.xinitrc''' file to configure '''~/.xsession'''.

<pre>
sudo -H -u kodi bash -c "ln -s ~/.xinitrc ~/.xsession"
</pre>

You need to use '''sudo''' to run this command. If you do not have '''sudo''', install it.

<pre>
apt install sudo
</pre>

If you create a symbolic link and want to remove it, simply remove the existing '''.xsession''' file you created.

<pre>
rm /home/kodi/.xsession
</pre>

Remember you can modify use and reuse the '''~/.xinitrc''' file to configure '''~/.xsession''' as often as you want. That is the purpose of the file. It does nothing on its own until you associate it with a user. On some systems using a DE such as Gnome, not all systems using Gnome, it may be necessary for '''.xsession''' to be '''.xsessionrc'''. Though this is more likely the case for organization network computers than a personal one, where configurations may vary on a diversity of machines. Most of the time, it will be '''.xsession''' rather than '''.xsessionrc''' that you want to create.

You must also autostart the X Window system, which differs somewhat from scenario to scenario. For most setups, all that is necessary is to edit the '''.bashrc''' file.

<pre>
nano ~/.bashrc
</pre>

Add the following as shown.

<pre>
if [[ ! $DISPLAY && $XDG_VTNR -eq 1 ]]; then
exec startx
fi
</pre>

If you wish to remain logged in after quitting X, remove the '''exec''' from the above. Other configurations can be applied, but are irrelevant to autostarting Kodi.

[https://wiki.archlinux.org/index.php/Xinit#Autostart_X_at_login Xinit Autostart X at login]

== Xsession to boot to app / WM / DE ==

You can use any window manager or desktop enviroment with a custom Xsession script as long as it is intalled.

You do this by creating '''~/.xinitrc''' script that contains the command to start the WM or DE.

For instance, if you are using FluxBox?

<pre>
#!/usr/bin/env bash
/usr/bin/kodi -fs &
exec fluxbox &
</pre>

The <code>-fs</code> option is full-screen.

To start Gnome with Kodi full-screen:

<pre>
#!/usr/bin/env bash
/usr/bin/kodi -fs &
exec gnome-session &
</pre>

Use the '''~/.xinitrc''' file to configure '''~/.xsession''' to create a custom login for any user, not just Kodi.

<pre>
sudo -H -u [username] bash -c "ln -s ~/.xinitrc ~/.xsession"
</pre>

You must reconfigure Xserver for any user that is not a privileged user to be able to start a custom Xsession.

<pre>
dpkg-reconfigure xserver-xorg-legacy
</pre>

And / or...

<pre>
dpkg-reconfigure xserver-xorg
</pre>

If both packages are installed, you must reconfigure both. Not all systems will use or require the legacy package to allow non-root users to start X.

== Add a custom Grub entry ==

If you want to boot to the CLI and manually launch an app or boot directly to Kodi without a DE or WM, add a custom grub entry.

The right way to add a custom grub entry is to copy the menu entry you want to change or duplicate.

Copy the default Grub configuration file and open it with a text editor on your desktop. If you use a text editor on the CLI, the text will be cut off by the window when copying and pasting.

<pre>
cp /boot/grub/grub.cfg grub.cfg
gedit grub.cfg
</pre>

Copy the menu entry and paste it into '''40_custom''' with a text editor in the CLI.

<pre>
nano /etc/grub.d/40_custom
</pre>

Where the menu entry contains '''quiet splash''' change it to '''text''' instead.

You should also change the name of the entry!

I just appended mine with “CLI” for command line interface.

To update Grub:

<pre>
update-grub
</pre>

To launch a WM you can type its name. I use Enlightment 17 or Fluxbox. It must be installed.

<pre>
fluxbox
</pre>

You must have FluxBox installed. There are countless other window managers.

To launch a DE you enter the appropriate command. For Gnome desktop:

<pre>
gnome-session
</pre>

For KDE:

<pre>
startkde
</pre>

or

<pre>
plasma-desktop
</pre>

For XFCE:

<pre>
startxfce4
</pre>

For Mate:

<pre>
mate-session
</pre>

For LXDE:

<pre>
startlxde
</pre>

You can either manually launch your apps, boot right into them, or create an Xsession for each user. This is great when you want to create a Kodi user for running Kodi only, and for making sure you can still login to your DE with your regular user account. You can boot to any app full-screen this way, not just Kodi. You can create a custom Xsession script for any user, configured with any startup applications running in full-screen mode or normally.

By optionally creating a Grub menu entry, you can create a different Grub menu selection to boot only to the CLI and start an Xsession with a script or run commands manually.

HOW-TO:Autostart Kodi for Linux

2018-04-27T13:36:07Z

W3tech: /* Xsession to boot to app / WM / DE */

<section begin="intro" /><big>Any or all or any combination of these methods can be used to configure a Debian-based X Window System to boot directly to Kodi. This should work on any Linux using the X Window System, but these instructions are particular to Debian derivatives, such as Ubuntu. A server edition is best for running only Kodi, but this page assumes booting into a desktop OS, not a server distro. However, the instructions here can be used for a server distro with even less configuration than for a desktop. Experiment inside VirtualBox before you apply any of these to your system and make a backup.</big><section end="intro" />

__TOC__

== Switch to root ==

<pre>
su
</pre>

or

<pre>
sudo su
</pre>

== Create a Kodi user ==

To use Kodi full-screen, you only have to create a standard user.

<pre>
adduser kodi
</pre>

To remove the password use:

<pre>
passwd -d kodi
</pre>

== Customize LightDM to autologin ==

You can utilize the ability to customize LightDM data manager by changing the builtin custom configuration file '''50-myconfig.conf''' using '''nano''' or another text editor. If you have no DE or WM you can install '''lightdm''', but should make sure to do a bit of research before you do. Most versions of Linux use LightDM, but many server versions do not. For Ubuntu Server with no DE, for example, installing '''lightdm''' is okay and necessary. Changing the behavior of LightDM is done using a custom '''50-myconfig.conf''' configuration file.

To see if you have '''lightdm''' use '''which'''.

<pre>
which lightdm
</pre>

If not, install it with '''apt'''.

<pre>
apt install lightdm
</pre>

Create a custom configuration file called '''50-myconfig.conf''' using '''nano''' or other CLI text editor.

<pre>
mkdir /etc/lightdm/lightdm.conf.d/
nano /etc/lightdm/lightdm.conf.d/50-myconfig.conf
</pre>

Inside this new file add the following text.

<pre>
[SeatDefaults]
autologin-user=kodi
</pre>

== Configure Kodi to autostart ==

Configure Kodi to autostart.

<pre>
mkdir -p ~/.config/autostart
ln -s /usr/bin/kodi ~/.config/autostart
</pre>

This method of autostart requires a desktop environment or DE. This is done a bit differently by each DE. Some helpful links can easily be found in today's Web search using any search engine.

[http://edoceo.com/gui/xfce-autostart-apps Autostart Apps in XFCE]

The Raspberry Pi is a bit more of a tweak, but these are excellent links that will tell you how. The first link is the most helpful to making sure Kodi autostarts in Pi. There are many settings on the Pi that control boot, and the first link gives the best most trouble-free way to boot directly to Kodi. The others facilitate more tweaks and settings relevant to other uses of the X Window System.

[https://www.leowkahman.com/2016/03/05/lamp-stack-on-raspberry-pi-with-kodi-running-at-startup/ LAMP stack on Raspberry Pi with Kodi running at startup]

[http://ozzmaker.com/enable-x-windows-on-piscreen/ Enable X Window System on PiScreen]

[https://raspberrypi.stackexchange.com/questions/59310/remove-boot-messages-all-text-in-jessie Remove boot messages all text in Raspbian - Raspberry Pi Stack Exchange]

[https://raspberrypi.stackexchange.com/questions/47823/how-to-prevent-autologin-of-gui How to prevent or allow autologin of GUI - Raspberry Pi Stack Exchange]

[http://www.raspberry-projects.com/pi/pi-operating-systems/raspbian/auto-running-programs-gui Auto running programs LXDE - Raspberry Pi Projects]

And, if you would rather, it is easier to follow the process provided by this link to modify the Raspbian image before installing it onto the microSD card.

[https://wiki.debian.org/RaspberryPi/qemu-user-static Modifying Raspbian with qemu-user-static]

The above link describes removing the DE from a Raspbian image, though Raspbian Lite is a much better starting point for using Qemu for this purpose.

On Raspbian, you configure LightDM differently for autologin, which is necessary to boot directly to Kodi.

<pre>
nano /etc/lightdm/lightdm.conf
</pre>

Uncomment the following line.

<pre>
#autologin-user=
</pre>

And add the user you want to autologin and autostart Kodi. The user is named '''kodi''' in this example.

<pre>
autologin-user=kodi
</pre>

If Kodi is not installed at the standard path, find it using the '''which''' command.

<pre>
which kodi
</pre>

You can also use the X11 Window System to autostart Kodi.

<pre>
nano /etc/X11/Xsession.d/startup-local
</pre>

Insert this text into the new file. Use CTRL + O + Enter + X to save the file.

<pre>
#!/bin/sh
/usr/bin/kodi &
</pre>

If you have a WM, such as Blackbox you can add it here as well.

<pre>
#!/bin/sh
/usr/bin/kodi &
blackbox &
</pre>

Set permissions to make it executable.

<pre>
chmod 755 /etc/X11/Xsession.d/startup-local
</pre>

This feature is available on X Window System operating systems without upgrading to Xserver. Most Linux distributions use the X Window System.

== Disable / enable the login prompt ==

You can disable the graphical login prompt.

<pre>
systemctl set-default multi-user.target
</pre>

To enable it again use.

<pre>
systemctl set-default graphical.target
</pre>

If you are using an autologin method associated with your DE or WM, you '''do not''' want to disable the graphical login.

Even if you are using something like [https://github.com/graysky2/kodi-standalone-service Kodi Standalone Service], you still need use a WM or a DE that installs the '''x-window-manager''' software package.

To ensure you have this installed use the '''which''' command.

<pre>
which x-window-manager
</pre>

If there is no such package, you can use '''apt''' to search your Linux distributions repository.

<pre>
apt-cache search x-window-manager
</pre>

This will general a list of packages containing '''x-window-manager''', which cannot be installed alone. If you are not using a DE, you need to use a WM. And, you can also use a compositing WM like Compiz, for fast 3D effects.

[https://wiki.archlinux.org/index.php/Compiz Compiz - ArchWiki]

A note on using Kodi Standalone Service, this package runs Kodi as a '''systemd''' service and disables the login for user '''kodi''' and will not work when autologin is enabled. In fact, it will break the login process if you autologin user '''kodi''' and run Kodi Standalone Service at the same time. This package is installed automatically with the standard Kodi package when you install Kodi on Raspbian, but must be configured manually for all other Linux distributions. You can run the '''which''' command to find this package as well.

<pre>
which kodi-standalone
</pre>

Be advised, Kodi Standalone Service still launches the Kodi GUI and still requires a WM even though it is running as a '''systemd''' service. When you install a WM such as '''xfwm4''' (the WM for XFCE4), the CLI will tell you if it provides the '''x-window-manager''' package.

<pre>
Setting up xfwm4 (4.12.4-1) ...
update-alternatives: using /usr/bin/xfwm4 to provide /usr/bin/x-window-manager (x-window-manager) in auto mode
</pre>

If you do not see this message at the end of the installation, the WM you selected does not provide this software package and may not actually be a complete WM itself but only part of a package containing a WM.

For a great example on exactly how you would do this with '''xfwm4''', see this ArchWiki entry.

[https://wiki.archlinux.org/index.php/Xfwm XFWM - ArchWiki]

== Create custom Xsession script ==

Most systems utilize the client version of the X11 software Kodi standalone service requires.

Upgrade to the server versions of the X Window System.

<pre>apt install xauth xorg xinit xserver-xorg-core xserver-xorg xserver-common</pre>

Create a custom Xsession script with a text editor.

<pre>
nano ~/.xinitrc
</pre>

To run Kodi full-screen make sure the text reads:

<pre>
#!/usr/bin/env bash
/usr/bin/kodi -fs &
exec gnome-session
</pre>

Replace the '''gnome-session''' with the DE or WM command you are using. See the last section for examples.

To make '''~/.xinitrc''' executable use.

<pre>
chmod +x ~/.xinitrc
</pre>

Use '''sudo''' and the '''~/.xinitrc''' file to configure '''~/.xsession'''.

<pre>
sudo -H -u kodi bash -c "ln -s ~/.xinitrc ~/.xsession"
</pre>

You need to use '''sudo''' to run this command. If you do not have '''sudo''', install it.

<pre>
apt install sudo
</pre>

If you create a symbolic link and want to remove it, simply remove the existing '''.xsession''' file you created.

<pre>
rm /home/kodi/.xsession
</pre>

Remember you can modify use and reuse the '''~/.xinitrc''' file to configure '''~/.xsession''' as often as you want. That is the purpose of the file. It does nothing on its own until you associate it with a user. On some systems using a DE such as Gnome, not all systems using Gnome, it may be necessary for '''.xsession''' to be '''.xsessionrc'''. Though this is more likely the case for organization network computers than a personal one, where configurations may vary on a diversity of machines. Most of the time, it will be '''.xsession''' rather than '''.xsessionrc''' that you want to create.

You must also autostart the X Window system, which differs somewhat from scenario to scenario. For most setups, all that is necessary is to edit the '''.bashrc''' file.

<pre>
nano ~/.bashrc
</pre>

Add the following as shown.

<pre>
if [[ ! $DISPLAY && $XDG_VTNR -eq 1 ]]; then
exec startx
fi
</pre>

If you wish to remain logged in after quitting X, remove the '''exec''' from the above. Other configurations can be applied, but are irrelevant to autostarting Kodi.

[https://wiki.archlinux.org/index.php/Xinit#Autostart_X_at_login Xinit Autostart X at login]

== Xsession to boot to app / WM / DE ==

You can use any window manager or desktop enviroment with a custom Xsession script as long as it is intalled.

You do this by creating '''~/.xinitrc''' script that contains the command to start the WM or DE.

For instance, if you are using FluxBox?

<pre>
#!/usr/bin/env bash
/usr/bin/kodi -fs &
exec fluxbox &
</pre>

The <code>-fs</code> option is full-screen.

To start Gnome with Kodi full-screen:

<pre>
#!/usr/bin/env bash
/usr/bin/kodi -fs &
exec gnome-session &
</pre>

Use the '''~/.xinitrc''' file to configure '''~/.xsession''' to create a custom login for any user, not just Kodi.

<pre>
sudo -H -u [username] bash -c "ln -s ~/.xinitrc ~/.xsession"
</pre>

You must reconfigure Xserver for any user that is not a privileged user to be able to start a custom Xsession.

<pre>
dpkg-reconfigure xserver-xorg-legacy
</pre>

And / or...

<pre>
dpkg-reconfigure xserver-xorg
</pre>

If both packages are installed, you must reconfigure both. Not all systems will use or require the legacy package to allow non-root users to start X.

== Add a custom Grub entry ==

If you want to boot to the CLI and manually launch an app, WM or DE, add a custom grub entry.

The right way to add a custom grub entry is to copy the menu entry you want to change or duplicate.

Copy the default Grub configuration file and open it with a text editor on your desktop. If you use a text editor on the CLI, the text will be cut off by the window when copying and pasting.

<pre>
cp /boot/grub/grub.cfg grub.cfg
gedit grub.cfg
</pre>

Copy the menu entry and paste it into '''40_custom''' with a text editor in the CLI.

<pre>
nano /etc/grub.d/40_custom
</pre>

Where the menu entry contains '''quiet splash''' change it to '''text''' instead.

You should also change the name of the entry!

I just appended mine with “CLI” for command line interface.

To update Grub:

<pre>
update-grub
</pre>

To launch a WM you can type its name. I use Enlightment 17 or Fluxbox. It must be installed.

<pre>
fluxbox
</pre>

You must have FluxBox installed. There are countless other window managers.

To launch a DE you enter the appropriate command. For Gnome desktop:

<pre>
gnome-session
</pre>

For KDE:

<pre>
startkde
</pre>

or

<pre>
plasma-desktop
</pre>

For XFCE:

<pre>
startxfce4
</pre>

For Mate:

<pre>
mate-session
</pre>

For LXDE:

<pre>
startlxde
</pre>

You can either manually launch your apps, boot right into them, or create an Xsession for each user. This is great when you want to create a Kodi user for running Kodi only, and for making sure you can still login to your DE with your regular user account. You can boot to any app full-screen this way, not just Kodi. You can create a custom Xsession script for any user, configured with any startup applications running in full-screen mode or normally.

By optionally creating a Grub menu entry, you can create a different Grub menu selection to boot only to the CLI and start an Xsession with a script or run commands manually.

HOW-TO:Autostart Kodi for Linux

2018-04-27T13:32:28Z

W3tech: /* Configure Kodi to autostart */

<section begin="intro" /><big>Any or all or any combination of these methods can be used to configure a Debian-based X Window System to boot directly to Kodi. This should work on any Linux using the X Window System, but these instructions are particular to Debian derivatives, such as Ubuntu. A server edition is best for running only Kodi, but this page assumes booting into a desktop OS, not a server distro. However, the instructions here can be used for a server distro with even less configuration than for a desktop. Experiment inside VirtualBox before you apply any of these to your system and make a backup.</big><section end="intro" />

__TOC__

== Switch to root ==

<pre>
su
</pre>

or

<pre>
sudo su
</pre>

== Create a Kodi user ==

To use Kodi full-screen, you only have to create a standard user.

<pre>
adduser kodi
</pre>

To remove the password use:

<pre>
passwd -d kodi
</pre>

== Customize LightDM to autologin ==

You can utilize the ability to customize LightDM data manager by changing the builtin custom configuration file '''50-myconfig.conf''' using '''nano''' or another text editor. If you have no DE or WM you can install '''lightdm''', but should make sure to do a bit of research before you do. Most versions of Linux use LightDM, but many server versions do not. For Ubuntu Server with no DE, for example, installing '''lightdm''' is okay and necessary. Changing the behavior of LightDM is done using a custom '''50-myconfig.conf''' configuration file.

To see if you have '''lightdm''' use '''which'''.

<pre>
which lightdm
</pre>

If not, install it with '''apt'''.

<pre>
apt install lightdm
</pre>

Create a custom configuration file called '''50-myconfig.conf''' using '''nano''' or other CLI text editor.

<pre>
mkdir /etc/lightdm/lightdm.conf.d/
nano /etc/lightdm/lightdm.conf.d/50-myconfig.conf
</pre>

Inside this new file add the following text.

<pre>
[SeatDefaults]
autologin-user=kodi
</pre>

== Configure Kodi to autostart ==

Configure Kodi to autostart.

<pre>
mkdir -p ~/.config/autostart
ln -s /usr/bin/kodi ~/.config/autostart
</pre>

This method of autostart requires a desktop environment or DE. This is done a bit differently by each DE. Some helpful links can easily be found in today's Web search using any search engine.

[http://edoceo.com/gui/xfce-autostart-apps Autostart Apps in XFCE]

The Raspberry Pi is a bit more of a tweak, but these are excellent links that will tell you how. The first link is the most helpful to making sure Kodi autostarts in Pi. There are many settings on the Pi that control boot, and the first link gives the best most trouble-free way to boot directly to Kodi. The others facilitate more tweaks and settings relevant to other uses of the X Window System.

[https://www.leowkahman.com/2016/03/05/lamp-stack-on-raspberry-pi-with-kodi-running-at-startup/ LAMP stack on Raspberry Pi with Kodi running at startup]

[http://ozzmaker.com/enable-x-windows-on-piscreen/ Enable X Window System on PiScreen]

[https://raspberrypi.stackexchange.com/questions/59310/remove-boot-messages-all-text-in-jessie Remove boot messages all text in Raspbian - Raspberry Pi Stack Exchange]

[https://raspberrypi.stackexchange.com/questions/47823/how-to-prevent-autologin-of-gui How to prevent or allow autologin of GUI - Raspberry Pi Stack Exchange]

[http://www.raspberry-projects.com/pi/pi-operating-systems/raspbian/auto-running-programs-gui Auto running programs LXDE - Raspberry Pi Projects]

And, if you would rather, it is easier to follow the process provided by this link to modify the Raspbian image before installing it onto the microSD card.

[https://wiki.debian.org/RaspberryPi/qemu-user-static Modifying Raspbian with qemu-user-static]

The above link describes removing the DE from a Raspbian image, though Raspbian Lite is a much better starting point for using Qemu for this purpose.

On Raspbian, you configure LightDM differently for autologin, which is necessary to boot directly to Kodi.

<pre>
nano /etc/lightdm/lightdm.conf
</pre>

Uncomment the following line.

<pre>
#autologin-user=
</pre>

And add the user you want to autologin and autostart Kodi. The user is named '''kodi''' in this example.

<pre>
autologin-user=kodi
</pre>

If Kodi is not installed at the standard path, find it using the '''which''' command.

<pre>
which kodi
</pre>

You can also use the X11 Window System to autostart Kodi.

<pre>
nano /etc/X11/Xsession.d/startup-local
</pre>

Insert this text into the new file. Use CTRL + O + Enter + X to save the file.

<pre>
#!/bin/sh
/usr/bin/kodi &
</pre>

If you have a WM, such as Blackbox you can add it here as well.

<pre>
#!/bin/sh
/usr/bin/kodi &
blackbox &
</pre>

Set permissions to make it executable.

<pre>
chmod 755 /etc/X11/Xsession.d/startup-local
</pre>

This feature is available on X Window System operating systems without upgrading to Xserver. Most Linux distributions use the X Window System.

== Disable / enable the login prompt ==

You can disable the graphical login prompt.

<pre>
systemctl set-default multi-user.target
</pre>

To enable it again use.

<pre>
systemctl set-default graphical.target
</pre>

If you are using an autologin method associated with your DE or WM, you '''do not''' want to disable the graphical login.

Even if you are using something like [https://github.com/graysky2/kodi-standalone-service Kodi Standalone Service], you still need use a WM or a DE that installs the '''x-window-manager''' software package.

To ensure you have this installed use the '''which''' command.

<pre>
which x-window-manager
</pre>

If there is no such package, you can use '''apt''' to search your Linux distributions repository.

<pre>
apt-cache search x-window-manager
</pre>

This will general a list of packages containing '''x-window-manager''', which cannot be installed alone. If you are not using a DE, you need to use a WM. And, you can also use a compositing WM like Compiz, for fast 3D effects.

[https://wiki.archlinux.org/index.php/Compiz Compiz - ArchWiki]

A note on using Kodi Standalone Service, this package runs Kodi as a '''systemd''' service and disables the login for user '''kodi''' and will not work when autologin is enabled. In fact, it will break the login process if you autologin user '''kodi''' and run Kodi Standalone Service at the same time. This package is installed automatically with the standard Kodi package when you install Kodi on Raspbian, but must be configured manually for all other Linux distributions. You can run the '''which''' command to find this package as well.

<pre>
which kodi-standalone
</pre>

Be advised, Kodi Standalone Service still launches the Kodi GUI and still requires a WM even though it is running as a '''systemd''' service. When you install a WM such as '''xfwm4''' (the WM for XFCE4), the CLI will tell you if it provides the '''x-window-manager''' package.

<pre>
Setting up xfwm4 (4.12.4-1) ...
update-alternatives: using /usr/bin/xfwm4 to provide /usr/bin/x-window-manager (x-window-manager) in auto mode
</pre>

If you do not see this message at the end of the installation, the WM you selected does not provide this software package and may not actually be a complete WM itself but only part of a package containing a WM.

For a great example on exactly how you would do this with '''xfwm4''', see this ArchWiki entry.

[https://wiki.archlinux.org/index.php/Xfwm XFWM - ArchWiki]

== Create custom Xsession script ==

Most systems utilize the client version of the X11 software Kodi standalone service requires.

Upgrade to the server versions of the X Window System.

<pre>apt install xauth xorg xinit xserver-xorg-core xserver-xorg xserver-common</pre>

Create a custom Xsession script with a text editor.

<pre>
nano ~/.xinitrc
</pre>

To run Kodi full-screen make sure the text reads:

<pre>
#!/usr/bin/env bash
/usr/bin/kodi -fs &
exec gnome-session
</pre>

Replace the '''gnome-session''' with the DE or WM command you are using. See the last section for examples.

To make '''~/.xinitrc''' executable use.

<pre>
chmod +x ~/.xinitrc
</pre>

Use '''sudo''' and the '''~/.xinitrc''' file to configure '''~/.xsession'''.

<pre>
sudo -H -u kodi bash -c "ln -s ~/.xinitrc ~/.xsession"
</pre>

You need to use '''sudo''' to run this command. If you do not have '''sudo''', install it.

<pre>
apt install sudo
</pre>

If you create a symbolic link and want to remove it, simply remove the existing '''.xsession''' file you created.

<pre>
rm /home/kodi/.xsession
</pre>

Remember you can modify use and reuse the '''~/.xinitrc''' file to configure '''~/.xsession''' as often as you want. That is the purpose of the file. It does nothing on its own until you associate it with a user. On some systems using a DE such as Gnome, not all systems using Gnome, it may be necessary for '''.xsession''' to be '''.xsessionrc'''. Though this is more likely the case for organization network computers than a personal one, where configurations may vary on a diversity of machines. Most of the time, it will be '''.xsession''' rather than '''.xsessionrc''' that you want to create.

You must also autostart the X Window system, which differs somewhat from scenario to scenario. For most setups, all that is necessary is to edit the '''.bashrc''' file.

<pre>
nano ~/.bashrc
</pre>

Add the following as shown.

<pre>
if [[ ! $DISPLAY && $XDG_VTNR -eq 1 ]]; then
exec startx
fi
</pre>

If you wish to remain logged in after quitting X, remove the '''exec''' from the above. Other configurations can be applied, but are irrelevant to autostarting Kodi.

[https://wiki.archlinux.org/index.php/Xinit#Autostart_X_at_login Xinit Autostart X at login]

== Xsession to boot to app / WM / DE ==

You can use any window manager or desktop enviroment with a custom Xsession script as long as it is intalled.

You do this by creating '''~/.xinitrc''' script that contains the command to start the WM or DE.

For instance, if you are using FluxBox?

<pre>
#!/usr/bin/env bash
/usr/bin/kodi -fs &
exec fluxbox &
</pre>

The <code>-fs</code> option is full-screen.

To start Gnome with Kodi full-screen:

<pre>
#!/usr/bin/env bash
/usr/bin/kodi -fs &
exec gnome-session &
</pre>

Use the '''~/.xinitrc''' file to configure '''~/.xsession''' to create a custom login for any user, not just Kodi.

<pre>
sudo -H -u [username] bash -c "ln -s ~/.xinitrc ~/.xsession"
</pre>

You must reconfigure Xserver for any user that is not a privileged user to be able to start a custom Xsession.

<pre>
dpkg-reconfigure xserver-xorg-legacy
</pre>

or

<pre>
dpkg-reconfigure xserver-xorg
</pre>

== Add a custom Grub entry ==

If you want to boot to the CLI and manually launch an app, WM or DE, add a custom grub entry.

The right way to add a custom grub entry is to copy the menu entry you want to change or duplicate.

Copy the default Grub configuration file and open it with a text editor on your desktop. If you use a text editor on the CLI, the text will be cut off by the window when copying and pasting.

<pre>
cp /boot/grub/grub.cfg grub.cfg
gedit grub.cfg
</pre>

Copy the menu entry and paste it into '''40_custom''' with a text editor in the CLI.

<pre>
nano /etc/grub.d/40_custom
</pre>

Where the menu entry contains '''quiet splash''' change it to '''text''' instead.

You should also change the name of the entry!

I just appended mine with “CLI” for command line interface.

To update Grub:

<pre>
update-grub
</pre>

To launch a WM you can type its name. I use Enlightment 17 or Fluxbox. It must be installed.

<pre>
fluxbox
</pre>

You must have FluxBox installed. There are countless other window managers.

To launch a DE you enter the appropriate command. For Gnome desktop:

<pre>
gnome-session
</pre>

For KDE:

<pre>
startkde
</pre>

or

<pre>
plasma-desktop
</pre>

For XFCE:

<pre>
startxfce4
</pre>

For Mate:

<pre>
mate-session
</pre>

For LXDE:

<pre>
startlxde
</pre>

You can either manually launch your apps, boot right into them, or create an Xsession for each user. This is great when you want to create a Kodi user for running Kodi only, and for making sure you can still login to your DE with your regular user account. You can boot to any app full-screen this way, not just Kodi. You can create a custom Xsession script for any user, configured with any startup applications running in full-screen mode or normally.

By optionally creating a Grub menu entry, you can create a different Grub menu selection to boot only to the CLI and start an Xsession with a script or run commands manually.

HOW-TO talk:Autostart Kodi for Linux

2018-04-27T13:20:38Z

W3tech: Changes update and planned changes