Login at Kodi Home

**Roby77** · (This post was last modified: 2018-04-30, 10:36 by Roby77.)

Tried to search but didn't find updatdd nfo,

See here that Milhouse says that something is changed

2700654 (post)

It's always for intel gpu best video setting for film mode

Kodi limited (16-235 activated) , gpu set in automatic and TV set in limited ?

(And check with Cal test clipping, gray scale ramp etc)

It's better to set gpu in full instead of automatic ? Or for intel full is default ?

Xrandr --verbose report gpu in Automatic

Xrandr --prop report gpu in full

sgamex · 2018-04-30, 12:35

I have a problem. I testet the Version from 428 and before. And i can't install any addon. It always says installation failed. And thats whit all addons i testet from the repos. Huh

What i doing wrong?

TheKraut · (This post was last modified: 2018-04-30, 20:41 by TheKraut.)

First of all, a big thank you to you guys for your hard work and commitment - especially @Milhouse for all the effort he puts into his daily builds!

I'm currently running the alpha builds on a brand-new Intel NUC7CJYH. Unfortunately, I've come across a minor nuisance: IR remote control with my Logitech Harmony 350 stops working, usually after 10 to 50 key presses. When I SSH into the system, irw output stops at the same time.

Remote control via Yatse still works perfectly afterwards. I've tested various builds between #0405 and #0429, but the problem persists. A reboot solves the problem, just for the game to begin again after a couple of key presses.

To cross check, I ran Ubuntu 18.04 LTS from a pen drive, and observed the very same behavior. Interestingly, when I created a #04050429 bootable disk, remote control works perfectly fine within the LE installer, so my educated guess is that the issue is not hardware related.

Any chance that this problem is linked to the MCE patches that were included in the latest 8.2.5 MR build?

Sorry for not providing any logs at this point - I'm not sure which of them may be relevant and I'll have to sanitize some of them first...

Thanks again for your great effort!

[Edit] KODI debug log from #0429 live
[Edit] System debug log from #0429 live
[Edit] Hardware debug log from #0429 live

jeinnor · 2018-04-30, 18:13

I submitted 2 logs via Libreelec as Libreelec went into safe mode because it crashed too many times and said that I needed to. the numbers were 1975 and 1976 respectively. Basically as soon as I run profiles with the latest updates from #0424 onwards, this problem occurs.

**Milhouse** · 2018-04-30, 18:57

(2018-04-30, 18:13)jeinnor Wrote: I submitted 2 logs via Libreelec as Libreelec went into safe mode because it crashed too many times and said that I needed to. the numbers were 1975 and 1976 respectively. Basically as soon as I run profiles with the latest updates from #0424 onwards, this problem occurs.

http://ix.io/1975 isn't a LibreELEC log.

Did you mean:

crash log: http://ix.io/1974
kodi log: http://ix.io/1976

?

It looks like a Python issue - the Python reuse optimisation doesn't appear to play well with Profiles.

HiassofT · 2018-04-30, 19:28

(2018-04-30, 16:13)TheKraut Wrote: Remote control via Yatse still works perfectly afterwards. I've tested various builds between #0405 and #0429, but the problem persists. A reboot solves the problem, just for the game to begin again after a couple of key presses.

To cross check, I ran Ubuntu 18.04 LTS from a pen drive, and observed the very same behavior. Interestingly, when I created a #0405 bootable disk, remote control works perfectly fine within the LE installer, so my educated guess is that the issue is not hardware related.

So does this mean #0405 in "Live Mode" from the bootable disk works fine, but when you install #0405 on your NUC it doesn't work?

If yes, do you have any manually setup config files (autostart.sh, lircd.conf, rc_maps.cfg, kodi advancesettings.xml etc) on your system?

so long,

Hias

jeinnor · 2018-04-30, 20:28

(2018-04-30, 18:57)Milhouse Wrote:
(2018-04-30, 18:13)jeinnor Wrote: I submitted 2 logs via Libreelec as Libreelec went into safe mode because it crashed too many times and said that I needed to. the numbers were 1975 and 1976 respectively. Basically as soon as I run profiles with the latest updates from #0424 onwards, this problem occurs.

http://ix.io/1975 isn't a LibreELEC log.

Did you mean:

crash log: http://ix.io/1974
kodi log: http://ix.io/1976

?

It looks like a Python issue - the Python reuse optimisation doesn't appear to play well with Profiles.

Yes, sorry, thought I saw 1975 ;-)

Is there any way of fixing this? I need profiles as I have 2 young boys and I like to keep the stuff seperate so that they cant watch stuff that is not age appropriate.

TheKraut · (This post was last modified: 2018-04-30, 20:46 by TheKraut.)

(2018-04-30, 19:28)HiassofT Wrote:
(2018-04-30, 16:13)TheKraut Wrote: Remote control via Yatse still works perfectly afterwards. I've tested various builds between #0405 and #0429, but the problem persists. A reboot solves the problem, just for the game to begin again after a couple of key presses.

