public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Permissions error on starting X.
Date: Sat, 3 Nov 2018 10:46:15 -0400	[thread overview]
Message-ID: <CAGfcS_nK8gUawcDuFT5UjwLkAP_QbfHg4G3o8UBXN7vdxNuiEw@mail.gmail.com> (raw)
In-Reply-To: <20181103140151.GA5029@ACM>

On Sat, Nov 3, 2018 at 10:01 AM Alan Mackenzie <acm@muc.de> wrote:
>
>
> If you start your X server from the command line with, e.g. startx, you
> now need to set the new(?) suid USE flag for the xorg-server package.
>

Sometimes. I thought this was only required if you're not using KMS.
Is this not the case?

The argument for defaulting it is that you had to both be using a
non-KMS driver, and you had to be running from the command line.  That
is a somewhat uncommon situation.

> The developers, in this instance, failed to raise the ebuild's version
> number from 1.20.3 when making this change, and also didn't notify users
> by a NEWS item, that I can see.

A news item would probably have been a good idea (it almost always
is).  I'm not sure why the ebuild wasn't revisioned.  As far as I can
tell this change does change what gets installed on-disk, and as a
result it is almost always appropriate to revision the ebuild (in this
case to -r1).  The only sorts of changes that generally don't justify
revisioning would be fixes to build systems that don't actually impact
what gets installed (assuming the old version built at all), and which
don't change any dependencies.  In that case there isn't really a
benefit to users to do a rebuild, since the new build will be
identical to the old.

> So - if you get a permissions error whilst trying to start X, setting
> the suid USE flag may well be the solution.

Yup.

-- 
Rich


  reply	other threads:[~2018-11-03 14:46 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-03 14:01 [gentoo-user] Permissions error on starting X Alan Mackenzie
2018-11-03 14:46 ` Rich Freeman [this message]
2018-11-03 23:17 ` Neil Bothwick
2018-11-04 18:39   ` Alarig Le Lay
2018-11-04  1:11 ` [gentoo-user] " Nikos Chantziaras
2018-11-04 10:22   ` Neil Bothwick
2018-11-04 16:04     ` Daniel Frey
2018-11-05 15:30   ` Grant Edwards
2018-11-05 16:27     ` Nikos Chantziaras
2018-11-05 16:35       ` Rich Freeman
2018-11-05 16:43         ` Nikos Chantziaras
2018-11-04  6:20 ` [gentoo-user] " Daniel Frey
2018-11-04 18:33   ` tuxic
2018-11-04 19:18     ` Neil Bothwick
2018-11-05  4:06       ` tuxic
2018-11-05  8:17         ` Neil Bothwick
2018-11-04 20:02     ` Daniel Frey
2018-11-05 15:29 ` [gentoo-user] " Grant Edwards
2018-11-07  3:59 ` [gentoo-user] " YUE Daian
2018-11-09  0:20   ` Hervé Guillemet
2018-11-09  8:49     ` gevisz
2018-11-09  9:19       ` YUE Daian
2018-11-09 10:24         ` Hervé Guillemet
2018-11-08 20:47 ` gevisz
2018-11-08 21:23   ` gevisz

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=CAGfcS_nK8gUawcDuFT5UjwLkAP_QbfHg4G3o8UBXN7vdxNuiEw@mail.gmail.com \
    --to=rich0@gentoo.org \
    --cc=gentoo-user@lists.gentoo.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