Kodi tu peux très bien l'installer en standalone avec une Fedora. C'est ce que j'ai fait sur une Beebox d'Asrock avec une installation minimale de Fedora.
Donc tu fais tout en ligne de commande jusqu'à avoir
Kodi qui démarre. Ensuite tu n'as qu'un serveur multimédia qui démarre et s'arrête, géré avec une souris ou une télécommande.
J'avais dû faire comme ci-dessous normalement mais faut voir s'il y aussi avec Wayland maintenant. Faudrait faire une recherche.
** Kodi requires a functioning X-Windows server to be present on the system it runs on. However, since it typically runs in fullscreen mode without any X-Windows decorations, it does not require any display managers or desktop environments such as Gnome or KDE. The following commands install a basic X-Windows setup.
NOTE: This will not cause your system to actually boot up into multi-user graphical mode (X-Windows) automatically. That will be done when the system starts up Kodi as a standalone application.
# dnf groupinstall "base-x"
** In order for the Kodi user-account to be able to use accelerated video driver within the X-Windows system, it must be added to the video user-group.
# usermod kodi -a -G video
** In order for the Kodi user-account to be able to produce audio within the X-Windows system, it must be added to the audio user-group.
# usermod kodi -a -G audio
** Installing Kodi from RPMFusion respository
# dnf install kodi
** Create Systemd Service File For X-Windows / Kodi
By default Fedora uses Systemd to manage services and daemons. The following creates a Systemd service file that, once enabled, will cause the system to autostart X-Windows as well as Kodi as a standalone, fullscreen application whenever the system is booted. Because it was manually created and not installed as part of any package, it gets placed in "
/etc/systemd/system" instead of "
/lib/systemd/systemd".
# vi /etc/systemd/system/kodi.service
[Unit]
Description = kodi-standalone using xinit
After = remote-fs.target systemd-user-sessions.service
[Service]
User = kodi
Group = kodi
PAMName = login
Type = simple
ExecStart = /usr/bin/xinit /usr/bin/dbus-launch /usr/bin/kodi-standalone -- :0 -nolisten tcp
Restart = on-abort
[Install]
WantedBy = multi-user.target
** Install DBUS addon for X-Windows
X-Windows requires that an addon be installed in order to become DBUS-aware, which in-turn is required in order for Kodi to be properly started at boot-time. This step provides the
/usr/bin/dbus-launch tool within in the Systemd service file from the previous step.
# dnf install dbus-x11
** Load and Enable New Systemd Service File
Now that the new Systemd service file has been created, Systemd needs to rescan its configuration to pick up the new file. Afterwards, the service is enabled for future reboots.
# systemctl daemon-reload
# systemctl enable kodi
** In order for Kodi to be able to poweroff the system, enter suspend-mode or initiate hibernation, a PolicyKit Local Authority configuration file needs to be created.
# vi /etc/polkit-1/localauthority/50-local.d/kodi_shutdown.pkla
[Actions for kodi user]
Identity=unix-user:kodi
Action=org.freedesktop.devicekit.power.*;org.freedesktop.upower.*;org.freedesktop.consolekit.system.*;org.freedesktop.login1.*
ResultAny=yes
** UPower (formerly DeviceKit-power) facilitates managing power devices attached to the system. It is what allows Kodi to actually manipulate power-related functions such as shutting everything down.
# dnf install upower
** In order for the X-Windows server to be started by a non-console user such as the Kodi account, a new Xwrapper configuration must be created. Also set the appropriate file permissions on the new configuration.
# vi /etc/X11/Xwrapper.config
allowed_users = anybody
# chmod 644 /etc/X11/Xwrapper.config