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][PATCHv2 0/3] Display manager proposal for x11 and wayland
Date: Tue, 13 May 2025 08:15:28 +0200 [thread overview]
Message-ID: <D9UT9GNAPNJ1.29E1A3PUIW2PR@bootlin.com> (raw)
In-Reply-To: <20250505224801.3181046-1-rs@ti.com>
On Tue May 6, 2025 at 12:47 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
>
Ok, so I tried again to merge this patch, and I believe I've got new
errors:
RESULTS - xorg.XorgTest.test_xorg_running: FAILED (1.43s)
...
AssertionError: 1 != 0 : Xorg does not appear to be running
https://autobuilder.yoctoproject.org/valkyrie/#/builders/9/builds/1579
https://autobuilder.yoctoproject.org/valkyrie/#/builders/20/builds/1567
https://autobuilder.yoctoproject.org/valkyrie/#/builders/67/builds/1620
https://autobuilder.yoctoproject.org/valkyrie/#/builders/68/builds/1661
https://autobuilder.yoctoproject.org/valkyrie/#/builders/74/builds/1582
https://autobuilder.yoctoproject.org/valkyrie/#/builders/92/builds/1589
Traceback (most recent call last):
File "/srv/pokybuild/yocto-worker/oe-selftest-armhost/build/meta/lib/oeqa/core/decorator/__init__.py", line 35, in wrapped_f
return func(*args, **kwargs)
File "/srv/pokybuild/yocto-worker/oe-selftest-armhost/build/meta/lib/oeqa/runtime/cases/weston.py", line 63, in test_wayland_info
self.assertEqual(status, 0, msg='wayland-info error: %s' % output)
~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AssertionError: 255 != 0 : wayland-info error: failed to create display: Connection refused
Traceback (most recent call last):
File "/srv/pokybuild/yocto-worker/oe-selftest-armhost/build/meta/lib/oeqa/core/decorator/__init__.py", line 35, in wrapped_f
return func(*args, **kwargs)
File "/srv/pokybuild/yocto-worker/oe-selftest-armhost/build/meta/lib/oeqa/runtime/cases/weston.py", line 67, in test_weston_can_initialize_new_wayland_compositor
existing_wl_processes = self.get_processes_of('weston-desktop-shell', 'existing')
File "/srv/pokybuild/yocto-worker/oe-selftest-armhost/build/meta/lib/oeqa/runtime/cases/weston.py", line 32, in get_processes_of
self.assertEqual(status, 0, msg='Retrieve %s (%s) processes error: %s' % (target, error_msg, output))
~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AssertionError: 1 != 0 : Retrieve weston-desktop-shell (existing) processes error:
Traceback (most recent call last):
File "/srv/pokybuild/yocto-worker/oe-selftest-armhost/build/meta/lib/oeqa/core/decorator/__init__.py", line 35, in wrapped_f
return func(*args, **kwargs)
File "/srv/pokybuild/yocto-worker/oe-selftest-armhost/build/meta/lib/oeqa/core/decorator/__init__.py", line 35, in wrapped_f
return func(*args, **kwargs)
File "/srv/pokybuild/yocto-worker/oe-selftest-armhost/build/meta/lib/oeqa/runtime/cases/weston.py", line 28, in test_weston_running
self.assertEqual(status, 0, msg=msg)
~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^
AssertionError: 1 != 0 : Weston does not appear to be running PID USER VSZ STAT COMMAND
Traceback (most recent call last):
File "/srv/pokybuild/yocto-worker/oe-selftest-armhost/build/meta/lib/oeqa/core/decorator/__init__.py", line 35, in wrapped_f
return func(*args, **kwargs)
File "/srv/pokybuild/yocto-worker/oe-selftest-armhost/build/meta/lib/oeqa/core/decorator/__init__.py", line 35, in wrapped_f
return func(*args, **kwargs)
File "/srv/pokybuild/yocto-worker/oe-selftest-armhost/build/meta/lib/oeqa/runtime/cases/weston.py", line 89, in test_weston_supports_xwayland
self.assertEqual(status, 0, msg=msg)
~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^
AssertionError: 1 != 0 : xwayland does not appear to be running
...
RESULTS - weston.WestonTest.test_wayland_info: FAILED (0.51s)
RESULTS - weston.WestonTest.test_weston_can_initialize_new_wayland_compositor: FAILED (0.30s)
RESULTS - weston.WestonTest.test_weston_running: FAILED (0.78s)
RESULTS - weston.WestonTest.test_weston_supports_xwayland: FAILED (0.49s)
https://autobuilder.yoctoproject.org/valkyrie/#/builders/23/builds/1661
https://autobuilder.yoctoproject.org/valkyrie/#/builders/75/builds/1514
Traceback (most recent call last):
File "/srv/pokybuild/yocto-worker/no-x11/build/meta/lib/oeqa/core/decorator/__init__.py", line 35, in wrapped_f
return func(*args, **kwargs)
File "/srv/pokybuild/yocto-worker/no-x11/build/meta/lib/oeqa/runtime/cases/weston.py", line 63, in test_wayland_info
self.assertEqual(status, 0, msg='wayland-info error: %s' % output)
AssertionError: 255 != 0 : wayland-info error: failed to create display: No such file or directory
...
RESULTS - weston.WestonTest.test_wayland_info: FAILED (0.52s)
https://autobuilder.yoctoproject.org/valkyrie/#/builders/25/builds/1596
https://autobuilder.yoctoproject.org/valkyrie/#/builders/35/builds/1545
https://autobuilder.yoctoproject.org/valkyrie/api/v2/logs/2356168/raw_inline
2025-05-12 21:09:25,962 - oe-selftest - INFO - ERROR: Nothing RPROVIDES 'weston-init' (but /srv/pokybuild/yocto-worker/reproducible/build/meta/recipes-graphics/wayland/weston_14.0.1.bb, /srv/pokybuild/yocto-worker/reproducible/build/meta/recipes-graphics/packagegroups/packagegroup-core-weston.bb RDEPENDS on or otherwise requires it)
2025-05-12 21:09:25,962 - oe-selftest - INFO - weston-init was skipped: Recipe weston-init, package weston-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-05-12 21:09:25,963 - oe-selftest - INFO - ERROR: Nothing RPROVIDES 'weston-dev' (but /srv/pokybuild/yocto-worker/reproducible/build/meta/recipes-graphics/wayland/weston_14.0.1.bb RDEPENDS on or otherwise requires it)
...
2025-05-12 21:09:25,963 - oe-selftest - INFO - ERROR: Nothing RPROVIDES 'weston' (but /srv/pokybuild/yocto-worker/reproducible/build/meta/recipes-graphics/wayland/weston_14.0.1.bb, /srv/pokybuild/yocto-worker/reproducible/build/meta/recipes-graphics/packagegroups/packagegroup-core-weston.bb RDEPENDS on or otherwise requires it)
...
2025-05-12 21:09:25,963 - oe-selftest - INFO - ERROR: Nothing RPROVIDES 'weston-examples' (but /srv/pokybuild/yocto-worker/reproducible/build/meta/recipes-graphics/packagegroups/packagegroup-core-weston.bb RDEPENDS on or otherwise requires it)
...
https://autobuilder.yoctoproject.org/valkyrie/#/builders/37/builds/1642
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2025-05-13 6:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-05 22:47 [oe-core][PATCHv2 0/3] Display manager proposal for x11 and wayland rs
2025-05-05 22:47 ` [oe-core][PATCHv2 1/3] emptty: add version 0.14.0 rs
2025-05-05 22:48 ` [oe-core][PATCHv2 2/3] weston-init: convert to virtual-emptty-conf rs
2025-05-05 22:48 ` [oe-core][PATCHv2 3/3] xserver-nodm-init: " rs
2025-05-06 7:47 ` [oe-core][PATCHv2 0/3] Display manager proposal for x11 and wayland Mathieu Dubois-Briand
2025-05-06 23:03 ` Randolph Sapp
2025-05-07 13:37 ` Alexander Kanavin
2025-05-07 20:42 ` Randolph Sapp
[not found] ` <183D59758C0F13FA.9842@lists.openembedded.org>
2025-05-08 20:39 ` Randolph Sapp
2025-05-09 8:27 ` Richard Purdie
2025-05-13 6:15 ` Mathieu Dubois-Briand [this message]
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=D9UT9GNAPNJ1.29E1A3PUIW2PR@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.