Bug#971675: x11-xserver-utils: xhost don't work anymore in Gnome+wayland
Package: x11-xserver-utils
Version: 7.7+8
Severity: normal
Dear Maintainer,
I used to do the following:
$ xhost +si:localuser:$USER
$ su - $USER
and then run some GUI programs.
From today I get the following error:
Unable to init server: Could not connect: Connection refused
Error: cannot open display: :0
I have try also to use
$ xhost +
I have try also the following with the same result
$ ssh -X -oForwardX11Trusted=no -l $USER 127.0.0.1
I have try using different Desktop Environment and all work correctly with:
Xfce
Gnome+X.org
I think that the problem is caused by some gnome package I have upgraded
yesterday:
Install: gir1.2-mutter-7:amd64 (3.38.0-2, automatic),
gstreamer1.0-pipewire:amd64 (0.3.12-1, automatic), libmozjs-78-0:amd64
(78.3.0-2, automatic), libmutter-7-0:amd64 (3.38.0-2, automatic)
Upgrade: libgoa-backend-1.0-1:amd64 (3.36.0-1, 3.37.90-2),
texlive-plain-generic:amd64 (2020.20200804-3, 2020.20200925-1),
gnome-control-center-data:amd64 (1:3.36.4-1, 1:3.38.0-2),
gnome-settings-daemon-commo
n:amd64 (3.36.1-1, 3.38.0-2), gnome-shell-extension-prefs:amd64
(3.36.6-1, 3.38.0-2), gnome-contacts:amd64 (3.36.2-1, 3.38-1),
gnome-session:amd64 (3.36.0-2, 3.38.0-2), texlive-latex-base:amd64
(2020.20200804
-3, 2020.20200925-1), gnome-session-common:amd64 (3.36.0-2, 3.38.0-2),
gvfs-backends:amd64 (1.44.1-1+b1, 1.46.0-2), gnome-control-center:amd64
(1:3.36.4-1, 1:3.38.0-2), libproxy1v5:amd64 (0.4.15-13, 0.4.15-14
), libgoa-1.0-0b:amd64 (3.36.0-1, 3.37.90-2), libgoa-1.0-common:amd64
(3.36.0-1, 3.37.90-2), libgjs0g:amd64 (1.64.3-1, 1.66.0-1),
libproxy1-plugin-gsettings:amd64 (0.4.15-13, 0.4.15-14),
texlive-fonts-recommended-doc:amd64 (2020.20200804-3, 2020.20200925-1),
texlive-base:amd64 (2020.20200804-3, 2020.20200925-1), gjs:amd64
(1.64.3-1, 1.66.0-1), gnome-settings-daemon:amd64 (3.36.1-1, 3.38.0-2),
texlive-latex-extra-doc:amd64 (2020.20200804-3, 2020.20200925-1),
texlive-pictures:amd64 (2020.20200804-3, 2020.20200925-1),
libmusicbrainz5cc2v5:amd64 (5.1.0+git20150707-9, 5.1.0+git20150707-10),
gdm3:amd64 (3.36.3-1, 3.38.0-2), texlive-fonts-recommended:amd64
(2020.20200804-3, 2020.20200925-1), debianutils:amd64 (4.9.1, 4.11.2),
gir1.2-gdm-1.0:amd64 (3.36.3-1, 3.38.0-2), mutter-common:amd64
(3.36.6-1, 3.38.0-2), texlive-latex-extra:amd64 (2020.20200804-3,
2020.20200925-1), libgdm1:amd64 (3.36.3-1, 3.38.0-2), gvfs-libs:amd64
(1.44.1-1+b1, 1.46.0-2), gvfs-fuse:amd64 (1.44.1-1+b1, 1.46.0-2),
libproxy-tools:amd64 (0.4.15-13, 0.4.15-14),
libproxy1-plugin-webkit:amd64 (0.4.15-13, 0.4.15-14),
gnome-shell-common:amd64 (3.36.6-1, 3.38.0-2), libjs-jquery-ui:amd64
(1.12.1+dfsg-5, 1.12.1+dfsg-7), gir1.2-goa-1.0:amd64 (3.36.0-1,
3.37.90-2), libproxy1-plugin-networkmanager:amd64 (0.4.15-13,
0.4.15-14), gnome-online-accounts:amd64 (3.36.0-1, 3.37.90-2),
gnome-shell-extensions:amd64 (3.36.2-1, 3.38.0-2),
gnome-session-bin:amd64 (3.36.0-2+b1, 3.38.0-2), gvfs:amd64
(1.44.1-1+b1, 1.46.0-2), libmusicbrainz5-2:amd64 (5.1.0+git20150707-9,
5.1.0+git20150707-10), gvfs-common:amd64 (1.44.1-1, 1.46.0-2),
daisy-player:amd64 (12.0-1, 12.1-1), gnome-shell:amd64 (3.36.6-1,
3.38.0-2), four-in-a-row:amd64 (1:3.36.2-1, 1:3.38.0-1),
texlive-latex-recommended-doc:amd64 (2020.20200804-3, 2020.20200925-1),
texlive-pictures-doc:amd64 (2020.20200804-3, 2020.20200925-1),
texlive-latex-recommended:amd64 (2020.20200804-3, 2020.20200925-1),
gvfs-daemons:amd64 (1.44.1-1+b1, 1.46.0-2), r-cran-survival:amd64
(3.2-3-1, 3.2-7-1), texlive-latex-base-doc:amd64 (2020.20200804-3,
2020.20200925-1), mutter:amd64 (3.36.6-1, 3.38.0-2)
In the Debian wiki[¹] say that all must work correctly with wayland:
I run various programs over the network, e.g. through ssh X11
forwarding, or xhost. How will this work under Wayland?
SSH X11 forwarding works like before for X11 applications via XWayland.
Native Wayland applications are not forwarded.
Ciao
Davide
[¹]
https://wiki.debian.org/Wayland#I_run_various_programs_over_the_network.2C_e.g._through_ssh_X11_forwarding.2C_or_xhost.__How_will_this_work_under_Wayland.3F
-- System Information:
Debian Release: bullseye/sid
APT prefers testing-debug
APT policy: (500, 'testing-debug'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.8.10-dp-20200925 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (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 x11-xserver-utils depends on:
ii cpp 4:10.2.0-1
ii libc6 2.31-3
ii libice6 2:1.0.10-1
ii libx11-6 2:1.6.12-1
ii libxaw7 2:1.0.13-1+b2
ii libxcursor1 1:1.2.0-2
ii libxext6 2:1.3.3-1+b2
ii libxi6 2:1.7.10-1
ii libxmu6 2:1.1.2-2+b3
ii libxmuu1 2:1.1.2-2+b3
ii libxrandr2 2:1.5.1-1
ii libxrender1 1:0.9.10-1
ii libxt6 1:1.2.0-1
ii libxxf86vm1 1:1.1.4-1+b2
x11-xserver-utils recommends no packages.
Versions of packages x11-xserver-utils suggests:
pn cairo-5c <none>
pn nickle <none>
ii xorg-docs-core 1:1.7.1-1.1
-- debconf-show failed
Reply to: