CoreELEC 19.2-Matrix Discussion

Please use this thread for general 19.2-Matrix discussion

3 Likes

Is this based on Kodi 19.2? Looked on the Kodi site but haven’t seen mention of 19.2 being available.

Milestone 19.2 not yet official announcement but 19.3 already in the works.

2 Likes

I’ve updated my two gxl_p212_1g boxes (an X96 and a Trongle X4) and they both have a problem with smb, particularly bad on my second box that is on WiFi (while the other is on 100 Mbps ethernet): when I try to skip to a next song most of the times there’s a very long delay before it is played and on my smb server I get these errors:

Oct  7 18:56:44 r1 smbd[23497]: [2021/10/07 18:56:44.456404,  0] smbd/oplock.c:330(oplock_timeout_handler)
Oct  7 18:56:44 r1 smbd[23497]:   Oplock break failed for file music/Album 1/Song 1.mp3 -- replying anyway
Oct  7 18:58:18 r1 smbd[23497]: [2021/10/07 18:58:18.809404,  0] smbd/oplock.c:330(oplock_timeout_handler)
Oct  7 18:58:18 r1 smbd[23497]:   Oplock break failed for file music/Album 2/Song 2.mp3  -- replying anyway

I first updated one box and saw the issue so I tested the other one before updating it and it was working fine as always, then updated it and it also started having the problem.

I’ve had a quick look for the above smbd errors and it should mean that the file requested is aleady in use and can’t be released but there are no other clients using these files at the moment.

@Portisch I’ll send you a link with logs.

From what version did you update? RC3?
If yes then please try nightly for test
http://coreelec.relkai.org/?dir=20210930
If still not working then
http://coreelec.relkai.org/?dir=20210830

Yes I updated from rc3.

So I tried both nightlies, no change, then I went back to rc3, also no change so I rebooted my router/smb server and then rc3 worked. I went back to 19.2 and it didn’t work again, rebooted my router, no change, went back to the 20210930 nightly, didn’t work, rebooted my router, no change, went back to the 20210830 nightly, didn’t work, rebooted my router, no change, went back to rc3 and this time it worked without a router reboot. So in conclusion only rc3 works with this.

Edit: I’ve also retested my other box, it still has the problem on 19.2, I’ve put it back on rc3 and it’s working fine.

No idea, samba was bumped after 20210930, but this is like your report not the problem.
You will need to find the last working image:
http://coreelec.relkai.org/

OK, I’ll do it later today.

Edit: so the culprit seems to be 20210827, although it happened once on 20210818 and on 20210823 and never on 20210812 (so it could be a combination of problems starting from 20210818), but several times from 20210827. This was on my ethernet box where this happens less often. On the images where it wasn’t happening (20210812, 20210818 and 20210823) I made many more tries.

See below my router’s logs.

20210812 (none)

20210818 (1)
Oct  8 09:13:23 r1 smbd[19748]: [2021/10/08 09:13:23.396172,  0] smbd/oplock.c:330(oplock_timeout_handler)
Oct  8 09:13:23 r1 smbd[19748]:   Oplock break failed for file music/Album/Song -- replying anyway

20210828 (7)
Oct  8 09:25:53 r1 smbd[29310]: [2021/10/08 09:25:53.338184,  0] smbd/oplock.c:330(oplock_timeout_handler)
Oct  8 09:25:53 r1 smbd[29310]:   Oplock break failed for file music/Album/Song -- replying anyway
Oct  8 09:26:44 r1 smbd[29310]: [2021/10/08 09:26:44.314262,  0] smbd/oplock.c:330(oplock_timeout_handler)
Oct  8 09:26:44 r1 smbd[29310]:   Oplock break failed for file music/Album/Song -- replying anyway
Oct  8 09:27:26 r1 smbd[29310]: [2021/10/08 09:27:26.019177,  0] smbd/oplock.c:330(oplock_timeout_handler)
Oct  8 09:27:26 r1 smbd[29310]:   Oplock break failed for file music/Album/Song -- replying anyway
Oct  8 09:28:03 r1 smbd[29310]: [2021/10/08 09:28:03.252192,  0] smbd/oplock.c:330(oplock_timeout_handler)
Oct  8 09:28:03 r1 smbd[29310]:   Oplock break failed for file music/Album/Song -- replying anyway
Oct  8 09:28:47 r1 smbd[29310]: [2021/10/08 09:28:47.127204,  0] smbd/oplock.c:330(oplock_timeout_handler)
Oct  8 09:28:47 r1 smbd[29310]:   Oplock break failed for file music/Album/Song -- replying anyway
Oct  8 09:29:38 r1 smbd[29310]: [2021/10/08 09:29:38.514194,  0] smbd/oplock.c:330(oplock_timeout_handler)
Oct  8 09:29:38 r1 smbd[29310]:   Oplock break failed for file music/Album/Song-- replying anyway
Oct  8 09:31:39 r1 smbd[29310]: [2021/10/08 09:31:39.545180,  0] smbd/oplock.c:330(oplock_timeout_handler)
Oct  8 09:31:39 r1 smbd[29310]:   Oplock break failed for file music/Album/Song -- replying anyway

20210827 (4)
Oct  8 09:34:56 r1 smbd[614]: [2021/10/08 09:34:56.952174,  0] smbd/oplock.c:330(oplock_timeout_handler)
Oct  8 09:34:56 r1 smbd[614]:   Oplock break failed for file music/Album/Song -- replying anyway
Oct  8 09:35:31 r1 smbd[614]: [2021/10/08 09:35:31.353180,  0] smbd/oplock.c:330(oplock_timeout_handler)
Oct  8 09:35:31 r1 smbd[614]:   Oplock break failed for file music/Album/Song -- replying anyway
Oct  8 09:36:22 r1 smbd[614]: [2021/10/08 09:36:22.728181,  0] smbd/oplock.c:330(oplock_timeout_handler)
Oct  8 09:36:22 r1 smbd[614]:   Oplock break failed for file music/Album/Song -- replying anyway
Oct  8 09:38:38 r1 smbd[614]: [2021/10/08 09:38:38.284176,  0] smbd/oplock.c:330(oplock_timeout_handler)
Oct  8 09:38:38 r1 smbd[614]:   Oplock break failed for file music/Album/Song -- replying anyway

20210823 (1)
Oct  8 09:46:22 r1 smbd[4790]: [2021/10/08 09:46:22.928173,  0] smbd/oplock.c:330(oplock_timeout_handler)
Oct  8 09:46:22 r1 smbd[4790]:   Oplock break failed for file music/Album/Song -- replying anyway

20210827 (11)
Oct  8 09:54:15 r1 smbd[13093]: [2021/10/08 09:54:15.137178,  0] smbd/oplock.c:330(oplock_timeout_handler)
Oct  8 09:54:15 r1 smbd[13093]:   Oplock break failed for file music/Album/Song -- replying anyway
Oct  8 09:55:11 r1 smbd[13093]: [2021/10/08 09:55:11.248177,  0] smbd/oplock.c:330(oplock_timeout_handler)
Oct  8 09:55:11 r1 smbd[13093]:   Oplock break failed for file music/Album/Song -- replying anyway
Oct  8 09:56:08 r1 smbd[13093]: [2021/10/08 09:56:08.379182,  0] smbd/oplock.c:330(oplock_timeout_handler)
Oct  8 09:56:08 r1 smbd[13093]:   Oplock break failed for file music/Album/Song -- replying anyway
Oct  8 09:56:56 r1 smbd[13093]: [2021/10/08 09:56:56.708184,  0] smbd/oplock.c:330(oplock_timeout_handler)
Oct  8 09:56:56 r1 smbd[13093]:   Oplock break failed for file music/Album/Song -- replying anyway
Oct  8 09:57:37 r1 smbd[13093]: [2021/10/08 09:57:37.362190,  0] smbd/oplock.c:330(oplock_timeout_handler)
Oct  8 09:57:37 r1 smbd[13093]:   Oplock break failed for file music/Album/Song -- replying anyway
Oct  8 09:58:11 r1 smbd[13093]: [2021/10/08 09:58:11.986167,  0] smbd/oplock.c:330(oplock_timeout_handler)
Oct  8 09:58:11 r1 smbd[13093]:   Oplock break failed for file music/Album/Song -- replying anyway
Oct  8 09:59:04 r1 smbd[13093]: [2021/10/08 09:59:04.342224,  0] smbd/oplock.c:330(oplock_timeout_handler)
Oct  8 09:59:04 r1 smbd[13093]:   Oplock break failed for file music/Album/Song -- replying anyway
Oct  8 09:59:46 r1 smbd[13093]: [2021/10/08 09:59:46.863174,  0] smbd/oplock.c:330(oplock_timeout_handler)
Oct  8 09:59:46 r1 smbd[13093]:   Oplock break failed for file music/Album/Song -- replying anyway
Oct  8 10:00:30 r1 smbd[13093]: [2021/10/08 10:00:30.273180,  0] smbd/oplock.c:330(oplock_timeout_handler)
Oct  8 10:00:30 r1 smbd[13093]:   Oplock break failed for file music/Album/Song -- replying anyway
Oct  8 10:01:07 r1 smbd[13093]: [2021/10/08 10:01:07.976175,  0] smbd/oplock.c:330(oplock_timeout_handler)
Oct  8 10:01:07 r1 smbd[13093]:   Oplock break failed for file music/Album/Song -- replying anyway
Oct  8 10:02:52 r1 smbd[13093]: [2021/10/08 10:02:52.128174,  0] smbd/oplock.c:330(oplock_timeout_handler)
Oct  8 10:02:52 r1 smbd[13093]:   Oplock break failed for file music/Album/Song -- replying anyway

20210812 (none)

There were a lot of updates this day :thinking:
Could you also upload log for any broken build after this issue occurred to check if something visible there?
And see message in PM and try please test builds

I sent you some logs.

Edit: I’ve talked with @boot2k3 about this and there are no apparent issues on my logs.

It could be related to my setup, I’ll wait for other people to update to 19.2 and report any issues before taking further steps.

Any idea, why the download shows rc3 still?

Just refresh the page :wink:
As for automatic update it will be enabled a little bit later.

1 Like

Coreelec 19.2 matrix using smb or anything my windows 10 machine can not see it on my beelink gs king x i heard somewhere its a coreelec issue?

I have a problem with 19.2_rc3 which does not exist on any 9.x.y version on my N2:

For years I’m using a WiFi keyboard Rii mini i8+ via USB WiFi dongle connected to USB 3.0 port, and the problem is short keypress. Using this keyboard for years my finger actions on the keyboard are pretty much automatic. The thing is that the short keypress is way to short and about 95% precent of the time I end up with a long keypress action instead of intended short keypress. As if the time for short keypress is only about 50ms, and on all 9.x.y versions it is about 300-400ms…

Posted this problem some time ago in 19.2 rc-3 thread and got none suggestion/solution…
Updated my N2 to 19.2 and there is no change with this behaviour. There is no such problem with 19.2 on Windows (PC) and Android (Firestick 4k) Kodi 19.2 installations.
Is there any dev willing to take a look at this, and can I somehow help with additional info, so that I do not have to be the world champion in fast key-press any more?

What was broken about the “HDR > SDR functionality”, or what’s improved?

This functionality was broken for HDR displays.

I experience it too on with all my flircs and N2s. It also worked “correctly” on the 9.x versions. I’ve now been trained to be very quick on the press, but still hold it too long fairly often.

I solved the Samba problem on 19.2 by disabling oplocks on my router’s smb.conf using the info here: Samba Slow - Oplock break failed for file - SysAdmins Diary

It’s just curing the symptom but I’m happy that I could update to 19.2.

About | FAQ | Terms of Service | Privacy Policy | Legal Notice