From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from atuin.qyliss.net (localhost [IPv6:::1]) by atuin.qyliss.net (Postfix) with ESMTP id 4297C1164E for ; Sun, 20 Jul 2025 08:33:42 +0000 (UTC) Received: by atuin.qyliss.net (Postfix, from userid 993) id C30B511698; Sun, 20 Jul 2025 08:33:39 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 4.0.1 (2024-03-26) on atuin.qyliss.net X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,DMARC_MISSING,RCVD_IN_DNSWL_LOW,SPF_HELO_PASS autolearn=unavailable autolearn_force=no version=4.0.1 Received: from fhigh-b8-smtp.messagingengine.com (fhigh-b8-smtp.messagingengine.com [202.12.124.159]) by atuin.qyliss.net (Postfix) with ESMTPS id CAB3811695 for ; Sun, 20 Jul 2025 08:33:38 +0000 (UTC) Received: from phl-compute-12.internal (phl-compute-12.phl.internal [10.202.2.52]) by mailfhigh.stl.internal (Postfix) with ESMTP id A7E687A015B; Sun, 20 Jul 2025 04:33:37 -0400 (EDT) Received: from phl-mailfrontend-01 ([10.202.2.162]) by phl-compute-12.internal (MEProxy); Sun, 20 Jul 2025 04:33:37 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alyssa.is; h=cc :content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:subject :subject:to:to; s=fm1; t=1753000417; x=1753086817; bh=tQumcmsbVu 3T5ok/IVSwUhWTpT7g97LMjYpfP/FH5/s=; b=ArRgxPcGfcmgwo9hI/85dqLJFz HLjUuEg8lteDMpYepof2N1vTQVomAyMsGSTu9v7q35NkWRz3es3xCBDvBbxcfTo1 XFgZqJRNNsqY+tmvhA31t0Ds0J353jTdmzS245EEuHkxMkxzoyjsrdywZwoVShP/ vacR4IKHeXo5CUcbVOZlf6n+GuYmkTSvTzwYOQoJ1E1gIgWvyuQL2lIvptv8Cl/p B+PsSZtYltpq0Id3YgJ7v8OfSMjqXOkjX4SuWfKPKh8VqI9tJyoPIklK8+8e725x fP35nxBJ5Vrjq1haTwKv8cMfigJTvr6LE7XyRpgsYYtGf7kcFgdI1QSV39vw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:subject:subject:to :to:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t= 1753000417; x=1753086817; bh=tQumcmsbVu3T5ok/IVSwUhWTpT7g97LMjYp fP/FH5/s=; b=B9Ibt22DwYJIo/eOaAAUSMiFFYRfRRL4Pj4bjkNKrZrxnqCaXvu HotaMQevMtqrwnC791e4vUHZFzH3Gc0bFfeTGc510ljdEELoRRRISxisrauSxE47 ZpfWhyueYfZMSIGZSjWNqO/TsS/TE0po39RlQDXmTIarlkT82FHpVR/KmPoLqTPS KKBzhlIB1+dVPxPxnN4nHJT2R3FPhAcovXjFlGgnwGVij9Tl2gV5n75sOb7tuMqP cjbKjM3KO6w6GyaQhNoiL07xJ897p2yDOkHvG3knH3jbzmp7Iy87SOJSC0TE6ajo CpgZjvo6XouXRldRS6D+eE1WabKvvZyubjQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeeffedrtdefgdeikeejfecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpuffrtefokffrpgfnqfghnecuuegr ihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjug hrpefhvffujghffffkgggtsehgtderredttdejnecuhfhrohhmpeetlhihshhsrgcutfho shhsuceohhhisegrlhihshhsrgdrihhsqeenucggtffrrghtthgvrhhnpefgtefgkeehff ejtedtueehgeefkeffledvieehheffjeeugffhveetleektdekgfenucffohhmrghinhep ghhithhhuhgsrdgtohhmpdhqvghmuhdrohhrghenucevlhhushhtvghrufhiiigvpedtne curfgrrhgrmhepmhgrihhlfhhrohhmpehhihesrghlhihsshgrrdhishdpnhgspghrtghp thhtohepvddpmhhouggvpehsmhhtphhouhhtpdhrtghpthhtohepuggvmhhiohgsvghnoh hurhesghhmrghilhdrtghomhdprhgtphhtthhopeguvghvvghlsehsphgvtghtrhhumhdq ohhsrdhorhhg X-ME-Proxy: Feedback-ID: i12284293:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sun, 20 Jul 2025 04:33:36 -0400 (EDT) Received: by sf.qyliss.net (Postfix, from userid 1000) id 810CF2C62D024; Sun, 20 Jul 2025 10:33:35 +0200 (CEST) From: Alyssa Ross To: Demi Marie Obenour , Spectrum OS Development Subject: Re: "make run-qemu" gets Wayland protocol error In-Reply-To: References: <013e1c97-7fd7-4a3d-9d13-d1d93965f9be@gmail.com> <87frerjnxt.fsf@alyssa.is> <87cy9vjmtg.fsf@alyssa.is> <87a54zjms4.fsf@alyssa.is> Date: Sun, 20 Jul 2025 10:33:33 +0200 Message-ID: <877c03jm76.fsf@alyssa.is> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" Message-ID-Hash: BJ2O36FPAXQC2MYLULK6TPVCXGG22WE6 X-Message-ID-Hash: BJ2O36FPAXQC2MYLULK6TPVCXGG22WE6 X-MailFrom: hi@alyssa.is X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-devel.spectrum-os.org-0; header-match-devel.spectrum-os.org-1; header-match-devel.spectrum-os.org-2; header-match-devel.spectrum-os.org-3; header-match-devel.spectrum-os.org-4; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.9 Precedence: list List-Id: Patches and low-level development discussion Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Demi Marie Obenour writes: > On 7/20/25 04:20, Alyssa Ross wrote: >> Alyssa Ross writes: >>=20 >>> Demi Marie Obenour writes: >>> >>>> On 7/20/25 03:55, Alyssa Ross wrote: >>>>> Demi Marie Obenour writes: >>>>> >>>>>> If I run `make run-qemu` under a Wayland compositor (tested with both >>>>>> Sway and Weston), I get a Wayland protocol error ("invalid object 0") >>>>>> and QEMU exits. It appears that there is a problem with >>>>>> wayland-proxy-virtwl. I get the following error from foot: >>>>>> >>>>>> warn: main.c:437: 'C' is not a UTF-8 locale, falling back to 'C.UTF-= 8' >>>>>> warn: config.c:3520: no configuration found, using defaults >>>>>> Fontconfig warning: no elements found. Check configuratio= n. >>>>>> Fontconfig warning: adding /var/cache/fontconfig >>>>>> Fontconfig warning: adding fontconfig >>>>>> err: wayland.c:1714: no compositor >>>>>> err: wayland.c:2248: failed to flush wayland socket: Connection res= et by peer >>>>>> >>>>>> And the following from wayland-proxy-virtwl: >>>>>> >>>>>> 2025-07-20 02:14:48.638 wl-proxy [WARNING]: Error handling client= : Invalid_argument("invalid bounds in Cstruct.LE.get_uint32 [0,0](4096) off= =3D0 len=3D4") >>>>> >>>>> This is partially fixed with , >>>>> which is more recent than Spectrum's pinned Nixpkgs. I expect to >>>>> update that in the next few days, but until then, you can apply it on >>>>> top of the Nixpkgs revision in lib/nixpkgs.default.nix, and then pass >>>>> --arg config '{pkgsFun =3D import /path/to/nixpkgs;}' to any Spectrum >>>>> Nix command. >>>>> >>>>> With that change, I'm able to run foot fine in QEMU. gnome-text-edit= or >>>>> runs but prints errors and looks weird, and Firefox doesn't even star= t. >>>>> crosvm built from the same tag as rutabaga_gfx used by QEMU works fin= e, >>>>> so I think it must be a QEMU bug. I spent some time yesterday trying= to >>>>> debug it, but didn't get anywhere so far. If I can't figure it out s= oon >>>>> I'll open an upstream bug report. >>>> >>>> That's a good idea. Would it be possible to use vhost-user as a >>>> workaround? That would use crosvm's implementation instead. >>> >>> No. crosvm and QEMU have different ideas of what vhost-user-gpu. >>> QEMU expects to provide all the graphical stuff itself, using the >>> vhost-user-gpu protocol[1], whereas the crosvm one has the backend do >>> almost everything (like every other vhost-user device =E2=80=94 also mu= ch better >>> for sandboxing). >>> >>> [1]: https://www.qemu.org/docs/master/interop/vhost-user-gpu.html#vhost= -user-gpu-protocol >>=20 >> Possibly the best way to test this would be to use crosvm, which also >> supports virtio-sound. > > I thought the only implemented backends were CrAS and Android. Oh, maybe, but I think it also supports vhost-user-sound, so might be usable with vhost-device? I started packaging vhost-device-sound the other day, btw. Not quite done yet. --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEARYKAB0WIQRV/neXydHjZma5XLJbRZGEIw/wogUCaHyp3QAKCRBbRZGEIw/w ohvHAP9G2Jb862r29AFBsjMu4+LmtHarSoHXARYjY/+4zginmgD9E2Pe5fvnwV/c fcIwZTZwQ9Rs+6mjmVG2zVv2ONup9Qw= =IxPA -----END PGP SIGNATURE----- --=-=-=--