You could try to move your current install with the the below link as a back up, install fresh, then move it back. It might not work but it also might fix the problem.
But like I said, I HIGHLY recommend especially if you have a large library to move to another OS that has a modern file system like ZFS or BTRFS that has snapshots so you don’t ever have to deal with this again. This is from experience. It is worth learning something new. I’ll be moving to Linux with Docker soon actually because it seems BSD always gets the lowest priority when it comes to Plex.
Not sure if you have Windows System Restore set up but that might be able to roll you back… or break everything worse. Like it usually likes to do.
I’ll just roll back to the first 1.22 version and see if that helps. The uninstall/reinstall is tedious, but quicker than doing any sort of migration/remigration.
Things are settled down post-rollback on the Mac, meanwhile. No idea what the devs are doing here, but 1.23.xx versions all seem to be borked.
I’m very tempted to just port things over to Linux Mint (I was on Ubuntu for a while, but it all went horribly wrong one day and I never rebuilt.)
Just a FYI… I installed the LD_LIBRARY_PATH change and the latest build and all is well. But I have not done anything yet with adding new content so… I hope that they get this fix into the next build.
I wonder how they release something without testing something as basic as this. The first time it happened it is OK, we understand sh*t happens. But they have done now a couple of releases WITH the giant bug included after the problem is well known. I understand they want to fix it properly and that might take time but at least release something that works, so at least include the workaround.
Plex must have one of the worst QA departments ever.
Plex Team, can we get an update on this issue? Has the problem been identified? Do you need more logs? I am fine just leaving updates turned off but it would be nice to get an update. It has been radio silence for a while now.
