LE is not a company. We have no products. There is no Engineering, no Project Management, no Product Management, no Marketing, .. and no Sales. We do have a support forum. You are welcome to use it (as-is) .. or not. Your choice.
Posts by chewitt
-
-
It was related to reserved memory regions.
See: https://patchwork.kernel.org/project/linux-…[email protected]/
-
Interesting. Thanks for the tip..
-
LE11 uses Python 3.11.12. What are the add-ons?
-
LibreELEC is $free open-source software not a PRODUCT from a company, and no user from any timezone has a right to instant or rapid support from the unpaid volunteers who give up their free time to work on the distro and staff this forum.
-
The legacy images do not contain vendor u-boot, they are designed to boot from SD card (with vendor u-boot on eMMC to initiate boot) or to replace the Android image on eMMC (again working with the original vendor u-boot on eMMC). If no u-boot on eMMC .. no boot.
The vendor u-boot code "works" but is horrible. Upstream u-boot also "works" and is cleaner to work with for packaging. Your Hub has a hardware problem. If you fix that (in hardware) the upstream u-boot works fine.
-
Read the sections on scrapers and how to use directories/filenames to get things to scrape accurately. They apply to offline media and the local filesystem scraper as much as online scrapers. If you store media in the right structure and filenames it all "just works" .. and if you stick with some homebrew structure that doesn't follow the rules the results are probably doesn't work.
-
Old LE version will be using the NTFS-3G userspace filesystem driver and current LE version will be using a new in-kernel NTFS filesystem driver. That will explain differences in how things are mounted and perhaps different error messages. It doesn't explain how things got corrupted in the first place; but with USB media PSU's and or the simple fact of NTFS + removable media =
-
dial tcp: lookup registry-1.docker.io on 192.168.1.1:53: no such host.
^ that's a DNS resolution failure. You might need to investigate Docker comms.
-
So i am struggling to understand why someone has gone to lengths to make this rule?? it's not in any standard that I am aware of, and it's easy to do on other devices so slightly puzzled.
You are welcome to complain to the upstream maintainers of ConnMan who authored/coded the connection manager whose features and capabilities we expose via the dbus agent in the Settings add-on. TL/DR; we didn't code anything or go to any lengths.
Unless you're planning to submit upstream patches to change worklows; the workaround will be to create a systemd service that runs before kodi.target and after network-online.target, that applies your preferred DNS server config to the active ethernet service using a connmanctl command. You'll find some useful prior art for something similar in other forum posts from users trying to change service (routing) order for VPN connections (also done with connmanctl commands).
NB: initial post approval applies to everyone and while your posts might not be visible to all users, they will be visible to mods/staff who are most likely to be the people replying. It is done solely for anti-spam reasons only, and is effective, and the algorithm that auto-manages it normally lifts restrictions quickly. If you're deeply offended by it or ragingly impatient, you're probably in the wrong forum.
-
Your DNS server failed to resolve "registry-1.docker.io" so the pull failed. Fix the network issue.
-
False-positives. Automated code-analysis/scanning or process inspection/monitoring tools are both clever and dumb. Off the top of my head I'd expect them to detect and flag that the app is unsigned, downloads files from the internet, destructively writes (overwrites) the boot sector of removable media, and contains Chinese|Russian strings. Those are all characteristics frequently associated with malicious code, but in our case the resulting app is entirely benign.
I have contacts at Crowdstrike so will have a word to see if their false detection can be corrected. I never heard of the other vendor .. so prob. some whizzy new exciteable analysis technology that doesn't work so great.
Thanks for flagging. It's good to know when these things occur.
-
Windows is a bit stupid and doesn't understand removable media with multiple partitions. Write this 'image' to the card and it will overwrite the MBR partition table; erasing knowledge of the partitions. Windows will then see the SD card as a normal unformatted drive again:
NB: The LE USB/SD creator app has this "image" listed under the Tools download section.
-
-
Known issue with currently no known fix: https://github.com/LibreELEC/LibreELEC.tv/issues/7166
-
Kodi uses the "Videos" menu to give a quick file-browser interface. It does not show any artwork unless the file happens to have been scraped into a library view (and thus references to the artwork-to-use are available). The "Movies" and "TV Shows" menus are library based, you need to "scrape" content in to them; either using internet scrapers or a local file scraper (which would e.g. find local artwork in the same folder). I suggest you have a read of https://kodi.wiki/view/Scrapers.
-
Not that I'm aware of, but the better place to ask would be the Kodi forums (under add-on development). NB: Profiles is one of the icky areas of the Kodi codebase; lots of old code that is known to have issues and nobody really volunteering to maintain it.
-
If you're primarily going to use LE, perhaps make a little effort to understand Games in Kodi.
