KODI crashes on latest osmc for raspi4

Help and Support
1

Since last update Kodi started to crash and TV shows “no hdmi input” error.
When checking via ssh mediacenter status, I see a few errors or warnings, pasted below.
I am using very latest img of osmc for raspi4 with latest apt update / apt full-upgrade, installed yesterday.
When such issue happens, I stop mediacenter and restart, sometimes it helps but sometimes I have to reboot whole rpi4
I also set up debugging logs, which I paste when available

status of mediacenter service:
osmc@osmc:~$ sudo systemctl status mediacenter

  • mediacenter.service - media center application
    Loaded: loaded (/lib/systemd/system/mediacenter.service; enabled; vendor preset: enabled)
    Active: active (running) since Fri 2021-08-20 17:19:04 CEST; 1min 35s ago
    Main PID: 388 (mediacenter)
    Tasks: 54 (limit: 3932)
    CGroup: /system.slice/mediacenter.service
    |-388 /bin/bash /usr/bin/mediacenter
    |-462 sudo -u osmc LIRC_SOCKET_PATH=/var/run/lirc/lircd /usr/lib/kodi/kodi.bin --standalone -fs
    `-475 /usr/lib/kodi/kodi.bin --standalone -fs

Aug 20 17:19:44 osmc mediacenter[388]: Traceback (most recent call last):
Aug 20 17:19:44 osmc mediacenter[388]: File “/usr/lib/python3.7/importlib/resources.py”, line 190, in path
Aug 20 17:19:44 osmc mediacenter[388]: NameError: name ‘FileNotFoundError’ is not defined
Aug 20 17:19:45 osmc sudo[569]: osmc : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/rm /var/tmp/osmc.settings.sockfile
Aug 20 17:19:45 osmc sudo[569]: pam_unix(sudo:session): session opened for user root by (uid=0)
Aug 20 17:19:45 osmc sudo[569]: pam_unix(sudo:session): session closed for user root
Aug 20 17:19:46 osmc sudo[577]: osmc : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/mv /var/tmp/config-user.txt /boot/config-user.txt
Aug 20 17:19:46 osmc sudo[577]: pam_unix(sudo:session): session opened for user root by (uid=0)
Aug 20 17:19:46 osmc mediacenter[388]: mv: failed to preserve ownership for ‘/boot/config-user.txt’: Operation not permitted
Aug 20 17:19:46 osmc sudo[577]: pam_unix(sudo:session): session closed for user root

Loaded: loaded (/lib/systemd/system/mediacenter.service; enabled; vendor preset: enabled)
Active: active (running) since Fri 2021-08-20 17:23:44 CEST; 4s ago
Main PID: 740 (mediacenter)
Tasks: 45 (limit: 3932)
CGroup: /system.slice/mediacenter.service
|-740 /bin/bash /usr/bin/mediacenter
|-755 sudo -u osmc LIRC_SOCKET_PATH=/var/run/lirc/lircd /usr/lib/kodi/kodi.bin --standalone -fs
`-756 /usr/lib/kodi/kodi.bin --standalone -fs

Aug 20 17:23:45 osmc mediacenter[740]: Mesa warning: failed to remap glCompileShaderIncludeARB
Aug 20 17:23:45 osmc mediacenter[740]: Mesa warning: failed to remap glIsNamedStringARB
Aug 20 17:23:45 osmc mediacenter[740]: Mesa warning: failed to remap glGetNamedStringARB
Aug 20 17:23:45 osmc mediacenter[740]: Mesa warning: failed to remap glGetNamedStringivARB
Aug 20 17:23:45 osmc mediacenter[740]: Mesa warning: failed to remap glEGLImageTargetTexStorageEXT
Aug 20 17:23:45 osmc mediacenter[740]: Mesa warning: failed to remap glEGLImageTargetTextureStorageEXT
Aug 20 17:23:45 osmc mediacenter[740]: Mesa warning: failed to remap glCopyImageSubDataNV
Aug 20 17:23:45 osmc mediacenter[740]: Mesa warning: failed to remap glViewportSwizzleNV
Aug 20 17:23:45 osmc mediacenter[740]: Mesa warning: failed to remap glAlphaToCoverageDitherControlNV
Aug 20 17:23:45 osmc mediacenter[740]: Mesa warning: failed to remap glInternalBufferSubDataCopyMESA
Aug 20 17:23:45 osmc mediacenter[740]: Mesa warning: failed to remap glAlphaToCoverageDitherControlNV
Aug 20 17:23:45 osmc mediacenter[740]: Mesa warning: failed to remap glInternalBufferSubDataCopyMESA
Aug 20 17:24:02 osmc sudo[832]: osmc : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/mv /var/tmp/config-user.txt /boot/config-user.txt
Aug 20 17:24:02 osmc sudo[832]: pam_unix(sudo:session): session opened for user root by (uid=0)
Aug 20 17:24:02 osmc mediacenter[740]: mv: failed to preserve ownership for ‘/boot/config-user.txt’: Operation not permitted
Aug 20 17:24:02 osmc sudo[832]: pam_unix(sudo:session): session closed for user root
Aug 20 17:24:03 osmc mediacenter[740]: Exception ignored in: <generator object path at 0xd178d870>
Aug 20 17:24:03 osmc mediacenter[740]: Traceback (most recent call last):
Aug 20 17:24:03 osmc mediacenter[740]: File “/usr/lib/python3.7/importlib/resources.py”, line 190, in path
Aug 20 17:24:03 osmc mediacenter[740]: NameError: name ‘FileNotFoundError’ is not defined

