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 586CB3CFD; Wed, 15 Jul 2026 18:25:34 +0000 (UTC) Received: by atuin.qyliss.net (Postfix, from userid 993) id E6B183CF4; Wed, 15 Jul 2026 18:25:30 +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-b1-smtp.messagingengine.com (fhigh-b1-smtp.messagingengine.com [202.12.124.152]) by atuin.qyliss.net (Postfix) with ESMTPS id 006D33CF2 for ; Wed, 15 Jul 2026 18:25:28 +0000 (UTC) Received: from phl-compute-05.internal (phl-compute-05.internal [10.202.2.45]) by mailfhigh.stl.internal (Postfix) with ESMTP id B68CE7A0098; Wed, 15 Jul 2026 14:25:26 -0400 (EDT) Received: from phl-frontend-03 ([10.202.2.162]) by phl-compute-05.internal (MEProxy); Wed, 15 Jul 2026 14:25:26 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alyssa.is; h=cc :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=1784139926; x=1784226326; bh=4OewvneTYt uTwO4GnyVdBfLVU3WaGtJ09JCwL8iC/gw=; b=OJx3qcIL5rC2jvQdKUETPjVR1i vvqoDGNBxQJ1vymAnUGJLh6iUafy4MKdrYimO2rPAABiAL6fCprIALsMghc8XASy dYXrcEHXpdpMxoNQBuBnHTAm7B0RvBYzc+7E2nbCkQlXVY/kxtdGaNAnQ28Cd2HE 6zpCyF22x6dj9r1A0a5CePevJNW0vM/p4/Ro+sbGTSUUhq5rIQQ2f5eJGtyMtMkh zbwrxPnPkViOIEt4zh8WbLZhJ6T1YrOourFDDmyYkvsirszvHeKYbG1+ep6Pa44p yMfQ2FBoOeD1f4iKtG2p4zLDCa8FPTYhYFmIycc2YR1tGYeXHLpa3iqx4UiA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc: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= 1784139926; x=1784226326; bh=4OewvneTYtuTwO4GnyVdBfLVU3WaGtJ09JC wL8iC/gw=; b=TABgiFZ5fgDchFNWD8HABtK7xVfnWrn+ELq3g7edDxMirO5eOc3 inxFx3dZCQVK5g/Feq58cdKsnfjuzqvz6tYSU3Xq8z+T4U8XzvTdBeNP76Nbray4 Ns7XPZYoqqiDzi3uDrSw2Ytb1hr3DWXU4+tFoCrk7sb/6i4/HYgdPTq+JNW8Wxyj bzRj/xaK8U7Adipkiyr736Gh5GNbSahgchn/JVUfCp1hVtvZ6A9dfB+WrJa9lGr3 rhTT4JhntTnj8/WQ0wfZly68dZWxiqOxsiBxET1SwtdmGH63KwdUhgh5cqGL5iB3 ofTFgjNlsI5hby0E9EzO9Hv8kvJ5LSX86FA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: dmFkZTEegW8KyjMaib3SNMX4QGpKMytynOdzV6cAlc4f/4IKas3TOP6RB3QLu7kqB+ha3d o4ni4tiI7AjfmIcoK2lrwVYZJm73eO0DvLLI6mTpmqmQVBerRbxg3HrYnDSRp3PD91iGM0 ECNbnI4m5P67jiizOLRXdPEFb/7/K/zfk9CSQybZLrYV6WqeoNpK/40cwn8RcFJNpioF+l 0wYEh5itTZmuDRkS1mPFa4bnEi+kXOwxMWOxiWNLI+eGJKXjKJ4iRmojk7zAVIbj2an4Wo D60r7wvk7bRD0F/BVZjDayjop8KhUJ17D6eX4NZI6wx1oVy0zg380qKc3pwvQATm9VeMgM gJee3wh5Dy5wM0UEz1OUTZRvGVgtkOt09vxotsD8z+wsGnzX9yDhxI0zajIJNw8rejJdTl W1WBggB0+yvQfpq+8e6UedEUymUVtNFGmNIVVzhWx42eMpvB2IK/AdILsSSlNIYTxCOZGm ckUbs2YvNmUV3BVokwSFZXx7XRjeNiX28+ZPtzyzRfhFKJtjNlu6qyef09zAwrsXkCJ9gA z4q/NHazrw7vd8FwHWZEA+wVx0cL6xxyfs9U10IEUcwmEbmVc62lpiNeLSkacLpI1eUfJ8 G/CIHhgWon1s+wTzDe0V/WJ18hi3SUop5MHpW/qd6t3cf+sjOIsCuEDb/eaA X-ME-Proxy: Feedback-ID: i12284293:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 15 Jul 2026 14:25:25 -0400 (EDT) Received: by mbp.qyliss.net (Postfix, from userid 1000) id 3B1588955475; Wed, 15 Jul 2026 20:25:23 +0200 (CEST) From: Alyssa Ross To: colby@colbyt.com Subject: Re: Cosmic Progress In-Reply-To: References: Date: Wed, 15 Jul 2026 20:25:21 +0200 Message-ID: <87bjc8qfe6.fsf@alyssa.is> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" Message-ID-Hash: SF3UISEZFANBEXADR3IC7BNAIM5YNVY2 X-Message-ID-Hash: SF3UISEZFANBEXADR3IC7BNAIM5YNVY2 X-MailFrom: hi@alyssa.is X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; 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; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: "devel@spectrum-os.org" X-Mailman-Version: 3.3.10 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 colby@colbyt.com writes: > Not sure why this email didn't send but trying again from my regular addr= ess! -- thanks for all the great updates - so speedy! > > On Saturday, July 11th, 2026 at 1:32 AM, CCT wrote: > >> Thank you for posting this. Since our last conversation, I=E2=80=99ve be= en further prototyping a COSMIC-based downstream of Spectrum for PolymerOS,= so there is useful overlap here. >> PolymerOS currently replaces the standard panel and dock with custom sur= faces and carries several small cosmic-comp changes for trust decorations, = presence attestation, and compositor readiness. I=E2=80=99ve attached scree= nshots from two stages of the prototype. >> >> A few notes and questions: >> >> - Immutable configuration: COSMIC=E2=80=99s configuration code attempts = to write defaults when loading. Because our /etc/xdg is immutable, we curre= ntly seed a writable runtime copy from an administrator-owned immutable bas= eline. Is there an intended COSMIC location or pattern for this? From=20what I've saw in my work with it, COSMIC stuff only *requires* an empty configuration directory to exist, e.g. etc/xdg/cosmic/com.system76.CosmicComp/v1, so I just created some empty directories in the Makefile. None of the files within need to exist, and it doesn't seem to mind if it can't write those files when it's running. I'd be interested to hear if you see otherwise. >> - Socket and readiness: Our separately supervised services need a stable= Wayland socket path and an explicit signal that the compositor is ready. I= s the intended long-term API an absolute socket path supplied to cosmic-com= p, potentially followed by service-manager socket activation? Would COSMIC = accept a service-manager-neutral readiness signal, such as writing once to = an inherited file descriptor, so s6-based systems do not need a downstream = patch? This is also already addressed in my series. s6 now comes with a program that translates systemd readiness notification into s6 readiness notification, so we use that. It only required a small bug fix that has now been accepted by s6 upstream. As for the Wayland socket, I aim to get cosmic-comp upstream to either support creating the Wayland socket on a given absolute path (which is what the series currently does), or to support being started with a listening Wayland socket file descriptor. My first PR for the former has already been accepted by wayland-rs, but further progress requires a release of those libraries so Smithay can use that functionality. >> - QEMU and VNC: The desktop is usable with software rendering, without m= aking virgl mandatory. We would prefer both software and accelerated modes = to remain supported. We normally use hardware acceleration, while software = rendering is valuable for testing compositor security decorations and for h= eadless builders. I think it should be fine as long as you have Mesa's software rendering drivers available on your host. (hardware.graphics.enable on NixOS =E2=80= =94 despite the name it's not necessary to have any actual graphics hardware for that to work, the option just needs to be enabled so the drivers are installed.) If that doesn't work, let me know and we can see what can be done. --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEARYKAB0WIQRV/neXydHjZma5XLJbRZGEIw/wogUCalfQkQAKCRBbRZGEIw/w ooLoAP0WmV4iHjX1dmKpU/515l7IiKggzkybrwdCH0qf6dGf8QEArpeMctpL9nF1 bXEs9QvDRz4cReVbc+piCA8k8eBMSAw= =BIoU -----END PGP SIGNATURE----- --=-=-=--