Archive talk:Install Kodi on Fedora 26 using RPMFusion packages

Guide rewrite

I am going to be revising a few sections soon.

1. Firewall: You can leave it enabled and just open the following ports: TCP: 1151, 8080, and UDP: 1900, 9777
2. Pulseaudio: Kodi is fully functional with pulseaudio installed and enabled.
3. Systemd service: If you have GDM installed (and autologin enabled) you do not need any of the service script or other changes so it makes this guide much more simple. As the old saying goes: Keep It Simple Stupid.

Mooninite (talk) 09:05, 8 April 2015 (EDT)

1. Thanks for the firewall-related tips. I believe the port-list that should be opened will depend on individual circumstances. For example on my standalone setup the kodi.bin process is listening on ports TCP (8080, 1147) and UDP (9777, 1900). Were I to utilize miniDLNA I would have to add TCP port 8200. Airplay can potentially require TCP (80, 443, 554, 3689, 5297, 5289) and UDP (554, 5289, 5353). Given that this is a standalone environment and making custom adjustments to the firewall as services are enabled/disabled is an advanced topic, it seems much simpler to leave the firewall disabled - with the caveats already mentioned in the wiki.
2. Pulseaudio still has some deficiencies, such has lacking support for TrueHD or DTS-MA, preventing use of Dolby Pro Logic II, etc. Refer to PulseAudio for some further explanation. Actually, the only real advantage Pulseaudio offers is non-exclusive use of the audio subsystem, in cases where you'd like (for example) desktop sounds or other apps to co-exist with Kodi. Since this guide is strongly focused on creating a standalone Kodi environment, Pulseaudio makes little sense to utilize. Given its deficiencies and lack of countervailing advantages, there's no reason to utilize PulseAudio.
3. Why would you want GDM to be installed? It's just an unnecessary layer of functionality that introduces complexity but offers little/no benefit. At the very least you'd then have to set up GDM-based auto-login, which is not only extra complexity but a potential security risk. The spirit of this guide is to create a standalone, lightweight installation of Kodi with minimal additional requirements. You are exactly right re: KISS, and introducing a dependency on an unnecessary software layer would seem to contravene this.

You made some earlier edits that removed the section on disabling SELinux. Kodi may have evolved to the point where it can properly function in an SELinux-Enforcing environment, but it used to have issues. I will test in an enforcing environment and update the wiki accordingly. However until I've tested it I will revert your changes to restore the SELinux section.

Thanks again for the tips!

Wirerydr (talk) 12:03, 24 April 2015 (EDT)

Hope you don't mind that I added a section for CEC, it was a feature I needed and I thought it may be useful until libcec>=3.0.0 is put into the fedora repos and the rpm in rpmfusion is rebuilt.

Slashnull (talk) 13:46, 15 January 2016 (EDT)

Don't mind at all Slashnull - TYVM for the contribution, and also for maintaining the existing look-and-feel. I may reorder things a bit to avoid CEC users from doing a double install of the generic and then CEC-enabled RPMs, but that's trivial.

Cheers... Wirerydr (talk) 00:20, 18 January 2016 (EST)

Hi Spazticclown - thanks for the video-group contribution. In my experience this is not actually necessary in order to run Kodi as described in this HowTo - not on any version of Fedora from F19 through to the current F23, anyway. I believe as long as the user is in group 'wheel' (which it is as a result of step 3.3), that is sufficient. Just to be sure I took a look at my main kodi box running in my livingroom, and confirmed that user Kodi is not present in group 'video' (gid 39). As such I have reverted back to before your change, but I did want to thank you again for your contribution.

Cheers... Wirerydr (talk) 23:51, 7 February 2016 (EST)