Admin message

Due to an influx of spam, we have had to require each new account to be manually approved. Please register an account and then write an email to accountsupport@archlinux.org to get it approved. Sorry for the inconvenience.

python-gobject 3.52 breaks multiple apps (libpeas related)
<!-- Please read our Bug reporting guidelines before opening a bug: https://wiki.archlinux.org/title/Bug_reporting_guidelines If you want to help catching more bugs upfront, consider joining the Arch Testing Team: https://wiki.archlinux.org/title/Arch_Testing_Team --> # 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
issue