I just noticed on my x86-64 based system that with the nightlies I have some libraries with invalid symbolic links. I was wanting to try fixing it however I'm having a hard time identifying where those links get generated when building. Specifically the libraries I'm looking at libGL and libGLX, which you can see below are pointed at the wrong directories:Code
lrwxrwxrwx 1 root root 10 Sep 23 14:25 /usr/lib/libGL.so -> libGL.so.1 lrwxrwxrwx 1 root root 17 Sep 23 14:25 /usr/lib/libGL.so.1 -> /var/lib/libGL.so -rwxr-xr-x 1 root root 538960 Sep 23 14:25 /usr/lib/libGL.so.1.7.0 lrwxrwxrwx 1 root root 11 Sep 23 17:01 /usr/lib/libGLU.so -> libGLU.so.1 lrwxrwxrwx 1 root root 15 Sep 23 17:01 /usr/lib/libGLU.so.1 -> libGLU.so.1.3.1 -rwxr-xr-x 1 root root 461768 Sep 23 17:01 /usr/lib/libGLU.so.1.3.1 lrwxrwxrwx 1 root root 11 Sep 23 14:25 /usr/lib/libGLX.so -> libGLX.so.0 lrwxrwxrwx 1 root root 18 Sep 23 14:25 /usr/lib/libGLX.so.0 -> /var/lib/libGLX.so -rwxr-xr-x 1 root root 133712 Sep 23 14:25 /usr/lib/libGLX.so.0.0.0 lrwxrwxrwx 1 root root 15 Sep 23 14:25 /usr/lib/libGLX_glvnd.so.0 -> libGLX.so.0.0.0 lrwxrwxrwx 1 root root 29 Sep 23 14:25 /usr/lib/libGLX_indirect.so.0 -> /var/lib/libGLX_indirect.so.0 lrwxrwxrwx 1 root root 16 Sep 23 17:01 /usr/lib/libGLX_mesa.so -> libGLX_mesa.so.0 lrwxrwxrwx 1 root root 20 Sep 23 17:01 /usr/lib/libGLX_mesa.so.0 -> libGLX_mesa.so.0.0.0 -rwxr-xr-x 1 root root 459984 Sep 23 17:01 /usr/lib/libGLX_mesa.so.0.0.0 -rwxr-xr-x 1 root root 1289616 Sep 23 17:04 /usr/lib/libGLX_nvidia.so.0 lrwxrwxrwx 1 root root 14 Sep 23 14:25 /usr/lib/libGL_glvnd.so.1 -> libGL.so.1.7.0 -rwxr-xr-x 1 root root 1267800 Sep 23 17:04 /usr/lib/libGL_nvidia-legacy.so.1 lrwxrwxrwx 1 root root 18 Sep 23 14:25 /usr/lib/libGLdispatch.so -> libGLdispatch.so.0 lrwxrwxrwx 1 root root 22 Sep 23 14:25 /usr/lib/libGLdispatch.so.0 -> libGLdispatch.so.0.0.0 -rwxr-xr-x 1 root root 711128 Sep 23 14:25 /usr/lib/libGLdispatch.so.0.0.0
If someone could please point me in the correct direction. Thank you!
Turns out whether those libraries exist in /var/lib seems to be controlled at boot time. In testing a boot switch for my hardware, it disabled those files existing.
Appears to be an issue in the GLES code, an unintended variable assignment. I'll be taking this over to Kodi.
I have found an issue with GBM, confirmed with both Generic and Amlogic, when configured as limited colour range. The issue being that images lines for dvb subtitles have the range conversion applied twice. In other words, the lines where dvb_subtitles are rendered, not just the text but the whole width of the screen appears lighter then the rest of the screen.
This does not occur with Generic-Legacy (X11) nor Kodi (X11) on Ubuntu 22.04 (x64).
I can provide a kodi debug log, however I'm not sure it would help.
There has been a continual up and down over the last couple years with regard to the reboot issue.
If you try a google, there is a back and forth breakage between the Kernel and u-boot. General summary seems to be related to the power for attached devices, e.g. SD-Card, USB, EMMC, so what you have attached also seems to impact whether you are impacted or not. Even just changing the speed of SD-Card has an impact.
For any of the Libreelec team, the following might be of some help if you hadn't already seen:
Armbian - meson64: edge: rework to kernel 5.19 which with regard to the reboot issue just references
This discussion of CONFIG_DRM_MESON=m vs. CONFIG_DRM_MESON=y in terms of a broadly acceptable solution.
Armbian's later update to Kernel 6.0.13 continued to follow suit on CONFIG_DRM_MESON=y
Using the latest Generic-Legacy nightlies, there are missing library dependencies for the music visualization plugins. Seems to be a case of the plugins being compiled for Generic (GBM) instead of Generic-Legacy (X11). Below is for shadertoy, but the others are similar.
I had cleaned out any archived copies in the packages folder, so I don't think it got a previously cached copies of the plugins.Code
ldd: $warning: you do not have execution permission for `./visualization.shadertoy.so.20.3.0' linux-vdso.so.1 => linux-vdso.so.1 (0x00007fff70fa6000) libGLESv2.so.2 => not found libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x00007ff15b05b000) libm.so.6 => /usr/lib/libm.so.6 (0x00007ff15af7e000) libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x00007ff15af5e000) libc.so.6 => /usr/lib/libc.so.6 (0x00007ff15ad9e000) /usr/lib64/ld-linux-x86-64.so.2 => /usr/lib64/ld-linux-x86-64.so.2 (0x00007ff15b2dc000)
I have gotten it working. Hopefully the following would provide assistance to anyone else encountering the problem.
I was setup using the main lirc configuration file, Lircd.conf. As a test, I switched to using the distributed toml keymap file (see /usr/lib/udev/rc_keymaps/*). To do so, remove the lircd.conf and create a file ~/.config/.rc_maps.cfg containing:
* * hauppauge.toml
So follow these instructions instead of the Lirc documentation.
I'm using an IR remote that is using the Hauppauge codes (PVR-250). Both a Hauppauge remote as well as a Harmony universal programmed as Hauppauge. The IR receiver being the built-in Odroid C2 one, so meson-ir.
The lirc.conf for the remote is the borg standard Hauppauge from the lirc website.
ir-keytable -t shows only one scan code per key. I also note that it immediately responds for each keypress, there is no waiting for the second keypress.
Using the nightlies on an Arm - Odroid C2, there is an issue for my remote following the upgrade to Lirc 0.10.2.
In short, Lirc 0.10.2 does not issue commands on each keypress. Instead, the key presses appear to be queued, with the queue being translated to commands on every 2nd key press. For example:
- Press down button - No effect on Kodi
- Press right button - Kodi responds with a down action (and navigation sound) followed by a right action (and navigation sound).
In terms of the nightlies:
- Working LibreELEC-AMLGX.arm-11.0-nightly-20221007-9c1305e-odroid-c2
- Not working LibreELEC-AMLGX.arm-11.0-nightly-20221008-1d2cd1d-odroid-c2
Between those two builds is Pull lirc: update to 0.10.2 #6966
The Kodi debug log does not help since it only records when it receives the commands from Lirc, which is after the issue.
I misread the situation Thanks for pointing it out.
Sorry. Looking back I realize I could have written that clearer.
So to clarify, for x86-64:
- Generic (GBM) - missing libraries
- Generic-Legacy (x11) - works
vpeter thanks. With the rebuild of the binary plugins, everything is good now.
I will note though that generic-legacy is required due to the dependencies on X11. GBM is missing the libraries so Kodi will just sit with the spinner spinning, no recognition that the libraries didn't load unless you check a debug log. For GBM, the missing are:
libXext.so.6 => not found
libX11.so.6 => not found
libxcb.so.1 => not found
The builds versus hash in order of commit history are:
Build date Hash 20220720 (works) 3a4dc81 20220723 (broken) 0da8a26 20220723 (broken) 0008ab5
In order of commit, the Pulls covering that range are:
3a4dc81 Pull #6717
1182c1a Pull #6721
13bb8f3 Pull #6724
06fd018 Pull #6715
2cc0585 Pull #6726
771b9b9 Pull #6470
f529cc9 Pull #6727
0da8a26 Pull #6729
0008ab5 Pull #6730
None of them are obvious as to breakage. If you were able to build Libreelec yourself, I would probably start by looking at #6727 as that appears to have triggered issues for others as well.
Sorry, issues is not with Libreelec. The issue is related to makemkv not playing nice with the current Libreelec. Removing makemkv or upgrading to a more recent compile resolves the issue.
daniel235 so it worked fine with 2022 June 08 build of b78941a?
If that build worked fine, then the question would be if pull #6673 caused the problem. That was merged 2022 July 08. So try something just after that. Something like
Then to confirm that pull is the issue, try the build just before
If it is that pull, then it will need to be dissected some as there are a number of changes included in it, library and Kodi changes.
When trying to play a physical bluray disc using nightlies (x64)(nightly-20221114-9c34b63 11.0), they aren't working.
This is a disc that has worked on this system previously using much older Libreelec versions.
chewitt, issue is if one wants to disable the service. It can't be disabled as the symbolic link, from the "WantedBy" dependency, can never be deleted due to the file system being read only.
When ServiceA has a "WantedBy" ServiceB, a symbolic link is created under ServiceB that results in ServiceA being run. When using systemd to disabled ServiceA, systemd would delete the symbolic link.
In this case our filesystem is read only, so systemd cannot delete the symbolic link under kodi.target, thus the ledfix service can never really be disabled as kodi.target is always running it.