Your message dated Thu, 14 May 2026 17:33:51 +0000
with message-id <[email protected]>
and subject line Bug#1050980: fixed in awesome 4.3-9
has caused the Debian Bug report #1050980,
regarding awesome: please set XDG_CURRENT_DESKTOP and use it to configure
xdg-desktop-portal
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.)
--
1050980: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050980
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: awesome
Version: 4.3-7
Severity: normal
User: [email protected]
Usertags: portals.conf
xdg-desktop-portal 1.17.x introduces a new way to select which portals will
be used for which desktop environments, modelled on mimeapps.list:
- each desktop environment should provide a file like
/usr/share/xdg-desktop-portal/awesome-portals.conf
- the filename is ${DESKTOP}-portals.conf where ${DESKTOP} is the desktop
environment's entry in $XDG_CURRENT_DESKTOP (the same as the DesktopNames
from /usr/share/{x,wayland-}sessions/*.desktop), folded to lower case
- sysadmins and users can override this via files named portals.conf or
${DESKTOP}-portals.conf in various locations like /etc/xdg-desktop-portal
and ~/.config/xdg-desktop-portal
But as far as I can tell, awesome doesn't set XDG_CURRENT_DESKTOP, so for
the purposes of this mechanism, it's not programmatically distinguishable
from any other desktop environment or window manager.
XDG_CURRENT_DESKTOP is also used in pre-existing freedesktop.org standards
like the OnlyShowIn/NotShowIn fields for .desktop files, and the ability to
provide a desktop-environment-specific mimeapps.list. Setting
XDG_CURRENT_DESKTOP would allow awesome to participate in those
specifications.
To reproduce
============
* Start from a basic non-GUI virtual machine (I used autopkgtest-build-qemu)
* Ensure that a user account exists
* apt install lightdm xorg awesome
* reboot
* Log in as the user account, selecting "awesome" from the menu of
possible X11 sessions
* Open a terminal and run:
env | grep XDG_CURRENT_DESKTOP
systemctl --user show-environment
(It's the systemd activation environment that matters here, more than
`env`, because xdg-desktop-portal will typically be run as a systemd
user service.)
Expected result
===============
XDG_CURRENT_DESKTOP should be set to a colon-separated sequence of
desktop environment names, most specific first. awesome seems to be its
own thing rather than being based on another desktop environment or
window manager, so
XDG_CURRENT_DESKTOP=awesome
would seem appropriate.
This would allow the awesome session to have its own
desktop-environment-specific mimeapps.list or portals.conf(5), for
example /usr/share/xdg-desktop-portal/awesome-portals.conf.
Actual result
=============
XDG_CURRENT_DESKTOP is unset.
This means that xdg-desktop-portal configuration can only be done via a
non-desktop-specific portals.conf, but that's not really something that a
non-opinionated distribution like Debian can usefully ship in a centralized
way, so each user of awesome who wants a working xdg-desktop-portal will
have to configure it themselves.
At the moment, this is mitigated by xdg-desktop-portal (>= 1.17) having
been patched to fall back to xdg-desktop-portal-gtk as a last-resort
desktop-environment-specific backend, but hard-coding that implementation
isn't really something we should be doing centrally (and the idea was
rejected upstream), so I intend to remove that patch before trixie
is released.
Suggested fix
=============
Add a sequence of semicolon-separated desktop environment names to
/usr/share/xsessions/awesome.desktop, most likely just "awesome":
DesktopNames=awesome;
(For example, icewm and windowmaker use "ICEWM" and "WindowMaker" in
their equivalent xsessions file.)
And then create a /usr/share/xdg-desktop-portal/awesome-portals.conf
with whatever portal backends are desired for an awesome session,
for example perhaps this:
[preferred]
default=gtk;
Please see portals.conf(5) or its source code
https://github.com/flatpak/xdg-desktop-portal/blob/main/doc/portals-conf.rst
for full details.
Thanks,
smcv
--
This is part of a mass bug filing:
https://lists.debian.org/debian-devel/2023/08/msg00311.html
--- End Message ---
--- Begin Message ---
Source: awesome
Source-Version: 4.3-9
Done: Reiner Herrmann <[email protected]>
We believe that the bug you reported is fixed in the latest version of
awesome, 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.
Reiner Herrmann <[email protected]> (supplier of updated awesome 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, 14 May 2026 19:07:13 +0200
Source: awesome
Architecture: source
Version: 4.3-9
Distribution: unstable
Urgency: medium
Maintainer: Reiner Herrmann <[email protected]>
Changed-By: Reiner Herrmann <[email protected]>
Closes: 1050980 1131184
Changes:
awesome (4.3-9) unstable; urgency=medium
.
* Import upstream fix for crash when gtk3 and gtk4 are installed.
(Closes: #1131184)
* Update Standards-Version to 4.7.4.
- drop Priority: optional, which is now default
* Drop Rules-Requires-Root: no, as it is the default.
* Set DesktopNames in session file to let login managers set
XDG_CURRENT_DESKTOP.
* Install xdg-desktop-portal configuration. (Closes: #1050980)
* Modify watch file to use release tarball and signature.
Checksums-Sha1:
860521f45742bb81fce76b1bd3b5e30a9a1b6874 2802 awesome_4.3-9.dsc
7b0556b09b9d16ff8a4147ab5240ca9a4ca47b2f 26028 awesome_4.3-9.debian.tar.xz
39ae5c6a10259a5cbb08f826280fca3284fd9d28 14535 awesome_4.3-9_amd64.buildinfo
Checksums-Sha256:
1c11cd14e6f52747c26b1a9cd65f8327c24d3da7c6be9c7da58913ecfa927825 2802
awesome_4.3-9.dsc
6af62a22318633ab9a6e99f78c0f3ed2c2dd8a6e60105953767a85faeefe8850 26028
awesome_4.3-9.debian.tar.xz
13abbd4c0346b0bb6377078aa18fe866688093a48bcacbc2a53ba7fadc4abb7d 14535
awesome_4.3-9_amd64.buildinfo
Files:
10389be49c6cce63ea88211e7b021d92 2802 x11 optional awesome_4.3-9.dsc
d632e5817dbaaeb586dd80f522f86117 26028 x11 optional awesome_4.3-9.debian.tar.xz
49f9d237ec5043148e2abf3b1777999f 14535 x11 optional
awesome_4.3-9_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEE2Pb6feok2Q1urHM7zPBJKNsO6qcFAmoGAeoACgkQzPBJKNsO
6qdpPhAAikSXft+y2s8Gt7sGjEcHu+c5SHqraH3i+aY2fVyckCqveSBd8FGvF297
OjkRWNUxSxR4oD/fdH9bhwSwSzGVZ/o85NinBLiZsgQKr8QFIPLrp8hNPXiYIljG
2SX1S6evV4E7zOoUaHcUMcLLWX93qAld9Ib6mNctV1aw/6YJhDrdASm2AFssuygy
+mc1lXPSTQC5DPRj5LF4oNhsCEu+rN1SZt5VYgdvfF/NXORlTLIKyWyJ1saJSow7
BeBCbM1CKWpSnwRbWqk/rfLijsMgn1fTSMe0nrU6b1HGsJ7LflJV5tuzI522AIIh
jmRV1D6B97prHzfZ/fnhe24jBG24ShwNGyPEKHLrjTApEmg/79udmnUnjEsjP7z9
xokfgH4MjJAeW5+CZ3qx9IkOfWTPoSRCYHo1X/OTk/FyKJMBnRoeZj5GQBEjo7m2
TfngI49vDL1HU8X//Z8HFY4TUrS18e5AZ1SDqvKGkRLZDqByTRqG6fLI5txNVgsG
zuBJbb+6CcWZ7OoJy42G2mOcTwTrmQnMkJlpPnUaS9XGfghR2c/gevDB5uB3gtli
eqw2xB8Q3wVIT4n0+LtMOJ3DX8B7lggrZWRCU8feV1wxiMz7iwknJCHtl1UF6Yx4
STlmh7laA7nkn+ipkeUfhmo8OgPunZVqI6n+ipUhDh9xa1BTXvs=
=+c4p
-----END PGP SIGNATURE-----
pgp4GSnYcdnBa.pgp
Description: PGP signature
--- End Message ---
