+- Kodi Community Forum (https://forum.kodi.tv)
+-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33)
+--- Forum: Skins Support (https://forum.kodi.tv/forumdisplay.php?fid=67)
+---- Forum: Arctic: Zephyr - Reloaded (https://forum.kodi.tv/forumdisplay.php?fid=221)
+---- Thread: Mod Arctic Zephyr: Generations (Jarvis / Leia) [3.4.70 / Coming Soon] (/showthread.php?tid=257970)
RE: Arctic Zephyr: From Ashes (Jarvis / Krypton) [3.2.11 / 4.0.01] - Guardian Hope - 2016-06-01
(2016-05-31, 14:15)leviathansmiles Wrote: @Guardian Hope - I just noticed, somewhat weirdly, that the refresh button is present when I go to the info screen for individual episodes of TV shows. It doesn't display for movies though.
I have discovered what I believe to be the bug which was introduced into 3.2.10/3.2.11 and will release an update to correct the issue in 3.2.20 - the "Arctic Zephyr: From Ashes Summer 2016 Update" which should be due out by the middle of June. It appears an "Visible" condition was removed from the refresh button which triggered the issue.
The 3.2.20 update is another significant update to Arctic Zephyr: From Ashes. While the Spring 2016 update removed the legacy code and positioned the skin for proper Jarvis compatibility, full Jarvis compatibility hadn't been implemented yet as evident by certain code snippets used in Isengard. These changes are a necessity and will mostly be behind the scene changes although I am certain some changes will have an affect on the functionality of certain aspects.
3.2.20 will also form the basis for the Autumn 2016 Update (3.3.30 / 4.0.30) which should also bring a functional skin to Krypton rather than one that is highly experimental and mostly doesn't work. Based on the progress of Krypton, I anticipate it will be entering beta stages by the Autumn 2016 Update if not RC stages.
As no one has provided a system log of the kernel panic for the Raspberry-Pi I have no way to diagnose and correct the issue (this is different from the Kodi log; this is the system log file). You might need the boot log file (if applicable; some enterprise distributions have a boot log file which would be helpful). Therefore, it is unlikely 3.2.20 will correct any Raspberry-Pi issues. However, I did come across an interesting read suggesting that Kodi 16(.1) has had some issues with skins on the Raspberry-Pi and that it doesn't installed the required "xbmc.gui" needed for Jarvis.
Updates will also occur to the credits page and perhaps there will be a few color enhancements updates as well in 3.2.20. Full Rotten Tomatoes support will also be introduced.
Please expect this update by June 18th (this is my target date and is of course subject to change).
For Those That Want to Contribute
If there's a feature you are aching to have in Arctic Zephyr: From Ashes and know how to do make it happen or if you just want to help out, GitHub has the entire source for AZ:FA. Several branches have been established: master (this will serve as the "current release"); dormer (the Jarvis version of this skin); danvers (the Krypton version of this skin), "*-dev" [where * is a version number] (the "current development" branches).
Starting with this upcoming update, contributions should be directed to the "*-dev" branches. This should allow for better version tracking and bug fixing moving forward.
RE: Arctic Zephyr: From Ashes (Jarvis / Krypton) [3.2.11 / 4.0.01] - leviathansmiles - 2016-06-01
(2016-06-01, 02:16)Guardian Hope Wrote:(2016-05-31, 14:15)leviathansmiles Wrote: @Guardian Hope - I just noticed, somewhat weirdly, that the refresh button is present when I go to the info screen for individual episodes of TV shows. It doesn't display for movies though.
I have discovered what I believe to be the bug which was introduced into 3.2.10/3.2.11 and will release an update to correct the issue in 3.2.20 - the "Arctic Zephyr: From Ashes Summer 2016 Update" which should be due out by the middle of June. It appears an "Visible" condition was removed from the refresh button which triggered the issue.
Thanks for taking the time to look into this. I look forward to the update.
RE: Arctic Zephyr: From Ashes (Jarvis / Krypton) [3.2.11 / 4.0.01] - fabrizio5680 - 2016-06-01
@Guardian Hope, thanks for the info, looking forward to updates and the damn flicker bug gone!
The problem with update library is when it sets a series wrong, such as House of Cards (UK) instead of (US) version. So far I've managed to rectify wrong matching with tvshow.nfo/movie.nfo files.
RE: Arctic Zephyr: From Ashes (Jarvis / Krypton) [3.2.11 / 4.0.01] - drivesoslow - 2016-06-02
(2016-05-30, 18:04)lusephur Wrote: Any clues as to why version 4.0.0.1 when downloaded and installed from the Emby Beta repository on the latest nightly libreelec (but most likely also on the latest git of Krypton) will not load when selected in the appearance menu? the device simply blinks and reloads the existing skin.
If you copy DialogConfirm.xml from a different skin into the Artic skin's folder it will load. This is how I use Arctic and AZ:FA on nightly builds.
RE: Arctic Zephyr: From Ashes (Jarvis / Krypton) [3.2.11 / 4.0.01] - Guardian Hope - 2016-06-02
(2016-06-02, 06:19)drivesoslow Wrote:(2016-05-30, 18:04)lusephur Wrote: Any clues as to why version 4.0.0.1 when downloaded and installed from the Emby Beta repository on the latest nightly libreelec (but most likely also on the latest git of Krypton) will not load when selected in the appearance menu? the device simply blinks and reloads the existing skin.
If you copy DialogConfirm.xml from a different skin into the Artic skin's folder it will load. This is how I use Arctic and AZ:FA on nightly builds.
Noted. Will make the appropriate adjustments to replace DialogOK.xml / DialogProgress.xml / DialogYesNo.xml with DialogConfirm.xml for the Krypton release on the 18th (I read Krypton's changes).
RE: Arctic Zephyr: From Ashes (Jarvis / Krypton) [3.2.11 / 4.0.01] - Guardian Hope - 2016-06-03
Ahead of the June 18th, 2016 release of the "Summer 2016" Update I have included a changelog of all changes inclusive for both Dormer (Jarvis) and Danvers (Krypton) version of Arctic Zephyr: From Ashes. Please note that 3.2.20 is an LTS (Long Term Support) release with no significant changes planned to be made to the skin until Autumn 2016 (October/November). Minor patches will be made to address bugs as they come up. This is to align AZ:FA with the release of Krypton.
No Raspberry-Pi owner has come forward with any system logs so I can't see why the kernel panics are happening and therefore there is no fix in 3.2.20 nor have I made fixing it a priority for the same exact reason. If someone does come forward, we'll try to determine an appropriate patch.
Arctic Zephyr: From Ashes "Summer 2016 Update"
Code:
Arctic Zephyr: From Ashes "Summer 2016 Update" - Released June 18, 2016
Dormer: 3.2.20 / Danvers: 4.0.20
ARCTIC ZEPHYR: FROM ASHES ANNIVERSARY EDITION (DANVERS) IS IN EARLY PREVIEW AND FUNCTIONALITY IS NOT A GUARANTEE. FEEDBACK ON THE DANVERS RELEASES WILL ALLOW FOR A BETTER TRANSITION FROM JARVIS (KODI 16) TO KRYPTON (KODI 17).
The "Summer 2016 Update" to Arctic Zephyr: From Ashes is a Long Term Support (LTS) release built for stability and reliability. It features a number of changes to Arctic Zephyr: From Ashes to enhance the user experience. No major releases are scheduled for Arctic Zephyr: From Ashes until the "Autumn 2016 Update" in October or November. Bugfixes will be made through minor patch releases.
"About From Ashes" has been updated with new credits which were missing in the "Spring 2016 Update"
Info Banner Code Has Been Completely Commented Out for Dormer and Danver Releases
Rotten Tomatoes Has Been Added to the Video Information Screen
Rotten Tomatoes Has Been Added to the "Views"
Fixes to Broken Code Lines During 3rd Gen Color Enhancement Implementation
Danvers ONLY: Adds "DialogConfirm.xml"
New Textures Have Been Added
Unused Textures Have Been Removed
4th Generation Color Enhancer Has Been Added
Ability to change Dialog Menu Background
Ability to change Dialog Menu Text
Ability to change Dialog Disabled Text
Ability to change Dialog Buttons Highlight
Ability to change Hubs Menu Highlight
Ability to change Hubs Text Color Highlight
Ability to change Hubs Widget Highlight Border
Ability to change Hubs Widget Sublabel
Ability to change Side Blade Menu Highlight Color
Implemented new Busy Spinner into all applicable windows
Fixed File Browser not displaying Folder and File Icons properly
Changed "script.toolbox" to "script.skinhelper" for Backup and Restore in Skin Settings.
Added new Color Themes Category in Skin Settings, With Ability to Create and Manage Custom Themes
Added Ability to Select Day/Night Themes
Anniversary View Foundation Added (Currently Disabled)
WARNING: Raspberry-Pi Owners Have Reported boot loops from "Kernel Panics" after using Arctic Zephyr: From Ashes. This can be fixed by manually editing the config file to restore Confluence. There is currently no known resolution to this bug. If you have a system log file, please provide it so that the user experience on the Raspberry-Pi may be fixed.RE: Arctic Zephyr: From Ashes (Jarvis / Krypton) [3.2.11 / 4.0.01] - h4xdaplanet - 2016-06-03
(2016-06-03, 03:25)Guardian Hope Wrote: No Raspberry-Pi owner has come forward with any system logs so I can't see why the kernel panics are happening and therefore there is no fix in 3.2.20 nor have I made fixing it a priority for the same exact reason. If someone does come forward, we'll try to determine an appropriate patch.
Guardian - I have a rPi with osmc on it and can send you logs tonight, just let me know which log you need. I love this skin but couldn't keep using it with the bootloop.
RE: Arctic Zephyr: From Ashes (Jarvis / Krypton) [3.2.11 / 4.0.01] - faugusztin - 2016-06-03
(2016-06-03, 03:25)Guardian Hope Wrote: No Raspberry-Pi owner has come forward with any system logs so I can't see why the kernel panics are happening and therefore there is no fix in 3.2.20 nor have I made fixing it a priority for the same exact reason. If someone does come forward, we'll try to determine an appropriate patch.
Problem is, there is nothing in the logs to help you either. It dies on :
Code:
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x0098d3a0 in CWinEventsLinux::MessagePump() ()
[Current thread is 1 (Thread 0x7502b000 (LWP 623))
....
Thread 1 (Thread 0x7502b000 (LWP 623)):
#0 0x0098d3a0 in CWinEventsLinux::MessagePump() ()
#1 0x76fa2fb4 in ?? () from /lib/ld-linux-armhf.so.3
Backtrace stopped: previous frame identical to this frame (corrupt stack?)]I personally moved HTPC tasks to my Skylake based computer for now, so i didn't test it more.
RE: Arctic Zephyr: From Ashes (Jarvis / Krypton) [3.2.11 / 4.0.01] - Guardian Hope - 2016-06-03
(2016-06-03, 03:29)h4xdaplanet Wrote:(2016-06-03, 03:25)Guardian Hope Wrote: No Raspberry-Pi owner has come forward with any system logs so I can't see why the kernel panics are happening and therefore there is no fix in 3.2.20 nor have I made fixing it a priority for the same exact reason. If someone does come forward, we'll try to determine an appropriate patch.
Guardian - I have a rPi with osmc on it and can send you logs tonight, just let me know which log you need. I love this skin but couldn't keep using it with the bootloop.
It's the system log file. Typically, to access this on OSMC from what I have read, you need to SSH into your rPi and navigate to the directory containing the log files for the system itself (not Kodi but the actual OS which is a derivative of Debian). Depending on the distribution and what changes OSMC have made, you may find several log files of importance ranging from basic error_log to system.log (etc.).
(2016-06-03, 11:14)faugusztin Wrote:(2016-06-03, 03:25)Guardian Hope Wrote: No Raspberry-Pi owner has come forward with any system logs so I can't see why the kernel panics are happening and therefore there is no fix in 3.2.20 nor have I made fixing it a priority for the same exact reason. If someone does come forward, we'll try to determine an appropriate patch.
Problem is, there is nothing in the logs to help you either. It dies on :
Code:Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x0098d3a0 in CWinEventsLinux::MessagePump() ()
[Current thread is 1 (Thread 0x7502b000 (LWP 623))
....
Thread 1 (Thread 0x7502b000 (LWP 623)):
#0 0x0098d3a0 in CWinEventsLinux::MessagePump() ()
#1 0x76fa2fb4 in ?? () from /lib/ld-linux-armhf.so.3
Backtrace stopped: previous frame identical to this frame (corrupt stack?)]
I personally moved HTPC tasks to my Skylake based computer for now, so i didn't test it more.
You're right; if it's a segmentation fault be thrown by ld-linux than this makes this an issue which is out of my hands but I can of course get in touch with the developers of OSMC or have someone do so. Segmentation faults are seldom caused by an addon and the problem is usually underlying in the code that an addon is running on - not the other way around.
If both reports are segmentation faults that tells me that AZ:FA is triggering an already underlying condition in OSMC which is resulting in the kernel panic. OSMC appears to be based on Debian and AZ:FA runs fine on normal Debian. Actually, it runs fine on a lot of Linux distributions.
However, if it is indeed ld-linux throwing this error the problem is with the OSMC distribution.
Has anyone tried Raspbian (Debian), Ubuntu Core, or Windows IoT Core with Kodi and AZ:FA? It would pretty much rule anything else being at fault out.
RE: Arctic Zephyr: From Ashes (Jarvis / Krypton) [3.2.11 / 4.0.01] - faugusztin - 2016-06-03
FYI that segfault was on LibreELEC, not OSMC.
RE: Arctic Zephyr: From Ashes (Jarvis / Krypton) [3.2.11 / 4.0.01] - locomot1f - 2016-06-03
I've run AZ:FA on my Ubuntu system.
with exceptions to the aforementioned files that need to be updated (Dialog.xml, etc.), the skin runs fine.
i should also note that my build does not use the Emby File System. i just downloaded the necessary script as described on the first post.
RE: Arctic Zephyr: From Ashes (Jarvis / Krypton) [3.2.11 / 4.0.01] - locomot1f - 2016-06-03
oh! running Kodi (17.0-ALPHA2 Git:91a1cd5)
RE: Arctic Zephyr: From Ashes (Jarvis / Krypton) [3.2.11 / 4.0.01] - Guardian Hope - 2016-06-05
(2016-06-03, 20:20)locomot1f Wrote: I've run AZ:FA on my Ubuntu system.
with exceptions to the aforementioned files that need to be updated (Dialog.xml, etc.), the skin runs fine.
i should also note that my build does not use the Emby File System. i just downloaded the necessary script as described on the first post.
Exactly, Linux itself runs like a charm which makes me think that maybe a package which is installed with other distributions like Ubuntu, Ubuntu Server, Debian, RHEL, etc. are missing from the OSMC/LibreElec distributions which is causing the segmentation fault (that's a pretty serious crash in the enterprise world; I've had many multi-hour meetings over such things).
rPi owners: I want you all to hold in there and raise this issue on the respective distribution you are using's means of discourse (forums, etc.). Likewise, I will personally take the time to set aside to reach out to these distributions through far more official channels but debugging this issue may be difficult and there is no "quick fix" known at the moment.
Everyone: I am watching and getting emails of new replies to this thread but since my time is being stretched I am focusing on things that I need to focus on: running an organization and preparing to move. I am also working on the skin for the upcoming release mid-month. However, to make sure I am on top of everything my replies will be spaced a part.
RE: Arctic Zephyr: From Ashes (Jarvis / Krypton) [3.2.11 / 4.0.01] - h4xdaplanet - 2016-06-05
Thanks Guardian Hope - I've started a thread over at OSMC:
https://discourse.osmc.tv/t/artic-zephyr-from-ashes-skin-sadface-on-reboot/17042
RE: Arctic Zephyr: From Ashes (Jarvis / Krypton) [3.2.11 / 4.0.01] - xbishop - 2016-06-06
Would it be possible to add an option to shrink the vertical height of the bars on the home screen?
The home bar could be cut down to ~half size and look much better.
http://i.imgur.com/oIv0cRu.jpg