Skip to content
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

Closed
6 tasks
anthonybtedesco opened this issue May 23, 2024 · 8 comments · Fixed by #25245
Closed
6 tasks

kodi 21.0-4 crashing 6.5.3-1-MANJARO #25243

anthonybtedesco opened this issue May 23, 2024 · 8 comments · Fixed by #25245
Labels
Triage: Needed (managed by bot!) issue that was just created and needs someone looking at it

Comments

@anthonybtedesco
Copy link

anthonybtedesco commented May 23, 2024

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:

[mattricks@lauer ~]$ cat kodi_crashlog-20240523_120343.log | grep error
#6  0x00007f41ad2ab3dd in __cxxabiv1::__cxa_throw (obj=<optimized out>, tinfo=0x55ebf534df98 <typeinfo for fmt::v10::format_error>, dest=0x7f41adf013c0) at /usr/src/debug/gcc/gcc/libstdc++-v3/libsupc++/eh_throw.cc:98
#7  0x00007f41adf00065 in fmt::v10::detail::throw_format_error(char const*) () at /usr/lib/libfmt.so.10
2024-05-23 12:03:42.926 T:2912    error <general>: DBus error: org.freedesktop.DBus.Error.InvalidArgs - No such property “OnLowBattery”
2024-05-23 12:03:42.927 T:2912    error <general>: DBus error: org.freedesktop.DBus.Error.InvalidArgs - No such property “CanSuspend”
2024-05-23 12:03:42.927 T:2912    error <general>: DBus error: org.freedesktop.DBus.Error.InvalidArgs - No such property “CanHibernate”
[mattricks@lauer ~]$

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.

@xbmc-gh-bot xbmc-gh-bot bot added the Triage: Needed (managed by bot!) issue that was just created and needs someone looking at it label May 23, 2024
@neo1973
Copy link
Member

neo1973 commented May 23, 2024

The full content of kodi_crashlog-20240523_120343.log is required, I can't work with just the snippets.

@neo1973 neo1973 added the Ignored rules issue that does not follow the rules (no template, missing debug log, ...) label May 23, 2024
@xbmc-gh-bot
Copy link

xbmc-gh-bot bot commented May 23, 2024

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:

  • Reports must follow our template and have all relevant fields filled in.
  • A full debug log is always mandatory.
    • Make sure that you restart Kodi after setting the log level to debug.
    • Log files may not be modified except for the removal of personally identifying information, usernames/passwords and similar.
    • For build errors, include a full build log instead.
  • You may not have any banned add-ons installed.
  • Bugs should be reproduced on a clean Kodi installation whenever possible.

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.

@anthonybtedesco
Copy link
Author

anthonybtedesco commented May 23, 2024

@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.

@neo1973
Copy link
Member

neo1973 commented May 23, 2024

Thanks :)

Thread 1 (Thread 0x7f41a8723bc0 (LWP 2912)):
#0  0x00007f41ad087194 in ??? () at /usr/lib/libc.so.6
#1  0x00007f41ad033d70 in raise () at /usr/lib/libc.so.6
#2  0x00007f41ad01b4c0 in abort () at /usr/lib/libc.so.6
#3  0x00007f41ad297a9b in __gnu_cxx::__verbose_terminate_handler () at /usr/src/debug/gcc/gcc/libstdc++-v3/libsupc++/vterminate.cc:95
#4  0x00007f41ad2ab10c in __cxxabiv1::__terminate (handler=<optimized out>) at /usr/src/debug/gcc/gcc/libstdc++-v3/libsupc++/eh_terminate.cc:48
#5  0x00007f41ad2ab179 in std::terminate () at /usr/src/debug/gcc/gcc/libstdc++-v3/libsupc++/eh_terminate.cc:58
#6  0x00007f41ad2ab3dd in __cxxabiv1::__cxa_throw (obj=<optimized out>, tinfo=0x55ebf534df98 <typeinfo for fmt::v10::format_error>, dest=0x7f41adf013c0) at /usr/src/debug/gcc/gcc/libstdc++-v3/libsupc++/eh_throw.cc:98
#7  0x00007f41adf00065 in fmt::v10::detail::throw_format_error(char const*) () at /usr/lib/libfmt.so.10
#8  0x00007f41adf0e388 in ??? () at /usr/lib/libfmt.so.10
#9  0x00007f41adf0e4ee in void fmt::v10::detail::vformat_to<char>(fmt::v10::detail::buffer<char>&, fmt::v10::basic_string_view<char>, fmt::v10::detail::vformat_args<char>::type, fmt::v10::detail::locale_ref) () at /usr/lib/libfmt.so.10
#10 0x00007f41adf0ea24 in fmt::v10::vformat[abi:cxx11](fmt::v10::basic_string_view<char>, fmt::v10::basic_format_args<fmt::v10::basic_format_context<fmt::v10::appender, char> >) () at /usr/lib/libfmt.so.10
#11 0x000055ebf2c2d8a5 in CRenderSystemGL::InitRenderSystem() ()
#12 0x000055ebf3188bfe in CApplication::InitWindow(RESOLUTION) ()
#13 0x000055ebf3190d3b in CApplication::CreateGUI() ()
#14 0x000055ebf30206a6 in XBMC_Run ()
#15 0x000055ebf2a49751 in main ()

It looks like things go wrong here:

// Get the GL version number
m_RenderVersionMajor = 0;
m_RenderVersionMinor = 0;
const char* ver = (const char*)glGetString(GL_VERSION);
if (ver != 0)
{
sscanf(ver, "%d.%d", &m_RenderVersionMajor, &m_RenderVersionMinor);
m_RenderVersion = ver;
}
CLog::Log(LOGINFO, "CRenderSystemGL::{} - Version: {}, Major: {}, Minor: {}", __FUNCTION__, ver,
m_RenderVersionMajor, m_RenderVersionMinor);

glGetString seems to return null, CLog::Log throws an exception because of that, that isn't caught and Kodi gets terminated. We can fix the crash here but even so I have doubts that things will work then because glGetString returning null hints on something being very strange.

@neo1973 neo1973 removed the Ignored rules issue that does not follow the rules (no template, missing debug log, ...) label May 23, 2024
@anthonybtedesco
Copy link
Author

@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?

@neo1973
Copy link
Member

neo1973 commented May 23, 2024

Interesting, so you think this is a deeper problem in my OS configuration rather than a kodi problem?

Yes, that's most likely. If this would be a more common Kodi problem this would most likely already have been reported.

The weird thing is I've had it running on here before, is there any way for me to refresh these libraries its using?

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 --debug option, this will create a debug log and maybe it contains some useful additional information.

@sarbes
Copy link
Member

sarbes commented May 23, 2024

This report sounds awfully close to #18076

@anthonybtedesco
Copy link
Author

anthonybtedesco commented May 23, 2024

This report sounds awfully close to #18076

Cheerio mate, that was it.
EDIT: remove libvdpau-va-gl

neo1973 added a commit to neo1973/xbmc that referenced this issue May 23, 2024
…nter

There is no meaningful way to proceed, therefore terminate.

Fixes xbmc#25243.
garbear pushed a commit to garbear/xbmc that referenced this issue Jul 4, 2024
… a null pointer

There is no meaningful way to proceed, therefore terminate.

Fixes xbmc#25243.
garbear pushed a commit to garbear/xbmc that referenced this issue Jul 4, 2024
… a null pointer

There is no meaningful way to proceed, therefore terminate.

Fixes xbmc#25243.
garbear pushed a commit to garbear/xbmc that referenced this issue Jul 4, 2024
… a null pointer

There is no meaningful way to proceed, therefore terminate.

Fixes xbmc#25243.
garbear pushed a commit to garbear/xbmc that referenced this issue Jul 4, 2024
… a null pointer

There is no meaningful way to proceed, therefore terminate.

Fixes xbmc#25243.
garbear pushed a commit to garbear/xbmc that referenced this issue Jul 6, 2024
… a null pointer

There is no meaningful way to proceed, therefore terminate.

Fixes xbmc#25243.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Triage: Needed (managed by bot!) issue that was just created and needs someone looking at it
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants