Just installed Debian 12 from scratch and Kodi, only using ALSA for sound.
I have two sound devices, the HDMI to my sound receiver and an external DAC.
Every thing runs good with great sound quality, but I got 3 HDMI connection in Kodi gui that I do not use (the first one I use even spells out name of sound receiver). The only configuration I had done is to set index of cards in /etc/modprobe.d/sound.conf to (as it was flipped in order during reboot); options snd_hda_intel index=0 options snd-usb-audio index=1 So how can I remove the unused HDMI sinks in ALSA, should I just edit some Kodi file, witch files to edit? EDIT AI chat gpt sugested adding an udev rule. So what I did: Created the file: /etc/udev/rules.d/99-nvidia-hdmi.rules With this content: > SUBSYSTEMS=="sound", ATTRS{id}=="NVidia", ATTRS{device}=="7", KERNEL=="card*", OPTIONS+="ignore_device" SUBSYSTEMS=="sound", ATTRS{id}=="NVidia", ATTRS{device}=="8", KERNEL=="card*", OPTIONS+="ignore_device" SUBSYSTEMS=="sound", ATTRS{id}=="NVidia", ATTRS{device}=="9", KERNEL=="card*", OPTIONS+="ignore_device" Made it executable: sudo chmod u+x /etc/udev/rules.d/99-nvidia-hdmi.rules Did a reboot of machine. But that did not function, still the sinks in kodi gui. Something I missed, a prefix for the card, maybee ( I tried to read about it on internet, but it is quit complicated.

Apologies in advance if there is an existing answer I should consult... Fired up Kodi for the first time on my Ubuntu Studio 24.04 box. It has a 1 TB hard drive, of which almost half is consumed by the .flac files. Before running Kodi, about a quarter of the disc was free. I went through and added the appropriate media directories to to kodi's configuration, and initially it seemed to be working. Came back this morning, selected music, and rather than coming up with the list of albums Kodi locked up, unable to write log files to a full disk. Killing Kodi confirms disk is full, but it isn't clear what or where the additional space was consumed. /home, including the media, still reports under 500GB. Going through other directories under / with sudo du, I'm not finding anything over 12 GB (for /usr). So I'm very confused about where the space went. Admittedly ls | xargs sudo du -sh executed from / reports that it can't access things under /proc/117484 or /run/user/1000/doc. Has anyone else seen this, or does anyone have a suggestion for where to look for the missing gigabytes? (No, I haven't tried just rebooting yet; I'm a trifle afraid to do so before I know I have enough disk space to run safely. )

I'm trying to work around an issue I have with hidden fuse files locked by kodi.bin. Please note that I'm already trying to resolve the root cause for the actual issue through other threads but havn't been successful at it yet (it's probably an issue with kodi or more likely its extension vfs.rar). **Some context:** - 1 computer running under Ubuntu 22.04 - when I boot the computer, 1 user (let's call it "kodiuser") auto logs in and start kodi as a standalone session - kodi is set to use the extension vfs.rar to watch movies that are stored in rar files - right now, after I'm done with the movie, I can't delete the folder of this movie until I have restarted kodi, which is not handy because of the kodi standalone session (so I usually user the kodi remote on my phone to reboot the server) - this is due to the fact that kodi hasn't released some of the files **What I'd like to do:** - connect to the computer terminal as the user "kodiuser" maybe (or another one that is sudoer?) - kill kodi.bin - restart kodi **Problem:** Because it is set to a kodi standalone session, when kodi.bin is killed it gets me to the ubuntu user connection landing page (sorry I don't know how to call this properly, but that's where you have to log in with a user to open a linux graphical session) -> I think that this implies that in addition to killing it I should start a new standalone kodi session from this same command line, which should equal to restarting kodi. What do you think? Any guidance to the command line I would have to execute if this is doable? I hope this is clear. Thanks in advance.

I have a new home-made HTPC running Debian bullseye + X11 + LightDM + Kodi 19. The HTPC is connected to a Plasma screen and my local network but not much else (no mouse, no keyboard). Kodi is controlled through Kore, an android remote control app for Kodi that works over the network. My problem is that X doesn't see the remote control's actions as user activity so, after about 10mn, the screen goes black and a mouse has to be plugged-in and jiggled to wake up the screen. My first idea was to disable DPMS and be done with it:

nano /usr/share/X11/xorg.conf.d/10-monitor.conf

Section "Extensions"
        Option      "DPMS" "Disable"
EndSection

But for some reason it didn't work. In the meantime, I changed my mind and thought that having the screen go black after real inactivity would be great, considering the screen is a Plasma and is prone to burn-ins. So: Ho do I make X11 see Kore's inputs as user activity? I have an idea, which would be to make Kore connect to a dummy port (say 8081). Then have a python script running forever on the HTPC, listening on 8081 and forwarding requests to the port Kodi listens on (say 8082). Every time my script proxies a requests, it would trigger a key press (something like Ctrl pressed + Ctrl released to avoid side-effect). I haven't tested it yet but I thought I'd get some different ideas form the community first.

I'd like to lock my Debian10/KDE system to one program and prevent any interaction of a user with anything beyond the always-on-top fullscreen program, making it impossible to shut down, to minimize, to open the process manager and to show the tray bar by pressing the Windows key. In particular I'd like to lock it to the media center Kodi in a way that closing/minimizing it or opening other software requires the root password. (This would also require the root-password for the shutdown button within Kodi or at least e.g. a custom key-combination). Is this possible with some software or CLI commands / parameters *within the current session* (maybe using KDE Plasma Activities )? And if not how could this get implemented technically?

I have a raspberry pi with a Wireguard Server and a number of peer's Android, Windows and another Raspberry pi. The tunnel works on all clients (for example i can ping my upnp server). The thing that does not work is that on the Raspi client it does not find the upnp server. I can ping the server but kodi for example can not find it. On the other clients it does work. VLC for example can find the server on these client's but only when i set the allowed addresses to 0.0.0.0/0. I guess that this some routing thing or the way that a upnp server works.? So i did the same thing on the pi but still it can not find the server. But ping is still working. I was wondering if this could be because i connect the pi via wifi? Maybe someone has an idea. Thank you for your help.

The current version of Kodi in Debian10's repositories is v17.6. This version didn't work properly (it wasn't usable). Hence I'm trying to install the latest version. I followed the steps of the "Debian/Ubuntu build guide" of the Kodi repository except that I didn't add the PPA. I used sudo apt build-dep kodi as packages "flatbuffers-dev" and "libshairplay-dev" could not be found and there wasn't an installation candidate for "libmysqlclient-dev" when trying to build dependencies manually. When trying to follow the steps of "Build Kodi" of the "Linux build guide" which are the last step of the "Debian/Ubuntu build guide" I get these errors when running command cmake ../kodi -DCMAKE_INSTALL_PREFIX=/usr/local -DX11_RENDER_SYSTEM=gl: > CMake Error at CMakeLists.txt:95 (core_add_library): Unknown CMake > command "core_add_library". > > > CMake Warning (dev) in CMakeLists.txt: No cmake_minimum_required > command is present. A line of code such as > > cmake_minimum_required(VERSION 3.13) > > should be added at the top of the file. The version specified may > be lower if you wish to support older CMake versions for this > project. For more information run "cmake --help-policy CMP0000". > This warning is for project developers. Use -Wno-dev to suppress it. > > -- Configuring incomplete, errors occurred! Do I need to add the PPA and should I? Or is there something else that should be done to compile it? Would it be recommended to install it via the flatpak instead?

I’ve decided to turn an old Compaq Presario V3700 to create a media center with Kodi. Stats: - CPU: Intel Pentium Dual T2410 2 GHz - RAM: 443/971 mb used - SWAP: 1942 - Display: Mobile GM965/GL960 Integrated Graphics Controller (seems to be 2, primary and secondary) - HD: 149.1 G (+ 2 x 931.5G external HD for media storage). More on https://pastebin.com/wf6haWL3

free
              total        used        free      shared  buff/cache   available
Mem:         995224      450560       81964       99960      462700      284572
Swap:       1989628      491776     1497852

The laptop wasn’t doing too bad with Windows. Initially installed Lubuntu, then was advised on the Lubuntu forum to install Ubuntu Server. I did that, it was fun, then installed Kodi. However, the whole machine is just super slow. The boot lasts several minutes, opening Kodi takes 30 seconds or so, and I have to wait several seconds between every mouse / menu selection of Kodi. Movies are also not playing smoothly buy jump frames instead. This is not a Kodi issue though. In the process I installed Firefox to help downloading a couple of things and looking up info, and similarly opening or closing Firefox or a new tab there on can take up to a minute. It’s insanely slow—I feel I’m back in the 2000s. Based on my experience with this laptop with Windows and my past experience with Ubuntu all the way back to 2006 until now, I’m pretty sure this is not normal. So having declared the symptoms, what can I do next? I don’t mind installing any distro that can be of service, so I’m not married to Ubuntu here. Any suggestions?

I believe LibreElec is using some form of BusyBox. I've done lots searching and been unable to find where password rules can be changed. Since my LibreElec media player is not connected to the internet, I feel fine using short numeric passwords. It's my machine and am willing to deal with any consequences that result.

I have a Kodi 16.1 installation on a Ubuntu 16 VM and it has stopped working. It constantly crashes when it is scraping TV. I have removed ~/.kodi and it works normally, but as soon as I added back my advancedsettings.xml and pointed it to my TV directory it crashed. Oddly, it was able to scrape my Movie library just fine, only TV causes an issue. Here is some of the log, it was 7MB log so I trimmed some stuff. Any ideas what could be the issue? ############## Kodi CRASH LOG ############### ################ SYSTEM INFO ################ Date: Sat Aug 3 04:38:57 PDT 2019 Kodi Options: Arch: x86_64 Kernel: Linux 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:07:12 UTC 2016 Release: Ubuntu 16.04.5 LTS (Xenial Xerus) ############## END SYSTEM INFO ############## ############### STACK TRACE ################# =====> Core file: /home/sysadmin/core (2019-08-03 04:38:57.897997384 -0700) ========================================= [New LWP 2892] [New LWP 2857] [New LWP 2859] [New LWP 2860] [New LWP 2862] [New LWP 2866] [New LWP 2867] [New LWP 2868] [New LWP 2869] [New LWP 2871] [New LWP 2873] [New LWP 2875] [New LWP 2876] [New LWP 2877] [New LWP 2878] [New LWP 2879] [New LWP 2880] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `/usr/lib/kodi/kodi.bin'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x00007f129c372bbc in _int_malloc (av=av@entry=0x7f1254000020, bytes=bytes@entry=79) at malloc.c:3353 [Current thread is 1 (Thread 0x7f1286542700 (LWP 2892))] Thread 17 (Thread 0x7f124dffb700 (LWP 2880)): #0 0x00007f129c3ee5d3 in select () at ../sysdeps/unix/syscall-template.S:84 #1 0x0000000001044936 in JSONRPC::CTCPServer::Process() () #2 0x0000000001d2ac6f in CThread::Action() () #3 0x0000000001d2af2f in CThread::staticThread(void*) () #4 0x00007f12a26866ba in start_thread (arg=0x7f124dffb700) at pthread_create.c:333 #5 0x00007f129c3f841d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 16 (Thread 0x7f124e7fc700 (LWP 2879)): #0 0x00007f129c3ee5d3 in select () at ../sysdeps/unix/syscall-template.S:84 #1 0x00000000010429bc in SOCKETS::CSocketListener::Listen(int) () #2 0x000000000103689e in EVENTSERVER::CEventServer::Run() () #3 0x0000000001036b48 in EVENTSERVER::CEventServer::Process() () #4 0x0000000001d2ac6f in CThread::Action() () #5 0x0000000001d2af2f in CThread::staticThread(void*) () #6 0x00007f12a26866ba in start_thread (arg=0x7f124e7fc700) at pthread_create.c:333 #7 0x00007f129c3f841d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Update: Looks like the issue is related to TVDB.com API Changes and AddOn Update. Going to post this thread regardless and update when fix is live, but nothing is wrong with my installation it appears. See --> https://forum.kodi.tv/showthread.php?tid=345935

I have been trying to launch Kodi on my Raspbian Buster. I did a fresh install of Raspbian Buster Lite and then installed Kodi.

sudo apt install kodi

As I don't need the GUI I think I just have to manually install a few dependencies for running Kodi as the only UI required app. I followed the instruction here https://www.raspberrypi.org/forums/viewtopic.php?t=192499 with a small adjustment to the location of the kodi.service to put it in /etc instead of /lib as they mention here. Tried all following ways to launch Kodi.

kodi
kodi-standalone
sudo systemctl start kodi

All of them fail with same error. As people are saying there is no xserver required I anyhow tried installing xserver, but it still gives me same error when xserver is installed. Is there any expert out there who knows how to solve or point me in right direction? On my previous Raspbian Stretch all was working fine, but don't recall if I did anything special 2 years ago, to make this work.

$ cat kodi_crashlog-20190715_212803.log
############## Kodi CRASH LOG ###############

################ SYSTEM INFO ################
 Date: Mon 15 Jul 21:28:03 BST 2019
 Kodi Options:
 Arch: armv7l
 Kernel: Linux 4.19.57-v7+ #1244 SMP Thu Jul 4 18:45:25 BST 2019
 Release: Raspbian GNU/Linux 10 (buster)
############## END SYSTEM INFO ##############

############### STACK TRACE #################
############# END STACK TRACE ###############

################# LOG FILE ##################

21:27:33.630 T:1831238192  NOTICE: special://profile/ is mapped to: special://masterprofile/
21:27:33.631 T:1831238192  NOTICE: -----------------------------------------------------------------------
21:27:33.631 T:1831238192  NOTICE: Starting Kodi from Debian (17.6 Debian package version: 2:17.6+dfsg1-4+b1). Platform: Linux ARM 32-bit
21:27:33.631 T:1831238192  NOTICE: Using Release Kodi from Debian x32 build
21:27:33.631 T:1831238192  NOTICE: Kodi from Debian compiled from 2:17.6+dfsg1-4+b1 by GCC 8.2.0 for Linux ARM 32-bit version 4.18.20 (266772)
21:27:33.631 T:1831238192  NOTICE: Running on Raspbian GNU/Linux 10 (buster), kernel: Linux ARM 32-bit version 4.19.57-v7+
21:27:33.631 T:1831238192  NOTICE: FFmpeg version/source: 4.1.3-1+rpt1
21:27:33.631 T:1831238192  NOTICE: Host CPU: ARMv7 Processor rev 4 (v7l), 4 cores available
21:27:33.631 T:1831238192  NOTICE: ARM Features: Neon disabled
21:27:33.631 T:1831238192  NOTICE: special://xbmc/ is mapped to: /usr/share/kodi
21:27:33.631 T:1831238192  NOTICE: special://xbmcbin/ is mapped to: /usr/lib/arm-linux-gnueabihf/kodi
21:27:33.631 T:1831238192  NOTICE: special://xbmcbinaddons/ is mapped to: /usr/lib/arm-linux-gnueabihf/kodi/addons
21:27:33.631 T:1831238192  NOTICE: special://masterprofile/ is mapped to: /home/pi/.kodi/userdata
21:27:33.631 T:1831238192  NOTICE: special://envhome/ is mapped to: /home/pi
21:27:33.631 T:1831238192  NOTICE: special://home/ is mapped to: /home/pi/.kodi
21:27:33.631 T:1831238192  NOTICE: special://temp/ is mapped to: /home/pi/.kodi/temp
21:27:33.631 T:1831238192  NOTICE: special://logpath/ is mapped to: /home/pi/.kodi/temp
21:27:33.631 T:1831238192  NOTICE: The executable running is: /usr/lib/arm-linux-gnueabihf/kodi/kodi.bin
21:27:33.631 T:1831238192  NOTICE: Local hostname: raspberrypi
21:27:33.631 T:1831238192  NOTICE: Log File is located: /home/pi/.kodi/temp//kodi.log
21:27:33.631 T:1831238192  NOTICE: -----------------------------------------------------------------------
21:27:33.637 T:1831238192   ERROR: DBus: Error org.freedesktop.DBus.Error.ServiceUnknown - The name org.freedesktop.UPower was not provided by any .service files
21:27:33.701 T:1831238192  NOTICE: load settings...
21:27:33.743 T:1831238192   ERROR: PulseAudio: Failed to connect context
21:27:33.743 T:1831238192  NOTICE: PulseAudio might not be running. Context was not created.
21:27:33.777 T:1831238192  NOTICE: Found 1 Lists of Devices
21:27:33.777 T:1831238192  NOTICE: Enumerated ALSA devices:
21:27:33.777 T:1831238192  NOTICE:     Device 1
21:27:33.778 T:1831238192  NOTICE:         m_deviceName      : @
21:27:33.778 T:1831238192  NOTICE:         m_displayName     : Default (bcm2835 ALSA bcm2835 ALSA)
21:27:33.778 T:1831238192  NOTICE:         m_displayNameExtra:
21:27:33.778 T:1831238192  NOTICE:         m_deviceType      : AE_DEVTYPE_PCM
21:27:33.778 T:1831238192  NOTICE:         m_channels        : FL,FR
21:27:33.778 T:1831238192  NOTICE:         m_sampleRates     : 8000,11025,16000,22050,32000,44100,48000,64000,88200,96000,176400,192000
21:27:33.778 T:1831238192  NOTICE:         m_dataFormats     : AE_FMT_S16NE,AE_FMT_S16LE,AE_FMT_U8
21:27:33.778 T:1831238192  NOTICE:         m_streamTypes     : No passthrough capabilities
21:27:33.788 T:1831238192  NOTICE: No settings file to load (special://xbmc/system/advancedsettings.xml)
21:27:33.788 T:1831238192  NOTICE: No settings file to load (special://masterprofile/advancedsettings.xml)
21:27:33.788 T:1831238192  NOTICE: Default Video Player: VideoPlayer
21:27:33.788 T:1831238192  NOTICE: Default Audio Player: paplayer
21:27:33.788 T:1831238192  NOTICE: Disabled debug logging due to GUI setting. Level 0.
21:27:33.788 T:1831238192  NOTICE: Log level changed to "LOG_LEVEL_NORMAL"
21:27:33.789 T:1831238192  NOTICE: Loading player core factory settings from special://xbmc/system/playercorefactory.xml.
21:27:33.789 T:1831238192  NOTICE: Loaded playercorefactory configuration
21:27:33.789 T:1831238192  NOTICE: Loading player core factory settings from special://masterprofile/playercorefactory.xml.
21:27:33.789 T:1831238192  NOTICE: special://masterprofile/playercorefactory.xml does not exist. Skipping.
21:27:33.806 T:1831238192  NOTICE: Running database version Addons27
21:27:33.856 T:1831238192  NOTICE: ADDONS: Using repository repository.xbmc.org
21:27:33.905 T:1831238192   ERROR: X11 Error: No Display found
21:27:33.905 T:1831238192   FATAL: CApplication::Create: Unable to init windowing system


############### END LOG FILE ################

############ END Kodi CRASH LOG #############

Got an HTPC running Mint. $ cat /etc/os-release NAME="Linux Mint" VERSION="19 (Tara)" ID=linuxmint ID_LIKE=ubuntu It has a TV connected via HDMI. Prior to the update if I rebooted the machine via ssh it would start fine while the TV was off. But I did an upgrade: sudo apt-get update && sudo apt-get dist-upgrade now it won't boot unless the attached TV is on. This is why I am always reluctant to update Linux, things tend to get broken. Just so it's clear, this isn't headless, it's just headless some of the time (when the TV is off). How do I tell it to boot whether it has a TV attached or not? This was working until the update. So something got updated and broke it. The 2 answers here were not the fix for it. I suspect it has something to do with Grub or Wayland but I don't want to mess around with that unless I am positive I'm doing the right thing. ### Specifics - MSI Cubi-017BUS Intel Broadwell U PCH-LP Black Mini / Booksize Barebone System - Tried this as well - Mint not detecting HDMI Monitor

My rPI3 runs very slowly with Kodi on it. I installed Kodi in March 2018 through LibreELEC. Kodi is at its latest version. Any suggestion? 1. The bootup time is fairly fast; it boots up in less than a minute which is a pleasant time for me. 2. Kodi interface is unbearable instead. Whenever I click any option it honestly takes 1 minute to load to the next page. If I need to browse for movies (I use the Midian add-on), every time I need to change a page it takes at least minute. If I select a certain movie to play the Raspberry Pi3 can take from 5 to 10 minutes, but lately it has failed to load it and freezes the complete system.  In the end for this reason I stopped using it. 3. The micro SD card I use is 16 GB Kingston, (SDC4 / 16 GB, 4 years old I suppose). 4. My source power is the official Raspberry power supply bought in March 2018.