[TESTING] Kodi 17 (Krypton) Beta Builds for all platforms

Sad face when editing/browsing a previusly working, now dead, UPnP video source. When in Jarvis you would just get the browser window again in Krypton i get a sad face.

Haven’t looked real close on upstream bug reports, since i can’t find em.

Haveing two pi’s, a pi2 running jarvis and a pi3 running krypton. When I stumbeled upon this my ethernet cable had come loose from the pi2 and the UPnP source was dead, tried to edit it and clicked browse and voila sad-face.

Removed the source on pi3, check the cable on pi2, readded the source, checked that it was working. Removed the cable and tried edit/browsing again the sad-face. Did the same but other way around, removing ethernet cable from pi3 and Jarvis(pi2) just gives the standard browser window (no sad-face)

Logs successfully uploaded.
Logs available at http://paste.osmc.io/adolabubep

Edit: After installing Krypton beta4 on my windows machine, and haveing the same crash when editing a dead UPnP. I guess it’s an upstream issue

Please create a trac ticket: http://trac.kodi.tv/
Or post here: Kodi Community Forum - OS independent / Other

hope this is enough: Bug editing dead UPnP sources

Include the debug log in the post. That is the first thing a dev will ask for before looking into it.

Transcript going from GMC build to this build resulted in the following errors.

7-libbluray-osmc armhf 0.9.3-1 [169 kB]
Get:3 http://apt.osmc.tv/ krypton/main rbp2-mediacenter-osmc armhf 16.9.0-2 [35.1 MB]
Fetched 35.4 MB in 11s (3,064 kB/s)
Preconfiguring packages …
(Reading database … 27290 files and directories currently installed.)
Preparing to unpack …/tzdata_2016h-0+deb8u1_all.deb …
Unpacking tzdata (2016h-0+deb8u1) over (2016f-0+deb8u1) …
Setting up tzdata (2016h-0+deb8u1) …

Current default time zone: ‘Europe/London’
Local time is now: Thu 27 Oct 19:47:12 BST 2016.
Universal Time is now: Thu Oct 27 18:47:12 UTC 2016.
Run ‘dpkg-reconfigure tzdata’ if you wish to change it.

(Reading database … 27293 files and directories currently installed.)
Preparing to unpack …/mediacenter-skin-osmc_4.1.1-1_all.deb …
Unpacking mediacenter-skin-osmc (4.1.1-1) over (3.1.0-4) …
dpkg: warning: unable to delete old directory ‘/usr/share/kodi/addons/script.skinshortcuts/resources/lib’: Directory not empty
dpkg: warning: unable to delete old directory ‘/usr/share/kodi/addons/script.skinshortcuts/resources’: Directory not empty
dpkg: warning: unable to delete old directory ‘/usr/share/kodi/addons/script.skinshortcuts’: Directory not empty
dpkg: warning: unable to delete old directory ‘/usr/share/kodi/addons/script.module.simplejson/lib/simplejson’: Directory not empty
dpkg: warning: unable to delete old directory ‘/usr/share/kodi/addons/script.module.simplejson/lib’: Directory not empty
dpkg: warning: unable to delete old directory ‘/usr/share/kodi/addons/script.module.simplejson’: Directory not empty
dpkg: warning: unable to delete old directory ‘/usr/share/kodi/addons/script.module.unidecode/lib/unidecode’: Directory not empty
dpkg: warning: unable to delete old directory ‘/usr/share/kodi/addons/script.module.unidecode/lib’: Directory not empty
dpkg: warning: unable to delete old directory ‘/usr/share/kodi/addons/script.module.unidecode’: Directory not empty
Preparing to unpack …/armv7-libbluray-osmc_0.9.3-1_armhf.deb …
Unpacking armv7-libbluray-osmc (0.9.3-1) over (0.9.2-1) …
Preparing to unpack …/rbp2-mediacenter-osmc_16.9.0-2_armhf.deb …
Unpacking rbp2-mediacenter-osmc (16.9.0-2) over (16.8-170) …
dpkg: error processing archive /var/cache/apt/archives/rbp2-mediacenter-osmc_16.9.0-2_armhf.deb (–unpack):
trying to overwrite ‘/usr/lib/kodi/system/players/VideoPlayer/libdvdnav-arm.so’, which is also in package armv7-libdvdnav-osmc 5.0.4-1
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Processing triggers for mime-support (3.58) …
Errors were encountered while processing:
/var/cache/apt/archives/rbp2-mediacenter-osmc_16.9.0-2_armhf.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

Any help appreciated.

Update to the latest GMC build first.

Is it necessary to get GMC bevor this?

sudo -s
echo “deb http://apt.osmc.tv krypton main” >> /etc/apt/sources.list
apt-get update
apt-get -y dist-upgrade && reboot

to when I want to get B4?

No, but no official B4 has been published yet.

GMC will have commits from B4, but they are different to what will be in OSMC’s Krypton release

hmm, I make the update like you post in the first one, it says Krypton 17.0BETA4

The current published version is based on Beta 3. At the time of publishing, Beta 4 was not available. Remember Team Kodi tag the build at the start, rather than the end.

My actually Beta from your source

As mentioned above, the version number in Kodi doesn’t mean much. You should follow the version written on the thread.

Because as soon as Beta 3 is released, the version gets bumped to +1. You are running a Pi version which is based off newclock5, so may have some additional commits, but this is still not Beta 4.

It says so I no intention to not believe what Kodi shows me, so don’t trust Kodi what it says about his age…

Hello, I just did the instructions in the OP to install this beta version on a Raspberry Pi 3.
However, I’m unable to switch profiles at all using this build.

To replicate the issue, I moved the .kodi folder entirely, restarted the media center, logged in with the default user, created a new profile, then loaded it from the context menu. As soon as I do that, or if I enter with that profile on the login screen, I get a sad face page and kodi crashes.

Here are the logs, in case they help:
http://paste.osmc.io/oyukayorac

Could this be caused by a corrupted installation?
Is there anyway to rollback to the previous version and try to reapply the update from there?

Thanks!

There is no straightforward way to move back, as stated in the opening post:

If you took an image of your card before you upgraded then of-course you can just re-image over the top. If not you may be best saving a backup of your old /home/osmc/.kodi folder and re-installing.

Thanks for the reply!
It seems like I somehow managed to fix my issue, at least it doesn’t crash every time anymore. I made tons of tries, with moving back and forth files and folders, so unfortunately I cannot pinpoint the exact fix.
It still crashes sometime when switching tho, but I think that’s a Kodi issue, as I had those on Jarvis too.
Thanks anyway for the help, I will keep the card image tip in mind next time I want to try a new build, eheh :slight_smile:

hello, i have upgraded to 17 yesterday and all went smoothly. however i am not seeing the new skin…any way to get that working?

**nevermind, figured it out!

thanks

Couple of things with the latest build

  • While I appreciate the darker color to see text better the color balance for the whole screen is off now. Right side is way too brighter than the left

  • Love the new “loading” symbol, however it is very laggy on pi 2

Sorry for the delay. Here you are

Throttled: 0x0
{‘arm_frequency_capped_occurred’: 0, ‘currently_throttled’: 0, ‘under_voltage_occurred’: 0, ‘under_voltage’: 0, ‘arm_frequency_capped’: 0, ‘throttling_occurred’: 0}

Hi @sam_nazarko did you look about that bug about the external drives and the automatically mount?

Thanks