Your message dated Thu, 24 Apr 2025 12:38:20 +0000
with message-id <[email protected]>
and subject line Bug#1092859: fixed in thunarx-python 0.5.2-3
has caused the Debian Bug report #1092859,
regarding thunarx-python: Fails to allow plugins to run
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 [email protected]
immediately.)


-- 
1092859: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1092859
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: thunarx-python
Version: 0.5.2-2+b5
Severity: important
X-Debbugs-Cc: [email protected]

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***
Installing a plugin depending on thunarx-python, i.e., rabbitvcs-thunar, causes
thunar execution to fail, see bug #958088. The cause of the failure of this
plugin is rightly attributed to thunarx-plugin somehow not compiling correctly
for Python3.

First off: There's no corresponding bug filed for thunarx-python and bug
#958088 has not been moved to this package. Therefore this bug is filed, so
that the cause of #958088 is highlighted.

Second: By building the code myself (on trixie, using debuild -i -us -uc -b)
the resulting shared object (thunarx-python.so), dropped in place of the
offending binary, works without issue.

Therefore my conclusion is that the upstream code _is_ capable to be compiled
with Python 3, so it presumably is an issue with the build environment.

This is made evident by the following experiment:
1) With the so installed from the Debian package
host# strings thunarx-python.so | grep lib
libthunarx-3.so.0
libgtk-3.so.0
libpython3.13.so.1.0
libgobject-2.0.so.0
libglib-2.0.so.0
libc.so.6
thunarx-python: Setting GI_TYPELIB_PATH to /usr/lib/x86_64-linux-
gnu/girepository-1.0
/usr/lib/x86_64-linux-gnu/girepository-1.0
thunarx-python: g_module_open /usr/lib/x86_64-linux-gnu/lib.so.1.0
/usr/lib/x86_64-linux-gnu/lib.so.1.0
g_module_open libpython failed: %s

1) With the so from the self build Debian package
host# strings thunarx-python.so | grep lib
libthunarx-3.so.0
libgtk-3.so.0
libpython3.12.so.1.0
libgobject-2.0.so.0
libglib-2.0.so.0
libc.so.6
thunarx-python: Setting GI_TYPELIB_PATH to /usr/lib/x86_64-linux-
gnu/girepository-1.0
/usr/lib/x86_64-linux-gnu/girepository-1.0
thunarx-python: g_module_open /usr/lib/x86_64-linux-gnu/libpython3.12.so.1.0
/usr/lib/x86_64-linux-gnu/libpython3.12.so.1.0
g_module_open libpython failed: %s

The difference from '/usr/lib/x86_64-linux-gnu/lib.so.1.0' to
'/usr/lib/x86_64-linux-gnu/libpython3.12.so.1.0' is telling.


-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'testing-debug'), (500, 
'stable-updates'), (500, 'stable-security'), (500, 'oldstable-updates'), (500, 
'oldstable-security'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.12.6-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages thunarx-python depends on:
ii  libc6            2.40-4
ii  libglib2.0-0t64  2.82.4-1
ii  libgtk-3-0t64    3.24.43-4
ii  libpython3.13    3.13.1-2
ii  libthunarx-3-0   4.20.0-1
ii  thunar           4.20.0-1

thunarx-python recommends no packages.

thunarx-python suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
Source: thunarx-python
Source-Version: 0.5.2-3
Done: Colin Watson <[email protected]>

We believe that the bug you reported is fixed in the latest version of
thunarx-python, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Colin Watson <[email protected]> (supplier of updated thunarx-python package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Thu, 24 Apr 2025 13:18:12 +0100
Source: thunarx-python
Architecture: source
Version: 0.5.2-3
Distribution: unstable
Urgency: medium
Maintainer: Ritesh Raj Sarraf <[email protected]>
Changed-By: Colin Watson <[email protected]>
Closes: 1092859 1103704
Changes:
 thunarx-python (0.5.2-3) unstable; urgency=medium
 .
   * Team upload.
   * Build-depend on python3-setuptools (closes: #1092859, #1103704).
   * Build-depend on pkgconf rather than pkg-config.
Checksums-Sha1:
 2af3d95f37c51a7a9f1f7122a61e20cc591f1050 2235 thunarx-python_0.5.2-3.dsc
 42c125a5ef6d362536b3c125fc97043e04c5e141 2088 
thunarx-python_0.5.2-3.debian.tar.xz
Checksums-Sha256:
 f1f46e2e0d9ce5ee209ee3f1c8b2babe59ed2f0c75c3b5a61e93eb7f66059677 2235 
thunarx-python_0.5.2-3.dsc
 26688dc8d749534c6045d575ad2cbea5d65d9406ad894c28e607d62d4e000a23 2088 
thunarx-python_0.5.2-3.debian.tar.xz
Files:
 550fa5337e98af9d67edd4426165019f 2235 xfce optional thunarx-python_0.5.2-3.dsc
 ee8497a6815ae8c62c63c5aac80c8cc7 2088 xfce optional 
thunarx-python_0.5.2-3.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEErApP8SYRtvzPAcEROTWH2X2GUAsFAmgKLFkACgkQOTWH2X2G
UAsCGg/7BDqky7Kgd9ZMd0IAxZJWlyEmdxvy1Pfp6IUd8DB0JEJMm20k8XjWCn9l
n9GG1NJsE5Kv3etI2+mGO4m72plouKJx2xic0HDM3Jgaa044fH9qTDtrQdRp3k97
SScxGUzIC77PgRDh0qCNykhm/9KWqscUOQjzUogX9eccNss8Sz9xiSYegol6tlJ5
zmRRC7kWHgfQKB+FVVZ/Ox2mGmxsCaz47q4ZzA1os24/nA9MQJc/5i3mcHVB7i99
dLUQ4kMRVNqMq3b2VCrKrD6LtNc9EJIFRKv46jfpd0shATMi0nJEbBwFaHjB/ofX
FWIVqayeva4QLEDSE3RByvGg5fqvPftW4Gs1b1ywnX8Y9uNFPYUxvCtx4aHaPlNy
vLImFT11oUmbyKfCCxGIrdATU7wEfSBggiODdPnKWjlZqmBEvROt5X2PJBLVLtzq
Gt4f5oDpCTKzLfGx8EOZo3s7fB53dYAs7rOLxKxX8yzZAT/EZYbnyeO5/Pv1F2S4
BmwJuFO3gScqH4+/MfHUnLgBDTSC673bucWXRHSH71XI0FjlAAPd7apYH0rqhiul
MvvektFT9XLU/qFnnasyurhHhK7onNtE6LDDTCeZu9GPkBU+TyY3u1pMqgfd9+3z
1Pit1KsKYqS7VJt1L2KV77WkJ4p7BdYXU19Km5uIqGQ8epjV3PQ=
=gWJY
-----END PGP SIGNATURE-----

Attachment: pgpm_kuNI0sPg.pgp
Description: PGP signature


--- End Message ---

Reply via email to