Re: [oe-core][PATCHv12 0/6] Display manager proposal for x11 and wayland

["Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>]

On Thu Dec 18, 2025 at 8:10 PM CET, rs wrote:
> From: Randolph Sapp <rs@ti.com>
>
> Hello maintainers, I wanted to wait for the latest tag to get cut before
> bringing this back up, but here it is. This version addresses most of the
> concerns I've seen regarding this series and adds on a little more functionality
> considering we now allow for proper session selection.
>
> This led me into a bit of a dive into the desktop-entry-spec [1] and associated
> validator [2] that I wouldn't mind some opinions on as well if people are
> curious about that.
>
> Legacy details follow:
>
> 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 [3].
> 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.
>

Hi Randolph,

Thanks for the new version. It looks like it got better. Still, we got a
few issues on the autobuilder.

First, issue, probably because of nopasswdlogin group:

 NOTE: Resolving any missing task queue dependencies
2025-12-19 08:42:54,839 - oe-selftest - INFO -       ERROR: Nothing RPROVIDES 'xserver-nodm-init' (but /srv/pokybuild/yocto-worker/reproducible/build/layers/openembedded-core/meta/recipes-graphics/packagegroups/packagegroup-core-x11.bb RDEPENDS on or otherwise requires it)
2025-12-19 08:42:54,839 - oe-selftest - INFO -       xserver-nodm-init was skipped: Recipe xserver-nodm-init, package xserver-nodm-init: system groupname "nopasswdlogin" does not have a static ID defined. Add nopasswdlogin to one of these files: /srv/pokybuild/yocto-worker/reproducible/build/build-st/meta-selftest/files/static-group
2025-12-19 08:42:54,839 - oe-selftest - INFO -       NOTE: Runtime target 'xserver-nodm-init' is unbuildable, removing...
2025-12-19 08:42:54,839 - oe-selftest - INFO -       Missing or unbuildable dependency chain was: ['xserver-nodm-init']
2025-12-19 08:42:54,839 - oe-selftest - INFO -       ERROR: Nothing RPROVIDES 'packagegroup-core-x11-utils' (but /srv/pokybuild/yocto-worker/reproducible/build/layers/openembedded-core/meta/recipes-graphics/packagegroups/packagegroup-core-x11.bb, /srv/pokybuild/yocto-worker/reproducible/build/layers/openembedded-core/meta/recipes-graphics/packagegroups/packagegroup-core-x11-base.bb RDEPENDS on or otherwise requires it)
2025-12-19 08:42:54,840 - oe-selftest - INFO -       No eligible RPROVIDERs exist for 'packagegroup-core-x11-utils'
2025-12-19 08:42:54,840 - oe-selftest - INFO -       NOTE: Runtime target 'packagegroup-core-x11-utils' is unbuildable, removing...
2025-12-19 08:42:54,840 - oe-selftest - INFO -       Missing or unbuildable dependency chain was: ['packagegroup-core-x11-utils']
2025-12-19 08:42:54,840 - oe-selftest - INFO -       NOTE: Runtime target 'packagegroup-core-x11-base' is unbuildable, removing...
2025-12-19 08:42:54,840 - oe-selftest - INFO -       Missing or unbuildable dependency chain was: ['packagegroup-core-x11-base', 'packagegroup-core-x11-utils']
2025-12-19 08:42:54,840 - oe-selftest - INFO -       NOTE: Runtime target 'core-image-sato' is unbuildable, removing...
2025-12-19 08:42:54,840 - oe-selftest - INFO -       Missing or unbuildable dependency chain was: ['core-image-sato', 'packagegroup-core-x11-base', 'packagegroup-core-x11-utils']
2025-12-19 08:42:54,840 - oe-selftest - INFO -       ERROR: Nothing RPROVIDES 'packagegroup-core-x11' (but /srv/pokybuild/yocto-worker/reproducible/build/layers/openembedded-core/meta/recipes-graphics/packagegroups/packagegroup-core-x11.bb RDEPENDS on or otherwise requires it)
2025-12-19 08:42:54,840 - oe-selftest - INFO -       No eligible RPROVIDERs exist for 'packagegroup-core-x11'

https://autobuilder.yoctoproject.org/valkyrie/#/builders/37/builds/3049

The second one is again on xorg.XorgTest.test_xorg_running:

Traceback (most recent call last):
  File "/srv/pokybuild/yocto-worker/qa-extras2/build/layers/openembedded-core/meta/lib/oeqa/core/decorator/__init__.py", line 35, in wrapped_f
    return func(*args, **kwargs)
  File "/srv/pokybuild/yocto-worker/qa-extras2/build/layers/openembedded-core/meta/lib/oeqa/core/decorator/__init__.py", line 35, in wrapped_f
    return func(*args, **kwargs)
  File "/srv/pokybuild/yocto-worker/qa-extras2/build/layers/openembedded-core/meta/lib/oeqa/core/decorator/__init__.py", line 35, in wrapped_f
    return func(*args, **kwargs)
  File "/srv/pokybuild/yocto-worker/qa-extras2/build/layers/openembedded-core/meta/lib/oeqa/runtime/cases/xorg.py", line 31, in test_xorg_running
    self.assertEqual(status, 0, msg=msg)
    ~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^
AssertionError: 1 != 0 : Xorg does not appear to be running   PID USER       VSZ STAT COMMAND
...
RESULTS - xorg.XorgTest.test_xorg_running: FAILED (1.30s)

https://autobuilder.yoctoproject.org/valkyrie/#/builders/26/builds/2862

I had a look at the corresponding QEMU boot log, but there is no
error in there.

Thanks,
Mathieu

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