Forum

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.-

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.

@bluecherry
Could you please update xbian-package-xbmc only?
And after restart Kodi, disable devel repo again

(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.

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

(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!

(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

After today's final release, when should be expect Kodi v18 final hit the stable repo?

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

Found it! Thanks!

Package: xbian-package-xbmc
Version: 18.0-1548726528

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

(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+)

(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:


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:

(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

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