On Tue Dec 16, 2025 at 9:37 PM CET, Randolph Sapp via lists.openembedded.org
wrote:
> From: Randolph Sapp <[email protected]>
>
> 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.
>
> [1] https://gitlab.freedesktop.org/xdg/xdg-specs/-/merge_requests/110
> [2] https://gitlab.freedesktop.org/xdg/desktop-file-utils/-/merge_requests/28
> [3] https://github.com/tvrzna/emptty
Hi Randolph,
Thanks for the new version.
It look like this is breaking the xorg.XorgTest.test_xorg_running runtime
test:
Traceback (most recent call last):
File
"/srv/pokybuild/yocto-worker/qemuarm64-alt/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/qemuarm64-alt/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/qemuarm64-alt/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/qemuarm64-alt/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.97s)
https://autobuilder.yoctoproject.org/valkyrie/#/builders/9/builds/2849
https://autobuilder.yoctoproject.org/valkyrie/#/builders/20/builds/2838
https://autobuilder.yoctoproject.org/valkyrie/#/builders/67/builds/2898
https://autobuilder.yoctoproject.org/valkyrie/#/builders/92/builds/2856
Can you have a look at this issue?
Thanks,
Mathieu
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#228064):
https://lists.openembedded.org/g/openembedded-core/message/228064
Mute This Topic: https://lists.openembedded.org/mt/116816264/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