To cross check, I ran Ubuntu 18.04 LTS from a pen drive, and observed the very same behavior. Interestingly, when I created a #04050429 bootable disk, remote control works perfectly fine within the LE installer, so my educated guess is that the issue is not hardware related.
So does this mean #0405 in "Live Mode" from the bootable disk works fine, but when you install #0405 on your NUC it doesn't work?

If yes, do you have any manually setup config files (autostart.sh, lircd.conf, rc_maps.cfg, kodi advancesettings.xml etc) on your system?

so long,

Hias

Hi Hias,

Sorry, I got the version wrong in the last sentence you quoted. Let me just briefly summarize my long post:

- RC not working: LE #0405, #0429 (and a couple of versions in between) when installed
- RC not working: LE #0429 when run in live mode (KODI log in my original post above; didn't bother to test any other version)
- RC not working: Ubuntu 18.04 LTS in live mode
- RC working: #0429 when booting to text-based installer

By "not", I mean more specifically: It is working for a seemingly random, double digit number of key presses after a reboot. Then, it ceases to work.

No manual config files in either configuration.

I was guessing on a kernel problem with 4.14/4.15. However, given that the installer works fine, it may well be UI related (and shouldn't be hardware related, I presume).

Let me know if you need any more logs.

Nekromantik · 2018-04-30, 21:10

@Milhouse crash happened again where it freezes
crash log does not contain anything after 3pm and now currently 8pm here.
Kodi log is only thing thats got something in it and here it is:

https://pastebin.com/vTin7Zah

**Milhouse** · 2018-04-30, 21:13

(2018-04-30, 20:28)jeinnor Wrote:
(2018-04-30, 18:57)Milhouse Wrote:
(2018-04-30, 18:13)jeinnor Wrote: I submitted 2 logs via Libreelec as Libreelec went into safe mode because it crashed too many times and said that I needed to. the numbers were 1975 and 1976 respectively. Basically as soon as I run profiles with the latest updates from #0424 onwards, this problem occurs.

http://ix.io/1975 isn't a LibreELEC log.

Did you mean:

crash log: http://ix.io/1974
kodi log: http://ix.io/1976

?

It looks like a Python issue - the Python reuse optimisation doesn't appear to play well with Profiles.
Yes, sorry, thought I saw 1975 ;-)

Is there any way of fixing this? I need profiles as I have 2 young boys and I like to keep the stuff seperate so that they cant watch stuff that is not age appropriate.

Remember these are test builds, so occasional instability is to be expected - if you need stability over features then release builds would be my recommendation. That said I/we appreciate the testing you all do which probably wouldn't happen if these builds weren't being used as daily drivers so for the time being it might be best if you stick with #0421 until the Python/Profile issues are solved (I've pinged the developer).

**Milhouse** · 2018-04-30, 21:15

(2018-04-30, 21:10)Nekromantik Wrote: @Milhouse crash happened again where it freezes
crash log does not contain anything after 3pm and now currently 8pm here.
Kodi log is only thing thats got something in it and here it is:

https://pastebin.com/vTin7Zah

When it crashes are you able to ping the PC, connect with ssh etc.?

Nekromantik · 2018-04-30, 21:18

(2018-04-30, 21:15)Milhouse Wrote:
(2018-04-30, 21:10)Nekromantik Wrote: @Milhouse crash happened again where it freezes
crash log does not contain anything after 3pm and now currently 8pm here.
Kodi log is only thing thats got something in it and here it is:

https://pastebin.com/vTin7Zah

When it crashes are you able to ping the PC, connect with ssh etc.?

Yup
I can ssh in and browse it via NFS but mouse and remote dont work. So cant stop or rewind or press back, The actual Kodi UI freezes.

**Milhouse** · 2018-04-30, 21:22

(2018-04-30, 21:18)Nekromantik Wrote: Yup
I can ssh in and browse it via NFS but mouse and remote dont work. So cant stop or rewind or press back, The actual Kodi UI freezes.

It's most likely a deadlock bug in Kodi. Next time it happens if you execute kill -SIGSEGV $(pidof kodi.bin) it should crash Kodi and produce a crash log that might then give some clues.

Nekromantik · 2018-04-30, 22:58

(2018-04-30, 21:22)Milhouse Wrote:
(2018-04-30, 21:18)Nekromantik Wrote: Yup
I can ssh in and browse it via NFS but mouse and remote dont work. So cant stop or rewind or press back, The actual Kodi UI freezes.

It's most likely a deadlock bug in Kodi. Next time it happens if you execute kill -SIGSEGV $(pidof kodi.bin) it should crash Kodi and produce a crash log that might then give some clues.

ok thanks will try that next time it happens and upload crash log.

Nekromantik · 2018-04-30, 23:25

(2018-04-30, 21:22)Milhouse Wrote:
(2018-04-30, 21:18)Nekromantik Wrote: Yup
I can ssh in and browse it via NFS but mouse and remote dont work. So cant stop or rewind or press back, The actual Kodi UI freezes.

It's most likely a deadlock bug in Kodi. Next time it happens if you execute kill -SIGSEGV $(pidof kodi.bin) it should crash Kodi and produce a crash log that might then give some clues.

Happened again
Did the above and it produced crash log: https://pastebin.com/HSFeMXAr