2017-07-27, 20:36
After # 0722, VU + Backend TV no longer works. Can someone help me?
Also the Fonts of CEC Eight Pulse is not visible.
Also the Fonts of CEC Eight Pulse is not visible.
(2017-07-27, 20:36)Cosmicbase Wrote: After # 0722, VU + Backend TV no longer works. Can someone help me?
(2017-07-27, 20:36)Cosmicbase Wrote: Also the Fonts of CEC Eight Pulse is not visible.
pvr.argustv
pvr.demo
pvr.filmon
pvr.hdhomerun
pvr.iptvsimple
pvr.mediaportal.tvserver
pvr.mythtv
pvr.nextpvr
pvr.njoy
pvr.pctv
pvr.stalker
pvr.vbox
pvr.vuplus
pvr.wmc
(2017-07-27, 20:36)Cosmicbase Wrote: Also the Fonts of CEC Eight Pulse is not visible.
# uname -a
Linux rpi512 4.12.3 #1 Thu Jul 27 21:21:16 BST 2017 armv6l GNU/Linux
# vcgencmd version
Jul 22 2017 00:01:46
Copyright (c) 2012 Broadcom
version f52771674311a841405cea05e8738a526dd60ee1 (clean) (release)
# lsb_release
LibreELEC (Milhouse): devel-20170727212009-#0727-gad01993 [Build #0727]
# Kodi version
(18.0-ALPHA1 Git:d5e502f). Platform: Linux ARM 32-bit
(2017-07-27, 20:44)Milhouse Wrote:(2017-07-27, 20:36)Cosmicbase Wrote: After # 0722, VU + Backend TV no longer works. Can someone help me?
Not without a debug log (wiki).
What "backend tv" ?
(2017-07-27, 20:36)Cosmicbase Wrote: Also the Fonts of CEC Eight Pulse is not visible.
You really don't have to mention this on every post. It's a known issue.
(2017-07-03, 09:22)Vimes Wrote:(2017-07-03, 02:24)Milhouse Wrote:(2017-07-02, 20:49)Vimes Wrote: Just had another one of those "Preparing...0%" type of issues.
It's caused by Kodi deadlocking while accessing smb:// (which in your case is being caused by a library scan) - some sort of race condition, perhaps.
Unfortunately I don't have a solution (other than not using smb:// at all).
Thanks.
If I had not pressed play on that TV show it would have stuck at preparing....0% without changing. I have menu access and normally I would just reboot it and that would sort things out. Accessing the library is the way to create tha tdeadlock and crash.
Thanks anyway. I suppose it is just an "SMB" thing
(2017-07-27, 23:26)Cosmicbase Wrote: I mean VU+/ enigma2 client. When I switch to a channel, the picture remains Black.
Because with #0722 everything is alright for me.
(2017-07-27, 23:32)Milhouse Wrote:(2017-07-27, 23:26)Cosmicbase Wrote: I mean VU+/ enigma2 client. When I switch to a channel, the picture remains Black.
Because with #0722 everything is alright for me.
Channel switching is now broken in most of the PVR addons, and following PR12552 in #0727 many PVR addons no longer build and have been dropped until they do.
You'll just have to wait until your addon is updated with PVR API 5.4.0 support. Feel free to open an issue on github: https://github.com/kodi-pvr/pvr.vuplus/commits/master
(2017-07-27, 23:27)Milhouse Wrote:(2017-07-03, 09:22)Vimes Wrote:(2017-07-03, 02:24)Milhouse Wrote: It's caused by Kodi deadlocking while accessing smb:// (which in your case is being caused by a library scan) - some sort of race condition, perhaps.
Unfortunately I don't have a solution (other than not using smb:// at all).
Thanks.
If I had not pressed play on that TV show it would have stuck at preparing....0% without changing. I have menu access and normally I would just reboot it and that would sort things out. Accessing the library is the way to create tha tdeadlock and crash.
Thanks anyway. I suppose it is just an "SMB" thing
This should be fixed in #0727
(2017-07-27, 22:53)Potze Wrote: I had a problem with my remote ( logitec harmony ):
After the build #713 the remote doesn't work anymore. I had tested much builds:
531: works
710: works
712: works
713: works
714: doesn't boot after update
715, 716, 720,726: no remote control
I hope this could help, if more information is needed, I will do my best.
Best wishes
(2017-07-24, 22:51)garbear Wrote:Ignore input doesn't work with the motion controllers, however mapping the buttons in kodi did work (although it's still telling me it is the player 2). I can't test retroplayer yet because the libretro compatibility seems to be incorrect... I posted this in the other thread!(2017-07-24, 19:17)linkinsoldier Wrote:(2017-07-24, 18:36)garbear Wrote: Definitely sounds like a bluetooth driver, but there's no reason we can't fix this in Kodi. Kodi should ignore the controller unless you've mapped it in the controller window. Is this the case?Nope, I actually select "no" when I was asked If I want to configure it (also deleted and tried yes but no change...). Side note: this message does only pop up with #714 or newer...
Any way we can assist more to find and fix this bug? Should we create a bug ticket (where?)?
That's what I mean, after you press "No", it will be safely ignored forever. Is the problem, then, that the real controller isn't working? Can you map this in the controller configuration window? Settings -> System -> Input -> Configure controllers.
BTW, if the motion controller interferes with mapping, you want to use the "Ignore Input" utility on the right of the controller window.