This bug was fixed in the package update-manager - 1:24.04.5
---
update-manager (1:24.04.5) noble; urgency=medium
* Require Gdk3, as at least one function is used that is not in Gdk4
(LP: #2054197).
* Run linting tests during build time as well.
[ Calvin Mwadime ]
*
** Changed in: update-manager (Ubuntu)
Status: New => Fix Committed
** Changed in: update-manager (Ubuntu)
Assignee: (unassigned) => Nathan Teodosio (nteodosio)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
> So I think this would just introduce such error in the other direction
(4->3).
That was a short-sighted conclusion, adding the require_version to the
entry point script will do.
** Merge proposal linked:
https://code.launchpad.net/~nteodosio/update-manager/+git/update-manager/+merge/464333
1. Testing that the other way around (3->4), I get
--->
% ./update-manager --data-dir=$PWD/data
Traceback (most recent call last):
File "/home/nteodosio/canonical/ubuntu-pro/update-manager/./update-manager",
line 38, in
from UpdateManager.UpdateManager import UpdateManager
File
I can't reproduce this exact error, but I do get an error if the Gdk
imported is version 4:
>>> from gi.repository import Gdk
:1: PyGIWarning: Gdk was imported without specifying a version first.
Use gi.require_version('Gdk', '4.0') before import to ensure that the right
version gets loaded.
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
