Quote:10:34:41 T:140017228158720 ERROR: EXCEPTION Thrown (PythonToCppException) : -->Python callback/script returned the following error<--
- NOTE: IGNORING THIS CAN LEAD TO MEMORY LEAKS!
Error Type: <type 'exceptions.KeyError'>
Error Contents: ('likeCount',)
Traceback (most recent call last):
File "/home/kodi/.kodi/addons/script.extendedinfo/plugin.py", line 91, in <module>
Main()
File "/home/kodi/.kodi/addons/script.extendedinfo/plugin.py", line 21, in __init__
start_info_actions(self.infos, self.params)
File "/home/kodi/.kodi/addons/script.extendedinfo/resources/lib/process.py", line 249, in start_info_actions
orderby=params.get("orderby", "relevance"))
File "/home/kodi/.kodi/addons/script.extendedinfo/resources/lib/YouTube.py", line 137, in search_youtube
videos = handle_youtube_videos(results["items"], extended=True)
File "/home/kodi/.kodi/addons/script.extendedinfo/resources/lib/YouTube.py", line 50, in handle_youtube_videos
item["likes"] = ext_item['statistics']['likeCount']
KeyError: ('likeCount',)
-->End of Python script error report<--
10:34:41 T:140017030252288 ERROR: GetDirectory - Error getting plugin://script.extendedinfo/?info=youtubesearch&&id="The Train Job" TV show
Fix this please and provide another
Debug Log
No idea - I just returned from a business trip and did not follow code changes the last two days ... let's wait for @
FernetMenta.
I've been testing these dev builds on my Braswell NUC using the OpenELEC images, however I stopped updating back before video passthrough was added because you mentioned no longer including the Kernel fix for Braswell.
I completely understand not wanting to waste time continually patching kernels, however do the newest OpenELEC images have a new enough kernel that the Braswell fix is no longer needed? Or to put the question another way, is there any way I can help test these newer builds using the OpenELEC images and my Braswell NUC?
Thanks for all of your hard work so far. It was certainly a relief to see someone supporting these chips, now that Intel has semi-officially claimed they have no plans to support them in Windows for High-Res Audio Passthrough.
(2015-10-11, 19:15)fritsch Wrote: [ -> ]Use team kodi ppa instead of fernetmenta. Pvr addons are packacked by wsnipex for this howto here, so they actually are compatible.
Yeah, after updating today nothing works. Are the fernetmenta builds just nightlies of the 16.0 alpha?
I didn't realize I was getting myself into alpha testing with this install. I have reverted to the team-xbmc ppa.
Having a TV system that doesn't work 100% of the time can be harmful to the relationship with the significant other :p
(2015-10-15, 23:47)EXT64 Wrote: [ -> ]I've been testing these dev builds on my Braswell NUC using the OpenELEC images, however I stopped updating back before video passthrough was added because you mentioned no longer including the Kernel fix for Braswell.
I completely understand not wanting to waste time continually patching kernels, however do the newest OpenELEC images have a new enough kernel that the Braswell fix is no longer needed? Or to put the question another way, is there any way I can help test these newer builds using the OpenELEC images and my Braswell NUC?
Thanks for all of your hard work so far. It was certainly a relief to see someone supporting these chips, now that Intel has semi-officially claimed they have no plans to support them in Windows for High-Res Audio Passthrough.
Openelec builds never had any bsw kernel fixes. They will come after kernel 4.3 is out. Those patched kernels were done for Ubuntu only.
BTW. latest ppa from today and oe image from yesterday work fine again. Vaapi was broken cause of an off by one error.
(2015-10-16, 06:21)mattlach Wrote: [ -> ] (2015-10-11, 19:15)fritsch Wrote: [ -> ]Use team kodi ppa instead of fernetmenta. Pvr addons are packacked by wsnipex for this howto here, so they actually are compatible.
Yeah, after updating today nothing works. Are the fernetmenta builds just nightlies of the 16.0 alpha?
I didn't realize I was getting myself into alpha testing with this install. I have reverted to the team-xbmc ppa.
Having a TV system that doesn't work 100% of the time can be harmful to the relationship with the significant other :p
Yeah, see the second post of this thread. You are a tester not a customer. Ppa is fixed again.
@
fritsch how do you think the addons should be fixed, should the linux version probe for gl/gles runtime (will there be symbol conflicts if we link both, should it be lazy linked?) or should there be a dedicated build. i'm leaning towards the first if at all doable..
If the first can be done - this would be great of course.
In the concrete case here I think a simple recompile and linker fix would make that work again. Though projectm is a beast - OE alone carries multiple patches to get it running at all ..
yes, relink et al is basically option 2. but fundamentally there will be a glx vs egl and gl vs gles need in all rendering addons eventually.
(2015-10-16, 08:08)fritsch Wrote: [ -> ]Openelec builds never had any bsw kernel fixes. They will come after kernel 4.3 is out. Those patched kernels were done for Ubuntu only.
Ah, well in that case I might as well get back on testing the newest images.
(2015-10-12, 21:41)icebaer Wrote: [ -> ]Yes, no debug log no help. You're right ;o)
Here we go.... hopefully....
kodi.log > http://paste.ubuntu.com/12765890/
mesa > http://paste.ubuntu.com/12765877/
dmesg > http://paste.ubuntu.com/12765892/
xrandr > http://paste.ubuntu.com/12765896/
Been playing two other files now. Both normally play fine in 24p.
I have exactly the sam issue. It seems it is xorg / intel driver related. I have added this as a first line to my .xinitrc:
Code:
(LC_ALL=EN /usr/bin/date ; /usr/bin/xrandr ; /usr/bin/sleep 15 ; LC_ALL=EN /usr/bin/date ; /usr/bin/xrandr ) > ~/xrandr.log &
and guess what:
Code:
Fri Oct 16 14:56:48 CEST 2015
Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767
DP1 disconnected (normal left inverted right x axis y axis)
DP2 disconnected (normal left inverted right x axis y axis)
HDMI1 disconnected (normal left inverted right x axis y axis)
HDMI2 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 1600mm x 900mm
1920x1080 60.00*+
VGA1 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)
Fri Oct 16 14:57:03 CEST 2015
Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767
DP1 disconnected (normal left inverted right x axis y axis)
DP2 disconnected (normal left inverted right x axis y axis)
HDMI1 disconnected (normal left inverted right x axis y axis)
HDMI2 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 1600mm x 900mm
1920x1080 60.00*+ 50.00 59.94 30.00 25.00 24.00 29.97 23.98
1920x1080i 60.00 50.00 59.94
1280x1024 60.02
1360x768 60.02
1152x864 59.97
1280x720 60.00 50.00 59.94
1024x768 60.00
800x600 60.32
720x576 50.00
720x576i 50.00
720x480 60.00 59.94
640x480 60.00 59.94
720x400 70.08
VGA1 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)
When the sleep time is less than 15s it reports just one mode.
(2015-10-16, 15:13)Ales Wrote: [ -> ]I have exactly the sam issue.
Since this most likely not related to this VAAPI version, we may continue with this, in
this new thread.
And hopefully find a solution
(2015-10-16, 08:10)fritsch Wrote: [ -> ] (2015-10-16, 06:21)mattlach Wrote: [ -> ] (2015-10-11, 19:15)fritsch Wrote: [ -> ]Use team kodi ppa instead of fernetmenta. Pvr addons are packacked by wsnipex for this howto here, so they actually are compatible.
Yeah, after updating today nothing works. Are the fernetmenta builds just nightlies of the 16.0 alpha?
I didn't realize I was getting myself into alpha testing with this install. I have reverted to the team-xbmc ppa.
Having a TV system that doesn't work 100% of the time can be harmful to the relationship with the significant other :p
Yeah, see the second post of this thread. You are a tester not a customer. Ppa is fixed again.
@
fritsch - installed the new updates this morning. Everything is back to normal. Thanks!