Bug#1084133: mutter: FTBFS on armhf: Directory "/tmp/.X11-unix" is not writable
Simon McVittie
smcv at debian.org
Mon Oct 7 09:58:24 BST 2024
Control: tags -1 + pending
On Sun, 06 Oct 2024 at 22:54:54 +0100, Simon McVittie wrote:
> I think what is happening in mutter could perhaps be this:
>
> mutter requires /tmp/.X11-unix (for Xwayland) for some of its unit tests.
>
> On architectures where xvfb-run works as intended, it creates
> /tmp/.X11-unix as a side-effect, and then by the time mutter needs it,
> it already exists and all is well.
>
> But, on armhf with the current libunwind8 from unstable, Xvfb is crashing,
> so it doesn't get far enough to create /tmp/.X11-unix; but for whatever
> reason, the xvfb-run script doesn't detect that and continues to run
> dh_auto_test anyway, and we end up running the mutter unit tests without
> them being wrapped in Xvfb, hence /tmp/.X11-unix never got created.
I've uploaded a version of mutter that I hope fixes the FTBFS (47.0-3)
but it seems to have got stuck or lost somewhere between the upload queue
on usper and the actual archive. I've asked #debian-ftp to take a look.
smcv
More information about the pkg-gnome-maintainers
mailing list