From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from aws-us-west-2-korg-lkml-1.web.codeaurora.org (localhost.localdomain [127.0.0.1]) by smtp.lore.kernel.org (Postfix) with ESMTP id 3A859C28B2F for ; Sat, 15 Mar 2025 00:36:55 +0000 (UTC) Received: from fllvem-ot04.ext.ti.com (fllvem-ot04.ext.ti.com [198.47.19.246]) by mx.groups.io with SMTP id smtpd.web10.1455.1741999006014226619 for ; Fri, 14 Mar 2025 17:36:46 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@ti.com header.s=ti-com-17Q1 header.b=BTp4HT6e; spf=pass (domain: ti.com, ip: 198.47.19.246, mailfrom: rs@ti.com) Received: from lelv0265.itg.ti.com ([10.180.67.224]) by fllvem-ot04.ext.ti.com (8.15.2/8.15.2) with ESMTPS id 52F0aHTS2275773 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Fri, 14 Mar 2025 19:36:17 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ti.com; s=ti-com-17Q1; t=1741998977; bh=G35GRApcb4Bmb6lfOIR296mg+hrcbzoivs1oVjRanlE=; h=Date:CC:Subject:From:To:References:In-Reply-To; b=BTp4HT6eDrOnIpzrxgaE8Lhlqcv5fPVFEaI6COT6E1zlfY0HX3S00wz8WY6CeSNqG YfOPdZum5zKwJSbG7Xgw4p8kCrQ4SXYaTt+Lf7rQYNkoUWjNSYa0VOYucbeN9ZTxgS NBFA5KVnwOJDA+joKamOBMH8Oh5t2fHehfCePY8Q= Received: from DLEE102.ent.ti.com (dlee102.ent.ti.com [157.170.170.32]) by lelv0265.itg.ti.com (8.15.2/8.15.2) with ESMTPS id 52F0aHNH031704 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=FAIL); Fri, 14 Mar 2025 19:36:17 -0500 Received: from DLEE108.ent.ti.com (157.170.170.38) by DLEE102.ent.ti.com (157.170.170.32) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2507.23; Fri, 14 Mar 2025 19:36:16 -0500 Received: from lelvsmtp6.itg.ti.com (10.180.75.249) by DLEE108.ent.ti.com (157.170.170.38) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2507.23 via Frontend Transport; Fri, 14 Mar 2025 19:36:17 -0500 Received: from localhost (rs-desk.dhcp.ti.com [128.247.81.144]) by lelvsmtp6.itg.ti.com (8.15.2/8.15.2) with ESMTP id 52F0aH9I027477; Fri, 14 Mar 2025 19:36:17 -0500 MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" Date: Fri, 14 Mar 2025 19:36:17 -0500 Message-ID: CC: , , , , , , , , , , , Subject: Re: [oe-core][RFC 0/3] Display manager proposal for x11 and wayland From: Randolph Sapp To: Randolph Sapp , Alexander Kanavin X-Mailer: aerc 0.20.1-0-g2ecb8770224a References: <20250314002937.672768-1-rs@ti.com> In-Reply-To: X-C2ProcessedOrg: 333ef613-75bf-4e12-a4b1-8e3623f5dcea List-Id: X-Webhook-Received: from li982-79.members.linode.com [45.33.32.79] by aws-us-west-2-korg-lkml-1.web.codeaurora.org with HTTPS for ; Sat, 15 Mar 2025 00:36:55 -0000 X-Groupsio-URL: https://lists.openembedded.org/g/openembedded-core/message/212865 On Fri Mar 14, 2025 at 2:14 PM CDT, Randolph Sapp wrote: > On Fri Mar 14, 2025 at 4:14 AM CDT, Alexander Kanavin wrote: >> On Fri, 14 Mar 2025 at 01:30, wrote: >>> Example implementation of emptty for weston-init following the request = on the >>> previous RFC [1] and previous example [2]. This variant is applicable t= o master. >>> >>> This packages emptty and a default configuration for emptty as "emptty"= and >>> "emptty-conf" respectively. This allows the existing init packages to o= verride >>> the configuration similar to the way grub boot configs are handled. >>> >>> The weston-init package still handles the weston config and weston user= setup as >>> it always has. The only real difference from a consumer standpoint is t= hat the >>> autologin group for the weston user changed from "wayland" to the more = generic >>> "nopasswdlogin". >>> >>> [1] https://lists.openembedded.org/g/openembedded-core/message/212640 >>> [2] https://lists.openembedded.org/g/openembedded-core/message/212785 >> >> I quickly checked this locally. There are some issues that need to be >> addressed before this goes to the autobuilder: >> >> 1. WARNING: emptty-0.13.0-r0 do_recipe_qa: QA Issue: Recipe emptty in >> /srv/work/alex/poky/meta/recipes-graphics/emptty/emptty_0.13.0.bb does >> not have an assigned maintainer. Please add an entry into >> meta/conf/distro/include/maintainers.inc. [missing-maintainer] > > Yeah. I wouldn't mind maintaining this package and can set that. Just did= n't > know if there was someone I needed to check with before I did that. > >> 2. With default poky config: >> >> ERROR: Nothing RPROVIDES 'pam-plugin-succeed-if' (but >> /srv/work/alex/poky/meta/recipes-graphics/emptty/emptty_0.13.0.bb >> RDEPENDS on or otherwise requires it) >> NOTE: Runtime target 'pam-plugin-succeed-if' is unbuildable, removing... >> Missing or unbuildable dependency chain was: ['pam-plugin-succeed-if'] >> ERROR: Required build target 'emptty' has no buildable providers. >> Missing or unbuildable dependency chain was: ['emptty', 'pam-plugin-succ= eed-if'] >> >> You should either make the pam dependency optional (via PACKAGECONFIG >> subject to pam in DISTRO_FEATURES), or use REQUIRED_DISTRO_FEATURES. > > Good point. I added the PACKAGECONFIG to remove pam support, that should = also > toggle the runtime dep on pam-plugin-succeed-if. Will address in the prop= er > series. > >> 3. Again, with default poky config: >> >> NOTE: Multiple providers are available for runtime virtual-emptty-conf >> (emptty, weston-init) >> Consider defining a PREFERRED_RPROVIDER entry to match virtual-emptty-co= nf >> >> >> Alex > > That last note is perplexing. Patch 3/3 is literally setting the default = runtime > provider for virtual-emptty-conf. I'm also seeing the following notice th= ough: > > NOTE: Multiple providers are available for runtime libnss-mdns (avahi-lib= nss-mdns, mdns) > Consider defining a PREFERRED_RPROVIDER entry to match libnss-mdns > > Is there some other variable I need to set for master? Is that message no= w being > printed if 2 package are being produced? If that's the case I can check = the > PREFERRED_RPROVIDER variable and conditionally prevent producing the empt= ty-conf > package, but that feels a little hacky. Anyone have any better ideas abou= t that? > > - Randolph Another fun issue. This actually adds additional checks to user accounts us= ing unix_chkpwd in pam and an equivalent mechanism in the libxcrypt path. It's uncovered a relatively interesting issue around device initialization where system time is reset to a date prior to the build in the case where there i= s no RTC to read and the weston user's login attempts fail until the time catche= s up. The password change for that user is in the future. Forcing a time jump during startup with a custom service resolves the issue= , but it's unusual nothing else has had any problems with this. I thought I remem= ber Yocto defaulting the OS time to the image build time. Was I hallucinating t= hat? - Randolph