2

You should paste full logs, not snippets.

3

Debug logs pasted at
https://paste.osmc.tv/avusexeziq

Config detail:
rpi4 4GB
osmc 2021.08-1, installed 2 days ago 19.8. from image file to clean card, then apt update, apt full-upgrade
TV Samsung QE55QN95A

The behavior is like this:

  • start raspi4
  • osmc/kodi starts to Estuary GUI
  • after minute or two, the screen gets black and TV reports no HDMI signal (I executed no add-on yet)
  • logging to osmc via ssh
  • mediacenter is running, but with messages as pasted below
  • sudo systemctl stop mediacenter
  • sudo systemctl start mediacenter
  • Estuary shows up on TV again
    I can’t say exactly when this started to happen, but for sure this issues didn’t happened last week and before.
    I haven’t done any sw updates on my TV

Just for time correlation, between debug logs and event, here is mediacenter service status at TV goes black and then after mediacenter restart.

osmc@osmc:~$ sudo systemctl status mediacenter

  • mediacenter.service - media center application
    Loaded: loaded (/lib/systemd/system/mediacenter.service; enabled; vendor preset: enabled)
    Active: active (running) since Sat 2021-08-21 08:41:39 CEST; 2min 9s ago
    Main PID: 402 (mediacenter)
    Tasks: 53 (limit: 3932)
    CGroup: /system.slice/mediacenter.service
    |-402 /bin/bash /usr/bin/mediacenter
    |-456 sudo -u osmc LIRC_SOCKET_PATH=/var/run/lirc/lircd /usr/lib/kodi/kodi.bin --standalone -fs
    `-462 /usr/lib/kodi/kodi.bin --standalone -fs

Aug 21 08:41:42 osmc mediacenter[402]: Mesa warning: failed to remap glAlphaToCoverageDitherControlNV
Aug 21 08:41:42 osmc mediacenter[402]: Mesa warning: failed to remap glInternalBufferSubDataCopyMESA
Aug 21 08:42:41 osmc mediacenter[402]: Exception ignored in: <generator object path at 0xd033ab70>
Aug 21 08:42:41 osmc mediacenter[402]: Traceback (most recent call last):
Aug 21 08:42:41 osmc mediacenter[402]: File “/usr/lib/python3.7/importlib/resources.py”, line 190, in path
Aug 21 08:42:41 osmc mediacenter[402]: NameError: name ‘FileNotFoundError’ is not defined
Aug 21 08:42:42 osmc sudo[580]: osmc : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/mv /var/tmp/config-user.txt /boot/config-user.txt
Aug 21 08:42:42 osmc sudo[580]: pam_unix(sudo:session): session opened for user root by (uid=0)
Aug 21 08:42:42 osmc mediacenter[402]: mv: failed to preserve ownership for ‘/boot/config-user.txt’: Operation not permitted
Aug 21 08:42:42 osmc sudo[580]: pam_unix(sudo:session): session closed for user root

osmc@osmc:~$

osmc@osmc:~/.kodi$ sudo systemctl status mediacenter

  • mediacenter.service - media center application
    Loaded: loaded (/lib/systemd/system/mediacenter.service; enabled; vendor preset: enabled)
    Active: failed (Result: timeout) since Sat 2021-08-21 08:45:09 CEST; 2min 48s ago
    Process: 402 ExecStart=/usr/bin/mediacenter (code=killed, signal=KILL)
    Process: 725 ExecStopPost=/usr/bin/mediacenter stop (code=exited, status=0/SUCCESS)
    Main PID: 402 (code=killed, signal=KILL)
    Tasks: 0 (limit: 3932)
    CGroup: /system.slice/mediacenter.service

Aug 21 08:42:42 osmc mediacenter[402]: mv: failed to preserve ownership for ‘/boot/config-user.txt’: Operation not permitted
Aug 21 08:42:42 osmc sudo[580]: pam_unix(sudo:session): session closed for user root
Aug 21 08:44:48 osmc systemd[1]: Stopping media center application…
Aug 21 08:45:09 osmc systemd[1]: mediacenter.service: State ‘stop-sigterm’ timed out. Killing.
Aug 21 08:45:09 osmc systemd[1]: mediacenter.service: Killing process 402 (mediacenter) with signal SIGKILL.
Aug 21 08:45:09 osmc systemd[1]: mediacenter.service: Killing process 456 (sudo) with signal SIGKILL.
Aug 21 08:45:09 osmc systemd[1]: mediacenter.service: Killing process 462 (kodi.bin) with signal SIGKILL.
Aug 21 08:45:09 osmc systemd[1]: mediacenter.service: Main process exited, code=killed, status=9/KILL
Aug 21 08:45:09 osmc systemd[1]: mediacenter.service: Failed with result ‘timeout’.
Aug 21 08:45:09 osmc systemd[1]: Stopped media center application.

osmc@osmc:~/.kodi$ sudo systemctl start mediacenter

osmc@osmc:~/.kodi$ sudo systemctl status mediacenter

  • mediacenter.service - media center application
    Loaded: loaded (/lib/systemd/system/mediacenter.service; enabled; vendor preset: enabled)
    Active: active (running) since Sat 2021-08-21 08:48:04 CEST; 4min 21s ago
    Main PID: 771 (mediacenter)
    Tasks: 53 (limit: 3932)
    CGroup: /system.slice/mediacenter.service
    |-771 /bin/bash /usr/bin/mediacenter
    |-786 sudo -u osmc LIRC_SOCKET_PATH=/var/run/lirc/lircd /usr/lib/kodi/kodi.bin --standalone -fs
    `-787 /usr/lib/kodi/kodi.bin --standalone -fs

