python-gobject 3.52 breaks multiple apps (libpeas related)

Description:

Upgrading to python-gobject from 3.50 to 3.52 breaks rhythmbox. At launch 3 warnings are displayed and then rhythmbox hangs indefinitely.

$ rhythmbox
/usr/lib/python3.13/site-packages/gi/module.py:57: Warning: cannot register existing type 'GIRepository'
  repository = Repository.get_default()
/usr/lib/python3.13/site-packages/gi/module.py:57: Warning: g_once_init_leave_pointer: assertion 'result != 0' failed
  repository = Repository.get_default()
/usr/lib/python3.13/site-packages/gi/module.py:57: Warning: g_object_new_with_properties: assertion 'G_TYPE_IS_OBJECT (object_type)' failed
  repository = Repository.get_default()

Downgrading python-gobject to 3.50 solves the issue.

Additional info:

• package version(s): 3.52.3-2
• config and/or log files: N/A
• link to upstream bug report, if any: none

I'm not sure whether it's an issue with rhythmbox or python-gobject. In one hand, rhythmbox has not changed since 2024/11/12 and therefore the issue might be on the python-gobject since it's caused by upgrading it to 3.52. On the other hand, Gimp works fine although it also depends on python-gobject.

On my system cache I only have python-gobject versions 3.50.0-1, 3.50.0-2 and 3.52.3-2. I haven't tested it against versions 3.52.2-1, 3.52.2-2 and 3.52.3-1.

I'm not sure either if this is a packaging or upstream issue. I looked at both rhythmbox and python-gobject issues list and didn't found anything that sounds related. I also looked at the python-gobject change log and haven't found anything that sounds related. I therefore assume this might eventually be a packaging issue, although I don't know how to explain it.

• https://gitlab.gnome.org/GNOME/pygobject/-/issues
• https://gitlab.gnome.org/GNOME/rhythmbox/-/issues
• https://pygobject.gnome.org/changelog.html

Steps to reproduce:

1. upgrade pacman -Suy
2. start rhythmbox: it stalls indefinitely
3. downgrade pacman -U /var/cache/pacman/pkg/python-gobject-3.50.0-2-x86_64.pkg.tar.zst
4. start rhythmbox: it works

added priority3-normal severity4-low statusunconfirmed labels

assigned to @freswa, @toolybird, and @gromit

changed title from Upgrading to python-gobject from 3.50 to 3.52 breaks rhythmbox to Upgrading python-gobject from 3.50 to 3.52 breaks rhythmbox

python-gobject 3.52.3-2 also breaks liferea 1.14.6-1.

I'm currently having this problem with xed. The error messages are exactly the same.

Thanks for the report. There is definitely some kind of problem. Same error in: gedit-plugins#3 (closed)

Rebuilding the affected pkgs doesn't solve it. It's looking like a git bisect is required to identify the offending upstream commit...

added scoperegression severity2-high statusconfirmed labels and removed severity4-low statusunconfirmed labels

assigned to @heftig and @fabiscafe and unassigned @freswa, @toolybird, and @gromit

The problem is that python-gobject now uses libgirepository-2.0 (glib2 package), which cannot coexist with libgirepository-1.0 (libgirepository package) in the same process. What a mess.

Oh dear...not good. So far it appears all the reported broken apps are also linked to libpeas.. so yeah, kinda makes sense.

Maybe it's best if affected folks temporarily downgrade to python-gobject-3.50.0-2 and stay there until a solution is worked out? I'll test to see if this is viable...

Does it mean that all packages that depend on both libgirepository-1.0 and python-gobject need to be rebuilt to use libgirepository-2.0.so from glib2 package? Is it feasible?

UPD: From what I see these packages are: blueprint-compiler, eog/eog-plugins, gedit/gedit-plugins, gitg, gnome-music, gobject-introspection/gobject-introspection-runtime, libpeas/libpeas-demos, mutter, rhythmbox, totem, python-twisted.

UPD2: Maybe just dropping libgirepository-1.0 dependency is enough for that?

changed title from Upgrading python-gobject from 3.50 to 3.52 breaks rhythmbox to python-gobject 3.52 breaks multiple apps (libpeas related)

mentioned in issue gedit-plugins#3 (closed)

marked gedit-plugins#3 (closed) as a duplicate of this issue

marked this issue as related to gedit-plugins#3 (closed)

mentioned in issue libpeas#2 (closed)

marked libpeas#2 (closed) as a duplicate of this issue

marked this issue as related to libpeas#2 (closed)

mentioned in commit libpeas@75310ec6

Removed the python3 loader from libpeas. Not loading Python plugins is preferable to crashing when trying to do so.

Can we expect to be able to use them again in near future?

I'm not working on that.