Your message dated Wed, 09 Jul 2025 11:00:13 +0000 with message-id <E1uZSX7-00Bsl5-9r@fasolo.debian.org> and subject line Bug#1090384: fixed in xfce-polkit 0.3+v20220621-1 has caused the Debian Bug report #1090384, regarding xfce4: desktop environment metapackage should provide a polkit agent 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.) -- 1090384: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1090384 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: xfce4: desktop environment metapackage should provide a polkit agent
- From: Simon McVittie <smcv@debian.org>
- Date: Tue, 17 Dec 2024 20:18:35 +0000
- Message-id: <Z2Hcm16KW5iJhzOv@remnant.pseudorandom.co.uk>
Package: xfce4 Version: 4.18 Severity: important As discussed on #1076728, there is a de facto expectation that each "good" desktop environment will provide a polkit authentication agent that is suitable for it, similar to the expectation for o.fd.Notifications. I've reported this as a bug in the xfce4 metapackage, but it might make sense to push it down into a "smaller", lower-level package like xfce4-session (I am not familiar with the details of XFCE's design). There are two main ways to get a polkit agent: 1. Integrate it directly into the desktop shell, as has been done by GNOME since 3.0 and various GNOME derivatives like Phosh. XFCE has not done this, that I know of. 2. Depend on a separate polkit agent UI program that is appropriate for the desktop environment, and arrange for it to be started during graphical session login, either via /etc/xdg/autostart or by explicitly starting it. XFCE does not have its own polkit agent (https://github.com/ncopa/xfce-polkit exists, but is unmaintained and has not been packaged in Debian) so it will have to borrow someone else's. One straightforward way to implement (2.) would be to add a dependency on a specific polkit agent implementation that fits well into XFCE, or an or-group (Depends: impl1|impl2|...) for more than one implementation, where each implementation has an /etc/xdg/autostart/*.desktop whose ShowIn and/or OnlyShowIn fields allow it to be run under XFCE. If the chosen implementation is desktop-specific, it would be best to contact its maintainers, let them know that XFCE is also relyiing on that implementation, and perhaps offer to co-maintain it. Note that merely adding a direct or indirect dependency on the polkit-1-auth-agent virtual package is *not* enough to resolve this bug: that virtual package is provided by some polkit agents that are either integrated into a different desktop environment (gnome-shell, etc.), or standalone programs that have an OnlyShowIn that excludes them from being used by XFCE (polkit-kde-agent-1, etc.). Installing one of those will not provide a working polkit authentication agent under XFCE. Historically, policykit-1-gnome has been treated as the polkit agent of last resort. However, it was originally intended to be GNOME-specific, and is a GNOME-2-era implementation which is no longer maintained (see #990271), so I don't think anything involving a dependency on policykit-1-gnome would be a good solution to this issue. If the XFCE downstream or upstream maintainers feel that policykit-1-gnome is the implementation they want to be using, then someone will need to fork it under a less misleading name and become the fork's new upstream maintainer. Borrowing a polkit agent from LXDE or MATE would probably be a better solution. I suspect that new installations of XFCE are currently pulling in the unmaintained policykit-1-gnome by default, possibly via a long and unintended dependency chain. Comparing with some other major distros: - Arch seems to install (their equivalent of) policykit-1-gnome by default, despite it being dead upstream, but offers xfce-polkit as an alternative; - Fedora ships xfce-polkit Please choose a suitable polkit agent and add it as a dependency, or at least as a Recommends. Thanks, smcv
--- End Message ---
--- Begin Message ---
- To: 1090384-close@bugs.debian.org
- Subject: Bug#1090384: fixed in xfce-polkit 0.3+v20220621-1
- From: Debian FTP Masters <ftpmaster@ftp-master.debian.org>
- Date: Wed, 09 Jul 2025 11:00:13 +0000
- Message-id: <E1uZSX7-00Bsl5-9r@fasolo.debian.org>
- Reply-to: Peter Blackman <peter@pblackman.plus.com>
Source: xfce-polkit Source-Version: 0.3+v20220621-1 Done: Peter Blackman <peter@pblackman.plus.com> We believe that the bug you reported is fixed in the latest version of xfce-polkit, 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 1090384@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Peter Blackman <peter@pblackman.plus.com> (supplier of updated xfce-polkit 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 ftpmaster@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Sat, 21 Jun 2025 16:45:55 +0100 Source: xfce-polkit Binary: xfce-polkit xfce-polkit-dbgsym Architecture: source arm64 Version: 0.3+v20220621-1 Distribution: unstable Urgency: medium Maintainer: Peter Blackman <peter@pblackman.plus.com> Changed-By: Peter Blackman <peter@pblackman.plus.com> Description: xfce-polkit - Simple PolicyKit authentication agent for Xfce Closes: 1090384 1103663 Changes: xfce-polkit (0.3+v20220621-1) unstable; urgency=medium . * Initial release. (Closes: #1103663, #1090384) Checksums-Sha1: 936283dc671b32d8a523aa74db3d09419b9c2701 1959 xfce-polkit_0.3+v20220621-1.dsc e7b133b96bdd108e99f432d48efebc1dad953141 16236 xfce-polkit_0.3+v20220621.orig.tar.xz 2a3676fe9e8ba4914ebb3cb561e2b65245709884 1804 xfce-polkit_0.3+v20220621-1.debian.tar.xz 14c5b6cc0db855c5e5c62ae891cba09811aafa82 19856 xfce-polkit-dbgsym_0.3+v20220621-1_arm64.deb a46246d3e0e3c8c60e3ae41285c6724ba0e2cff0 14780 xfce-polkit_0.3+v20220621-1_arm64.buildinfo 107b42cae1e8524ac4347b109da23081baf0e4eb 7532 xfce-polkit_0.3+v20220621-1_arm64.deb Checksums-Sha256: 7f81b13c31cb3c118ad0ceb542d7798b6a3a8830dca45e0673e26303070699f0 1959 xfce-polkit_0.3+v20220621-1.dsc 5cd12a854b5dcfef21135f0d997707fa6fdf49a3c70888008914beb862990814 16236 xfce-polkit_0.3+v20220621.orig.tar.xz b735706d0ea6dffd6cb88ce20ecc227007543d0110cf5679b560e8be2522f23f 1804 xfce-polkit_0.3+v20220621-1.debian.tar.xz c8ae8cf8f280c72881446c4ac76d221b58ff51fd43429e6d084a4f900b5dc062 19856 xfce-polkit-dbgsym_0.3+v20220621-1_arm64.deb ad0a204184a038b061e84bd0dbbf95c54477799096ee25e907b0c0cd57d48001 14780 xfce-polkit_0.3+v20220621-1_arm64.buildinfo 38cf8e901d2021ea64aaf18ccda1dafab7717b89b0a808813dd6c0a74665bf17 7532 xfce-polkit_0.3+v20220621-1_arm64.deb Files: 35417a3f6e447d6412ccd98a80d99d52 1959 admin optional xfce-polkit_0.3+v20220621-1.dsc e9f40b18e067b083d2a8996673953d7a 16236 admin optional xfce-polkit_0.3+v20220621.orig.tar.xz c4fd4245e2f62f9fb086eb7105f754aa 1804 admin optional xfce-polkit_0.3+v20220621-1.debian.tar.xz a09fae4b41e8aad560cb138eff2cfaea 19856 debug optional xfce-polkit-dbgsym_0.3+v20220621-1_arm64.deb 57cbe90c080565b14e37019ba99de155 14780 admin optional xfce-polkit_0.3+v20220621-1_arm64.buildinfo 94659d1f3118ee8d8b8b5393d1b89faa 7532 admin optional xfce-polkit_0.3+v20220621-1_arm64.deb -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEfRrP+tnggGycTNOSXBPW25MFLgMFAmhXSmkACgkQXBPW25MF LgNS8w//TWOJRTXle9VCs0T14/2KYe4ZcgDGGZwKxNq5SvrxAoSj1Q+Z98GCPBd5 lWgx0t2saNzlekJht1BBISgtUh8GDjDb/HlzKGyo3iIKzqrWxWmgxxL5oeANtTjG bwfyp6MHgA6kXgxhFeNNI7r7U2mhapn9g0EJ+jnXOXAWUkakj0Mj+aw65qThrSNg IaIJAINarLwTK0BRVHq+rmas3Gakz49XKJ4bsolUyGTNOk+CBGsx5mk9uUXLkLN/ IC6UG2uasLjzdkFK2Ir7zldz2xzsS51a9OrXchzMmfGrLqOOyuUIXjcLfEq3DaP0 JEtditge9gZolpH2sIntrcH/Gw26iT86vp9vwaAoVO7RHFZSVowJExH6yefQ/kfe lsqJCoxPgUXA6Xf2d16dZZsSOqbSvaylfPNMMqdpZ/wHrhSum3dch22tfOCgeWoH hzC+Htq0eslNS04Yra8WcO6hJCAdaZPjUNAav4+3K5st//OlatDVcB2uLe0HgiwV ORIQs6kzmRgFPifKkCdhSWN99JXBS4VPhNnIBep5tQKkzzZmOK5LxpxgeWeHRS6H l10QA7YwPd0Xr92C1Ve/fbPseBV6Nh918tpoMcoASKWVxY/HiWS2CbpMkclzE166 3RK3wQLsjxmRdgH4f/PK37KWHpFnIG3Hg3fXtIs1AwGgSaJL/kk= =WdyJ -----END PGP SIGNATURE-----Attachment: pgp_Xal0kIAEN.pgp
Description: PGP signature
--- End Message ---