Posts by jmooremcc

    I believe I may have found the cause of the problem.

    One of my Python reference books made the following statement:


    "The locale must be installed on the OS, otherwise setlocale raises a locale Error: unsupported locale setting exception."

    From: Ramalho, Luciano. Fluent Python: Clear, Concise, and Effective Programming (p. 130). O'Reilly Media. Kindle Edition.

    So I'm hypothesizing that the locale must not be installed in LE version 9.1.002.

    chewitt, If my hypothesis is correct, is there anything I can do to fix the problem short of recompiling?

    I've written a kodi add-on that successfully runs under LE 8.2.5 and under Kodi Leia running on a windows 10 computer. However, when I run my add-on using LE version 9.1.002 on a Raspberry Pi 2, I get the following error:

    This is the code snippet from the module that produced the error:

    from datetime import datetime, timedelta
    import locale
    __Version__ = "1.1.0"
    locale.setlocale(locale.LC_ALL, '')

    This is the same code that's found in the locale documentation found here.

    import locale
    locale.setlocale(locale.LC_ALL, '')

    I've never seen this error under any other OS running my add-on and am really puzzled why it's happening.

    Does anyone have any suggestions on how to fix this problem?

    I think I have resolved my issue with Leia by eliminating the advancedsettings.xml file that was inherited from Krypton. So far, the sluggishness I was experiencing appears to have gone away. However, I'm still having a problem with the screen going black or freezing for 4 to 8 seconds when changing a channel. Has anyone else experienced this problem?

    Kodi Leia runs poorly compared to Krypton on my Raspberry Pi 2. Specifically it appears to run sluggishly when playing live TV using nextPVR. I've encountered the following problems with LE 9.0.2 (Kodi Leia 18.2):

    1. The initial problem I encountered was the screen going black when changing channels. I resolved this issue by getting rid of all overclocking code in my config.txt file.
    2. The next problem I encountered was the video skipping frames in order to maintain sync. I partially resolved this issue, but not to my satisfaction, by turning off de-interlacing under video settings.
    3. Another problem I encountered was the audio being out of sync with the video. This problem is intermittent and I have not found a permanent solution to the issue.
    4. When changing channels, the screen will freeze or go black for a good 8 seconds while the audio is playing and then suddenly jump to the video syncing with the audio.
    5. Finally I my system would crash whenever I attempted to perform time shifting. This turned out to be an issue with a setting in the nextPVR add-on.

    I've used two different methodologies to create my system files:

    (1) Clean install of LE version 9.02 using LE USB-SD Creator. After an initial setup, I restored from a backup created by the current version of LE 8.2.5.

    (2) Clean install of LE version 8.2.5 using LE USB-SD Creator. After an initial setup, I restored from a backup created by my current version of LE 8.2.5. After verifying that everything was working properly, I upgraded the system to LE version 9.0.2.

    Note: Both systems are licensed to use the Pi's hardware MPEG2 decoder.

    Has anyone else experienced similar problems running Leia on a Raspberry Pi 2 or higher?

    I re-imaged my sdcard and the stuttering during playback has gone away. However, while watching live TV, anytime I click a button on my remote the screen goes black and the audio stops playing. The screen also goes black when I remotely change the channel using JSONPRC.

    Anyone have any idea why this is happening and what can be done to fix it?

    I don't have this problem with LE v8.25.

    LE9 Kodi.Log

    I've just installed LE 9.0 Kodi Leah V18 on my Raspberry Pi 2. I'm using NextPVR for my Live TV functionality. I can playback recordings OK, however, I've encountered numerous problems watching live TV including stuttering video and large audio offsets. The screen also goes black when I click any buttons on my remote.

    Has anyone else experienced similar problems? If so, how did you resolve them?

    Any advice will be greatly appreciated.


    I'm attempting to build Version 8.2.5 on a Ubuntu 18.04.1 LTS (GNU/Linux 4.15.0-43-generic i686) system.

    I've followed the instructions to compile the code found on this website but I get the following errors:

    From the research I've done, it appears that the problem may be related to the following comment I found in the glob.c file:

    If I should be using the glob function from the GNU C Library instead of compiling glob.c, how would I make that happen?

    Or if I have to compile the glob.c file, how would I reconcile the reference to the __alloca function?

    The command I used to compile was:


    PROJECT=RPi2 ARCH=arm CUSTOM_VERSION="JM_8.2.5" make image

    I've also attached my logs for your inspection:



    Thank you in advance for your assistance.

    I too have a similar problem compiling 8.2.5. I'm getting the following errors:

    If anyone has any suggestions on how to resolve these issues, I would appreciate it.

    I've loaded this release on my RPi2. Whenever I try to restore my backup from 8.2.5, it appears to go OK but when it reboots, the restore has not taken place and the initial setup screen appears.

    Also when it does run, the audio is out of sync with the video.

    Anyone know what's happening and can anyone suggest any work arounds for this problem?

    I have two RPi2s and both exhibit the same problem when watching live TV. I'm using the NextPVR addon to connect to a backend NPVR server running on a Windows 10 desktop computer.

    In the first case, after watching live TV for up to 6 hours, the stream will suddenly freeze.

    Attached is the Kodi Log for this problem:

    Please note the following in the log file:

    18:20:20.130 T:1323352992 NOTICE: CVideoPlayerAudio::Process - stream stalled
    18:20:20.911 T:1331741600 INFO: CVideoPlayerVideo - Stillframe detected, switching to forced 29.970030 fps
    18:20:20.912 T:1331741600 DEBUG: CPullupCorrection: pattern lost on diff 166833.333344, number of losses 4
    18:20:22.755 T:1331741600 INFO: CVideoPlayerVideo - Stillframe left, switching to normal playback
    18:20:22.757 T:1722024864 DEBUG: Stream stalled, start buffering. Audio: 0 - Video: 0

    In the 2nd case, I've been using JSON RPC to remotely change the Live TV channels and periodically after a channel change, Kodi will freeze.

    Attached is the Kodi Log for this problem:

    Please note the following in the log file:

    19:59:54.177 T:1722233760 DEBUG: PVRManager - PerformChannelSwitch - switching to channel 'H & I'
    19:59:54.177 T:1722233760 DEBUG: AddOnLog: NextPVR PVR Client: SwitchChannel(10:H & I)
    19:59:54.177 T:1722233760 DEBUG: AddOnLog: NextPVR PVR Client: OpenLiveStream(10:H & I) (oid=7894)
    19:59:54.177 T:1722233760 DEBUG: AddOnLog: NextPVR PVR Client: OpenLiveStream() informing NextPVR of existing channel stream closing
    19:59:54.291 T:1243607968 INFO: CFileCache::Process - Source read didn't return any data! Hit eof(?)
    19:59:57.270 T:1722233760 NOTICE: PVRManager - PerformChannelSwitch - switched to channel 'H & I'

    In both cases, the RPi2 is still running and I'm able to log in to it using SSH.

    I've not been able to figure out why this is happening and would appreciate any help anyone can offer.

    Thank you in advance.

    The PSU is a CanaKit 5V 2.5A Raspberry Pi 3 B+ Power Supply / Adapter (UL Listed)

    I've attached the kodi log that was generated after the reboot.

    I have 4 crash logs that were generated on 11/9/18. I will attach 2 more for your review.

    If there are any settings that you could recommend that would improve the information in the log files, please let me know.

    My RPi crashes randomly and reboots. I saved a crash log that recently occurred while the RPi was essentially idle.

    The log indicated the following:


    Using host libthread_db library "/usr/lib/".

    Core was generated by `/usr/lib/kodi/kodi.bin --standalone -fs --lircdev /run/lirc/lircd'.

    Program terminated with signal SIGSEGV, Segmentation fault.

    #0 0x76f31b64 in memcmp () from /usr/lib/


    Is this a problem with /usr/lib/ If so, what can be done to fix it?

    I'm attaching the entire crash log for reference.


    • kodi_crash.log

      (366.87 kB, downloaded 191 times, last: )

    The LE staff have a generally low opinion on Realtek wireless devices. The hardware is probably reasonable, and performance on Windows is probably great because that's where they invest all the Engineering time. Their Linux drivers are an afterthought, and we're fed up with they way they breed chipsets and new drivers that rehash the same greatest-hits compilation of hacks over and over.

    Find something that uses the ath9k driver, which is in-kernel and much higher quality code.

    I've been unable to find a USB WiFI dongle that utilizes the ath9k driver and works with the 802.11ac standard. Everything I've found so far only meets the 802.11n standard and is not compatible with the 802.11ac standard.

    For those of us who are using a Raspberry Pi and want to use the 5G band because there's less interference with other WiFI devices, it appears that Realtec devices are our only choice.

    So chewitt, are you saying that the Edimax EW-7811UTC wifi dongle isn't any good?

    Amazon users give it 3.7 stars out of 5 and New Egg users gives it 4 eggs out of 5.

    So what do you recommend that will provide superior performance and can co-exist in an environment that has multiple channels with the same SSID?

    I thought I would share my experience with everyone about using an ac600 wifi dongle with a raspberry Pi. I have multiple Raspberry Pi systems ranging from the PI1 to a PI2 running version 8.2.5. I have to confess that I got very frustrated dealing with the problems I was experiencing. I even bought a new router, a tri-band EA9300 by Linksys, capable of handling 4k streaming data and my RPi2 was still having great difficulty connecting.

    Whenever I would try to connect to one of 5G channels, the PI2 would refuse to connect. So in frustration I decided to try the 2.4G channel. I put in the passphrase and everything was working just fine. But 10 minutes later, Kodi indicated that the connection had dropped and when I tried to re-establish the connection, the passphrase field was blank and required me to re-enter the passphrase once again. I tried over and over again to enter the passphrase only to have to repeat the process 10 minutes later.

    As it turns out, the drivers used by LE on the RPi aren't sophisticated enough to deal with a network with identical SSIDs and I have more than one router with the same SSID. I changed the SSID of the 2.4G channel on the new router and was then able to connect successfully without the connection dropping.

    With that success, I decided to try the 5G channel again. Unfortunately, the same problems surfaced again. I then realized that the EA9300, a tri-band router, gave both of its 5G channels the same SSID. So once again, the drivers in LE had problems connecting. I turned off the fancy "5GHz steering mode" on the router which allowed me to name each of the 5G channels individually. I was then able to connect to any of the available 5G channels with no problem.

    So the moral of the story is that if you use multiple SSIDs with Kodi boxes powered by a Raspberry Pi, make sure that the SSIDs are uniquely named so that you can avoid the conflicts I ran into.

    Nope. Our default config is wide open. It will change in LE9 so iptables restricts inbound connections to RFC1918 networks, but that still wouldn't explain why you cannot connect from a local network.

    Hi chewitt,

    I finally figured out what was going on. The Python interpreter in LE does not recognize the hostname 'localhost'. In my test script, changing host='localhost' to host='' fixes the problem.

    My Windows version of Python 2.7 does not suffer from this problem. Yes, I can successfully ping 'localhost' from the command line but binding a socket with 'localhost' causes the connection refused error problem I reported.