Bug#1006329: xwayland does not update dbus activation environment (DISPLAY, XAUTHORITY) on startup

[Jameson Graef Rollins]

Package: xwayland
Version: 2:22.1.0-1
Severity: important

For a couple of months now, when I launch sway, many dbus queries
timeout with a log like:

Feb 23 08:43:58 servo org.freedesktop.Notifications[4739]: failed to create display

Issuing the following command seems to fix the issue:

dbus-update-activation-environment --systemd DISPLAY XAUTHORITY

Clearly something should be handling this automatically but is not.
My best guess to what should be handling it is Xwayland, which I think
should be updating dbus with these variables when it launches.

Thanks!

jamie.


-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (600, 'testing'), (500, 'unstable-debug'), (200, 'unstable'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages xwayland depends on:
ii libc6 2.33-6
ii libdrm2 2.4.110-1
ii libepoxy0 1.5.9-2
ii libgbm1 21.2.6-1
ii libgcrypt20 1.9.4-5
ii libgl1 1.4.0-1
ii libpixman-1-0 0.40.0-1
ii libtirpc3 1.3.2-2
ii libwayland-client0 1.20.0-1
ii libxau6 1:1.0.9-1
ii libxcvt0 0.1.1-3
ii libxdmcp6 1:1.1.2-3
ii libxfont2 1:2.0.5-1
ii libxshmfence1 1.3-1
ii xserver-common 2:1.20.14-1

xwayland recommends no packages.

xwayland suggests no packages.

-- no debconf information

[Jameson Graef Rollins]

I might be mischaracterizing this as an Xwayland issue. Maybe it's a
sway issue? The problem starts before Xwayland is in the picture,
before any X apps are launched. waybar takes a long time to launch,
gpg-agent, pavucontrol, other things. They all have these dbus
timeouts, that all seem to be fixed when I run the following command:

dbus-update-activation-environment DISPLAY XAUTHORITY

So maybe it's just the DISPLAY variable that's actually relevant?
Somehow that variable is defined by sway before Xwayland is ever
launched, but it's not communicated to my dbus session, since it's
started by systemd --user before I launch sway.

jamie.

[Michel Dänzer]

On 2022-02-23 20:52, Jameson Graef Rollins wrote:
> I might be mischaracterizing this as an Xwayland issue. Maybe it's a
> sway issue?

It's definitely not an Xwayland issue; Xwayland (like any other X server) itself doesn't set these environment variables or launch any X11 client processes.


--
Earthling Michel Dänzer | https://redhat.com
Libre software enthusiast | Mesa and Xwayland developer