Posts by mglae

GBM connector can be forced via advancedsettings.xml.

First ssh in and use kmsprint to get the connected connector name of the screen.

Create advancedsettings.xml (replace "Virtual-1" with your connector name):

<advancedsettings version="1.0">

<!-- Debug Logging -->
<loglevel hide="false">1</loglevel> 

<!-- No monitor selection on GBM but connector can be forced: -->
<videoscreen>
<monitor>Virtual-1</monitor>
</videoscreen>

</advancedsettings>

Debug logging is enabled to ease the setup.

Perform systemctl restart kodi to test the configuration.

The log only show a crash of the LE-Settings log uploader.

To work around the issue please enable (and test) ssh access first. After the original crash log in via ssh and use the pastecrash command.

Patch is accepted upstream in inputstream.ffmpegdirect. I've created a LE13 PR.

emveepee Thanks for testing. I should have noted gdb shows the error sequence in ffmpegdirect::FFmpegStream::GetFFMpegOptionsFromInput().

chewitt IMO more likely the commit Jeroened showed in post #9, especially making the kodi CURL class final.

Can be the reason, the kodi CURL constructor is called but then inputstream.ffmpegdirectCURL::Parse() used.

This patch does fix the issue in my tests. Will try to create a PR tomorrow.

It is crashing in inputstream.ffmpegdirect calling CURL. But

You can increase crash log verbosity with touch /storage/.config/debug.enhanced from ssh. This may or may not show information.

Did you attach the power supply to the stick?

Quote from tokul

Do I have to delay kodi startup for update to fetch release information after network is up and ntp sets up clock?

In any case increase the max. network wait time in LibreELEC-Settings -> Network to e.g.45 sec.

There is no fix in kodi yet therefore nothing that can be updated.

1. Find all addons using <reuselanguageinvoker>:

   Code

   find /usr ~/.kodi/addons/ -name addon.xml -print0|xargs -0 grep -l '<reuselanguageinvoker>'

2. Copy all found (read only) addon directories below /usr to ~/.kodi/addons: cp -r /usr/[...] ~/.kodi/addons
3. Edit all found addons.xml below ~/.kodi/addons (including copied) and change <reuselanguageinvoker>true</reuselanguageinvoker> to <reuselanguageinvoker>false</reuselanguageinvoker>
4. Restart kodi and start testing: systemctl restart kodi

Most likely Kodi Issue #27025, see this thread.

As said in the issue, disabling <reuselanguageinvoker> seem to work around the crash. Easy to be tested for developers but hard to configure for users.

Firmware of mt7925e from ubuntu 6.16.8 mainline kernel:

$ modinfo mt7925e
[...]
firmware:       mediatek/mt7925/WIFI_MT7925_PATCH_MCU_1_1_hdr.bin
firmware:       mediatek/mt7925/WIFI_RAM_CODE_MT7925_1_1.bin
[...]

Quote from sunlollyking

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).

1. Safe Mode: don't rename .kodi or kodi.FAILED. Only perform needed changes in kodi.FAILED (or nothing) and reboot. Safe Mode is disabled on next boot.
2. I set my bet on this Python issue. I've seen it rarely myself but the question is why it lead to safe mode on your side.

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

Quote from yamcenutzer

Any one any ideas?

Kodi debug + system logs via pastekodi or LibreELEC-Settings of the failing and successful case?