Aug 21 08:48:22 osmc sudo[857]: pam_unix(sudo:session): session opened for user root by (uid=0)
Aug 21 08:48:22 osmc sudo[857]: pam_unix(sudo:session): session closed for user root
Aug 21 08:48:22 osmc sudo[865]: osmc : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/mv /var/tmp/config-user.txt /boot/config-user.txt
Aug 21 08:48:22 osmc sudo[865]: pam_unix(sudo:session): session opened for user root by (uid=0)
Aug 21 08:48:22 osmc mediacenter[771]: mv: failed to preserve ownership for ‘/boot/config-user.txt’: Operation not permitted
Aug 21 08:48:22 osmc sudo[865]: pam_unix(sudo:session): session closed for user root
Aug 21 08:48:23 osmc mediacenter[771]: Exception ignored in: <generator object path at 0xd20b84b0>
Aug 21 08:48:23 osmc mediacenter[771]: Traceback (most recent call last):
Aug 21 08:48:23 osmc mediacenter[771]: File “/usr/lib/python3.7/importlib/resources.py”, line 190, in path
Aug 21 08:48:23 osmc mediacenter[771]: NameError: name ‘FileNotFoundError’ is not defined

Hopefully all this helps.

Thank you.

4

To get a better understanding of the problem you are experiencing we need more information from you. The best way to get this information is for you to upload logs that demonstrate your problem. You can learn more about how to submit a useful support request here.

Depending on the used skin you have to set the settings-level to standard or higher, in summary:

  • enable debug logging at settings->system->logging

  • reboot the OSMC device twice(!)

  • reproduce the issue

  • upload the log set (all configs and logs!) either using the Log Uploader method within the My OSMC menu in the GUI or the ssh method invoking command grab-logs -A

  • publish the provided URL from the log set upload, here

Thanks for your understanding. We hope that we can help you get up and running again shortly.

OSMC skin screenshot:

image
image957×540 224 KB

5

sorry, but the log I pasted at the beginning of my post isn’t OK? These logs are taken the same way as you suggested in your post.

This is the log link I pasted also in previous post
Debug logs pasted at
https://paste.osmc.tv/avusexeziq

6

Didn’t see that on my phone

7

“paste.osmc.tv” slash “avusexeziq”

OR this link
the debug log

trying other formats :slight_smile:

8

Reduce your GUI resolution. Also do you have active cooling of the Pi4?

We recommend people with 4K TV’s set their user interface (UI) to 1080p. Kodi’s UI is not optimized for 4K yet and this can put unnecessary demands on your device and can lead to a suboptimal picture quality, as well as potentially cause other issues.

The settings we recommend are as follows…

Settings>System>Display>Resolution> 1920x1080p
Settings>System>Display>Whitelist> (empty) *
Settings>Player>Videos>Adjust display refresh rate> On start/stop

Some televisions may also need, or benefit from, the following being set…

System>Display>Force 4:2:2 colour subsampling> (enable)

With the above settings your UI will be output in Full HD and your 4K content will be output in 4K. *Information regarding the whitelist can be found here. If you have any doubt, feel free to upload some logs so we can verify that your settings are indeed correct.

9

The thing is, that I am using osmc on rpi4 since early betas in 4k resolution and this problem started just few days ago.
If there is possibility to go back to latest beta, I would go back to try.

I will try your advice to see if it helps on another issues I have (and also other users) with live TV playback, where kodi crashes to “:frowning: screen” or freezes and this issue is there since first betas.

10

I can’t find System>Display>Force 4:2:2 colour subsampling even in Exper settings mode

11

That one is most likely Vero specific

12

I have the same problem since today; yesterday it was working fine. I didn’t reboot my RasPi or changed anything, I just restarted the mediacenter service as Kodi was hanging :frowning:

Kodi doesn’t start anymore (even after reboot) and I have these Mesa errors in the journal.

13

Please post logs