luisv

Members
  • Posts

    195
  • Joined

  • Last visited

Posts posted by luisv

  1. Since you... "had a devil of a time deciding whether to simply update to the 4.19 kernel now..." 6.6.6 was the version number that came to mind?   🤣😎

     

    As an FYI, I was able to upgrade both of my servers without the need for any holy water, crosses, chanting or other types of rituals.  

    • Like 5
    • Upvote 1
  2. 16 minutes ago, cybrnook said:

    I will go to the movie store and get Sicario this weekend, as posted before. I know this triggers the crash, and was also the same movie that caused @luisv 's crash as well.

     

    @Djoss if you have a movie rental store near you, you likely could reproduce the same, might be easier to collect logs. If not, let me know what i need to gather at the time it's happening, specifically.

     

    If I can help in any way, let me know.  Feel free to send me a message with details.

  3. 2 minutes ago, cybrnook said:

    Either option is going to be within the container os itself. I would recommend this for now:

     

    CONFIRMED: This fixed it, and ripping works again - no segfault:

    /usr/bin # cp -p /usr/lib/jvm/java-1.8-openjdk/jre/lib/amd64/jli/libjli.so /lib

     

    I am not sure if it will be persistent through container reboots yet, haven't tried.

    You can click on your container icon and there is a terminal option to get you there.

     

    I get the following message, sorry, never tried console access for a container before.  

     

    sh: /usr/bin: Permission denied

  4. I checked the MakeMKV forums and I don't see any posts for this specific disc.  Sorry, but I don't recall if other discs have required Java or not as it usually works or works once the docker is updated.  I went back a few versions, stopped at v1.8.0 as all had the same issue / failure.  I'll keep my eye on the MakeMKV forums for any updates as it's a recently released disc, so others should have similar issues.  Thanks for your time!

  5. As luck would have it, it seems to be related to the new disk.  I grabbed a bunch of others that were succesful and they are working just fine.  Wierd, I've never had an issue like this before, so I assumed it was due to the upgrade.  Is there a way to run a previous version of the container?  Sorry, but I don't recall what version I was previously running.