[Milhouse]

I haven't been following daily updates recently - 3D ISO wasn't working for a while. Today I updated to current #0602. My old problems 3D ISO playback and 1080i video stuttering are solved

I have new problem. Don't know if this was discussed earlier but on the upgrade Kodi updated my local movie database. Some new movies were not scanned into database at all. I try to rename files, select both scrapers The Movie Database and Universal Movie Scraper without any success. If I select Info in file browser I'm getting pup up with "Loading movie details" and "No information found" and file name. I used to get manual entry box where I could adjust title. All I can do now is click OK and back for file list. Those movies don't show up in movie list. The same applies to #0601.

Any ideas?

Debug log?  

 Local movie database issue.
Log file: http://ix.io/1cd8

Just tested it again with tonight #0603. The same issue. I checked it on 2 separate installations. Once the database from the past April goes through new Kodi version it gets upgraded with no way back. I tried to roll back to April release, delete the storage location and recreate the database. The same thing. Around 20% of the movies does not get recognized anymore. I made quick fresh SD install with LibreELEC-RPi2.arm-8.2.5.img.gz image and applied latest #0602 build. Works OK with all recognized.

It's the old upgraded database that gets corrupted with some titles locked out. I don't really want to go through recreation of everything from scratch. I have multiple installations.

Update:
First log was from folder scan.
Second log from trying to display "Info"
http://ix.io/1ce4

I'm not sure what the fundamental issue is - can you provide details of a movie that isn't recognised, maybe it's an odd naming convention?

Is this failure to recognise a movie happening during a library scan (adding a new movie), or during a database upgrade (as happened, possibly coincidentally, in #0602)?

Build #0602 included the first video database upgrade (v110) of this year, but if you're saying the problem is present in a build from April then I guess we can discount the db upgrade. The reason I asked for your logs was because I suspected a database error, but that looks OK - no errors.

Without knowing entirely what the problem is, it might be best if you can identify the first build with the problem.