• 1
  • 14
  • 15
  • 16(current)
  • 17
  • 18
Kodi from Debian - Support Thread
(2024-06-28, 09:04)TheJezstarr Wrote: <snip>
Code:
Fatal Python error: PyImport_AppendInittab: PyImport_AppendInittab() may not be called after Py_Initialize()
which suggests it might be about a Python3 update, rather than Kodi?
https://github.com/xbmc/xbmc/issues/24069
I suppose this means that Kodi won't work on Debian Testing until Omega comes through? Looks like it was rejected from Experimental?
Reply
Hi,

I am also having kodi crash on start on debian testing with these errors in the logs since upgrading from 2:20.5+dfsg-2+b1 to 2:20.5+dfsg-2+b2:

Code:

Fatal Python error: PyImport_AppendInittab: PyImport_AppendInittab() may not be called after Py_Initialize()
Thread 0x00007f10d74006c0 (most recent call first):
  <no Python frame>
Aborted (core dumped)

I tried quite a few steps to diagnose this:
​​​​​​* Rolling back to 2:20.5+dfsg-2+b1 from the snapshot repo and kodi still crashed
* Removing my .kodi folder and kodi can run
* Restoring my .kodi folder and 2:20.5+dfsg-2+b1 or 2:20.5+dfsg-2+b2 crash leading me to think 2:20.5+dfsg-2+b2 changed something in my .kodi folder
* Restoring my .kodi folder and leaving out either .kodi/addons OR .kodi/userdata will let kodi run

I am not sure what is my best next step to find when the issue is as I dont want to have to delete either userdata or all the addons and configs.
Reply
Pretty sure the problem is compatibility with the newer version of Python3, so only rolling back Python3 will fix it, but that'll come with all kinds of dependency hell.
Reply
I did not upgrade my python version when kodi started crashing. As per my apt log here are the upgrades at the time: pastebin. Nothing python in there.
Reply
(2024-07-02, 22:23)samsquanche Wrote: I did not upgrade my python version when kodi started crashing. As per my apt log here are the upgrades at the time: pastebin. Nothing python in there.

Ah, I see. The error you're getting is the same one as I am, but the bug report
https://github.com/xbmc/xbmc/issues/24069
blames python, and I did update a couple of python packages. Good to know I don't have to manage that chaos!

It doesn't seem to be addon related, either, as there's about a week between my last addon update, and the problem starting.
I can get Kodi to run by replicating your steps, though.
Reply
Started with a new .kodi directory, and adding in addons one-by-one. Have found two culprits so far, so will report in the appropriate location. Not a Kodi for Debian problem Smile
Reply
I have uploaded the bugfix releases for all 20.x into unstable - hope in 2-3 days they will be in testing.

Now switching back to v21 as upcoming ffmpeg7 transition needs my attention and slows mr down significantly Sad
Maintainer of Kodi from Debian | Got an issue with Kodi from Debian? Report it here: Kodi from Debian - Support Thread
Reply
(2024-07-03, 07:59)basilgello Wrote: I have uploaded the bugfix releases for all 20.x into unstable - hope in 2-3 days they will be in testing.

Now switching back to v21 as upcoming ffmpeg7 transition needs my attention and slows mr down significantly Sad

Thanks for all your hard work, @basilgello. I've been following the progress of the Kodi 20.x packages via the Debian QA tracker, but it seems Kodi 20.5 is still stuck in testing. Do you know when Kodi 20.5 will make it into stable for Debian 12?

Ideally, I'd like to see Kodi 21.x make it into stable given it's been 4 months since v21's release, but I'm not sure if you're still working on that. Any progress since 5 weeks ago?
Reply
I prepared 21.x a week ago, tested and attempted to upload to experimental than to unstable, but FTP Masters think different:

https://lists.debian.org/debian-multimed...00087.html (and thread)
https://lists.debian.org/debian-multimed...00269.html (and thread)

I am now blocked in this trap and either I persuade to accept my vision of Kodi, or it will get removed from Debian 13 / testing Sad
Maintainer of Kodi from Debian | Got an issue with Kodi from Debian? Report it here: Kodi from Debian - Support Thread
Reply
(2024-08-17, 17:06)basilgello Wrote: I prepared 21.x a week ago, tested and attempted to upload to experimental than to unstable, but FTP Masters think different:

https://lists.debian.org/debian-multimed...00087.html (and thread)
https://lists.debian.org/debian-multimed...00269.html (and thread)

I am now blocked in this trap and either I persuade to accept my vision of Kodi, or it will get removed from Debian 13 / testing Sad

Well that seems rather unreasonable and inconsistent with their existing rules (as you noted LibreOffice is allowed!)

Does this mean you'll have to maintain an unofficial repo, like you did for Buster, then?
Reply
(2024-08-17, 17:06)basilgello Wrote: I am now blocked in this trap and either I persuade to accept my vision of Kodi, or it will get removed from Debian 13 / testing Sad
This outcome should be avoided at all costs - up to and including acquiescing to their requests (however inconsistent or unreasonable we may believe them to be).

Debian (and its derivatives) are the single most used/most popular Linux distributions on user-facing end devices. There are considerable benefits that come with inclusion in the default package repo (trust, ease-of-use, reliable and fast repo mirrors, default inclusion in the repos for derivative distros) that Kodi will not benefit from if we create our own unofficial repo.

By my reading of the linked threads, the Debian Multimedia Maintainers are asking for the following:
  1. Do not create dozens of small language packages.
  2. Mention debian/dh-addon in debian/copyright.
  3. Acknowledge Kodi Translators and add them to debian/copyright.
  4. Do not mix GPL-2 software with GPL-3+ software.
You appear to have already addressed points 2 and 3, while point 4 seems to be a non-issue since (as you correctly pointed out) the GPL-3+ software at issue is not compiled into a binary, but rather an interpreted script.

Point 1 appears to be the last remaining issue the Debian Multimedia Maintainers have raised. Reading the linked bug report, I see that we pursued this idea of splitting each language up into its own individual package as a way to help a user complaining about too many languages showing up in their addon interface, making it difficult for that user to navigate that menu (which, in turn, was driven by another bug where a user was trying to use Kodi and switch to their preferred language without an internet connection).

While I love the fact that we're trying to deliver the best Kodi experience we can, bug reports like - where we're solving issues for less common use cases (once a Kodi install is configured, how often are users going into this submenu where they're inconvenienced by 77 alternate languages) - should not impair our access to a major distribution.

In this specific case, it seems to me we'd be doing the greatest good for the Kodi project by ensuring we're properly included in the Debian repos (which will then flow down to all the other derivative distros). If this means packaging up all the languages into a single package and suffering the inconvenience of having 77 languages show up in a submenu of the addon interface, so be it. It may result in a slightly degraded user experience for people who frequently scroll through that addon menu as that one user highlights in their bug report, but this poor user experience can be remediated in other ways (as you helpfully indicated in a potential solution you proposed to "mark the addons as 'uninstalled' in the user profile").

Alternatively, the default language in Kodi is English. If the Debian Multimedia Maintainers which to see fewer packages, then perhaps we lump the several English variants into one package (English, English (Australian), English (New Zealand), English (US)), while all others are included in another?

Hopefully, they'll see the logic of your response (i.e., LibreOffice does the same thing), but if they don't, then I don't think this is a hill we should be willing to die on.

At the end of the day, it'll be better for Kodi and its users if we're included in the standard repos vs. asking some users on some distributions to fall back to using an unofficial repo.
Reply
Quick update: I crafted another fix that bypasses NEW queue entirely and eliminates the need to split langpacks.

The idea us to create a local repository with language addons only in /usr/share/kodi and declare it official so addons from there can be later autoupdated by addons from mirrors.kodi.tv
Needs some testing but I am determined to get it accepted tonight Smile
Maintainer of Kodi from Debian | Got an issue with Kodi from Debian? Report it here: Kodi from Debian - Support Thread
Reply
That is excellent news. I'll continue to monitor the Debian QA tracker and once the packages go live, I'd be happy to help test/confirm everything works.
Reply
21.1 and full set of addons uploaded to unstable! As promised Smile

To test the bugfix for language, do not install kodi-repository-kodi, create new kodi masterprofile (new .kodi dur) and try setting language in Ssttings - Intefface - Region to any of choice.
Maintainer of Kodi from Debian | Got an issue with Kodi from Debian? Report it here: Kodi from Debian - Support Thread
Reply
That's great to hear. In your experience, about how long does it usually take for a package like 21.1 to propagate from Unstable to the Stable repo?

I've got a fully-updated version of Debian 12.6 ready to go that I'd be happy to test on, but would like to remain on Stable due to other roles my HTPC machine fulfills (hypervisor, SQL server, web server, file server).
Reply
  • 1
  • 14
  • 15
  • 16(current)
  • 17
  • 18

Logout Mark Read Team Forum Stats Members Help
Kodi from Debian - Support Thread0