[InuSasha]

Good catch,
problem is identified

i will take a look, howto disable the caching.
start to install a fresh 5.7.19 (i like docker )

Edit:

sql:


Code:
SET SESSION query_cache_type = OFF;
 

[Milhouse]

https://dev.mysql.com/doc/refman/5.7/en/...cache.html

Deprecated in 5.7.20, removed in 8.0, but users tend to upgrade their backend servers very slowly so MySQL Server versions with query cache could be around for quite a while and would suddenly start breaking with MariaDB Connector when users upgrade to LE 9.0.

Disabling per-connection (SET SESSION query_cache_type = OFF;) would help reduce support overhead (but might require an LE specific patch to Kodi, unless it can be conditional when building with MariaDB client?) Or we just ask users to disable query cache in the Server config, but that might affect other applications using the same server.

Thanks @HeresJohnny for reporting this.

[InuSasha]

Conditional maybe easy, we have the define `HAS_MARIADB`
Much more difficult is, to do this only for MySQL-backends

[Milhouse]

Conditional maybe easy, we have the define `HAS_MARIADB`

Great.

Much more difficult is, to do this only for MySQL-backends

Or just disable it regardless of the backend server?

What's odd, though, is that my version of MySQL Server (5.5.21) has query cache enabled and isn't a problem:

Code:

> SHOW VARIABLES LIKE 'version';
'version', '5.5.21'
> SHOW VARIABLES LIKE 'have_query_cache';
'have_query_cache', 'YES'
> SHOW VARIABLES LIKE 'query_cache_size';
'query_cache_size', '67108864'
> SHOW VARIABLES LIKE 'query_cache_type';
'query_cache_type', 'ON'

Maybe there are specific versions of MySQL that cause this problem with the MariaDB connector? It could even just be 5.7.19!

I think we should dig a bit deeper before clobbering the query cache, as we could be disabling it on working MySQL systems unnecessarily.

[HiassofT]

I found the problem. InuSasha's hint as to his version gave me some info to work with. I have MySQL 5.7.19 and he has 5.7.20. One of the main things that changed is that as of 5.7.20 query cache is disabled. I was using query cache so on a hunch I disabled it.

Hmmm. If I read the release notes correctly query cache hasn't been disabled, but it's use has now been officially deprecated. Query cache isn't enabled by default since 5.6 (from 2013) though.

So I'm not exactly sure what's going on. Can you try to re-enabling the query cache or upgrade to a newer version?

so long,

Hias

[HeresJohnny]

While digging for info on the web I found several sources that suggested query cache should be turned off anyway when using InnoDB. Milhouse, maybe you're using MyISAM?

I'll upgrade to 5.7.21 later.

[Milhouse]

While digging for info on the web I found several sources that suggested query cache should be turned off anyway when using InnoDB. Milhouse, maybe you're using MyISAM?

I'll upgrade to 5.7.21 later.

Definitely InnoDB:



Query caching isn't enabled/active by default in my version (5.5.21) as query_cache_size=0, but I have the following configuration which is working normally:

Code:

query_cache_size = 64M
query_cache_limit = 16M

[Milhouse]

I was using query cache so on a hunch I disabled it.

Can you post your complete my.cnf? Also what OS are you using to run MySQL 5.7.19 - Windows, Linux, Mac?

[InuSasha]

@HeresJohnny i can not reproduce your problem.
As Database i used the mysql:5.7.19 docker container from docker-hub.
Tested the datasbase with query_cache_type=ON/OFF, no problems at all.

can you send me the result of

sql:
show variables;

Sascha

[laric]

I got a failure to install #0216 (going from #0211) stating that my size was too small.

Is there a way to resize the partitions or is a full reinstll needed.. and if so.. what should be the start image to get a big enough fat partition?

[Milhouse]

Is there a way to resize the partitions or is a full reinstll needed.. and if so.. what should be the start image to get a big enough fat partition?

See first post, note#5.

[Milhouse]

New LibreELEC.tv Leia build #0216: Generic
(Supercedes previous build)

SHA256 Checksum: f039fcde41e5cd2e1697a15ad895ce50a2895abdaed4fbce1ef5e4532d89e380 (Generic)

text:
# uname -a

Linux NUC 4.14.18 #1 SMP Fri Feb 16 21:18:46 GMT 2018 x86_64 GNU/Linux



# lsb_release

