+- Forum (http://forum.xbian.org)
+-- Forum: Software (/forum-6.html)
+--- Forum: Testing & Experimental (/forum-21.html)
+--- Thread: Kodi v18 (Leia) testbuilds (/thread-3962.html)
RE: Kodi v18 (Leia) testbuilds - dgarciam - 19th Sep, 2018 01:57 PM
So, now we are at beta 1. This is normally when i pick stuff up.
What are the annoying hellish behavior that you had come to expect and love from beta 1?
Thanks,
Dan.-
RE: Kodi v18 (Leia) testbuilds - bluecherry - 17th Oct, 2018 07:27 AM
Software
XBian version: XBian_Latest_rpi3.img.gz
XBMC/Kodi version: 17
Overclock settings: None?
Hardware
Device type and model: Raspberry Pi 2 Model B Desktop (Quad Core CPU 900 MHz, 1 GB RAM)
Power supply rating: Kootek® Micro USB Power Supply Wall Charger AC Adapter for Raspberry Pi 2 Model B+ B Plus - 5V 2A 6.5Ft
SD card size and make/type: SanDisk Ultra 32GB UHS-I/Class 10 Micro SDHC
Network (Ethernet or wireless): Ethernet
Connected devices (TV, USB, network storage, ...): TV
Problem description:
I downloaded the XBian-installer.exe for windows. Ran the installer, plug the SD card into the Pi, boot from the SDcard. Xbian/Kodi loads fine, go through the setup wizard. Enable the devel repo, refresh the package list, and install all the upgrades. The box pops up and says a reboot is required.
I reboot and the xbian loading screen is stuck on "loading" with no further progress. I'm unable to ssh to pull any logs. Rebooting produces the same result. The only solution is to re-image the SDcard with XBian_Latest_rpi3.img.gz and use Kodi 17.
I'd like to try Kodi 18, but no matter what I try it gets stuck on the "loading" screen after enabling devel and installing the updates.
How to reproduce:
See above.
RE: Kodi v18 (Leia) testbuilds - Nachteule - 17th Oct, 2018 07:38 AM
@bluecherry
Could you please update xbian-package-xbmc only?
And after restart Kodi, disable devel repo again
RE: Kodi v18 (Leia) testbuilds - bluecherry - 17th Oct, 2018 08:20 AM
(17th Oct, 2018 07:38 AM)Nachteule Wrote: @bluecherry
Could you please update xbian-package-xbmc only?
And after restart Kodi, disable devel repo again
Yes, no problem. So you want me to re-image the SD card, boot into Kodi 17, enable devel repo in the GUI and then update xbian-package-xbmc from the CLI? What is the command(s) to do so? My CLI skills are a work in progress.
RE: Kodi v18 (Leia) testbuilds - Nachteule - 17th Oct, 2018 08:23 AM
sudo apt-get update;sudo apt-get install xbian-package-xbmc;kodi stop;kodi start
Edit:
Just did it, flashed latest image and installed xbian-package-xbmc from devel repo (see above). Works
Have to figure out next days which package(s) is/are the culprit in devel repo
RE: Kodi v18 (Leia) testbuilds - bluecherry - 17th Oct, 2018 08:53 AM
(17th Oct, 2018 08:23 AM)Nachteule Wrote: Just did it, flashed latest image and installed xbian-package-xbmc from devel repo (see above). Works
Yes, can confirm works great for me too! Thank you so much!
RE: Kodi v18 (Leia) testbuilds - Nachteule - 17th Oct, 2018 08:53 AM
(17th Oct, 2018 08:53 AM)bluecherry Wrote:(17th Oct, 2018 08:23 AM)Nachteule Wrote: Just did it, flashed latest image and installed xbian-package-xbmc from devel repo (see above). Works
Yes, can confirm works great for me too! Thank you so much!
You're welcome
RE: Kodi v18 (Leia) testbuilds - dgarciam - 31st Jan, 2019 06:21 AM
After today's final release, when should be expect Kodi v18 final hit the stable repo?
RE: Kodi v18 (Leia) testbuilds - Nachteule - 31st Jan, 2019 06:25 AM
Kodi 18.0 final is still available in staging repo only, packages were built yesterday. If you don't want to wait, you just have to enable staging repository
It will be moved into stable repo probably at next weekend
RE: Kodi v18 (Leia) testbuilds - dgarciam - 31st Jan, 2019 07:02 AM
Found it! Thanks!
Package: xbian-package-xbmc
Version: 18.0-1548726528
RE: Kodi v18 (Leia) testbuilds - dgarciam - 1st Feb, 2019 11:31 AM
This is weird. I did a fresh flash on SD card, updated just the xbmc package on stage repo, and all boots fine. But when i enable remote control, i get a message "failed to start" and everything freezes. Have to get into the box via ssh, restart the service and everything is disabled again.
Have you had this experience?
(31st Jan, 2019 06:25 AM)Nachteule Wrote: Kodi 18.0 final is still available in staging repo only, packages were built yesterday. If you don't want to wait, you just have to enable staging repository
It will be moved into stable repo probably at next weekend
RE: Kodi v18 (Leia) testbuilds - Nachteule - 1st Feb, 2019 12:05 PM
(1st Feb, 2019 11:31 AM)dgarciam Wrote: This is weird. I did a fresh flash on SD card, updated just the xbmc package on stage repo, and all boots fine. But when i enable remote control, i get a message "failed to start" and everything freezes. Have to get into the box via ssh, restart
What is meant by 'remote control'
Quote:the service and everything is disabled again.
Have you had this experience?
No, I'm using Kodi Leia for months on 3 Pi's (2x Pi1, 1x Pi3 and 1x Pi3B+)
RE: Kodi v18 (Leia) testbuilds - dgarciam - 1st Feb, 2019 01:22 PM
(1st Feb, 2019 12:05 PM)Nachteule Wrote:(1st Feb, 2019 11:31 AM)dgarciam Wrote: This is weird. I did a fresh flash on SD card, updated just the xbmc package on stage repo, and all boots fine. But when i enable remote control, i get a message "failed to start" and everything freezes. Have to get into the box via ssh, restart
What is meant by 'remote control'
Quote:the service and everything is disabled again.
Have you had this experience?
No, I'm using Kodi Leia for months on 3 Pi's (2x Pi1, 1x Pi3 and 1x Pi3B+)
In this setting page: Kodi Remote Control when i go to enable the last option: "Allow remote control from applications on other systems", so i can use Yatse from my cellular phone, i get the error that says that "Remote Communications Server" failed to start
(1st Feb, 2019 01:22 PM)dgarciam Wrote:(1st Feb, 2019 12:05 PM)Nachteule Wrote:(1st Feb, 2019 11:31 AM)dgarciam Wrote: This is weird. I did a fresh flash on SD card, updated just the xbmc package on stage repo, and all boots fine. But when i enable remote control, i get a message "failed to start" and everything freezes. Have to get into the box via ssh, restart
What is meant by 'remote control'
Quote:the service and everything is disabled again.
Have you had this experience?
No, I'm using Kodi Leia for months on 3 Pi's (2x Pi1, 1x Pi3 and 1x Pi3B+)
In this setting page: Kodi Remote Control when i go to enable the last option: "Allow remote control from applications on other systems", so i can use Yatse from my cellular phone, i get the error that says that "Remote Communications Server" failed to start
This is an extract from kodi.log:
Terminal
01:26:56.977 T:1548956032 ERROR: CVideoPlayer::OpenInputStream - error opening [/run/lirc/lircd]
01:26:56.977 T:1548956032 NOTICE: CVideoPlayer::OnExit()
01:26:57.489 T:1848279664 NOTICE: CVideoPlayer::CloseFile()
01:26:57.489 T:1848279664 NOTICE: VideoPlayer: waiting for threads to exit
01:26:57.489 T:1848279664 NOTICE: VideoPlayer: finished waiting
01:26:57.550 T:1848279664 WARNING: OnMessage: Suspiciously long time to handle GUI_MSG_PLAYBACK_STARTED (0.26s)
01:27:55.115 T:1848279664 NOTICE: CWebServer[8080]: Started
01:28:05.544 T:1848279664 NOTICE: ES: Stopping event server with confirmation
01:28:05.903 T:1583870336 NOTICE: ES: UDP Event server stopped
01:28:05.904 T:1729511808 NOTICE: ES: Starting UDP Event server on port 9777
01:28:05.975 T:1848279664 ERROR: JSONRPC Server: Failed to connect to sdpd
01:28:05.984 T:1848279664 ERROR: JSONRPC Server: Failed to create serversocket(s)
01:28:22.861 T:1848279664 ERROR: Create - fatal error creating thread EventServer - old thread id not null
I'll enable detailed logs, and try again to see what I get
This time, i erased the old .log files, and enabled debug level log.
Repeted the process, got the error dialog shown here:
After i clicked it to go away, I noticed that it appeared enabled, so I went to Yatse and tried to add the server again and it rebooted.
Then i went to check the logs and got obviously a lot of info. Eliminated all the lines with "CLibInputPointer::ProcessMotion" , "event.button.button:" and "debounce state:", since they appear to be information about the position of the mouse, and now will copy the last copied the events until i think is the moment i got into the page:
Terminal
03:31:51.238 T:1848889968 DEBUG: ------ Window Deinit (Settings.xml) ------
03:31:51.238 T:1848889968 DEBUG: FreeVisualisation() done
03:31:51.265 T:1848889968 DEBUG: ------ Window Init (SettingsCategory.xml) ------
03:31:51.266 T:1848889968 DEBUG: Window SettingsCategory.xml was already loaded
03:31:51.266 T:1848889968 DEBUG: Alloc resources: 0.71ms
03:31:58.965 T:1848889968 DEBUG: ProcessMouse: trying mouse action leftclick
03:31:58.966 T:1848889968 NOTICE: ES: Stopping event server with confirmation
03:31:59.938 T:1575743872 NOTICE: ES: UDP Event server stopped
03:31:59.938 T:1575743872 DEBUG: Thread EventServer 1575743872 terminating
03:31:59.938 T:1705783680 DEBUG: Thread EventServer start, auto delete: false
03:31:59.938 T:1705783680 NOTICE: ES: Starting UDP Event server on port 9777
03:31:59.950 T:1567355264 DEBUG: Thread TCPServer 1567355264 terminating
03:31:59.951 T:1848889968 ERROR: JSONRPC Server: Failed to connect to sdpd
03:31:59.955 T:1848889968 DEBUG: JSONRPC Server: Failed to bind IPv4 serversocket
03:31:59.958 T:1848889968 ERROR: JSONRPC Server: Failed to create serversocket(s)
03:31:59.958 T:1848889968 DEBUG: ------ Window Init (DialogConfirm.xml) ------
03:31:59.959 T:1848889968 DEBUG: Window DialogConfirm.xml was already loaded
03:31:59.959 T:1848889968 DEBUG: Alloc resources: 0.17ms
03:32:07.334 T:1848889968 DEBUG: ------ Window Deinit (Pointer.xml) ------
03:32:07.819 T:1828712832 DEBUG: CLibInputKeyboard::ProcessKey - using delay: 250ms repeat: 33ms
03:32:07.820 T:1567355264 DEBUG: Thread Timer start, auto delete: false
03:32:07.832 T:1848889968 DEBUG: Keyboard: scancode: 0x63, sym: 0x013c, unicode: 0x0000, modifier: 0x0
03:32:07.832 T:1848889968 DEBUG: HandleKey: printscreen (0xf0db) pressed, action is Screenshot
03:32:07.833 T:1848889968 INFO: Loading skin file: FileBrowser.xml, load type: KEEP_IN_MEMORY
03:32:07.844 T:1848889968 DEBUG: Skin file /usr/local/share/kodi/addons/skin.estuary/xml/FileBrowser.xml loaded in 11.21ms
03:32:07.845 T:1848889968 DEBUG: Alloc resources: 12.00ms (11.51 ms skin load)
03:32:07.846 T:1848889968 DEBUG: ------ Window Init (FileBrowser.xml) ------
03:32:07.846 T:1848889968 DEBUG: Window FileBrowser.xml was already loaded
03:32:07.846 T:1848889968 DEBUG: Alloc resources: 0.03ms
03:32:08.037 T:1567355264 DEBUG: Thread Timer 1567355264 terminating
03:32:08.049 T:1848889968 DEBUG: Keyboard: scancode: 0x63, sym: 0x013c, unicode: 0x0000, modifier: 0x0
03:32:09.394 T:1848889968 DEBUG: ------ Window Init (Pointer.xml) ------
03:32:10.432 T:1848889968 DEBUG: ProcessMouse: trying mouse action leftclick
03:32:12.832 T:1848889968 DEBUG: ProcessMouse: trying mouse action leftclick
03:32:13.105 T:1848889968 DEBUG: ------ Window Deinit (FileBrowser.xml) ------
03:32:13.236 T:1848889968 DEBUG: Saving screenshot /home/xbian/screenshot000.png
03:32:13.249 T:1567355264 DEBUG: Thread JobWorker start, auto delete: true
03:32:13.249 T:1567355264 DEBUG: cached image '/home/xbian/screenshot000.png' size 1920x1080
03:32:15.682 T:1848889968 DEBUG: ProcessMouse: trying mouse action leftclick
03:32:15.939 T:1848889968 DEBUG: ------ Window Deinit (DialogConfirm.xml) ------
03:32:15.965 T:1848889968 ERROR: Create - fatal error creating thread EventServer - old thread id not null
03:32:15.968 T:1848889968 DEBUG: CPythonInvoker(0, /usr/local/share/kodi/addons/plugin.xbianconfig/services.py): trigger Monitor abort request
03:32:16.008 T:1636823424 DEBUG: XBian : abort requested
03:32:16.208 T:1636823424 DEBUG: XBian : xbianworker service finished
03:32:16.222 T:1636823424 DEBUG: XBian services finished
03:32:16.222 T:1636823424 INFO: CPythonInvoker(0, /usr/local/share/kodi/addons/plugin.xbianconfig/services.py): script successfully run
03:32:16.222 T:1636823424 DEBUG: onExecutionDone(0, /usr/local/share/kodi/addons/plugin.xbianconfig/services.py)
03:32:16.237 T:1636823424 INFO: Python interpreter interrupted by user
03:32:16.237 T:1636823424 DEBUG: Thread LanguageInvoker 1636823424 terminating
03:32:16.237 T:1848889968 DEBUG: CPythonInvoker(0, /usr/local/share/kodi/addons/plugin.xbianconfig/services.py): script termination took 269ms
03:32:16.238 T:1848889968 DEBUG: CPythonInvoker(1, /usr/local/share/kodi/addons/script.service.xbian.upstart-bridge/service.py): trigger Monitor abort request
03:32:16.309 T:1628434816 DEBUG: XBian XBMC-Upstart bridge: got notification for event onAbortRequested
03:32:16.310 T:1628434816 INFO: CPythonInvoker(1, /usr/local/share/kodi/addons/script.service.xbian.upstart-bridge/service.py): script successfully run
03:32:16.310 T:1628434816 DEBUG: onExecutionDone(1, /usr/local/share/kodi/addons/script.service.xbian.upstart-bridge/service.py)
03:32:16.315 T:1628434816 INFO: Python interpreter interrupted by user
03:32:16.315 T:1628434816 DEBUG: Thread LanguageInvoker 1628434816 terminating
03:32:16.315 T:1848889968 DEBUG: CPythonInvoker(1, /usr/local/share/kodi/addons/script.service.xbian.upstart-bridge/service.py): script termination took 77ms
03:32:16.316 T:1739583872 DEBUG: Thread CRBPWorker 1739583872 terminating
03:32:44.245 T:1567355264 DEBUG: Thread JobWorker 1567355264 terminating (autodelete)
03:33:06.861 T:1567355264 DEBUG: CWebServer[8080]: request received for /jsonrpc
03:33:13.577 T:1810887040 DEBUG: CAESinkPi:Drain delay:50ms now:0ms
03:33:14.939 T:1739583872 DEBUG: CWebServer[8080]: request received for /jsonrpc
RE: Kodi v18 (Leia) testbuilds - Nachteule - 1st Feb, 2019 02:04 PM
(1st Feb, 2019 01:22 PM)dgarciam Wrote:(1st Feb, 2019 12:05 PM)Nachteule Wrote:(1st Feb, 2019 11:31 AM)dgarciam Wrote: This is weird. I did a fresh flash on SD card, updated just the xbmc package on stage repo, and all boots fine. But when i enable remote control, i get a message "failed to start" and everything freezes. Have to get into the box via ssh, restart
What is meant by 'remote control'
Quote:the service and everything is disabled again.
Have you had this experience?
No, I'm using Kodi Leia for months on 3 Pi's (2x Pi1, 1x Pi3 and 1x Pi3B+)
In this setting page: Kodi Remote Control when i go to enable the last option: "Allow remote control from applications on other systems", so i can use Yatse from my cellular phone, i get the error that says that "Remote Communications Server" failed to start
(1st Feb, 2019 01:22 PM)dgarciam Wrote:(1st Feb, 2019 12:05 PM)Nachteule Wrote:(1st Feb, 2019 11:31 AM)dgarciam Wrote: This is weird. I did a fresh flash on SD card, updated just the xbmc package on stage repo, and all boots fine. But when i enable remote control, i get a message "failed to start" and everything freezes. Have to get into the box via ssh, restart
What is meant by 'remote control'
Quote:the service and everything is disabled again.
Have you had this experience?
No, I'm using Kodi Leia for months on 3 Pi's (2x Pi1, 1x Pi3 and 1x Pi3B+)
In this setting page: Kodi Remote Control when i go to enable the last option: "Allow remote control from applications on other systems", so i can use Yatse from my cellular phone, i get the error that says that "Remote Communications Server" failed to start
This is an extract from kodi.log:
Terminal
01:26:56.977 T:1548956032 ERROR: CVideoPlayer::OpenInputStream - error opening [/run/lirc/lircd]
01:26:56.977 T:1548956032 NOTICE: CVideoPlayer::OnExit()
01:26:57.489 T:1848279664 NOTICE: CVideoPlayer::CloseFile()
01:26:57.489 T:1848279664 NOTICE: VideoPlayer: waiting for threads to exit
01:26:57.489 T:1848279664 NOTICE: VideoPlayer: finished waiting
01:26:57.550 T:1848279664 WARNING: OnMessage: Suspiciously long time to handle GUI_MSG_PLAYBACK_STARTED (0.26s)
01:27:55.115 T:1848279664 NOTICE: CWebServer[8080]: Started
01:28:05.544 T:1848279664 NOTICE: ES: Stopping event server with confirmation
01:28:05.903 T:1583870336 NOTICE: ES: UDP Event server stopped
01:28:05.904 T:1729511808 NOTICE: ES: Starting UDP Event server on port 9777
01:28:05.975 T:1848279664 ERROR: JSONRPC Server: Failed to connect to sdpd
01:28:05.984 T:1848279664 ERROR: JSONRPC Server: Failed to create serversocket(s)
01:28:22.861 T:1848279664 ERROR: Create - fatal error creating thread EventServer - old thread id not null
I'll enable detailed logs, and try again to see what I get
Ok, understood. I get same error on fresh install, but on my regular installations everything is ok. Have to inspect deeper tomorrow what's wrong there
My last test for today/tonight: I replaced all services.* settings in file /home/xbian/.kodi/userdata/guisettins.xml from a working installation and voila, remote control is enabled and seems to work
RE: Kodi v18 (Leia) testbuilds - dgarciam - 1st Feb, 2019 11:43 PM
Well, at first i migrated my current working install and it booted fine.
Yatse recognized the install, but wasn't able to move anything.
I then proceded to turn the option off and then on and got the error.
After that i just decided to install clean and import all