Your message dated Sun, 02 Feb 2025 16:49:18 +0000
with message-id <[email protected]>
and subject line Bug#1085336: fixed in picom 12.5-1
has caused the Debian Bug report #1085336,
regarding picom: calls dbus_get_local_machine_id() which has bad error-handling
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.)
--
1085336: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1085336
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: picom
Version: 11.2-0.1
Severity: normal
Tags: upstream
picom calls dbus_get_local_machine_id(), which has no good mechanism
for reporting an error, and therefore will spam warnings to standard error
(and possibly crash) if the D-Bus machine ID has not been set up correctly.
This function should be considered deprecated.
If it is necessary to call this function, please prefer to use
dbus_try_get_local_machine_id(), which takes a DBusError parameter and
therefore can be used to report errors in whatever way is considered to
be most appropriate by the caller. This has been available in upstream
stable releases since dbus 1.12.0 (2017).
It looks as though picom only calls dbus_get_local_machine_id()
because it's implementing the o.fd.DBus.Peer interface. I suspect
that this might not be necessary at all, because libdbus will usually
implement the o.fd.DBus.Peer interface for you anyway, without needing
application-specific code to be written for it. So maybe the code that
implements o.fd.DBus.Peer.GetMachineId and ….Peer.Ping can just be deleted?
Thanks,
smcv
--- End Message ---
--- Begin Message ---
Source: picom
Source-Version: 12.5-1
Done: Mohammed Bilal <[email protected]>
We believe that the bug you reported is fixed in the latest version of
picom, 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.
Mohammed Bilal <[email protected]> (supplier of updated picom 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: Sun, 26 Jan 2025 17:14:42 +0000
Source: picom
Architecture: source
Version: 12.5-1
Distribution: unstable
Urgency: medium
Maintainer: Nikos Tsipinakis <[email protected]>
Changed-By: Mohammed Bilal <[email protected]>
Closes: 1085336
Changes:
picom (12.5-1) unstable; urgency=medium
.
[ Mohammed Bilal ]
* d/rules: add explicit link against atomic on some 32 bit archs
* New upstream version 12.5 (Closes: #1085336)
* d/control:
- Add myself as uploader.
- replace pkg-config with pkgconf
- replace asciidoc with asciidoctor
- remove libxext-dev,libxcb-dpms0-dev (no longer needed)
- update min version of libconfig-dev
- Bump Standards-Version to 4.7.0 (no changes needed)
* d/salsa-ci.yml: enable salsa-ci
Checksums-Sha1:
a611a615b5357029b70001a71ff1ea16aa87323b 2313 picom_12.5-1.dsc
b184ad68ca12c288ebefa8ace567e23d04901190 674165 picom_12.5.orig.tar.gz
e050f85c4c0c47176b9ef564dbc7407a8eb6c263 3856 picom_12.5-1.debian.tar.xz
59972a9f6171c0a939efe9c4ec245884821ad543 10498 picom_12.5-1_amd64.buildinfo
Checksums-Sha256:
081094bdaeb617856a77cd810e0bb9d83b37e394c78d8801d84f622b8c943809 2313
picom_12.5-1.dsc
627fa5d7c590df3ba8d2c41eb35d3859f7826bd28fa49e92a0e04fb60ed77904 674165
picom_12.5.orig.tar.gz
14f21e001acc255f84ae1786bb9ede851c53fe0346425101a46feb67b835a285 3856
picom_12.5-1.debian.tar.xz
e88112865a064f22dddbd7a9ed2af169f5f0f4f53ba693048080f634733c88ed 10498
picom_12.5-1_amd64.buildinfo
Files:
6f5fb1a8f75ff79b129ac31726c052cb 2313 x11 optional picom_12.5-1.dsc
0e1d2bd5a57853bfa03b24ce6a0b870f 674165 x11 optional picom_12.5.orig.tar.gz
097c5bd9730c5564feac1f525af43cf7 3856 x11 optional picom_12.5-1.debian.tar.xz
817aca2268755fcd088bec4bdc31a077 10498 x11 optional
picom_12.5-1_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJDBAEBCgAtFiEErsQCieDzzvOjoQVQoerXSQ1o084FAmefn0wPHHJtYkBkZWJp
YW4ub3JnAAoJEKHq10kNaNPOIKYQAJusjxiAWRgr2kIa+Ssetwp1ZqKvfNXAqjB6
D2400qJWc6O3aRi2GU8ll/MV/629+A1vEslVNCMGrwnP8Yd6iK3whOqtJ/LcVcMU
gyQcR6MHrWPEJjaL3Ne9Ai+AwwqRBu13s1HQXc72YpMVjUKarne6s7/LVjoreAcM
p2DkZ6xLwdo3gB60qsfzajXXFV2O4LjNCVuSwxYQ7gdYvKY+65b8CGpTEsJUIWch
X+uczZOaecz6PV5k1vTW4lyz73wFh12PXsvFOLXsKd9qEQFWOI67/ijqgM0JpJfn
xd1TqvJGPHstV8IisWaRegEoZDSB7zAUc9fk+ID2L3PpjRlND9ADg78hX6W6j0qa
dgBkzay+B/SK1JW5esBEqMynZqB4oreX/z+NkYrPq6QD8bl9/ZXAxgxZmzCeRNo7
QP7/h6adtT484toDesC/ApeOr3lNtwKh2sGg/zOdv/sMbVmPAO1Um24yTOGb2Hxb
r8ldBtDEaQ65QBTdX0brfmztVnr29Ce0jpTPGvWoZ0UgGWHCNtrfgPwTX2MmDDKN
OqogLJngVPuxniogJU1SwNKNIeRslo3uLgXOTuf/GmDhp92VqtuTWoVYu7LYO5Hp
cdA/2h+OOLarRfBPvS/ePt2gcQbGjIQVkNYCi1Iw63EnxntQCyQAjUduUXZJL8Tm
I/vprTJD
=da5c
-----END PGP SIGNATURE-----
pgpnaKTVohjZm.pgp
Description: PGP signature
--- End Message ---
