All of lore.kernel.org
 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][PATCHv4 1/5] libx11: create tmpfile dir for x11 domain socket
Date: Fri, 16 May 2025 18:18:01 +0200	[thread overview]
Message-ID: <D9XPYFVP0CD4.358B3UWM5A4PI@bootlin.com> (raw)
In-Reply-To: <20250515214919.1404453-2-rs@ti.com>

On Thu May 15, 2025 at 11:49 PM CEST, rs wrote:
> From: Randolph Sapp <rs@ti.com>
>
> Register a tmpfile.d or volatile directory entry for the x11 domain
> socket so this will always be created with the correct permissions.
>
> Currently some x11 related applications will create this directory if it
> doesn't already exist, but this is not true for everything. In addition,
> if the application in question isn't started as root, it's possible this
> directory can be owned by a non-root user. This isn't an issue by
> itself, but it can potentially lead to problems in a multi-user
> environment.
>
> Signed-off-by: Randolph Sapp <rs@ti.com>
> ---

Hi Randolph,

Another build issue on various builders:

ERROR: libx11-1_1.8.12-r0 do_package: QA Issue: libx11: Files/directories were installed but not shipped in any package:
  /usr/lib/tmpfiles.d
  /usr/lib/tmpfiles.d/x11.conf
Please set FILES such that these items are packaged. Alternatively if they are unneeded, avoid installing them or delete them within do_install.
libx11: 2 installed and not shipped files. [installed-vs-shipped]
ERROR: libx11-1_1.8.12-r0 do_package: Fatal QA errors were found, failing task.

https://autobuilder.yoctoproject.org/valkyrie/#/builders/93/builds/1631
https://autobuilder.yoctoproject.org/valkyrie/#/builders/22/builds/1638
https://autobuilder.yoctoproject.org/valkyrie/#/builders/20/builds/1602
https://autobuilder.yoctoproject.org/valkyrie/#/builders/9/builds/1614

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



  parent reply	other threads:[~2025-05-16 16:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-15 21:49 [oe-core][PATCHv4 0/5] Display manager proposal for x11 and wayland rs
2025-05-15 21:49 ` [oe-core][PATCHv4 1/5] libx11: create tmpfile dir for x11 domain socket rs
2025-05-15 22:54   ` Denys Dmytriyenko
2025-05-16 16:18   ` Mathieu Dubois-Briand [this message]
2025-05-15 21:49 ` [oe-core][PATCHv4 2/5] emptty: add version 0.14.0 rs
2025-05-15 21:49 ` [oe-core][PATCHv4 3/5] weston-init: convert to virtual-emptty-conf rs
2025-05-15 21:49 ` [oe-core][PATCHv4 4/5] weston: remove deprecated weston-start scripts rs
2025-05-15 21:49 ` [oe-core][PATCHv4 5/5] xserver-nodm-init: convert to virtual-emptty-conf rs

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=D9XPYFVP0CD4.358B3UWM5A4PI@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.