Ubuntu
frescobaldi package

  1. Bug #1993213
  2. Comment #0

Comment 0 for bug 1993213

Revision history for this message
Abou Samra Jean (jean-abou-samra) wrote :

Ubuntu Jammy LTS ships Python 3.10 and Frescobaldi 3.1, but Frescobaldi 3.1 is known not to work with Python 3.10 due to a backwards-incompatible Python change that makes Python stricter about implicit type conversions in C extensions. See

https://github.com/frescobaldi/frescobaldi/issues/1398#issuecomment-1253599338

To reproduce, it should be enough to install Frescobaldi and try to compile any file, to get a backtrace like the one on the linked comment on GitHub. This bug manifests in several places, so the actual backtrace may be different.

This issue has been fixed in Frescobaldi 3.2.

So, right now, the Frescobaldi package in Jammy doesn't work at all. Therefore, please upgrade it to 3.2 so that it becomes usable again.

I am aware that upgrading a package within a stable release of Ubuntu is unusual, but this case is mentioned in the guidelines,

https://wiki.ubuntu.com/StableReleaseUpdates says:

“Stable release updates will, in general, only be issued in order to fix high-impact bugs. Examples of such bugs include:

[...]

    Bugs which represent severe regressions from the previous release of Ubuntu. This includes packages which are totally unusable, like being uninstallable or crashing on startup.”

Thank you.