public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: YUE Daian <sheepduke@gmail.com>
To: Alan Mackenzie <acm@muc.de>, gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Permissions error on starting X.
Date: Wed, 07 Nov 2018 11:59:55 +0800	[thread overview]
Message-ID: <87r2fxv8p0.fsf@work.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <20181103140151.GA5029@ACM>

On 2018-11-03 14:01, Alan Mackenzie <acm@muc.de> wrote:
> Hello, Gentoo.
>
> HEADS UP!!!
>
> 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.
>
> This flag causes the binary to be installed with the setuid file flag,
> which causes it to run as root.
>
> 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.
>
> The matter was fairly intensively discussed in bug #669648 in Gentoo's
> bugzilla.
>
> So - if you get a permissions error whilst trying to start X, setting
> the suid USE flag may well be the solution.
>
> -- 
> Alan Mackenzie (Nuremberg, Germany).

I got the same problem yesterday.

My setup was startx + StumpWM.

I got "setblabla error: cannot open /dev/tty0 (permission denied)".

A possible solution without changing anything unnecessary is to run
startx as "startx -- vt1".

No need to change permission/ownership of anything.
It is just required that the user is in "video" group. No "tty" or
"input" needed.

I presume it is because your user does not have access to TTY other than
its login TTY. So if you log in by "tty1", just start X in "vt1".

Hope that helps somehow.

Danny


  parent reply	other threads:[~2018-11-07  4:00 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
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 ` YUE Daian [this message]
2018-11-09  0:20   ` [gentoo-user] " 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=87r2fxv8p0.fsf@work.i-did-not-set--mail-host-address--so-tickle-me \
    --to=sheepduke@gmail.com \
    --cc=acm@muc.de \
    --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