pygobject 
 15:11: 
 From: owner@bugs.debian.org 
  
 This is a multi-part message in MIME format... 
  
 Your message dated Wed, 05 Nov 2025 15:09:56 +0000 
 with message-id  
 and subject line Bug#1118501: fixed in entangle 3.0-6 
 has caused the Debian Bug report #1118501, 
 regarding entangle: not compatible with pygobject >= 3.52 
 to be marked as done. 
  
 This means that you claim that the problem has been dealt with. 
 If this is not the case it is now your responsibility to reopen the 
 Bug report if necessary, and/or fix the problem forthwith. 
  
 (NB: If you are a system administrator and have no idea what this 
 message is talking about, this may indicate a serious mail system 
 misconfiguration somewhere. Please contact owner@bugs.debian.org 
 immediately.) 
  
  
 -- 
 1118501: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1118501 
 Debian Bug Tracking System 
 Contact owner@bugs.debian.org with problems 
  
 Received: (at submit) by bugs.debian.org; 21 Oct 2025 11:57:38 +0000 
 X-Spam-Checker-Version: SpamAssassin 4.0.1-bugs.debian.org_2005_01_02 
  (2024-03-25) on buxtehude.debian.org 
 X-Spam-Level: 
 X-Spam-Status: No, score=-116.2 required=4.0 tests=BAYES_00, 
  BODY_INCLUDES_PACKAGE,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID, 
  DKIM_VALID_AU,DKIM_VALID_EF,FROMDEVELOPER,HAS_PACKAGE,SPF_HELO_NONE, 
  SPF_NONE,UNPARSEABLE_RELAY,USER_IN_DKIM_WELCOMELIST autolearn=ham 
  autolearn_force=no version=4.0.1-bugs.debian.org_2005_01_02 
 X-Spam-Bayes: score:0.0000 Tokens: new, 15; hammy, 150; neutral, 90; spammy, 
  0. spammytokens: 
  hammytokens:0.000-+--Hx-spam-relays-external:sk:stravin, 
  0.000-+--H*RT:sk:stravin, 0.000-+--Hx-spam-relays-external:311, 
  0.000-+--H*RT:311, 0.000-+--H*RT:108 
 Return-path:  
 Received: from stravinsky.debian.org ([2001:41b8:202:deb::311:108]:38364) 
  by buxtehude.debian.org with esmtps (TLS1.3:ECDHE_ 
 SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) 
  (Exim 4.96) 
  (envelope-from ) 
  id 1vBAzi-00B8Br-09 
  for submit@bugs.debian.org; 
  Tue, 21 Oct 2025 11:57:38 +0000 
 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=debian. 
 org; 
  s=smtpauto.stravinsky; h=X-Debian-User:Content-Type:MIME-Version:Message- 
 ID: 
  Subject:To:From:Date:Reply-To:Cc:Content-Transfer-Encoding:Content-ID: 
  Content-Description:In-Reply-To:References; 
  bh=asheXPbrSAzwvjj39q+juMO/icsXJgd+nPCKsQhTTBs=; b 
 =PNcQP5pJSMnNAhdKjAx1OWt6nq 
  +DqPcm/kHkhIsoToJ9/r7+U7Q36NR+lnnJl/Xh80f5QeO/E2qn 
 CC83eQblsyAgq/bnOvqVXRj7G+i 
  SFd4fNcyQk5GNPJ8bUX8pujzd45Kd1j7xDsQ/PxKtmBM//7e7P 
 MoziGgpz1WCtE2WiSOq9HflNmR0 
  gh6JEToDSvHgSLr/Y6fkQhjHtFZ6+ICIlcsALDaTde0jqWdsVL 
 5tQl4zn0Qw2d6pfXmSDJdsLqAv9 
  mBE3+L4rObnARWE/NLj8cLYL5cqg5lh3lJokL071bn8S5e8koh 
 bI+Dr6UtAA/3TxaAvvM1mMo5yXS 
  aPHMXueA==; 
 Received: from authenticated user 
  by stravinsky.debian.org with esmtpsa (TLS1.3:ECDH 
 E_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) 
  (Exim 4.94.2) 
  (envelope-from ) 
  id 1vBAzg-006ZSH-68 
  for submit@bugs.debian.org; Tue, 21 Oct 2025 11:57:36 +0000 
 Date: Tue, 21 Oct 2025 12:57:34 +0100 
 From: Simon McVittie  
 To: Debian Bug Tracking System  
 Subject: entangle: not compatible with pygobject >= 3.52 
 Message-ID:  
 MIME-Version: 1.0 
 Content-Type: text/plain; charset=us-ascii 
 Content-Disposition: inline 
 X-Debian-User: smcv 
 Delivered-To: submit@bugs.debian.org 
  
 Package: entangle 
 Version: 3.0-5 
 Severity: important 
 Tags: upstream forky sid 
 X-Debbugs-Cc: pygobject@packages.debian.org 
 Control: block 1118363 by -1 
  
 pygobject >= 3.52 (available in experimental) has switched from 
 libgirepository-1.0 to libgirepository-2.0 as its way to access GObject 
 libraries such as GTK. 
  
 libgirepository-1.0 and libgirepository-2.0 can be installed on the same 
 system, but they cannot both be used within the same process, because 
 they both register a GObject type named "GIRepository". This means that 
 pygobject, libpeas, and apps like entangle all need to agree on which 
 version they are going to use. 
  
 As a result we need to do a coordinated transition from: 
  
     pygobject 3.50.x 
     older libpeas 
     older pygobject-dependent apps 
  
 to: 
  
     pygobject >= 3.52 
     libpeas >= 1.36.0-6~ 
     newer pygobject-dependent apps 
  
 The symptom is that if you start entangle on a system that has the versions 
 of 
 pygobject and libpeas from experimental: 
  
     sudo apt install libgirepository-2.0-{0,dev} entangle 
     sudo apt install python3-gi{,-cairo}/experimental libpeas-{1.0-0, 
 dev}/experimental gir1.2-peas-1.0/experimental 
     entangle 
  
     (in the GUI) menu -> Preferences 
  
 the preferences dialog will not open, with messages like these: 
  
 >(entangle:16066): GLib-GObject-CRITICAL **: 12:52:53.847: cannot register 
 existing type 'GIRepository' 
 >(entangle:16066): GLib-CRITICAL **: 12:52:53.847: 
 g_once_init_leave_pointer: assertion 'result != 0' failed 
 >(entangle:16066): GLib-GObject-CRITICAL **: 12:52:53.847: 
 g_object_new_with_properties: assertion 'G_TYPE_IS_OBJECT (object_type)' 
 failed 
 >(entangle:16066): GLib-GObject-CRITICAL **: 12:52:53.847: 
 g_object_add_weak_pointer: assertion 'G_IS_OBJECT (object)' failed 
 >(entangle:16066): GLib-CRITICAL **: 12:52:53.847: g_once_init_leave: 
 assertion 'result != 0' failed 
 >(entangle:16066): GLib-GObject-CRITICAL **: 12:52:53.847: g_object_ref: 
 assertion 'G_IS_OBJECT (object)' failed 
  
 For GNOME apps, a similar issue is fixed in the latest experimental 
 uploads of eog, gedit, rhythmbox and totem, but now we need to do the 
 same for non-GNOME apps as well. 
  
 I expect that the necessary changes for this will be similar to those in 
 the experimental versions of eog, gedit, rhythmbox and totem, and 
 proposed for eom (#1118496) and pluma (#1118497). Initially, these 
 changes will need to be uploaded to experimental, either by a maintainer 
 or as an NMU. 
  
 After we get a transition slot from the release team, we will need to 
  
 [continued in next message] 
  
 --- SoupGate-Win32 v1.05 
  * Origin: you cannot sedate... all the things you hate (1:229/2)