Date: Thu, 07 Dec 2023 05:49:52 +0000 From: bugzilla-noreply@freebsd.org To: x11@FreeBSD.org Subject: [Bug 275445] x11/xwayland-run: wlheadless-run and xwfb-run fail to start without explicit -c cage Message-ID: <bug-275445-7141-HfpIzKp50g@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-275445-7141@https.bugs.freebsd.org/bugzilla/> References: <bug-275445-7141@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D275445 --- Comment #1 from Jan Beich <jbeich@FreeBSD.org> --- Alternatively, remove the port. It's a simple Python script, easy to run outside of ports. Without dogfooding and/or an upstream liaison there's no point. Worse, it's under GPLv2+ to hinder adoption and code sharing with ot= her projects. $ xwayland-run -- foo is equivalent to $ cage Xwayland -noreset :10 $ DISPLAY=3D:10 foo or as one-liner $ DISPLAY=3D:$(Xwayland -terminate -displayfd 1 2>/dev/null &) foo See also https://github.com/cage-kiosk/cage/issues/186 https://lists.freebsd.org/archives/freebsd-x11/2023-May/003312.html xwayland-run doesn't even try to prevent various GUI toolkits from bypassing rootful Xwayland, creating windows (directly on Cage or parent compositor) = that X11 WM within cannot control. This can be avoided by injecting "env -u WAYLAND_DISPLAY" but then why use xwayland-run if it doesn't help running a= pps within X11 WMs? --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-275445-7141-HfpIzKp50g>