Posts by GDPR-7

care to mark this thread as resolved => see: just under the thread title ?

- no crash log reader expert here -

and I'm not sure if it will fix your issue ...

but

1. I could read time jumps in your logs, e.g.

2022-08-17 21:49:30.423 T:28358    INFO <general>: Creating audio stream (codec id: 86016, channels: ...
2022-08-17 22:06:47.154 T:28358    INFO <general>: CVideoPlayerAudio::Process - stream stalled

I wonder where they are coming from ... (=> read first sentences in this comment)

2. debug seems to be OFF

3. you're using an old TVH4.2 (and likely the old HTSP)

4. several log's in one file

5. a lot of ssl errors

for 3.

the last TVH is 4.3 (I've no idea if 4.3 is available for RPi's and if it will help at all)

update your addons too

go to the next step (or reboot)

for 4:

one log or crashlog (with maybe the time stamp when the issue occured) should be sufficing !

so run in an terminal:

rm -fv ~/storage/.kodi/temp/*.log to clean old cruft

go to the next step (or reboot)

for 2.:

switch debug ON OR see "P.S."

reboot ! ( you skipped the both before ?! )

for 5.

no idea where they come from.

all I could think of: the addon HTSP; it has settings for https; maybe they cause the ssl error's ... (=> read first sentences in this comment)

P.S.

- attached is a file named advancedsettings.xml.txt

- remove the ".txt"- extension (only to trick the forum uploader here !) so that file is named "advancedsettings.xml"

- copy it to /storage/.kodi/userdata/ (if you do not already have a advancedsettings.xml" ! otherwise enhance yours with content of my one)

- reboot

what it does:

it will switch debug on and will prevent from writing debug info's in the top left monitor corner

!! NO need to (additional) switch debug on via System configuration !!!

to switch debug off: move the file out of /storage/.kodi/userdata/

hint (in case you want to run windows on the nuc in some years):

from time to time Intel declares their hardware as unsupported and immediately removes the support pages (Windows driver !)

no idea's

tricky problem !

Quote from Biomecanoid

I did that already - comment 9

not seen, was scrolled out of my field of view.

I'm stumped for an answer regarding the issue, sorry

okay, then a kodi.log during the freeze is needed, so that a developer could have a look

=> the steps from comment #8

as said "I'm not the world favorite log file reader", but some addon seem to me causing trouble, so my answer would be "all addon", you installed after you installed LE.

btw:

are you sure the movie was always working properly or do you experiences with all movies freezes ?

care to test against your freeze with a movie from here:

Home | Test Videos

Samsung : Introducing Quantum Dot Display HDR UHD 4K Demo | 4k Media

Samsung explains what is Quantum Dot with HDR. A quantum dot display utilizes semiconductor nanocrystals called quantum dots (QD). These dots may convert or…

4kmedia.org

4K Media | Free Ultra-HD / HDR / HLG / Dolby Vision 4K Video Demos

Uncompressed 4K demos, samples, and trailers, to show off your new ultra-HD (2160p) HDR/HLG/Dolby Vision television or monitor.

4kmedia.org

Arrrggghhh, didn't realized it ... (daily coffeine level wasn't reached here )

i would suggest the following:

- disable all addon's what were additional installed (weather [if weather is a default addon: disable it too], etc)

- clean "~/.kodi/temp/ maybe with "rm -vf /storage/.kodi/temp/*.log"

- reboot

- reproduce the issue

- don't restart kodi before you've uploaded the log

- upload the logs after the issue occured

Quote from Biomecanoid

logged in to SSH

that was at "Aug 25 21:24:12.232156" (in the journal)

but the kodi log files starts at "2022-08-25 21:28:41.824 T:1595"

me is confused (or I'm stupid)

if you have logged in after the the issue occured then one can't see what kodi was doing/has seen about the issue.

care to mark this thread as resolved (if so), see just under the thread title.

P.S.

sometimes it helps to install from the scratch (and -IIRC- is was the recommended way somewhere between some stable LE releases, see the forum menu point "Blog")

Quote from elonesna

It seems that you will have to wait for the correction of this bug.

yep, after one has figured what correction is needed ...

cause I'm not the world favorite logfile reader, someone other need to step in.

anyone ?

what I see is:

a lot of addon related warning/errors, esp. the message at this time stamp would make me nervous.

2022-08-25 21:28:42.642 T:1595

is this addon needed ?

are all addon up to date ?

in general:

it seems to be best to wait until the freeze occurs (maybe remembering the time when it occurs wouldn't be a mistake) and to upload the log again

Quote from Biomecanoid

what more information would you need to draw conclusions ?

turn debug on, reboot, wait until the issue occur, upload the link to the crash- or kodi.log

more to read:

https://wiki.libreelec.tv/support/log-files

Quote from elonesna

I have been using the "KN Switchtimer Service" addon from the "Kodinerds Addon Repo"

the switchtimer is buildin (!) since LE11 and it was working since moons

Quote from elonesna

Segmentation errors are usually caused by some program defect that is corrected with a more recent version!

please read the first sentence from comment #1 again and you would relalize that I'm (or at least I yesterday have been) on the most recent version !

nightly-20220823-65c516c (Generic.x86_64)

I was watching Sat-TV with a channel switch timer set.

when the timer fired kodi crashed repeatedly (~5 times) until the reboot into safe mode.

issue wasn't reproducible so far and never seen before.

I'm unsure if have seen the usual popup (10 sec down counter) before the switch happened.

I believe not !

for the record:

to get the box into normal boot again I ssh'ed into it and deleted under /storage/.kodi/userdata/Database

- Epg*.db

- TV*.db

no idea if it was the right thing to do, but it cleared the ~pending~ and crashing timer (normal boot was possible again)

crashlog (alas Debug was off):

Quote from polo_joe

then only restored tvheadend/hts + iptvsimple

try to install them via the repo's after removing /storage/.kodi again

~"you can't fix problems with the same methodes which let to them"~

(Einstein, free translated from german)

yup.

you could run the find command afterwards to verify this

care to mark this thread as resolved (see just under the thread title !)

arrrggghhh, my fault.

LE runs another find command with lesser options than the standard linux one !

F**k !

on the LE box you'll see the option with: find --help

so

find / -size +1048576k | more

will find all files greater than 1GB ...