Sad face after navigating movie cast members since 21.1

Select a movie in the library, navigate to cast, pick a cast member to bring up other movies with that person, select another movie, press back and I get a sad face every time. Happens on a V and a 4K+. Library and movies on a NAS via NFS with kernal auto mount if that makes a difference.

Which skin are you using?

OSMC default skin.

Tried to replicate here, not happening. Suggest you upload debug enabled logs.

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:

Also had this happened but while perusing the Plot view on the movie details. It’s not always reproducible. I’ve had the same sad face, which I assume it’s a crash, happen more frequently after stopping playing a file.
I don’t think this is related to update to 21.1 because the crashes when stopping a file happened before the update. Will try to get a log.

Different problem to me then, as I’ve been running OSMC for quite a few years and this has only just started for me. Now happens every time. I’ll get on with supplying logs.

https://paste.osmc.tv/hoqixiwizu

Just for the records, kodi log ends with multiple resetscrollclear messages and syslog has
pam_unix(sudo:session): session closed for user osmc Aug 29 19:01:13 livingveroplus mediacenter[2778]: /usr/bin/mediacenter: line 205: 2936 Bus error

Apologies, that goes completely over my head. Do I need to be doing anything else please, or are you saying the provided log is no good? Thank you.

All good, this was not meant for your “head” it was just a summary for any one who might look at this thread

I think it could be database corruption or corrupted artwork.

I have a PC with running 21.1 and Esturary pointed at the same database and library, and I’ev discovered that this doesn’t exhibit the sympton. I’ll try switching the Vero to Esturary and see if the problem goes away too.

If it is DB related, and pointers on what to do about it/how to identify the problem? DB was auto-upraded from v20.

Thank you.

I swapped the Vero V to Estuary and it then works OK, so it appears to only effect the OSMC skin. I definitely didn’t have this with the 20 database so I’ll rename the current ones and let the Vero V re-convert the 20 DB. Maybe that will fix it?

It’s possible.

I’ve ended up complete deleting the library database from the NAS, letting the Vero V re-create it with 21.1, and the repopulated it with a full re-scan. I think that can safely rule out a database corruption. No dice. It’s still doing exactly the same thing. Any suggestions on how to progress please?

Also to note: I can navigate directly to the ‘other’ move and back out with no problem, including looking at the suspect cast member, which I think also lets out corrupt artwork. If however I click through the cast member, select the ‘original’ movie and backup I get sad face again. i.e. it happens in both directions, but both movies appear fine in their own right. I accept you can’t reproduce it, but it certainly looks like a programatic problem to me. Thank you.

Can you leave it on Estuary for a bit and confirm that it does not re-occur at all?

Wilco. I have 3 Veros in regular use, all of which consitently display the symptom. I’ve switched them all from OSMC Skin to Estuary. If the problem reoccurs then I’ll update here.

I had the same issue with my Vero 4K+
Because I am not a home I cannot reproduce it or create logs. Will try this weekend.
I do remember that when I turned logging on I noticed that the CPU Kodi number was around 140% and went up way above 200% when I was quickly running through my list of movies.