Just curious, is there any action planned on this issue, as in either
shipping 2.1.0, or shipping the patch? Otherwise we'll be shipping a
Sigil build with broken plugin functionality out of the box.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Upstream released Sigil 2.1.0, carrying this patch, so it's no longer
necessary if an upgrade is planned.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055345
Title:
sigil < 2.1.0 plugin support
** Bug watch added: Debian Bug tracker #1064992
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064992
** Also affects: sigil (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064992
Importance: Unknown
Status: Unknown
--
You received this bug notification
** Summary changed:
- sigil <= 2.1.0 plugin support broken by Python 3.12
+ sigil < 2.1.0 plugin support broken by Python 3.12
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055345
Title:
sigil <
Public bug reported:
(Ubuntu 24.04 daily)
Due to a rather poorly documented API change in Python's ctypes module
in 3.12.0a4 and newer, Sigil versions less than the yet to be released
2.1.0 exhibit broken plugin support when running using Python 3.12 as
their interpreter.
The issue was
For what it's worth, this is still happening with noble.
Since the shipped /etc/apparmor.d/usr.sbin.cups-browsed fortunately
specifies "#include ", this can be worked
around without causing further headaches by adding the following to
/etc/apparmor.d/local/usr.sbin.cups-browsed (create that file
