Bug#914319: kodi: stale process on kodi crash
Package: kodi
Version: 2:17.6+dfsg1-4
Severity: important
Thank you for continuing to maintain Kodi. Hopefully, now that I've
switched to the Debian one, I'll have some time to help.
Meanwhile, here's something I noticed:
rrs@lenovo:~$ ps aux | grep kodi
root 25312 0.0 0.1 75284 13316 ? S 10:41 0:00 /usr/lib/x86_64-linux-gnu/sddm/sddm-helper --socket /tmp/sddm-auth7a7c9e75-6afb-4ff5-969a-0aef94e4f40d --id 1 --start kodi-standalone --user rrs --autologin
rrs 25315 0.0 0.0 2372 760 ? S 10:41 0:00 /bin/sh /usr/bin/kodi-standalone
rrs 25354 0.0 0.0 5832 472 ? Ss 10:41 0:00 /usr/bin/ssh-agent kodi-standalone
rrs 25358 0.0 0.0 2372 700 ? S 10:41 0:00 /bin/sh /usr/bin/kodi --standalone
rrs 25360 11.3 3.9 2949992 318956 ? SLl 10:41 3:18 /usr/lib/x86_64-linux-gnu/kodi/kodi.bin --standalone
rrs 28485 0.0 0.0 4764 940 pts/0 S+ 11:10 0:00 grep --color=auto kodi
11:10 ♒♒♒ ☺ 😄
Nov 22 10:40:54 lenovo sddm[24877]: Message received from greeter: Connect
Nov 22 10:40:54 lenovo sddm-greeter[25128]: Loading file:///usr/share/sddm/themes/debian-theme/Main.qml...
Nov 22 10:40:54 lenovo sddm-greeter[25128]: Adding view for "eDP-1" QRect(0,0 1920x1080)
Nov 22 10:40:54 lenovo sddm-greeter[25128]: Loading file:///usr/share/sddm/themes/debian-theme/Main.qml...
Nov 22 10:40:54 lenovo sddm-greeter[25128]: Adding view for "HDMI-1" QRect(1920,0 1920x1080)
Nov 22 10:40:54 lenovo sddm-greeter[25128]: Message received from daemon: Capabilities
Nov 22 10:40:54 lenovo sddm-greeter[25128]: Message received from daemon: HostName
Nov 22 10:41:04 lenovo kernel: kodi.bin[25043]: segfault at 0 ip 0000000000000000 sp 00007ffd1c3fd308 error 14 in kodi.bin[557762719000+43b000]
Nov 22 10:41:04 lenovo kernel: Code: Bad RIP value.
Nov 22 10:41:04 lenovo systemd[1]: Started Process Core Dump (PID 25157/UID 0).
Nov 22 10:41:04 lenovo kernel: kodi.bin[24958]: segfault at 0 ip 0000000000000000 sp 00007ffd2e5b0578 error 14 in kodi.bin[55aaf6870000+43b000]
Nov 22 10:41:04 lenovo kernel: Code: Bad RIP value.
Nov 22 10:41:04 lenovo systemd[1]: Started Process Core Dump (PID 25159/UID 0).
Nov 22 10:41:07 lenovo systemd-coredump[25158]: Process 25043 (kodi.bin) of user 1000 dumped core.
Stack trace of thread 25043:
#0 0x0000000000000000 n/a (n/a)
Nov 22 10:41:07 lenovo systemd-coredump[25160]: Process 24958 (kodi.bin) of user 1000 dumped core.
Stack trace of thread 24958:
#0 0x0000000000000000 n/a (n/a)
Nov 22 10:41:10 lenovo systemd-logind[24616]: Removed session 1.
Nov 22 10:41:25 lenovo polkitd(authority=local)[11874]: Registered Authentication Agent for unix-process:25280:144345 (system bus name :1.375 [/usr
Nov 22 10:41:26 lenovo polkitd(authority=local)[11874]: Operator of unix-process:25280:144345 successfully authenticated as unix-user:rrs to gain O
Nov 22 10:41:26 lenovo sddm[24877]: Signal received: SIGTERM
Nov 22 10:41:26 lenovo systemd[1]: Stopping Simple Desktop Display Manager...
Nov 22 10:41:26 lenovo sddm-greeter[25128]: The X11 connection broke (error 1). Did the X11 server die?
Nov 22 10:41:26 lenovo sddm[24877]: Greeter stopping...
Nov 22 10:41:26 lenovo sddm[24877]: Socket server stopping...
Nov 22 10:41:26 lenovo sddm[24877]: Socket server stopped.
Nov 22 10:41:26 lenovo sddm[24877]: Display server stopping...
Nov 22 10:41:26 lenovo sddm-helper[25113]: [PAM] Closing session
Nov 22 10:41:26 lenovo sddm-helper[25113]: pam_unix(sddm-greeter:session): session closed for user sddm
Nov 22 10:41:26 lenovo sddm-helper[25113]: [PAM] Ended.
Nov 22 10:41:26 lenovo systemd-logind[24616]: Session 7 logged out. Waiting for processes to exit.
Nov 22 10:41:26 lenovo systemd-logind[24616]: Removed session 7.
Nov 22 10:41:26 lenovo systemd[1]: user-runtime-dir@129.service: Unit not needed anymore. Stopping.
Nov 22 10:41:26 lenovo systemd[1]: Stopping User Manager for UID 129...
The recommendation been made is to not use kodi through any systemd
service script. Instead, users are recommended to setup an autologin
mechanism with a window manager of their choice, and then autostart
kodi. This works fine in an ideal world.
But, in cases where kodi crashes, it leaves stray processes behind. Then
a respawn of new kodi instance ends up having conflicts because part
process from the previous invocation is still occupying services, like
8080 and 9090.
Why are you recommending against the systemd service approach ? IIRC,
when I had set it up on my RPi, the systemd slice would reliably clean
all leftover processes when there was a crash.
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (900, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (100, 'experimental'), (1, 'experimental-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_IN:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages kodi depends on:
ii kodi-bin 2:17.6+dfsg1-4
ii kodi-data 2:17.6+dfsg1-4
Versions of packages kodi recommends:
ii kodi-repository-kodi [kodi-repository] 2:17.6+dfsg1-4
pn kodi-visualization-spectrum <none>
kodi suggests no packages.
-- no debconf information
Reply to: