Bug#1100726: kodi: Segmentation fault at startup

2025-03-26 Thread Alban Browaeys
Control: notfound -1 2:21.2+dfsg-3 Nevermind I found the rational in the Debian changelog. It turned out I did not upgrade kodi-pvr-nextpvr 21.3.1+ds-1 from trixie which also depends on lintinyxml2 but version 10, to kodi-pvr- nextpvr 21.3.2+ds-1 which depends on libtinyxml11. So the mixup of tin

Bug#1100726: kodi: Segmentation fault at startup

2025-03-26 Thread Alban Browaeys
Control: notfound -1 2:21.2+dfsg-3 Nevermind I found the rational in the Debian changelog. It turned out I did not upgrade kodi-pvr-nextpvr 21.3.1+ds-1 from trixie which also depends on lintinyxml2 but version 10, to kodi-pvr- nextpvr 21.3.2+ds-1 which depends on libtinyxml11. So the mixup of tin

Bug#1100726: kodi: Segmentation fault at startup

2025-03-26 Thread Alban Browaeys
Package: kodi Version: 2:21.2+dfsg-3 Followup-For: Bug #1100726 Dear Maintainer, With the revert of the fix for this bug in kodi 2:21.2+dfsg-3, this crash at startup is back. I see no rationale for this revert. Was it intentional to push the revert to Debian? I have: ii libtinyxml-dev:amd64

Bug#1100726: kodi: Segmentation fault at startup

2025-03-17 Thread Vasyl Gello
The bug is caused by stack corruption in new tinyxml2 library which migrated yesterday: #0 0x753cac71 in tinyxml2::XMLDocument::XMLDocument (this=this@entry=0x7fffdf50, processEntities=processEntities@entry=true, whitespaceMode=whitespaceMode@entry=tinyxml2::PRESERVE_WHITESPAC

Bug#1100726: kodi: Segmentation fault at startup

2025-03-17 Thread tv.debian
Hello, I am seeing the same on two Sid systems, one long time running Kodi, one tried fresh as a test. For me it was concomitant with a recent libc6 update in Sid. Crash log as follows: ## Kodi CRASH LOG ### SYSTEM INFO Date: Mon Mar

Bug#1100726: kodi: Segmentation fault at startup

2025-03-17 Thread Mathieu
Package: kodi Version: 2:21.2+dfsg-1 Severity: grave Justification: renders package unusable Hi, Since last upgrade on Friday, kodi crashes right at startup (segfault). I tried with a brand new profile too, without any success. Unfortunately, neither the stack trace nor the debug log helped me pi