[thalunil]

Hello,
i can start Kodi 18.6 - in the main screen after 2-3 seconds runtime it just exits without any further notice.
The Kodi crashlog can be found here: https://kallisti.at/tmp/kodi_crashlog-20...211818.log

When deleting the ~/.kodi directory it starts up normally.

How can i determine what is causing this crash?

thal

[black_eagle]

Probably this, given its a version from Gotham (v13).

xml:
2020-04-02 21:18:17.319 T:140449910085376 WARNING: script.module.python.twitch: API version |V5| is deprecated, update to |Helix| by |TBD|

[Klojum]

How can i determine what is causing this crash?

2020-04-02 21:18:15.698 T:140451759182336 NOTICE: Disabled debug logging due to GUI setting. Level 0.

One thing to do is to enable debugging in Kodi, and then restart Kodi before reproducing the error(s).
Then provide the new log file.

[thalunil]

How can i determine what is causing this crash?

2020-04-02 21:18:15.698 T:140451759182336 NOTICE: Disabled debug logging due to GUI setting. Level 0.

One thing to do is to enable debugging in Kodi, and then restart Kodi before reproducing the error(s).
Then provide the new log file. 

Well - this is not possible. Because Kodi exits immediately after startup.
With "kodi --debug" i obtained:
https://kallisti.at/tmp/kodi_crashlog-20...151431.log

Regarding the previous comment:
Deleting .kodi/addons/plugin.video.twitch/ is not helpful

[black_eagle]

Well - this is not possible. Because Kodi exits immediately after startup.

Yes, it is.  In a terminal you can do cd ~/.kodi/userdata .  Then you can use whatever text editor you have in your terminal (I use nano, but vi is quite common too) and create an advancedsettings.xml file.  eg nano advancedsettings.xml . Add this as the contents of the file
 

xml:
<advancedsettings>

    <loglevel hide="false">2</loglevel>

</advancedsettings>

Do this without Kodi running.  Then start it and it will start up in debugging mode.  It might also help if you install gdb if it's not already installed.  If it is, try executing ulimit -c unlimited from a terminal before starting Kodi.  It should pick up the backtrace when Kodi crashes and add it to the debug log. This would help in getting you a diagnosis.

[thalunil]

Well - this is not possible. Because Kodi exits immediately after startup.

Yes, it is.  In a terminal you can do cd ~/.kodi/userdata .  Then you can use whatever text editor you have in your terminal (I use nano, but vi is quite common too) and create an advancedsettings.xml file.  eg nano advancedsettings.xml . Add this as the contents of the file
 

xml:
<advancedsettings>

    <loglevel hide="false">2</loglevel>

</advancedsettings>

Do this without Kodi running.  Then start it and it will start up in debugging mode.  It might also help if you install gdb if it's not already installed.  If it is, try executing ulimit -c unlimited from a terminal before starting Kodi.  It should pick up the backtrace when Kodi crashes and add it to the debug log. This would help in getting you a diagnosis. 

Thank you. I followed these lines...
The logfile is at https://kallisti.at/tmp/kodi_crashlog-20...124847.log

I cannot spot a crashdump. gdb is installed.
ulimit core file size is unlimited

[fritsch]

Sorry: 

2020-04-05 12:48:46.756 T:139982668485120 NOTICE: FFmpeg version/source: 4.2.2

not supported here.

For your crashlog, start kodi from gdb directly and after the crash thread apply all bt

[black_eagle]

Just to expand on that in case you're not sure how to do it.

In a terminal do gdb /usr/lib64/kodi/kodi-x11.  When gdb starts type in run <enter>.  When Kodi crashes, do thread apply all bt and upload the output somewhere.  Type in quit to exit gdb.

[thalunil]

Just to expand on that in case you're not sure how to do it.

In a terminal do gdb /usr/lib64/kodi/kodi-x11.  When gdb starts type in run <enter>.  When Kodi crashes, do thread apply all bt and upload the output somewhere.  Type in quit to exit gdb.

thanks alot - i did obtain this dump:
https://kallisti.at/tmp/gdb-trace

Can one identify which addon is causing this crash?
Purging ~/.kodi/addons is recovering kodi, but I am curious what's going on.

[fritsch]

hread 29 (Thread 0x7fff7bfff700 (LWP 2601)):
#0  0x00007ffff7e0bea1 in raise () from /lib64/libc.so.6
#1  0x00007ffff7df553d in abort () from /lib64/libc.so.6
#2  0x00007ffff064a2e8 in ?? () from /usr/lib64/libffi.so.8
#3  0x00007fff54d3f354 in ?? () from /usr/lib64/python2.7/lib-dynload/_ctypes.so
#4  0x00007ffff76700ec in ?? () from /usr/lib64/libpython2.7.so.1.0
#5  0x00007fff54d38007 in ?? () from /usr/lib64/python2.7/lib-dynload/_ctypes.so
#6  0x00007fff54d381b9 in ?? () from /usr/lib64/python2.7/lib-dynload/_ctypes.so
#7  0x00007ffff7694878 in ?? () from /usr/lib64/libpython2.7.so.1.0
#8  0x00007ffff76bfcf4 in PyEval_EvalFrameEx () from /usr/lib64/libpython2.7.so.1.0
#9  0x00007ffff76b9df4 in PyEval_EvalFrameEx () from /usr/lib64/libpython2.7.so.1.0
#10 0x00007ffff76b8ad4 in PyEval_EvalCodeEx () from /usr/lib64/libpython2.7.so.1.0
#11 0x00007ffff76b87f9 in PyEval_EvalCode () from /usr/lib64/libpython2.7.so.1.0

That looks like ABI breakage somewhere. With debug logging and extra logging for python we might see more details.

[thalunil]

Sorry: 

2020-04-05 12:48:46.756 T:139982668485120 NOTICE: FFmpeg version/source: 4.2.2

not supported here.

For your crashlog, start kodi from gdb directly and after the crash thread apply all bt 

What are you refering to with this FFmpeg hint?

[fritsch]

You are using software we don't support. OpenSuse provides a mixed build with dependencies we neither did releast nor test. Means every support in here is "optional".

[thalunil]

You are using software we don't support. OpenSuse provides a mixed build with dependencies we neither did releast nor test. Means every support in here is "optional".

True, i got it.
What about the Flatpak version?
https://www.flathub.org/apps/details/tv.kodi.Kodi

Is this directly from the Kodi project?

thal

[wsnipex]

yes, the flatpak version is fine, but be aware that there are some limitations due to flatpak's sandboxing.