2022-06-26, 23:29
I'm trying to migrate my kodi to a new Intel NUC 11 but kodi keeps core dumping during startup when trying to run the stand-alone version as systemd service.
Starting kodi as a program after switching to the graphical.target does work but I need it to work without keyboard and mouse :-)
I'm assuming there is some configuration/permission error somewhere or some hardware related bug but I can't find it. If it was hardware I would have expected X to not work properly at all.
When it tries to start I can see X starting (the X mouse cursor appears) and then it blinks a few times as it crashes and gets auto restarted by systemd.
The old media player is running FC35 and is running just fine, but it has been constantly upgraded since Fedora 24 so it might just be working due to legacy settings.
I installed the same packages as are on the working kodi machine.
Initially the NUC was installed as a 'gnome desktop' but that was giving the same crash, I then reinstalled it as a 'minimal install' and tried to duplicate what was installed on the old kodi. (base-x and LXDE Desktop for gui)
I put logs on pastebin in a folder. (Sys info, crash dump(same contents as kodi.log + kernel info) and syslog entries from the crash.)
gdb does not seem to want to make a crash dump of kodi-standalone.
The new media player is running Fedora 36
Kodi is installed from rpmfusion -> kodi-19.4-1.fc36.x86_64
Currently running Kernel 5.18.6-200.fc36.x86_64 #1 SMP PREEMPT_DYNAMIC Wed Jun 22 13:46:18 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux but new ones come out almost daily.
Intel NUC nuc11tnkv7
CPU is a 11th Gen Intel® Core™ i7-1165G7
GPU is the on board 'Intel® Iris® Xe graphics or Intel® UHD graphics'
No configuration has been done on Kodi. Everything is default.
Default runlevel is multi-user so it does not try to start X twice.
systemd file:
Starting kodi as a program after switching to the graphical.target does work but I need it to work without keyboard and mouse :-)
I'm assuming there is some configuration/permission error somewhere or some hardware related bug but I can't find it. If it was hardware I would have expected X to not work properly at all.
When it tries to start I can see X starting (the X mouse cursor appears) and then it blinks a few times as it crashes and gets auto restarted by systemd.
The old media player is running FC35 and is running just fine, but it has been constantly upgraded since Fedora 24 so it might just be working due to legacy settings.
I installed the same packages as are on the working kodi machine.
Initially the NUC was installed as a 'gnome desktop' but that was giving the same crash, I then reinstalled it as a 'minimal install' and tried to duplicate what was installed on the old kodi. (base-x and LXDE Desktop for gui)
I put logs on pastebin in a folder. (Sys info, crash dump(same contents as kodi.log + kernel info) and syslog entries from the crash.)
gdb does not seem to want to make a crash dump of kodi-standalone.
The new media player is running Fedora 36
Kodi is installed from rpmfusion -> kodi-19.4-1.fc36.x86_64
Currently running Kernel 5.18.6-200.fc36.x86_64 #1 SMP PREEMPT_DYNAMIC Wed Jun 22 13:46:18 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux but new ones come out almost daily.
Intel NUC nuc11tnkv7
CPU is a 11th Gen Intel® Core™ i7-1165G7
GPU is the on board 'Intel® Iris® Xe graphics or Intel® UHD graphics'
No configuration has been done on Kodi. Everything is default.
Default runlevel is multi-user so it does not try to start X twice.
systemd file:
Quote:# cat /etc/systemd/system/kodi.service
[Unit]
Description = kodi-standalone using xinit
After = systemd-user-sessions.service
After = bluetooth.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