weirdly still have the red colour on estuary
You can reset it to default via Skin Colours setting.
weirdly still have the red colour on estuary
You can reset it to default via Skin Colours setting.
Sep 15 16:52:08.173131 LibreELEC kodi.sh[3986]: terminate called after throwing an instance of 'std::logic_error'
Sep 15 16:52:08.173131 LibreELEC kodi.sh[3986]: what(): busy dialog already running
Sep 15 16:52:09.244783 LibreELEC kodi.sh[3945]: Aborted (core dumped)
Double busy dialog is aborted.
There is a work around with merge of #27102 in Kodi Omega. Wait until Kodi is bumped for LE 12.2 nightlies (no PR yet).
chewitt Logs are from July before the switch to GL. At this time some to many LE13 addons have been from Omega branches.
To create useful logs always use the log and/or crashlog uploader of LibreELEC-Settings Addon or pastekodi/pastecrash from ssh
Any one any ideas?
Kodi debug + system logs via pastekodi or LibreELEC-Settings of the failing and successful case?
No or incorrect Widevine on new installations, see this inputstreamhelper issues
No, objtool error occur after successfully compiled.
PS: e.g. here you do find build patches up to kernel 6.17 (but the kernel will continue to complain).
There likely will be a patch to compile wl_linux..c. But the kernel will continue to BUG() every boot on the outdated binary Broadcom blob.
You have to change --latency too.
Use systemctl stop service.snapclient and systemctl start service.snapclient while testing, reboot only as final test.
If i still failing we will start talking about logging
Nice issue.
The implementation does only allow full minutes to be shown (beside seconds <= 60).
AC3 5.1 is transported over PCM 2.0.
If it does not work post a debug log playing some 5.1 content.
Optical cable is using the same protocol as ARC channel and only support PCM 2.0 or AC3 5.1.
Use TV(AC3) settings of Audio quickstart guide - Official Kodi Wiki.
It's a feature. When connecting to the Logfiles share a new log zip is generated. This may take some time on weak devices.
, after some investigation it seems that the Z890 chipset has a fault, in some circumstances you need to "disable" internal graphics
No. LE is only supporting a single GPU. If there are more than one the first configured wins the race. Unfortunately both GPUs may have been configured in parallel causing a crash.
Look for "xorg-configure" lines in your log.
Some discussion without fix (LE is mentioned): https://github.com/xbmc/xbmc/issues/16990