<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> <meta name="Generator" content="Microsoft Word 15 (filtered medium)"> <style></style> </head> <body lang="EN-US" link="blue" vlink="purple" style="word-wrap:break-word"> <div class="WordSection1"> Thanks, everybody.<o:p></o:p> <o:p> </o:p> After some trial and error, I find that if I install seatd in the host and the seatd dev package in the Toolbox container and I then symlink the host seatd socket into /tmp on the container, Weston seems to start up okay on my physical KMS connectors:<o:p></o:p> <o:p> </o:p> user@host:~$ toolbox enter<o:p></o:p> …<o:p></o:p> <o:p> </o:p> user@toolbox:~$ sudo ln -s /run/host/run/seatd.socket /run/<o:p></o:p> user@toolbox:~$ weston --backend=drm<o:p></o:p> <o:p> </o:p> -Matt<o:p></o:p> <o:p> </o:p> <div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in"> From: Daniel Stone <daniel@fooishbar.org> Date: Wednesday, June 5, 2024 at 5:07 AM To: Pekka Paalanen <pekka.paalanen@collabora.com> Cc: "Hoosier, Matt" <Matt.Hoosier@garmin.com>, "sir@cmpwn.com" <sir@cmpwn.com>, "contact@emersion.fr" <contact@emersion.fr>, Marius Vlad <marius.vlad@collabora.com>, "wayland-devel@lists.freedesktop.org" <wayland-devel@lists.freedesktop.org> Subject: Re: Ways to test Weston during development (Re: Full-motion zero-copy screen capture in Weston)<o:p></o:p> </div> <div> <o:p> </o:p> </div> <div> Hi, On Wed, 5 Jun 2024 at 09: 09, Pekka Paalanen <pekka. paalanen@ collabora. com> wrote: > On Tue, 4 Jun 2024 20: 33: 48 +0000 > "Hoosier, Matt" <Matt. Hoosier@ garmin. com> wrote: > > Tactical question: I somehow missed until <o:p></o:p> </div> <div> <o:p></o:p> </div> <pre style="white-space:pre-wrap">Hi,<o:p></o:p></pre> <pre><o:p> </o:p></pre> <pre>On Wed, 5 Jun 2024 at 09:09, Pekka Paalanen<o:p></o:p></pre> <pre><pekka.paalanen@collabora.com> wrote:<o:p></o:p></pre> <pre>> On Tue, 4 Jun 2024 20:33:48 +0000<o:p></o:p></pre> <pre>> "Hoosier, Matt" <Matt.Hoosier@garmin.com> wrote:<o:p></o:p></pre> <pre>> > Tactical question: I somehow missed until this point that the remote<o:p></o:p></pre> <pre>> > and pipewire plugins will only run if the DRM backend is being used.<o:p></o:p></pre> <pre>> ><o:p></o:p></pre> <pre>> > But the DRM backend *really* doesn't want to start nowadays unless<o:p></o:p></pre> <pre>> > you're running on a system with seatd and/or logind available.<o:p></o:p></pre> <pre>> > Toolbox [1] is the de facto way to develop on bleeding edge copies of<o:p></o:p></pre> <pre>> > components these days. But it logind and seatd aren't exposed into it.<o:p></o:p></pre> <pre>> ><o:p></o:p></pre> <pre>> > How do Weston people interactively develop on the Weston DRM backend<o:p></o:p></pre> <pre>> > nowadays?<o:p></o:p></pre> <pre>> ><o:p></o:p></pre> <pre>> > [1] <a href="https://urldefense.com/v3/__https:/docs.fedoraproject.org/en-US/fedora-silverblue/toolbox/__;!!EJc4YC3iFmQ!X9PIq-FMYhremNjhMhD6uGHUdYcYt4QKcl5CIjQAi0gYX5IyFx63gK1QZDWepwQBxB3mu1WTvjK2SJoQzfs$">https://urldefense.com/v3/__https://docs.fedoraproject.org/en-US/fedora-silverblue/toolbox/__;!!EJc4YC3iFmQ!X9PIq-FMYhremNjhMhD6uGHUdYcYt4QKcl5CIjQAi0gYX5IyFx63gK1QZDWepwQBxB3mu1WTvjK2SJoQzfs$</a><o:p></o:p></pre> <pre>><o:p> </o:p></pre> <pre>> I'm doing it old-school on my workstation, without any containers. What<o:p></o:p></pre> <pre>> dependencies my distribution does not provide, I build and install<o:p></o:p></pre> <pre>> manually into a prefix under $HOME:<o:p></o:p></pre> <pre>><o:p> </o:p></pre> <pre>> <a href="https://urldefense.com/v3/__https:/www.collabora.com/news-and-blog/blog/2020/04/10/clean-reliable-setup-for-dependency-installation/__;!!EJc4YC3iFmQ!X9PIq-FMYhremNjhMhD6uGHUdYcYt4QKcl5CIjQAi0gYX5IyFx63gK1QZDWepwQBxB3mu1WTvjK2Y5E0gB4$">https://urldefense.com/v3/__https://www.collabora.com/news-and-blog/blog/2020/04/10/clean-reliable-setup-for-dependency-installation/__;!!EJc4YC3iFmQ!X9PIq-FMYhremNjhMhD6uGHUdYcYt4QKcl5CIjQAi0gYX5IyFx63gK1QZDWepwQBxB3mu1WTvjK2Y5E0gB4$</a><o:p></o:p></pre> <pre>><o:p> </o:p></pre> <pre>> The "clean and reliable" is probably outdated in this era of<o:p></o:p></pre> <pre>> containers...<o:p></o:p></pre> <pre><o:p> </o:p></pre> <pre>Yes, doing it in containers is a little bit tricky since it's not<o:p></o:p></pre> <pre>exactly the design case. Honestly, on my Silverblue systems, I just<o:p></o:p></pre> <pre>install a bunch of relevant dependencies into the system image with<o:p></o:p></pre> <pre>rpm-ostree, and have a pile of self-built dependencies in a local<o:p></o:p></pre> <pre>prefix.<o:p></o:p></pre> <pre><o:p> </o:p></pre> <pre>This might give you some insight however:<o:p></o:p></pre> <pre><a href="https://urldefense.com/v3/__https:/github.com/containers/toolbox/issues/992__;!!EJc4YC3iFmQ!X9PIq-FMYhremNjhMhD6uGHUdYcYt4QKcl5CIjQAi0gYX5IyFx63gK1QZDWepwQBxB3mu1WTvjK21Tr-34M$">https://urldefense.com/v3/__https://github.com/containers/toolbox/issues/992__;!!EJc4YC3iFmQ!X9PIq-FMYhremNjhMhD6uGHUdYcYt4QKcl5CIjQAi0gYX5IyFx63gK1QZDWepwQBxB3mu1WTvjK21Tr-34M$</a><o:p></o:p></pre> <pre><o:p> </o:p></pre> <pre>It probably needs some minor changes in Weston but does at least seem doable ...<o:p></o:p></pre> <pre><o:p> </o:p></pre> <pre>Cheers,<o:p></o:p></pre> <pre>Daniel<o:p></o:p></pre> </div> </body> </html>