I think there were some major changes in mariadb server when bumped to v11. Will check tomorrow what is going on and how to fix.
Posts by vpeter
-
-
Looks like this variable is for server only? Because I don't see reference in mariadb-connector-c.
-
Looks like this works:
Diff
Display Morediff --git a/packages/databases/mariadb-connector-c/package.mk b/packages/databases/mariadb-connector-c/package.mk index f77ec39aa7..0a213c77fb 100644 --- a/packages/databases/mariadb-connector-c/package.mk +++ b/packages/databases/mariadb-connector-c/package.mk @@ -16,6 +16,7 @@ PKG_CMAKE_OPTS_TARGET="-DWITH_EXTERNAL_ZLIB=ON -DCLIENT_PLUGIN_MYSQL_CLEAR_PASSWORD=STATIC -DCLIENT_PLUGIN_MYSQL_OLD_PASSWORD=STATIC -DCLIENT_PLUGIN_REMOTE_IO=OFF + -DDEFAULT_SSL_VERIFY_SERVER_CERT=OFF " post_makeinstall_target() {
-
-
Can not running script
Sure you can run it and this will tell you exactly what is write protected or whatever issue is.
-
Why not checked the logs (journalctl -l) to see what is going on?
Or to run /storage/.config/irswitch.sh maualy from console? Before doing it kill already running instance.
-
Eventually you have to make it executable first: chmod +x autostart.sh.
not needed
-
Well, I don't think this is appropriate.
-
-
iamiub: follow this to restore bootloader environment in device. After that don't blame CE anymore
Restore CoreELEC changes to the boot processPut this file on CE USB stick (replace existing one) and use the first time boot procedure. Does it help or not? aml_autoscript (101 Bytes) File based on…discourse.coreelec.org -
Installed from LE11 OVA, running on Windows 11.
-
Here vmware workstation 17.5.1 works with LE 11 and LE12 - using vmware gpu (no passthrough).
-
Looks like the position in Kconfig file is wrong. Which means because of that linux config file is correct.
-
but i think in wrong way (manually edited instead menuconfig) "CONFIG_DVB_M88RS6060=m" is added in " # DVB-T (terrestrial) frontends" Section
What would be correct place?
-
-
First uninstall addon and also remove it's settings. Then install it again and check if works or still not.
Or you can fix it by running this commands in SSH terminal:
Codesed -i "s|TLSProtocol .*|TLSProtocol TLSv1.2 TLSv1.3|" /storage/.kodi/userdata/addon_data/service.proftpd/proftpd.conf rm -f /storage/.kodi/userdata/addon_data/service.proftpd/proftpd.*.pem systemctl restart service.proftpd
You can check the status of the service by command
-
Just hook local HDD and problem is no more
-