supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Samuel Holland <>
Subject: Re: s6 xinit replacement?
Date: Sun, 22 May 2022 11:33:30 -0500	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 5/22/22 10:07 AM, Guillermo wrote:
> Hello, Samuel.
> El sáb, 14 may 2022 a las 23:44, Samuel Holland escribió:
>> X is started at boot from my user supervision tree[1], which is started by the
>> user-* services in my system supervision tree[2].
>> [1]:
>> [2]:
> I had a look at your s6-rc service definitions, and it seems that you
> don't have one for the system-wide message bus (D-Bus) and elogind.
> That, in addition to having the tmpfs whose path is stored in
> XDG_RUNTIME_DIR mounted by a "user-setup@<your user>" system service,
> makes me think that you are not running those. On the other hand, IIUC
> the Xorg process is part of a supervision tree that runs with your
> (unprivileged) user and is launched by service "user-services@<your
> user>", and I suppose that Xorg is not a suid binary, so unless you do

Yes, all of those inferences are correct.

> something else, your Xorg*.log file should contain something like:
> (EE) systemd-logind: failed to get session: PID <Xorg's PID> does not
> belong to any known session
> ...
> (EE) open /dev/dri/card0: Permission denied
> ...
> (EE) Screen(s) found, but none have a usable configuration.
> So, what did you do? Did you also grant your user privileges for
> opening the /dev/dri/card* character special files?

Yes, I do that the "old-fashioned" way, by adding my user to the `video` group.
There's a rule shipped by default with udev that changes the group of the DRM

SUBSYSTEM=="drm", KERNEL!="renderD*", GROUP="video"

For multi-user systems, I would probably use something like seatd:


  reply	other threads:[~2022-05-22 16:33 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-11  3:36 dallinjdahl
2022-05-14  3:47 ` Guillermo
2022-05-14 23:45   ` dallinjdahl
2022-05-15  1:52     ` Laurent Bercot
2022-05-15 15:02       ` Guillermo
2022-05-17  4:10         ` Rio Liu
2022-05-15  2:44   ` Samuel Holland
2022-05-22 15:07     ` Guillermo
2022-05-22 16:33       ` Samuel Holland [this message]
2022-05-23 10:05       ` yianiris
2022-05-23 23:40         ` Guillermo
2022-05-27  2:04         ` Steve Litt
2022-05-28  4:07     ` Dallin Dahl
2022-05-28 17:15     ` Dallin Dahl
2022-05-28 19:43       ` Samuel Holland

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).