Debian Bug report logs - #856351
xinit does not run as normal user but as root only

Reply or subscribe to this bug.

Display info messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Harald Dunkel <harald.dunkel@aixigo.de>

To: submit@bugs.debian.org

Subject: parse_vt_settings: Cannot open /dev/tty0 (Permission denied)

Date: Tue, 28 Feb 2017 12:40:51 +0100

[Message part 1 (text/plain, inline)]

Package: xinit
Version: 1.3.4-3

running "xinit -- :4" on console /dev/tty1 fails with


X.Org X Server 1.19.1
Release Date: 2017-01-11
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian
Current Operating System: Linux dpcl082.ac.aixigo.de 4.9.13 #1 SMP Sun Feb 26 17:12:37 CET 2017 x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.9.13 root=UUID=eb332fc7-97c7-4ebd-b82f-24e569770822 ro nfs.nfs4_unique_id=e25a4169-41fe-4bc3-a604-1f1e0cd015b2 swapaccount=1 cgroup_enable=memory vsyscall=emulate quiet
Build Date: 20 January 2017  02:50:48AM
xorg-server 2:1.19.1-4 (https://www.debian.org/support)
Current version of pixman: 0.34.0
	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/home/user/.local/share/xorg/Xorg.4.log", Time: Tue Feb 28 11:09:36 2017
(==) Using config file: "/etc/X11/xorg.conf"
(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(EE)
Fatal server error:
(EE) parse_vt_settings: Cannot open /dev/tty0 (Permission denied)
(EE)
(EE)
Please consult the The X.Org Foundation support
	 at http://wiki.x.org
 for help.
(EE) Please also check the log file at "/home/user/.local/share/xorg/Xorg.4.log" for additional information.
(EE)
(EE) Server terminated with error (1). Closing log file.
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error


UID != 0, of course.
"startx -- :4" works as expected. Wonder why xinit tries /dev/tty0
instead of /dev/tty1?

Please fix for Stretch.


Thanx very much
Harri

[Xorg.4.log (text/x-log, attachment)]

Message #10 received at 856351@bugs.debian.org (full text, mbox, reply):

From: Harald Dunkel <harri@afaics.de>

To: 856351@bugs.debian.org

Subject: Re: parse_vt_settings: Cannot open /dev/tty0 (Permission denied)

Date: Mon, 22 May 2017 20:43:28 +0200

Any news on this?

Motivated by #862706 I kicked out my nvidia graphics card in my PC
at home and gave Intel graphics a try, just to find out that I am
struck by this problem again. Even worse, startx doesn't work, either.
Installing and reinstalling xserver-xorg-legacy didn't help :-(.

Sorry to say, but my PC in the office (Testing) with proprietary
nvidia driver installed is not affected.


Regards
Harri

Message #15 received at 856351@bugs.debian.org (full text, mbox, reply):

From: Jörgen Grahn <grahn@snipabacken.se>

To: 856351@bugs.debian.org

Subject: Re: parse_vt_settings: Permission denied <Cannotopen/dev/tty0>

Date: Mon, 3 Jul 2017 13:38:41 +0200

I got bitten by #856351 after upgrading to Debian 9 yesterday. I want
to be able to boot up, log in without any fancy login manager (not to
mention Desktop Environments), and then run 'startx' and go X11.  I
need to do this repeatedly, on different virtual consoles -- so I can
have simultaneous graphical logins.  Or rather, so I can have a login
and my Mom can have another one.

Anyway, what worked for me was to add

  needs_root_rights=yes

to /etc/X11/Xwrapper.config, as described in the corresponding man
page.  I haven't checked why this is needed, with my particular
hardware. (And I haven't verified that it fits my two-user scenario
above; it would be sad and a serious regression if it didn't.)

/Jörgen

-- 
  // Jörgen Grahn                  | mot du jour: Terylen             
\X/ <grahn@snipabacken.se>         |                                  

Message #20 received at 856351@bugs.debian.org (full text, mbox, reply):

From: Jörgen Grahn <grahn+debian@snipabacken.se>

To: 856351@bugs.debian.org

Subject: Re: parse_vt_settings: Permission denied <Cannotopen/dev/tty0>

Date: Wed, 26 Jul 2017 13:23:13 +0200

On Mon Jul  3 13:38:41 2017, grahn@snipabacken.se wrote:
> I got bitten by #856351 after upgrading to Debian 9 yesterday. I want
> to be able to boot up, log in without any fancy login manager (not to
> mention Desktop Environments), and then run 'startx' and go X11.  I
> need to do this repeatedly, on different virtual consoles -- so I can
> have simultaneous graphical logins.  Or rather, so I can have a login
> and my Mom can have another one.
> 
> Anyway, what worked for me was to add
> 
>   needs_root_rights=yes
> 
> to /etc/X11/Xwrapper.config, as described in the corresponding man
> page.  I haven't checked why this is needed, with my particular
> hardware. (And I haven't verified that it fits my two-user scenario
> above; it would be sad and a serious regression if it didn't.)

On the other hand, a second clean install of Debian 9 on identical
hardware did /not/ need /etc/X11/Xwrapper.config modification.

Group membership?  Some extra package installed?  I didn't have time
to investigate, and I don't easily have access to that second
installation.

/Jörgen

Message #25 received at 856351@bugs.debian.org (full text, mbox, reply):

From: Josip Rodin <joy@debbugs.entuzijast.net>

To: 856351@bugs.debian.org

Subject: ditto from screen

Date: Sat, 17 Feb 2018 21:11:44 +0100

Hi,

I saw this error message when I accidentally ran startx on tty1 from a
screen(1) session.

For some reason, there's a root-owned /dev/tty0 on the machine.
Should there be one? I certainly don't seem to see it - I have
six VTs set up, and e.g. /dev/tty1 where I'm running that startx
is owned by my user.

The only non-comment content of Xwrapper.config is "allowed_users=console"

man Xwrapper.config fails to run, oddly enough

-- 
     2. That which causes joy or happiness.

Send a report that this bug log contains spam.