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 <module>
from UpdateManager.UpdateManager import UpdateManager
File "/home/nteodosio/canonical/ubuntu-pro/update-manager/UpdateManager/UpdateManager.py", line 24, in <module>
gi.require_version('Gdk', '4.0')
File "/usr/lib/python3/dist-packages/gi/__init__.py", line 113, in require_version
raise ValueError('Namespace %s is already loaded with version %s' %
ValueError: Namespace Gdk is already loaded with version 3.0
<---
So I think this would just introduce such error in the other direction (4->3).
2. Actually the new_from_name constructor has different signatures in Gdk 3 and 4.
I also couldn't reproduce the issue in an unaltered Noble beta ISO.
As such, I suggest to let this sit unattended until confirmed.
1. Testing that the other way around (3->4), I get
---> dir=$PWD/ data nteodosio/ canonical/ ubuntu- pro/update- manager/ ./update- manager" , line 38, in <module> UpdateManager import UpdateManager nteodosio/ canonical/ ubuntu- pro/update- manager/ UpdateManager/ UpdateManager. py", line 24, in <module> require_ version( 'Gdk', '4.0') python3/ dist-packages/ gi/__init_ _.py", line 113, in require_version 'Namespace %s is already loaded with version %s' %
% ./update-manager --data-
Traceback (most recent call last):
File "/home/
from UpdateManager.
File "/home/
gi.
File "/usr/lib/
raise ValueError(
ValueError: Namespace Gdk is already loaded with version 3.0
<---
So I think this would just introduce such error in the other direction (4->3).
2. Actually the new_from_name constructor has different signatures in Gdk 3 and 4.
I also couldn't reproduce the issue in an unaltered Noble beta ISO.
As such, I suggest to let this sit unattended until confirmed.