•   
  • 1
  • 79
  • 80
  • 81(current)
  • 82
  • 83
  • 218
  •   
  Thread Closed
v17 LibreELEC Testbuilds for RaspberryPi (Kodi 17.0)
no luck for me in #704 either, not that I expected it.
(2016-07-05, 10:42)loggio Wrote: here you go:
http://pastebin.com/QMzYFQk6

the texture file is called modern_rounded.xbt ... Although , there's no reference to it in the log file... only reference to Textures.xbt. After changing to the modern_rounded theme I turned off the debug log.

Not seeing anything obvious but not really sure which log you wanted me to look at. Let's keep this simple.

Can you load the rounded theme in #0613, enable debug logging, then reboot so that the debug log is captured from the start.

Now run the following using ssh once the theme has loaded:

Code:
cat /storage/.kodi/temp/kodi.log | paste
journalctl -a | paste
texturecache.py screenshot

Paste the links, and use imgur.com to post the screenshot (you'll find it in the "Screenshots" share).

Now upgrade to #0704 and repeat the 3 commands above once the theme has failed to load - post the new links and screenshot.

This will allow the logs to be compared for any new behaviour.
Texture Cache Maintenance Utility: Preload your texture cache for optimal UI performance. Remotely manage media libraries. Purge unused artwork to free up space. Find missing media. Configurable QA check to highlight metadata issues. Aid in diagnosis of library and cache related problems.
(2016-07-05, 11:25)Milhouse Wrote:
(2016-07-05, 10:42)loggio Wrote: here you go:
http://pastebin.com/QMzYFQk6

the texture file is called modern_rounded.xbt ... Although , there's no reference to it in the log file... only reference to Textures.xbt. After changing to the modern_rounded theme I turned off the debug log.

Not seeing anything obvious but not really sure which log you wanted me to look at. Let's keep this simple.

Can you load the rounded theme in #0613, enable debug logging, then reboot so that the debug log is captured from the start.

Now run the following using ssh once the theme has loaded:

Code:
cat /storage/.kodi/temp/kodi.log | paste
journalctl -a | paste
texturecache.py screenshot

Paste the links, and use imgur.com to post the screenshot (you'll find it in the "Screenshots" share).

Now upgrade to #0704 and repeat the 3 commands above once the theme has failed to load - post the new links and screenshot.

This will allow the logs to be compared for any new behaviour.

Sure.
Here:

#0613
Kodi.log http://sprunge.us/ZaeO
Journal http://sprunge.us/gaZT

Screen:
Image



#0704
Kodi.log http://sprunge.us/bOZd
Journal http://sprunge.us/IViX

Screen:
Image
It's not immediately obvious from the logs what the problem is, but from the screenshot I can see the lack of rounded corners in #0704 - is that the extent of the problem? This may require input from someone more familiar with the skin/textures system.

As I see you switched from RPi2 to an x86 client with your last set of logs, presumably this isn't a Pi specific issue.
Texture Cache Maintenance Utility: Preload your texture cache for optimal UI performance. Remotely manage media libraries. Purge unused artwork to free up space. Find missing media. Configurable QA check to highlight metadata issues. Aid in diagnosis of library and cache related problems.
it's ever since that commit to Kodi on #0614 that's broken this.
Yes, I've switched to another machine (got kicked out of the living room) haha
The rounded theme in Titan rounds all the textures for the skin, posters, fanart etc...

So it's not specific to pie.
(2016-07-05, 12:29)loggio Wrote: it's ever since that commit to Kodi on #0614 that's broken this.
Yes, I've switched to another machine (got kicked out of the living room) haha
The rounded theme in Titan rounds all the textures for the skin, posters, fanart etc...

So it's not specific to pie.

Try build #0704x which has PR9960 reverted: RPi2
Texture Cache Maintenance Utility: Preload your texture cache for optimal UI performance. Remotely manage media libraries. Purge unused artwork to free up space. Find missing media. Configurable QA check to highlight metadata issues. Aid in diagnosis of library and cache related problems.
I am having the same issues. Fixed after I rolled back the version.


(2016-07-05, 08:17)f1vefour Wrote:
(2016-07-05, 02:00)jarvismeier Wrote: With this build i have both a Pi3 and a Pi2 that refuse to boot past the animated splash screen. i have narrowed it down to an issue with an Edimax Wireless AC600 USB dongle. If i remove it I can completely boot. Once booted if i plug the adapter back in Kodi locks hard and the unit becomes unresponsive.

This is the unit in question: https://www.amazon.ca/gp/product/B00FW6T...UTF8&psc=1

This would be due to the kernel switch, guess something is wrong in the driver code to your dongle.
(2016-07-05, 14:39)david1976aus Wrote: I am having the same issues. Fixed after I rolled back the version.


(2016-07-05, 08:17)f1vefour Wrote:
(2016-07-05, 02:00)jarvismeier Wrote: With this build i have both a Pi3 and a Pi2 that refuse to boot past the animated splash screen. i have narrowed it down to an issue with an Edimax Wireless AC600 USB dongle. If i remove it I can completely boot. Once booted if i plug the adapter back in Kodi locks hard and the unit becomes unresponsive.

This is the unit in question: https://www.amazon.ca/gp/product/B00FW6T...UTF8&psc=1

This would be due to the kernel switch, guess something is wrong in the driver code to your dongle.

This device is based on the RTL8812AU driver?

There's an updated RTL8812AU version of the driver with kernel 4.6 and 4.7 support, although it's essentially the same changes I already have in these builds - just enough changes to allow the driver to build against the latest 4.6 and 4.7 kernel (actually, the 4.7 upstream change is a bit of a hack). I'll bump to this newer version of the driver in the next build to see if it makes any difference, however if the problems continue please provide output of "dmesg", "lsmod" and "lsusb -v" from a working build (ie. #0703).

If we can't find a working driver I'm not sure what we'll do, these non-mainline Realtek drivers are always a bit of a liability as there's barely any official manufacturer support. If you can, buy something else that isn't based on Realtek hardware and that has mainline Linux kernel support (Broadcom, Intel etc.).
Texture Cache Maintenance Utility: Preload your texture cache for optimal UI performance. Remotely manage media libraries. Purge unused artwork to free up space. Find missing media. Configurable QA check to highlight metadata issues. Aid in diagnosis of library and cache related problems.
(2016-07-05, 17:30)Milhouse Wrote:
(2016-07-05, 14:39)david1976aus Wrote: I am having the same issues. Fixed after I rolled back the version.


(2016-07-05, 08:17)f1vefour Wrote: This would be due to the kernel switch, guess something is wrong in the driver code to your dongle.

This device is based on the RTL8812AU driver?

There's an updated RTL8812AU version of the driver with kernel 4.6 and 4.7 support, although it's essentially the same changes I already have in these builds - just enough changes to allow the driver to build against the latest 4.6 and 4.7 kernel (actually, the 4.7 upstream change is a bit of a hack). I'll bump to this newer version of the driver in the next build to see if it makes any difference, however if the problems continue please provide output of "dmesg", "lsmod" and "lsusb -v" from a working build (ie. #0703).

If we can't find a working driver I'm not sure what we'll do, these non-mainline Realtek drivers are always a bit of a liability as there's barely any official manufacturer support. If you can, buy something else that isn't based on Realtek hardware and that has mainline Linux kernel support (Broadcom, Intel etc.).

Yes this is based on this driver.

lsusb:
http://pastebin.com/fKAC7hGj

lsmod:
http://pastebin.com/Fr4bHrpX

dmesg:
http://pastebin.com/90zJ5fJx
@Milhouse

Wanted to try out the latest build comming from #0412.
I am getting a lot of SKIPS when playing live TV. (DVBLink v3.3.2) using the later builds. Don't know when this issue started. I know it runs fine on build #0412


http://pastebin.com/v4RPF6XL
MY CURRENT MEDIA PLAYER
INTEL DN2820FYKH NUC 2D/3D WINDOWS
ACER HD9500BD / MARANTZ SR7009 ATMOS 7.1.4

(2016-07-05, 13:45)Milhouse Wrote:
(2016-07-05, 12:29)loggio Wrote: it's ever since that commit to Kodi on #0614 that's broken this.
Yes, I've switched to another machine (got kicked out of the living room) haha
The rounded theme in Titan rounds all the textures for the skin, posters, fanart etc...

So it's not specific to pie.

Try build #0704x which has PR9960 reverted: RPi2

that fixed it! working fine now.

Image
(2016-07-05, 20:31)loggio Wrote: that fixed it! working fine now.

OK, well that was only a temporary revert so it will be broken again in tonight's build. I've posted a comment on PR9960 in order to try and determine if the issue is with Titan skin code, or with Kodi core code - the answer to that will determine who needs to fix what. If it's a Kodi core issue this may require a trac ticket.
Texture Cache Maintenance Utility: Preload your texture cache for optimal UI performance. Remotely manage media libraries. Purge unused artwork to free up space. Find missing media. Configurable QA check to highlight metadata issues. Aid in diagnosis of library and cache related problems.
(2016-07-04, 21:14)popcornmix Wrote:
(2016-07-04, 21:06)MikeKL Wrote: Having occasional Kodi GUI lockups where Estuary GUI goes blank (just the standard Estuary background colour, nothing on top), not easy to find way to repeat this lock-up.

Remove the overclock first, just to rule that out.
Assuming kodi is still running, but hung, I think if you run:
Code:
killall -SEGV kodi.bin
You will get a backtrace in ~/kodi/temp which may have some clues in.
OK with overclock removed kodi GUI locked up this evening using #0704, tried using "killall -SEGV kodi.bin" via ssh but all that seemed to do was reboot kodi?
(unless an actual reboot occurred around same time as command entered in ssh purely by coincidence)

No apparent specific trace file in /kodi/temp folder, just a couple of kodi crash-logs

http://pastebin.com/q5i43A0Q
http://pastebin.com/7nEhNR7g

A cookies.dat with following info

Code:
# Netscape HTTP Cookie File
# https://curl.haxx.se/docs/http-cookies.html
# This file was generated by libcurl! Edit at your own risk.

www.filmon.com    FALSE    /    FALSE    0    PHPSESSID    a40fepgmtvncqt72fb39acetn3
.filmon.com    TRUE    /    FALSE    1470343457    ftv_token    eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJGaWxtT25UViIsImF1ZCI6IkZpbG1PblRWX01HTyIsImV4cCI6MTQ3MDM0MzQ1NywibmJmIjoxNDY3NzUxMzk3LCJpYXQiOjE0Njc3NTE0NTcsInJlcXVlc3QiOnsidXNlciI6eyJpZCI6IjQyMTc2MjYzIiwiZW1haWwiOiJhdi5tZWRpYS5hbnl0aW1lLmFueXdoZXJlQGdtYWlsLmNvbSIsImFmZmlkIjpudWxsfX19.YSh-hTkHrAjJXqYxydx-ylGoiA30T4-obiiToPWnLeg
www.filmon.com    FALSE    /    FALSE    1470343457    lang    en
www.filmon.com    FALSE    /tv/api/    FALSE    0    ftv_defq    low
#HttpOnly_.thetvdb.com    TRUE    /    FALSE    1497389275    __cfduid    d6e74480757cc9a48cadb4bd3fd91ace31465853275
.itv1liveios-i.akamaihd.net    TRUE    /hls/live/203437/itvlive/ITV1MN/    FALSE    0    _alid_    kqO0K5UInN4hDrdsZfeTSQ==
.cp401489-vh.akamaihd.net    TRUE    /i/iplayerstream/secure_auth/,800kbps/modav/bUnknown-075c27b6-ad02-4f06-9985-efe82fb91f9b_b07hk5bl_1466451228552,1500kbps/modav/bUnknown-d4f6aeba-d2be-4d75-9142-237b81d0a742_b07hk5bl_1466452481952,3200kbps/modav/bUnknown-d4f6aeba-d2be-4d75-9142-237b81d0a742_b07hk5bl_1466454591581,.mp4.csmil/    FALSE    0    _alid_    js70qoAOC/p/595kf3n1EA==
.replayftv-vh.akamaihd.net    TRUE    /i/streaming-adaptatif_france-dom-tom/2016/S26/J1/142031579-5770d6db1df09-,standard1,standard2,standard3,standard4,.mp4.csmil/    FALSE    0    _alid_    c1W7xOIZymkfjQFYvDkrhg==
.replayftv-vh.akamaihd.net    TRUE    /i/streaming-adaptatif_france-dom-tom/2016/S26/J2/142031674-5772287eecab5-,standard1,standard2,standard3,standard4,.mp4.csmil/    FALSE    0    _alid_    i5coqTTUelxFTpkYDe3VEA==
.cp401489-vh.akamaihd.net    TRUE    /i/iplayerstream/secure_auth/,800kbps/modav/bUnknown-f0c5b9c5-3c28-4fd4-97e7-5613dee7dcd0_p02l7zd9_1425469434321,1500kbps/modav/bUnknown-f0c5b9c5-3c28-4fd4-97e7-5613dee7dcd0_p02l7zd9_1425469435701,3200kbps/modav/bUnknown-f0c5b9c5-3c28-4fd4-97e7-5613dee7dcd0_p02l7zd9_1425471071094,.mp4.csmil/    FALSE    0    _alid_    U1hqQBN4UUyYTcAm20z4Gw==
www.filmon.com    FALSE    /    FALSE    1467751457    affid    deleted

4 xxxxx-xxxxxxxx.fi (i.e. 10025-e82f7eb6.fi) which appear to contain urls and catchup information references related to use of iplayerwww and ITV add-ons before the kodi GUI lock then crash occurred?

Also not sure kodi lock up was quite same this time as GUI was unresponsive but this time had top and bottom bars of estuary GUI on screen with time in top right but not much else. (Last time nothing but Estuary background)

---edit-----Finally the full kodi.log after successful reboot-------
rPi3B+, SanDisk Ultra 8Gb SD, Milhouse kernel_5.x LE ​Testbuild (Kodi 19 Matrix) -> Onkyo TX-SR608 AV Receiver -> Philips 42" LCD TV
KVIM2 Pro, SanDisk Ultra 8Gb SD, kernel_5.x LE Testbuild (Kodi 19 Matrix) -> LG 27UD69-W 4K Monitor -> AudioEngine A2+ Speakers
(2016-07-05, 22:57)MikeKL Wrote: No apparent specific trace file in /kodi/temp folder, just a couple of kodi crash-logs

http://pastebin.com/q5i43A0Q

Yes, that's what we wanted. Looks like a PVR deadlock, which are not uncommon.
Not something I know about but I'll mention it on kodi Slack.

Code:
Thread 38 (Thread 0x5cfff3a0 (LWP 1458)):
#0  0x76d3bd44 in __lll_lock_wait (futex=0x27f1a7c, private=0) at lowlevellock.c:43
#1  0x76d34b0c in __GI___pthread_mutex_lock (mutex=0x27f1a7c) at pthread_mutex_lock.c:115
#2  0x003d1b10 in XbmcThreads::CountingLockable<XbmcThreads::pthreads::RecursiveMutex>::lock() ()
#3  0x0045a3a4 in CGUIWindowManager::GetWindow(int) const ()
#4  0x006f758c in PVR::CPVRChannelGroup::SearchAndSetChannelIcons(bool) ()
#5  0x006fa348 in PVR::CPVRChannelGroupInternal::UpdateGroupEntries(PVR::CPVRChannelGroup const&) ()
#6  0x006f96fc in PVR::CPVRChannelGroupInternal::Update() ()
#7  0x006fa750 in PVR::CPVRChannelGroups::Update(bool) ()
#8  0x006fceb8 in PVR::CPVRChannelGroupsContainer::Update(bool) ()
#9  0x00710f80 in PVR::CPVRManager::ExecutePendingJobs() ()
#10 0x00712ab0 in PVR::CPVRManager::Process() ()
#11 0x00a2bac0 in CThread::Action() ()

Thread 35 (Thread 0x688ff3a0 (LWP 1522)):
#0  0x76d3bd0c in __lll_lock_wait (futex=0x36a9e64, private=0) at lowlevellock.c:46
#1  0x76d34b0c in __GI___pthread_mutex_lock (mutex=0x36a9e64) at pthread_mutex_lock.c:115
#2  0x003d1b10 in XbmcThreads::CountingLockable<XbmcThreads::pthreads::RecursiveMutex>::lock() ()
#3  0x006fb6b8 in PVR::CPVRChannelGroups::GetGroupAll() const ()
#4  0x006fcda4 in PVR::CPVRChannelGroupsContainer::GetGroupAll(bool) const ()
#5  0x00719344 in PVR::CPVRGUIInfo::UpdateMisc() ()
#6  0x0071ac2c in PVR::CPVRGUIInfo::Process() ()
#7  0x00a2bac0 in CThread::Action() ()

Thread 1 (Thread 0x74eb4000 (LWP 1059)):
#0  0x76d3bd44 in __lll_lock_wait (futex=0x36a9e64, private=0) at lowlevellock.c:43
#1  0x76d34b0c in __GI___pthread_mutex_lock (mutex=0x36a9e64) at pthread_mutex_lock.c:115
#2  0x003d1b10 in XbmcThreads::CountingLockable<XbmcThreads::pthreads::RecursiveMutex>::lock() ()
#3  0x006fa5f4 in PVR::CPVRChannelGroups::GetSelectedGroup() const ()
#4  0x006fce00 in PVR::CPVRChannelGroupsContainer::GetSelectedGroup(bool) const ()
#5  0x0070e970 in PVR::CPVRManager::GetPlayingGroup(bool) ()
#6  0x0091ab88 in PVR::CGUIWindowPVRBase::OnInitWindow() ()
#7  0x0091e024 in PVR::CGUIWindowPVRGuide::OnInitWindow() ()
#8  0x00458854 in CGUIWindow::OnMessage(CGUIMessage&) ()
#9  0x00779600 in CGUIMediaWindow::OnMessage(CGUIMessage&) ()
#10 0x0091eb7c in PVR::CGUIWindowPVRGuide::OnMessage(CGUIMessage&) ()
#11 0x0045ddf8 in CGUIWindowManager::ActivateWindow_Internal(int, std::vector<std::string, std::allocator<std::string> > const&, bool, bool) ()
#12 0x0045dfc0 in CGUIWindowManager::ActivateWindow(int, std::vector<std::string, std::allocator<std::string> > const&, bool, bool) ()
#13 0x0060fb4c in ?? ()
#14 0x0060e194 in CBuiltins::Execute(std::string const&) ()
#15 0x00792428 in CApplication::ExecuteXBMCAction(std::string, std::shared_ptr<CGUIListItem> const&) ()
#16 0x00792a74 in CApplication::OnMessage(CGUIMessage&) ()
#17 0x0045b88c in CGUIWindowManager::SendMessage(CGUIMessage&) ()
#18 0x0046f60c in CGUIAction::ExecuteActions(int, int, std::shared_ptr<CGUIListItem> const&) const ()
#19 0x00666490 in CStaticListProvider::OnClick(std::shared_ptr<CGUIListItem> const&) ()
#20 0x004a58a8 in CGUIBaseContainer::OnClick(int) ()
#21 0x00458074 in CGUIWindow::OnAction(CAction const&) ()
#22 0x0045bd5c in CGUIWindowManager::OnAction(CAction const&) const ()
#23 0x0078ffc0 in CApplication::OnAction(CAction const&) ()
#24 0x00608a00 in CInputManager::OnKey(CKey const&) ()
#25 0x00609014 in CInputManager::ProcessPeripherals(float) ()
#26 0x006099d8 in CInputManager::Process(int, float) ()
#27 0x00786db8 in CApplication::FrameMove(bool, bool) ()
#28 0x007e81c8 in CXBApplicationEx::Run() ()
#29 0x00669320 in XBMC_Run ()
#30 0x00357c34 in main ()
(2016-07-05, 23:13)popcornmix Wrote:
(2016-07-05, 22:57)MikeKL Wrote: No apparent specific trace file in /kodi/temp folder, just a couple of kodi crash-logs

http://pastebin.com/q5i43A0Q
Yes, that's what we wanted. Looks like a PVR deadlock, which are not uncommon.
Not something I know about but I'll mention it on kodi Slack.
OK so just to mention in case its important in relation to information I have posted in thread this time, I am currently continuing to run both tvheadend and filmon pvr's in tandem and when Pi goes through a full reboot I typically get a number of crashes before a full and clean boot-up.

Once Pi is fully booted up it appears to be stable for long periods and I can use both PVR via live TV option in GUI including EPG information etc.
(been using/testing like this for a while with nightly milhouse builds)
rPi3B+, SanDisk Ultra 8Gb SD, Milhouse kernel_5.x LE ​Testbuild (Kodi 19 Matrix) -> Onkyo TX-SR608 AV Receiver -> Philips 42" LCD TV
KVIM2 Pro, SanDisk Ultra 8Gb SD, kernel_5.x LE Testbuild (Kodi 19 Matrix) -> LG 27UD69-W 4K Monitor -> AudioEngine A2+ Speakers
  •   
  • 1
  • 79
  • 80
  • 81(current)
  • 82
  • 83
  • 218
  •   
  Thread Closed
 
Thread Rating:
  • 19 Vote(s) - 4.63 Average



Logout Mark Read Team Forum Stats Members Help
LibreELEC Testbuilds for RaspberryPi (Kodi 17.0)4.6319