It's clearly a bug on CEC:
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
Core was generated by `/usr/lib/kodi/kodi.bin --standalone -fs'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0xf7d26bec in CEC::CSLCommandHandler::ActivateSource(bool) () from /usr/lib/libcec.so.4Moved to bug reports.
Windows cannot access \\LibreELEC\Library
Check the spelling of the name. [...]
This could be right. Maybe just the letter "L":
ln -s /var/media/sda1-usb-Mass_Storage_Dev/TVshows /storage/library/TVshows
Copied start.elf from LibreELEC-RPi4.arm-11.0-nightly-20220618-b78941a.img
Why do you do this?
I would guess your AVR is the culprit here. It probably doesn't update the projectors HDMI capabilities correctly.
If you want to be sure, create a log when HDR10 is missing. If HDR10 isn't in the log, my theory is verified.
Try both HDMI outputs.
Theory: LE's Samba server has moved from SMB1 to SMB2 version. Since SMB2 file browsing doesn't work anymore: Click!
A symlink is a symlink, no matter from which side it's accessed.
So everybody, who is interested in latest Chrome, should update to LE 11 generic-legacy.
Update folder method from LE 10 generic-legacy to LE 11 generic-legacy is working.
Update folder method from LE 10 generic to LE 11 generic-legacy is untested.
Install LE 10.0.4 from scratch, and use HDMI-0 output.
You can't update from LE 9 to LE 10. You have to create a new microSD containing LE 10 or LE 11.
Upgrade / downgrade among LE 10 and LE 11 is possible without problems.
That's a known issue: Click!
I'm looking for this on the forum but I don't fund nothing
You have to go to the main page first, and use the search function from that location.
Then you'll find results like this: Can't find Jellyfin client
is this supposed to work on rpi4B? i have tried on mine and it doesnt work
It should work. Read this thread: Click!
Which LE version do you run? Can you make another screenshot on the top of the message?
LE uses Linux, and on Linux drivers are part of the kernel. So after changing hardware, the right driver should be automatically picked up from the kernel.
Kodi on Raspberry Pi OS is your best chance to activate your touch screen. So check the RPi forum: Click!
Because you don't describe your problem, and because I don't even know whether you run LE at all, I close this thread.
Use Raspberry Pi OS, not Raspbian. Installation should be easy: HOW-TO: Install Kodi on Raspberry Pi
