-
-
Notifications
You must be signed in to change notification settings - Fork 6.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
kodi 21.0-4 crashing 6.5.3-1-MANJARO #25243
Comments
The full content of |
Thank you for using Kodi and our issue tracker. This is your friendly Kodi GitHub bot 😉 The issue that you have opened was marked as ignoring the rules of our bug tracker by a team member. Please review the following requirements for issue reports and make sure that you follow all of them:
Please understand that adherence to these rules is required for the team to be able to handle the volume of open issues efficiently. The issue will be closed after one week has passed without satisfactory follow-up from your side. |
@neo1973 I apologize I thought i had uploaded it, but its there now, I cant make the log debug because I cant get into kodi. |
Thanks :)
It looks like things go wrong here: xbmc/xbmc/rendering/gl/RenderSystemGL.cpp Lines 42 to 53 in 3b2688a
|
@neo1973 Interesting, so you think this is a deeper problem in my OS configuration rather than a kodi problem? The weird thing is I've had it running on here before, is there any way for me to refresh these libraries its using? |
Yes, that's most likely. If this would be a more common Kodi problem this would most likely already have been reported.
If you did everything through the package manager then I can't think of problem that would be fixed by reinstalling packages. But you can try to launch Kodi with the |
This report sounds awfully close to #18076 |
Cheerio mate, that was it. |
…nter There is no meaningful way to proceed, therefore terminate. Fixes xbmc#25243.
… a null pointer There is no meaningful way to proceed, therefore terminate. Fixes xbmc#25243.
… a null pointer There is no meaningful way to proceed, therefore terminate. Fixes xbmc#25243.
… a null pointer There is no meaningful way to proceed, therefore terminate. Fixes xbmc#25243.
… a null pointer There is no meaningful way to proceed, therefore terminate. Fixes xbmc#25243.
… a null pointer There is no meaningful way to proceed, therefore terminate. Fixes xbmc#25243.
kodi_crashlog-20240523_120343.log
Bug report
Describe the bug
Here is a clear and concise description of what the problem is:
I have installed kodi using pacman from the offiicial repos and it crashes on start.
I'm just an average linux user, I've successfully run kodi on this machine and os instance before, however after some time sound was not functioning I suspected that this had to do with my sound configuration, but that turned out to be incorrect as YouTube and other programs were working along with DAW software such as reaper. I use pulseaudio and I'm pretty certain its all in order.
I began to receive errors about libvdpau-va-gl, so i installed it and then it would just seg fault. So I removed kodi using pacman -R and reinstalled it, only to have the same crashing problem.
when pacman -R'ing kodi I ensured that there were no mentions of kodi on my system with sudo find / -iname kodi ---> output was empty
Expected Behavior
Here is a clear and concise description of what was expected to happen:
Actual Behavior
Possible Fix
To Reproduce
Steps to reproduce the behavior:
Debuglog
The debuglog can be found here:
Screenshots
Here are some links or screenshots to help explain the problem:
Additional context or screenshots (if appropriate)
Here is some additional context or explanation that might help:
Your Environment
Used Operating system:
Android
iOS
tvOS
[ x] Linux
macOS
Windows
Windows UWP
Operating system version/name:
Kodi version: kodi 21.0-4
OS: 6.5.3-1-MANJARO
note: Once the issue is made we require you to update it with new information or Kodi versions should that be required.
Team Kodi will consider your problem report however, we will not make any promises the problem will be solved.
The text was updated successfully, but these errors were encountered: