On my UBUNTU 24.04.1 Kodi crash immediatelly after about 1 seconds. Only apparently work if i launch it from terminal. #320
Comments
|
what's the used flatpak version? should be at least 1.14 |
confirmed @razzeee the output it's this: The strange issue is the very fast crash... it's under two seconds :) More than a crash it seems like something is failing to start directly also because from the log that you get there do not seem to be any errors reported. |
|
I haven't tired it but maybe by installing the SKD + debug symbols Kodi is able to capture information about the crash in the crash log: |
ah ok... you have speak about this issue also on forum but I didn't understand your reply correctly until now. I thinks i can try.... but after this i have to start kodi with some particular commands ? |
|
Just start the same way as usual to produce the crash. And if we are lucky there will be a new kodi_crashlog_xxxxxx.log that contains the information about the crash. |
ok i start to download it: I hope this is not a full reinstall of kodi...... or it's be installed a different version of same app ? |
|
This is just the SDK and additional debug information. Kodi and the freedesktop runtime are not reinstalled. |
ok.. completed all.... now i start my normal usage and when obtain a new crashlog i upload/paste on kodi.paste.tv.... |
|
@neo1973 @razzeee Crash happened immediatelly right now.... Upload on paste.kodi.tv but apparently nothings it's different and there's no debug info..... https://paste.kodi.tv/tiquvufibi.kodi I don't have idea if i can to run with debug log.... i can modify some file setting manually to enable it ? |
|
Having the same issue on diet-pi (debian) with an intel NUC too, logs are similar to above (no debug info). EDIT: it loads as expected when reverting to commit |
Well, it was worth a try 🙂
That commit is before #309 so the freedesktop SDK update is likely the culprit. To investigate further we need the stack trace either via flatpak-coredumpctl or by running Kodi in GDB, both as described in https://docs.flatpak.org/en/latest/debugging.html |
interesting that here too we are faced with an Intel NUC.... If it were a common problem I don't think only you and I would report the same problem, do you think?
since I installed the sdk I would say that I am available for any test :) Installing the SDK took up about 3 or 4GB of space. I wouldn't want to "mess up" my HD by installing tools that would then be useless in my case because I don't have the skills to use them...... I hope you understand what I mean... |
|
Does the command |
ok thanks and sorry for my incompetence.... on this afternoon or at max ... I'll be able to tell you for sure later this evening, but there's something I read in the first lines of my previous logs, namely this: should this perhaps mean that I have to install the gdb package first? then maybe another oddity is that if I start it from the terminal this problem doesn't seem to occur.... the problem happens if you launch it from its icon among the apps then but now it even seems that every 2 or 3 random times kodi then start (sometime i see the Estuary skin image on my TV and kodi close himselft after about 5 second). I can't figure it out though, is it Kodi that crashes, but is it its entire ecosystem that closes (freedesktop or similar there doesn't seem to be any serious errors related to Kodi itself) ? |
|
gdb should be there, due to https://docs.flatpak.org/en/latest/debugging.html#debug-packages which you ran earlier |
|
Ok i can try.... the output it's this: You can understand my italian terminal windows ? what do I do, do I also install this package as you suggest or not? Anyway thanks for all support until now.... EDIT and ADD I thinks this is an issue on inputstream.adaptive.... but it's a totally different issue. Anyway.... right now for obtain kodi works i need to reclick 5 time the icon on ubuntu desktop :) EDIT num.2 What is this CWebServer? Isn't that what causes the crash because it fails to boot or something? |
|
My Daily usage it's become terrible.... in addiction of this istant crash right now KODI it's completely crash while watching a youtube video. in full playback and totally random with no apparent errors. The crash error log there's no report buffer error or similar..... tha kodi daily use it's every days terrible. It's ubuntu kernel ? Freedesktop bug and all session crash ? I don't have idea..... |
Yes, you have to install |
Installed the libflatpak-dev with about another 1GB of free space needed... strange. After that there's the error obtain. Again here: Also coredumpctl installed right now: Tryed this after installed: How i need to do right now ? |
|
Simply try to found some info by google... popped out other similar issue with other app close himself immediatelly after startup.. like this: |
At this point, I'm confused, if your app crashes instantly or if you can actually watch stuff. If it crashes instantly, you shouldn't be able to reach youtube? |
More often than not it crashes immediately and creates that crashlog file. but if I insist and launch kodi several times in the end it starts then it happens that I can use it for several hours or that it crashes after a few minutes even if it is in the GUI without doing anything. there is definitely something wrong... since it often doesn't start at all anyway I would say that it is normal that this undermines stability in the long term. if we can get there and figure out what is causing those instant crashes then we'll see if other crashes persist and then we can move on to something else. |
|
For example from right now i thinks i can try to use kodi starting from terminal using that: if I start it from the terminal it seems to always start. in this example i opened.. kodi started and i terminated it correctly from the GUI in fact you can see that it returned to the terminal prompt correctly. |
I reproduce the same problem on Ubuntu 24.04 and it's a NUC too (NUC5i3RYH to be precise). Thanks for the terminal workaround. It also made me realize that my problems with the Netflix plugin probably have the same root cause: it suddenly stopped starting video playback right when Kodi started crashing randomly at startup (if I try often enough I can get it to not crash). If I start Kodi from the terminal, it works like a charm again. |
We can't be sure that the problem is limited to users of NUCs and similar mini PC setups. It seems that now the general stability has been compromised in some way..... I'll try launching it from the terminal and using it with the terminal opened in background....if I get any weird crashes then see if anything appears in the crash log or normal log that can help us work around and fix the problem. |
|
If you want to know... after my last comment I used kodi for almost all 4 hours and no strange crashes. As an enthusiast I watched an event in "On Demand" on DAZN and for the whole duration never a buffering problem or similar or strange crashes like those reported so far. Then there are times instead where if I use its icon from the desktop it crashes instantly or after a few minutes of use. I'm confused like you :) ... but if you help me understand how to make this stacktrace thing work, let's see if it can be useful for the resolution... obviously thanks in advance. |
|
This afternoon for me a purpose test.... at my brothers home another mini pc with Ubuntu. it's an Asus VM40B. Also here i have updated all componet of ubuntu and kodi to latest flatpak build. Here apparently no problems... Come back right now to my home... turn on my NUC reach Ubuntu Desktop and Kodi not start :) LOL... I have try to make a look on Flatseal and i have tryed to reset all permission..... look on list there's it: do you know that "allow devel" could help to enable debug logs? |
|
Ok i have enabled this setting... right now when i launch kodi from icon and it's crash i can obtain the request to send the report towards someone. The thing is that if I launch Kodi from the terminal it starts and works fine. If launched from the desktop it doesn't work... the problem must be there somewhere. |
|
hey @neo1973 Interesting.. enable this setting now i can obtain this try to look here: kodi does not start.. what should I do at that point? How do I proceed? Where do I see any errors? Also @razzeee do you know how i need to continue how i can debug on this terminal windows ? |
|
@razzeee so is everything ok? Why does it say it can't find the file? I ask as a total ignoramus because honestly I don't understand if we've managed to figure out where the problem might be. It seems that now other linux distributions are starting to have the same problem. Is that right? |
Because the crash reporter doesn't know how to deal with Flatpaks sand boxing.
The crash happens in a third party library Kodi uses (udev). As similar crashes seem to happen with other applications using that library the crash is probably not due to Kodi doing something wrong but has other causes. This believe is reinforced by the very same Kodi working on the older freedesktop SDK without issues.
That's unclear in the context of Kodi. So far I only heard of problems on Ubuntu (and only certain installations). |
|
@neo1973 ok thanks for info.... if it's needed i'm here for some addictional test... Turned on my Mini PC about 5 minutes ago.... received two flatpak updated related to tv.kodi.Kodi and tv.kodi.Kodi.Debug (or somethings similar) I have update both them. For obtain kodi start i have need to click on icon about 10 times... lol :) for now if I understand I have to live with the problem hoping Kodi it doesn't become completely unusable. |
|
@neo1973 and @razzeee and it's right now start to crash also launch from terminal: as ever the crashlog not contain eny error... now try to run immediatelly after the coredumpctl and post the output in terminal |
At the second (gdb) prompt it's need to do other ? it's exist another command? From exit from gdb it's need to use CTRL+C or exist other command to close correctly this dump project ? How it's the crash correctly logged ? In the output i can't found the error and how the crash append... And because after two or three crash happen after that kodi start without any problems ? edit |
|
whit verbose from terminal: |
|
Can you try to disconnect as many USB devices as possible? Also, please update flatpak, you should be at least on 1.14.8 |
Indeed same here. It keeps getting worst... kodi_crashlog-20250113_202658.log
I disconnected everything but the keyboard, not improvement.
I installed flatpak from its ppa so I have 1.16.0. |
|
Note that it seems to work like a charm if I start a X.org based session instead of Wayland (the default on Ubuntu). Could worth trying that on your side @DjDiabolik (close the session, select your user, on the bottom right corner you have a choice between "Ubuntu" and "Ubuntu on XOrg"). |
|
I have also had this phenomenon for some time and it is completely random. I am here on a minusforum mini computer with AMD Ryzen 7 on Manjaro. It doesn't matter whether I start KODI via desktop shortcut or via the command line. I somehow have the feeling that it's an initialization problem when I look at the crash logs - funnily enough, restarting the computer has often helped when KODI didn't want to start at all, even after 20 attempts or so... |
Actually it's now starting to exhibit the same problem, so what helped was probably just the logout... |
Indeed, I just restarted the session (logout and login with Wayland this time) and it works fine (for now). |
@razzeee ok no problems.. how i can do this ?
@tmortagne yes.. if it's a purpose test no problems.. i can try to use Xorg instead wayland... |
|
@razzeee ok i thinks i have update my flatpak to 1.16.0. After that flatpak --version now say 1.16.0 I have reboot my Mini PC... At reboot i have tryed to use Kodi whit X.org instead using wayland....... apparently nothing changes. I have also tryed to leave only the mouse attached to one usb port... click on Kodi and sometimes crash other time kodi start.. Every time crash i can a new crashlog file it's created...... I even added the "data" folder to my favorites so I can delete the crashlog files it creates every now and then :) |
|
Every day a new game - today nothing seems to do it: /usr/bin/flatpak run --branch=stable --arch=x86_64 --command=kodi tv.kodi.Kodi --audio-backend=alsa |
|
5 minutes later no problem at all: /usr/bin/flatpak run --branch=stable --arch=x86_64 --command=kodi tv.kodi.Kodi --audio-backend=alsa |
|
@neo1973 and @razzeee about this request : Disconnect "Mouse" and my "Arcade Stick" from my MiniPC... leave connect only the Keyboard. Open a Terminal with CTRL+T and do this: In the 60 seconds of sleep i have disconnect also the Keyboard.... Kodi crash as ever also from terminal..... So.. whit this stupid test we can say it's not the 'udev' the issue ? |
|
output terminal: as ever the crashlog doesn't contain any info about really crash....: It may be a curiosity but when there are these immediate crashes the last line is always related to port 8080 and related to CWebserver. |
|
Day after day.... today crashlog generated until apparently kodi start succesfully (but need to see if crash after a lot of time without apparently same issue):
Lol.... there is definitely something that undermines the usual rock solid stability of kodi itself :) Hope bring back kodi works as ever :) |
|
|
|
The crash is well known and reproducible virtually by everyone so there is no point of reporting it happens here. We're waiting for someone to fix it. |
yes I know.. even ChatGPT if you ask for info it sends you back to this issue :) In fact, for now, as I said, I'm learning to live with the problem hoping that from one day to the next kodi doesn't become totally unusable at which point I'll get back to you. Thanks to the whole team for your patience. |
|
I've got a similar stacktrace as above: #0 __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
#1 0x0000728a76e9ae23 in __pthread_kill_internal (threadid=<optimized out>, signo=6) at pthread_kill.c:78
#2 0x0000728a76e4208e in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
#3 0x0000728a76e29882 in __GI_abort () at abort.c:79
#4 0x0000728a77f9493c in log_assert_failed (text=text@entry=0x728a77fbe0b0 "close_nointr(fd) != -EBADF", file=file@entry=0x728a77fbe09c "src/basic/fd-util.c", line=line@entry=75, func=<optimized out>) at ../src/basic/log.c:995
#5 0x0000728a77fa46d9 in safe_close (fd=fd@entry=59) at ../src/basic/fd-util.c:75
#6 0x0000728a77fb0296 in closep (fd=<synthetic pointer>) at ../src/basic/fd-util.h:45
#7 chaseat (dir_fd=<optimized out>, path=<optimized out>, flags=<optimized out>, ret_path=0x728a44bfeff8, ret_fd=<optimized out>) at ../src/basic/chase.c:84
#8 0x0000728a77fb4434 in chase.constprop.0 (path=0x728a18203a11 "sys/class/i2c-dev/i2c-10", ret_path=0x728a44bff080, ret_fd=0x728a44bff07c, flags=0, root=0x728a77fbe471 "/") at ../src/basic/chase.c:633
#9 0x0000728a77f9ecfa in device_set_syspath (device=0x728a18204770, _syspath=0x728a44bff1a0 "/sys/class/i2c-dev/i2c-10", verify=<optimized out>) at ../src/libsystemd/sd-device/sd-device.c:153
#10 0x0000728a77fb7e41 in device_new_from_syspath.constprop.0 (ret=ret@entry=0x728a44bff220, syspath=syspath@entry=0x728a44bff1a0 "/sys/class/i2c-dev/i2c-10", strict=true) at ../src/libsystemd/sd-device/sd-device.c:271
#11 0x0000728a77f97b93 in sd_device_new_from_syspath (ret=0x728a44bff220, syspath=0x728a44bff1a0 "/sys/class/i2c-dev/i2c-10") at ../src/libsystemd/sd-device/sd-device.c:280
#12 enumerator_scan_dir_and_add_devices (enumerator=enumerator@entry=0x728a18000e60, basedir=basedir@entry=0x728a77fbde47 "class", subdir1=subdir1@entry=0x728a18001b1b "i2c-dev", subdir2=subdir2@entry=0x0)
at ../src/libsystemd/sd-device/device-enumerator.c:723
#13 0x0000728a77f97f5f in enumerator_scan_dir (enumerator=enumerator@entry=0x728a18000e60, basedir=basedir@entry=0x728a77fbde47 "class", subdir=subdir@entry=0x0, subsystem=subsystem@entry=0x0)
at ../src/libsystemd/sd-device/device-enumerator.c:783
#14 0x0000728a77f9dc95 in enumerator_scan_devices_all (enumerator=0x728a18000e60) at ../src/libsystemd/sd-device/device-enumerator.c:962
#15 device_enumerator_scan_devices (enumerator=0x728a18000e60) at ../src/libsystemd/sd-device/device-enumerator.c:989
#16 device_enumerator_scan_devices (enumerator=0x728a18000e60) at ../src/libsystemd/sd-device/device-enumerator.c:969
#10 device_new_from_child (ret=0x7611c825b2f8, child=0x7611c825b2f0) at ../src/libsystemd/sd-device/sd-device.c:1066
#11 sd_device_get_parent (child=0x7611c825b2f0, ret=0x7611f5fff360) at ../src/libsystemd/sd-device/sd-device.c:1080
#12 0x00007612299ddf19 in device_new_from_parent (child=0x7611c825bf60) at ../src/libudev/libudev-device.c:381
#13 udev_device_get_parent (udev_device=0x7611c825bf60) at ../src/libudev/libudev-device.c:411
#14 0x000058219a57237a in PERIPHERALS::CPeripheralBusUSB::PerformDeviceScan (this=0x5821c5445410, results=...) at /run/build/kodi/xbmc/platform/linux/peripherals/PeripheralBusUSBLibUdev.cpp:111
#15 0x000058219b2e15c4 in PERIPHERALS::CPeripheralBus::ScanForDevices (this=0x5821c5445410) at /run/build/kodi/xbmc/peripherals/bus/PeripheralBus.cpp:128
#16 0x000058219a571e2d in PERIPHERALS::CPeripheralBusUSB::Process (this=0x5821c5445410) at /run/build/kodi/xbmc/platform/linux/peripherals/PeripheralBusUSBLibUdev.cpp:200
#17 0x000058219aa9370a in CThread::Action (this=0x5821c5445410) at /run/build/kodi/xbmc/threads/Thread.cpp:283
#18 0x000058219aa95105 in operator() (__closure=<optimized out>, pThread=0x5821c5445410, promise=...) at /run/build/kodi/xbmc/threads/Thread.cpp:152
#19 std::__invoke_impl<void, CThread::Create(bool)::<lambda(CThread*, std::promise<bool>)>, CThread*, std::promise<bool> > (__f=...) at /usr/include/c++/14.2.0/bits/invoke.h:61
#20 std::__invoke<CThread::Create(bool)::<lambda(CThread*, std::promise<bool>)>, CThread*, std::promise<bool> > (__fn=...) at /usr/include/c++/14.2.0/bits/invoke.h:96
#21 std::thread::_Invoker<std::tuple<CThread::Create(bool)::<lambda(CThread*, std::promise<bool>)>, CThread*, std::promise<bool> > >::_M_invoke<0, 1, 2> (this=<optimized out>) at /usr/include/c++/14.2.0/bits/std_thread.h:301
#22 std::thread::_Invoker<std::tuple<CThread::Create(bool)::<lambda(CThread*, std::promise<bool>)>, CThread*, std::promise<bool> > >::operator() (this=<optimized out>) at /usr/include/c++/14.2.0/bits/std_thread.h:308
#23 std::thread::_State_impl<std::thread::_Invoker<std::tuple<CThread::Create(bool)::<lambda(CThread*, std::promise<bool>)>, CThread*, std::promise<bool> > > >::_M_run(void) (this=<optimized out>)
at /usr/include/c++/14.2.0/bits/std_thread.h:253
#24 0x0000761228af69f4 in std::execute_native_thread_routine (__p=0x5821c4c64650) at ../../../../../libstdc++-v3/src/c++11/thread.cc:104
#25 0x0000761228898e0e in start_thread (arg=<optimized out>) at pthread_create.c:447
#26 0x000076122891d7d4 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:100 |
This comment has been minimized.
This comment has been minimized.
|
@ccope for purpose confrontation you can explain your hardware ? |
|
Intel NUC PAHi7 (11th Gen Core i7). Ubuntu 22.04, kernel 6.8.0-51, flatpak 1.16, running kodi-gbm 21.2. |
Lol another intel nuc... really interesting :) |
|
i am facing a similar issue. Kodi closes/crashes immediately after start.
Notebook
Yesterday while watching TV on Living room PC, Kodi closed/crashed suddenly. i guess it was when switching TV program. I went to my Notebook and started Kodi there and it crashed in the same way.
The logs are not much of a help for me, so i dragged my attention to AH2 Skin as it was crashing at that stage. Still on Notebook, i deleted guisettings.xml to get back to the default Skin and Kodi started again! I re-enabled AH2 Skin and Kodi crashed again on splash screen. Did the same on Living room PC with success. Maybe it's helpful?! |
|
@AdamNo2 no... it's not my skin the issue... i have tryed also to use the original estuary and crash happen randomly. |
Bug report
Describe the bug
Some days ago i have already reported this my issue on kodi.tv forum..... i have received one reply but i'm not fully understand if i need to do somethigs on my setup to fix the issue.
Anyway the issue it's descripted on the title:
Without any apparently error and without any warning or error the day before (the last night i use kodi how i ever do daily for watch youtube for example) about two days ago i have switch on my Intel Mini-PC and when at desktop i have try to launch Kodi but it's not start.
It seems to start but then it doesn't and in fact crashes after less than a minute so much so that it generates the crash file kodi_crashlog_xxxxxx.log where xxxx it's the date and time when crash appened.
Expected Behavior
Seeing the boot screen appear with the current skin that has been used for months now...
Actual Behavior
Described above
Possible Fix
I don't have idea...
To Reproduce
Steps to reproduce the behavior:
Debuglog
I can't obtain a DebugLog because I don't have the physical time to activate the function...
If i can enable it modifying some config files by hand let me know.
I can post the crashlog also posted on kodi.tv forum:
https://paste.kodi.tv/izunayuwem.kodi
Screenshots
I can made screenshot.. nothing appear on my TV :)
Additional context or screenshots (if appropriate)
...also here...
I have see one strange.. if i launch kodi directly from terminal apparently it's start. But after that for use kodi i need to maintain the terminal windows open in background.
Your Environment
Used Operating system:
Android
iOS
tvOS
Linux
macOS
Windows
Windows UWP
Operating system version/name: UBUNTU 24.04.1 LTS
Kodi version: 21.1 (21.1.0) Git:20240817-183eb85-dirty (directly from log upper here)
The text was updated successfully, but these errors were encountered: