Wow, they are really slow at pushing an update. The changes that needed to be made can be found [here]. As you can see the changes have been merged but there is no current build there so I just manually tweaked the current add-on. What follows is what I did that worked for me using a Windows PC.
Grab a copy of the cached add-on zip from Kodi at… ~/.kodi/addons/packages/script.plex-0.3.4.zip
and copy it to your PC and then unzip it. If you have SAMBA server installed in OSMC then you can just open Explorer and type in… \\192.168.x.x\osmc\.kodi\addons\packages\script.plex-0.3.4.zip
(replacting the ip address) and then just drag and drop the script.plex folder over to somewhere on your PC. Next install notepad++ if your don’t already have it. Open Notepad++ and File>open folder as workspace and select the script.plex folder you pulled from the zip file. Double click addon.xml and modify the version number on the fourth line to 0.3.4.1 and then save and close that file. In the workspace pane right click on the script.plex folder and select find in files. In the dialog box that comes up tell it to find “.isalive()” and replace “.is_alive()” and click “replace in files”. Close the workspace and quite Notepad++. In Explorer right click on the script.plex folder and select “compress to zip” and name it “script.plex-0.3.4.1” and then copy this zip file somewhere that you can access from within Kodi (like the osmc home folder). Finally you just need to go to the add-ons section of Kodi, tell it to “install from zip file” and point it to where you saved that zip.
One final note, don’t bother trying to directly edit ~/.kodi/addons/script.plex as that method doesn’t work.
quick note for mac users: you can access the .zip via cyberduck. Login as root / [your password], make all files visible (view -> show hidden files, or command-shift-R) to get to the .kodi folder.
You can batch change the files using BBedit, howto is here.
Drop the .zip anywhere convenient, and you might then want to login via terminal, navigate to wherever you dropped the zip file, and chown osmc:osmc script.plex-0.3.4.1.zip
Spending a little time with logs, the original logs I’ve uploaded missed the error, which is:
2022-06-27 19:12:01.283 T:17566 INFO <general>: Creating InputStream
2022-06-27 19:12:01.331 T:17566 INFO <general>: Creating Demuxer
2022-06-27 19:12:01.606 T:17566 INFO <general>: Opening stream: 0 source: 256
2022-06-27 19:12:01.606 T:17566 INFO <general>: CVideoPlayerVideo::OpenStream - Creating codec: 27
2022-06-27 19:12:01.606 T:17566 ERROR <general>: CDVDVideoCodecAmlogic::Open - InstanceGuard locked
2022-06-27 19:12:01.606 T:17566 INFO <general>: CVideoPlayerVideo::OpenStream - could not open video codec
2022-06-27 19:12:01.606 T:17566 INFO <general>: Opening stream: 1 source: 256
2022-06-27 19:12:01.606 T:17566 INFO <general>: Finding audio codec for: 86056
2022-06-27 19:12:01.607 T:17566 INFO <general>: CDVDAudioCodecFFmpeg::Open() Successful opened audio decoder eac3
2022-06-27 19:12:01.607 T:17566 INFO <general>: Closing stream player 3
2022-06-27 19:12:01.607 T:17566 INFO <general>: Opening stream: 2 source: 256
2022-06-27 19:12:01.908 T:17576 INFO <general>: CVideoPlayerVideo::OpenStream - Creating Codec: 27
2022-06-27 19:12:01.909 T:17576 INFO <general>: CDVDVideoCodecAmlogic: using Amlogic decoder H.264/MVC
2022-06-27 19:12:01.909 T:17576 INFO <general>: DVDVideoCodecAmlogic: Opened Amlogic Codec
So it appears that kodi is trying to play the next file too soon.
From a cursory search, it seems like a known issue Issue 20021. However, this was not something I had experienced prior to the Bullseye build. Could there be something to be done in OSMC?
@sammyrc34, can you post a complete log which shows that error? Or better: create a new log, but enable debug logging and also enable video component logging. That would show in detail what happens. I wonder why that was working before?
Thanks for the logs and your investigations . That issue which you’ve linked above helped a lot. There really is a race condition. It has nothing to do with that mentioned m_opened flag but it’s in that area. I suppose my recent refactoring has changed the timing and now that race condition leads to a crash more often than before.
I’ll try to fix it and keep you informed. If possible, it would be great if you could upload a debug log when you get that error again. That would be very helpful.
Using the image for the Vero 4k in first post to re-image my vero via a SD card.
On the screen it stated “Please Stand By” then a few moments later the OSMC splash screen shows then the screen goes blank. Waited for about 30 mins with screen still blank. is this expected for successful install as now when reboot with or without SD card it is the same as above.
@sammyrc34 This should now be fixed by @tanio99 and you should receive an update shortly which resolves the issue. It would be good if you could confirm if this was the case.
Thank you @sam_nazarko and @tanio99. My apologies for not responding earlier. I attempted to reproduce with the debug log but ran out of time before setting off on a holiday. I’ll apply the update and test in a couple of weeks when home again. Thank you again.
No image (black screen) with every 3D-.ISO movie-file
(all with mode Same as movie or Hardware based. Decoder/Stream am-h264mvc(hw))
I tried to play since last update.
Doesn’t matter if played in 3D or 2D.
New items shown in Video settings when playing them:
Video scaling method: Bilinear
Tone mapping: Reinhard
Tone mapping parameter: 1.00
2D-.ISOs and 3D-mkv-files are fine and without new items.
Guess you need logs - or reproducable by yourself?
Not a problem for me as I only decided to try this out of curiosity, but my vpn (openvpn setup via cli) doesn’t want to work on bullseye. From a fresh install, the network seems to be blocked. SSHing and running curl ipinfo.io returns curl: (6) Could not resolve host: ipinfo.io. Tried to upload logs but my osmc says it can’t retreive url. Ethernet is registered as connected in myosmc and reverting back to buster makes everything work again. Sorry I can’t provide more useful feedback, but maybe something you can look into.
. That issue which you’ve linked above helped a lot. There really is a race condition. It has nothing to do with that mentioned 