LibreELEC (Milhouse): devel-20180216210309-#0216-gc2fd843 [Build #0216]



# Kodi version

(18.0-ALPHA1 Git:f5871d9). Platform: Linux x86 64-bit

Based on tip of LibreELEC.tv master (c2fd843, changelog) and tip of XBMC master (374244d, changelog) with the following modifications:

• Includes latest kodi-platform master (36fb493)
  
• Includes latest libcec master (8adc786, ahead +26)
  
• Includes latest libnfs master (54405d9, ahead +120)
  
• Includes latest p8-platform master (a822e19)
  
• Includes latest addons: inputstream.adaptive (b28d3f0), inputstream.rtmp (b3ffc49), peripheral.joystick (02da6ed), pvr.argustv (a4d3ec7), pvr.demo (8f62053), pvr.dvblink (89d1687), pvr.dvbviewer (64c4356), pvr.filmon (2721611), pvr.hdhomerun (7379fbc), pvr.hts (095784b), pvr.iptvsimple (933a5c4), pvr.mediaportal.tvserver (dec444f), pvr.mythtv (3200b09), pvr.nextpvr (aa1c8d2), pvr.njoy (67b837d), pvr.octonet (689afbf), pvr.pctv (5b47d9f), pvr.stalker (77eec69), pvr.teleboy (3ae0297), pvr.vbox (57f3198), pvr.vdr.vnsi (4db947c), pvr.vuplus (f05f158), pvr.wmc (38e670a), pvr.zattoo (3c46173), vfs.libarchive (128394c)
  
• Include [env] compare (perma): kodi: reduce arm memory fragmentation
  
• Include [env] compare (perma): busybox: 2nd attempt at disabling busybox parallel build
  
• Include [env] compare (perma): dmidecode: initial package
  
• Include [env] patch: RPi/RPi2: enable Broadcom WiFi debugging (see details)
  
• Include [env] patch: libcec: fix PR390
  
• Include [env] patch: libcec: don't link non-existant libtinfo
  
• Include [env] patch: rev hack for kodi
  
• Include [env] patch: HACK: Disable multiple PVR addons during migration. Always enable inputstream.* and os.*
  
• Include [env] patch: Add experimental splash video for RPi
  
• Include [env] patch: Bump included addon versions to prevent online updates
  
• Include [env] patch: Add kodi binary addons (pvr, adsp, inputstream, vfs, other)
  
• Include [env] PR:2466 (perma): linux: update to linux-4.14.19 (-ish)
  
• Include [env] PR:2501 (perma): buildsystem: selectively build packages with debug
  
• Include [pkg] patch: skin.estuary: reduce system info font size (kodi)
  
• Include [pkg] PR:13274 (perma): Mode whitelist
  

Build Highlights:

1. Controller topology (multitap support)
   
2. libnfs updates
   

Build Details:

1. LibreELEC.tv:
   • tvheadend42: backport patch to fix jenkins (PR:2503, 1 commit, 1 file changed)
     
   • libva: update libva/libva-utils/intel-vaapi-driver 2.1.0 (PR:2491, 3 commits, 3 files changed)
     
   • kodi: updates for March 2018 (PR:2477, 11 commits, 26 files changed)
     
2. XBMC:
   • Controller topology (multitap support) (PR:13499, 3 commits, 57 files changed)
     
   • VideoPlayer: DirectX- implement tone mapping (PR:13549, 3 commits, 9 files changed)
     
   • [cleanup][omxplayer] remove unused headers (PR:13551, 1 commit, 3 files changed)
     
3. libnfs:
   • add conditional support for getpwnam() (c5eca21)
     
   • Merge branch 'master' of github.comahlberg/libnfs (c23ab16)
     
   • don't log an error if we cailed the name to uid/gid mapping (54405d9)
     

[fritsch]

Here's a photo from the artefacts i'm seeing:
image

 I think we found a fix. A glsl pow value was not properly clamped. Fernet is reinvestigating some details but said to PR the fix today. Thanks for the report.

[solidsatras]

I used 
LibreELEC v8.2.1 MR
and now I´m updating on a weekly basis with these builds.

Is there any benefit in starting fresh with new LibreELEC builds e.g.
LibreELEC v8.2.3 MR
or do these builds already contain all changes?

[Milhouse]

Is there any benefit in starting fresh with new LibreELEC builds e.g.
LibreELEC v8.2.3 MR
or do these builds already contain all changes?

No benefit, and yes.