Github messages for voidlinux
 help / color / mirror / Atom feed
From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: xorg-server: enable privilege-less Xorg 
Date: Sat, 26 Feb 2022 22:08:26 +0100	[thread overview]
Message-ID: <20220226210826.AlLPqySgTMxdRaCaPZDeb-abpcrHQWU76-YmpFDJfqs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35522@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 846 bytes --]

New comment by ahesford on void-packages repository

https://github.com/void-linux/void-packages/pull/35522#issuecomment-1052617335

Comment:
The point of the PR is to leave `xorg-server` in a state that *can* be configured to run rootless without requiring a custom build of the package. The point of my complaints was that
1. I don't want `elogind` to make X work;
2. Adding users to `input` is not generally advisable;
3. Because `xorg-server` works by default (with root privileges) *without* `elogind` and `input` group membership, we can't change `Xwrapper.config` and break people's currently working setups.

I would have hoped that `needs_root_rights = auto` would do the right thing by detecting that `elogind` was not available on my system and decide that root privileges were still needed, but it seems it makes the wrong call.

  parent reply	other threads:[~2022-02-26 21:08 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-10 23:57 [PR PATCH] " ArsenArsen
2022-02-11 10:23 ` dkwo
2022-02-11 11:12 ` ArsenArsen
2022-02-11 11:14 ` ArsenArsen
2022-02-11 13:37 ` dkwo
2022-02-11 13:46 ` ArsenArsen
2022-02-11 13:46 ` [PR PATCH] [Updated] " ArsenArsen
2022-02-11 13:56 ` dkwo
2022-02-11 22:09 ` leahneukirchen
2022-02-11 22:34 ` ArsenArsen
2022-02-11 22:42 ` leahneukirchen
2022-02-22 14:23 ` dkwo
2022-02-22 15:42 ` dkwo
2022-02-26 20:37 ` ahesford
2022-02-26 20:38 ` ahesford
2022-02-26 21:01 ` [PR PATCH] [Updated] " ArsenArsen
2022-02-26 21:04 ` dkwo
2022-02-26 21:08 ` ahesford [this message]
2022-02-26 21:54 ` ArsenArsen
2022-02-26 22:00 ` [PR PATCH] [Updated] " ArsenArsen
2022-02-28 15:07 ` dkwo
2022-02-28 15:21 ` ArsenArsen
2022-06-23  2:15 ` github-actions
2022-07-08  2:14 ` [PR PATCH] [Closed]: " github-actions

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=20220226210826.AlLPqySgTMxdRaCaPZDeb-abpcrHQWU76-YmpFDJfqs@z \
    --to=ahesford@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /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 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).