Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <rs@ti.com>, <richard.purdie@linuxfoundation.org>,
	<ross.burton@arm.com>, <alex@linutronix.de>,
	<otavio@ossystems.com.br>, <kexin.hao@windriver.com>,
	<afd@ti.com>, <detheridge@ti.com>, <denis@denix.org>,
	<reatmon@ti.com>
Cc: <openembedded-core@lists.openembedded.org>, <vijayp@ti.com>
Subject: Re: [oe-core][PATCHv6 0/5] Display manager proposal for x11 and wayland
Date: Wed, 21 May 2025 17:58:52 +0200	[thread overview]
Message-ID: <DA1YOI4L8TYX.ALF8S230UTO1@bootlin.com> (raw)
In-Reply-To: <20250520233935.740242-1-rs@ti.com>

On Wed May 21, 2025 at 1:39 AM CEST, rs wrote:
> From: Randolph Sapp <rs@ti.com>
>
> We've recently run into some issues with weston-init attempting to start Weston
> prior to all drm devices being registered. There's not really a good, scriptable
> mechanism to listen in to device registration events that works with the
> existing weston-init package. Well, at least one that doesn't involve polling
> files or introducing more dependency on the init system being used.
>
> I also see there is also a lot of scripting around starting X11,
> xserver-nodm-init, that (from my limited review) should experience the same
> issue.
>
> I'd like to introduce the following display manager for oe-core, emptty [1].
> This display manager is, as described upstream, a "Dead simple CLI Display
> Manager on TTY". It supports both x11 and wayland sessions, with togglable build
> parameters to completely remove x11 and pam dependencies. It's licensed MIT,
> which shouldn't be an issue for any users. (It is written in Go, if you have
> opinions about that.)
>
> With this, both weston-init and the xserver-nodm-init packages can be re-tuned
> to leverage this display manager and simply add a user and emptty config for an
> autologin session. This can resolve the current behavior across init systems
> without additional scripting, and move some development out of this layer.
>
> This lists myself as a maintainer of emptty as well as xserver-nodm-init and
> xuser-account since these are currently unassigned and I've reworked them
> significantly here.
>
> Sorry for the delay on this series. I found a few bugs in emptty that I wanted
> to address before submitting this officially.
>
> [1] https://github.com/tvrzna/emptty
>
> v2:
> 	- Address spelling issues in commit messages
> 	- Attempt to resolve some test related issues with weston
> 	- Add additional logs to X11 related tests
> v3:
> 	- Reset AUTOLOGIN_MAX_RETRY to the default value of 2. When running
> 	  under QEMU the first auth attempt almost always fails.
> v4:
> 	- Add a tmpfile entry for the x11 domain socket directory.
> 	- Remove some scripts associated with weston-init that were being
> 	  shipped with weston
> v5:
> 	- Move tmpfile data to individual files
> 	- Add explicit entries for these in the FILES variable
> v6:
> 	- Do not attempt to ship a tmpfiles.d entry in libx11
>

Hi Randolph,

Thanks for the version, but again a previously seen error. Sorry for
the bad news :(

RESULTS - xorg.XorgTest.test_xorg_running: FAILED (1.31s)
...
AssertionError: 1 != 0 : Xorg does not appear to be running   PID USER       VSZ STAT COMMAND

https://autobuilder.yoctoproject.org/valkyrie/#/builders/20/builds/1637
https://autobuilder.yoctoproject.org/valkyrie/#/builders/95/builds/1638
https://autobuilder.yoctoproject.org/valkyrie/#/builders/9/builds/1649

I will drop the patch on my side, but I will keep the a-full build
running, we might see some other failures in the coming hours:

https://autobuilder.yoctoproject.org/valkyrie/#/builders/29/builds/1630


-- 
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com



  parent reply	other threads:[~2025-05-21 15:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-20 23:39 [oe-core][PATCHv6 0/5] Display manager proposal for x11 and wayland rs
2025-05-20 23:39 ` [oe-core][PATCHv6 1/5] libx11: create tmpfile dir for x11 domain socket rs
2025-05-20 23:39 ` [oe-core][PATCHv6 2/5] emptty: add version 0.14.0 rs
2025-05-20 23:39 ` [oe-core][PATCHv6 3/5] weston-init: convert to virtual-emptty-conf rs
2025-05-20 23:39 ` [oe-core][PATCHv6 4/5] weston: remove deprecated weston-start scripts rs
2025-05-20 23:39 ` [oe-core][PATCHv6 5/5] xserver-nodm-init: convert to virtual-emptty-conf rs
2025-05-21 15:58 ` Mathieu Dubois-Briand [this message]
2025-05-27 22:16   ` [oe-core][PATCHv6 0/5] Display manager proposal for x11 and wayland Randolph Sapp
2025-05-28 11:53     ` Mathieu Dubois-Briand
2025-06-05  0:12       ` Randolph Sapp
2025-06-06 23:49         ` Randolph Sapp
     [not found]         ` <1846990D23EB4550.17668@lists.openembedded.org>
2025-06-14  1:04           ` Randolph Sapp
     [not found]           ` <1848C33B8404DBE8.1272@lists.openembedded.org>
2025-09-05 18:52             ` Randolph Sapp

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=DA1YOI4L8TYX.ALF8S230UTO1@bootlin.com \
    --to=mathieu.dubois-briand@bootlin.com \
    --cc=afd@ti.com \
    --cc=alex@linutronix.de \
    --cc=denis@denix.org \
    --cc=detheridge@ti.com \
    --cc=kexin.hao@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio@ossystems.com.br \
    --cc=reatmon@ti.com \
    --cc=richard.purdie@linuxfoundation.org \
    --cc=ross.burton@arm.com \
    --cc=rs@ti.com \
    --cc=vijayp@ti.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox