[SOLVED] Xorg fails to start under chroot after recent update

jeffcijubu · 2021-04-28 23:27:10

Hello,
I have several chroot containers, all of them broke after the last Xorg update, I had to downgrade to 1.20.10.

Startx output from a test container with the current xorg version:

[ 27774.923] _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root
[ 27774.925] (WW) Failed to open protocol names file lib/xorg/protocol.txt
[ 27774.926] 
X.Org X Server 1.20.11
X Protocol Version 11, Revision 0
[ 27774.929] Build Operating System: Linux Archlinux
[ 27774.930] Current Operating System: Linux cijubu 5.11.15-arch1-2 #1 SMP PREEMPT Sat, 17 Apr 2021 00:22:30 +0000 x86_64
[ 27774.930] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=uuid rw loglevel=3 quiet
[ 27774.932] Build Date: 13 April 2021  03:12:10PM
[ 27774.933]  
[ 27774.934] Current version of pixman: 0.40.0
[ 27774.935] 	Before reporting problems, check [url]http://wiki.x.org[/url]
	to make sure that you have the latest version.
[ 27774.935] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 27774.939] (==) Log file: "/home/jeff/.local/share/xorg/Xorg.0.log", Time: Wed Apr 28 19:37:58 2021
[ 27774.940] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 27774.941] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 27774.941] (==) No Layout section.  Using the first Screen section.
[ 27774.941] (==) No screen section available. Using defaults.
[ 27774.941] (**) |-->Screen "Default Screen Section" (0)
[ 27774.941] (**) |   |-->Monitor "<default monitor>"
[ 27774.941] (==) No monitor specified for screen "Default Screen Section".
	Using a default monitor configuration.
[ 27774.941] (==) Automatically adding devices
[ 27774.941] (==) Automatically enabling devices
[ 27774.941] (==) Automatically adding GPU devices
[ 27774.941] (==) Automatically binding GPU devices
[ 27774.941] (==) Max clients allowed: 256, resource mask: 0x1fffff
[ 27774.941] (WW) The directory "/usr/share/fonts/OTF" does not exist.
[ 27774.941] 	Entry deleted from font path.
[ 27774.941] (WW) The directory "/usr/share/fonts/Type1" does not exist.
[ 27774.941] 	Entry deleted from font path.
[ 27774.941] (WW) The directory "/usr/share/fonts/100dpi" does not exist.
[ 27774.941] 	Entry deleted from font path.
[ 27774.941] (WW) The directory "/usr/share/fonts/75dpi" does not exist.
[ 27774.941] 	Entry deleted from font path.
[ 27774.941] (==) FontPath set to:
	/usr/share/fonts/misc,
	/usr/share/fonts/TTF
[ 27774.941] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 27774.941] (II) The server relies on udev to provide the list of input devices.
	If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 27774.941] (II) Module ABI versions:
[ 27774.941] 	X.Org ANSI C Emulation: 0.4
[ 27774.941] 	X.Org Video Driver: 24.1
[ 27774.941] 	X.Org XInput driver : 24.1
[ 27774.941] 	X.Org Server Extension : 10.0
[ 27774.942] (++) using VT number 5

[ 27774.942] (EE) systemd-logind: failed to get session: PID 249 does not belong to any known session
[ 27774.942] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 27774.944] (--) PCI:*(0@0:2:0) 8086:5916:1028:0767 rev 2, Mem @ 0xd0000000/16777216, 0xc0000000/268435456, I/O @ 0x0000f000/64, BIOS @ 0x????????/131072
[ 27774.944] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 27774.944] (II) LoadModule: "glx"
[ 27774.944] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 27774.945] (II) Module glx: vendor="X.Org Foundation"
[ 27774.945] 	compiled for 1.20.11, module version = 1.0.0
[ 27774.945] 	ABI class: X.Org Server Extension, version 10.0
[ 27774.945] (==) Matched intel as autoconfigured driver 0
[ 27774.945] (==) Matched modesetting as autoconfigured driver 1
[ 27774.945] (==) Matched fbdev as autoconfigured driver 2
[ 27774.945] (==) Matched vesa as autoconfigured driver 3
[ 27774.945] (==) Assigned the driver to the xf86ConfigLayout
[ 27774.945] (II) LoadModule: "intel"
[ 27774.945] (WW) Warning, couldn't open module intel
[ 27774.945] (EE) Failed to load module "intel" (module does not exist, 0)
[ 27774.945] (II) LoadModule: "modesetting"
[ 27774.945] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[ 27774.946] (II) Module modesetting: vendor="X.Org Foundation"
[ 27774.946] 	compiled for 1.20.11, module version = 1.20.11
[ 27774.946] 	Module class: X.Org Video Driver
[ 27774.946] 	ABI class: X.Org Video Driver, version 24.1
[ 27774.946] (II) LoadModule: "fbdev"
[ 27774.946] (WW) Warning, couldn't open module fbdev
[ 27774.946] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 27774.946] (II) LoadModule: "vesa"
[ 27774.946] (WW) Warning, couldn't open module vesa
[ 27774.946] (EE) Failed to load module "vesa" (module does not exist, 0)
[ 27774.946] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 27774.946] (EE) 
Fatal server error:
[ 27774.948] (EE) xf86OpenConsole: Cannot open virtual console 5 (Permission denied)
[ 27774.948] (EE) 
[ 27774.949] (EE) 
Please consult the The X.Org Foundation support 
	at [url]http://wiki.x.org[/url]
 for help. 
[ 27774.953] (EE) Please also check the log file at "/home/jeff/.local/share/xorg/Xorg.0.log" for additional information.
[ 27774.954] (EE) 
[ 27774.955] (WW) xf86CloseConsole: KDSETMODE failed: Bad file descriptor
[ 27774.955] (WW) xf86CloseConsole: VT_GETMODE failed: Bad file descriptor
[ 27774.955] (EE) Server terminated with error (1). Closing log file.

Once a while I get issues like that, but this is the first time that I couldn't find a solution.
I would be glad if you could help me.

Last edited by jeffcijubu (2021-04-29 20:44:40)

loqs · 2021-04-28 23:49:33

https://bugs.archlinux.org/task/70469 ?

jeffcijubu · 2021-04-29 00:31:21

loqs wrote:

https://bugs.archlinux.org/task/70469 ?

Trying to run a root X from a normal user with X on a different virtual terminal fails with

The only differences are the first line in the log and the fact that I'm using chroot.

[ 27774.923] _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root

The Xwrapper.config is the same, after adding the SUID with 'sudo chmod u+s /etc/X11/Xwrapper.confing' the errors persist.
I will follow your comment in the bug with a clean chroot.

loqs · 2021-04-29 00:45:01

If fixing the suid did not resolve the issue then the cause is different.

seth · 2021-04-29 06:40:33

sudo chmod u+s /etc/X11/Xwrapper.confing

Typo aside, that's the wrong file to be SUID'…

2ManyDogs · 2021-04-29 12:18:21

Welcome to the forum. Please use [ code ] tags (not quote tags) when posting output. This makes the output easier to read and provides a scroll box for long output.

https://gitlab.archlinux.org/archlinux/ … s-and-code
https://bbs.archlinux.org/help.php#bbcode

jeffcijubu · 2021-04-29 20:42:16

seth wrote:

sudo chmod u+s /etc/X11/Xwrapper.confing
Typo aside, that's the wrong file to be SUID'…

I'm feeling so dumb right now.

teika · 2024-09-07 04:14:04

Sorry for using this thread, but a web search easily hits this.

 _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root

This line appears always (if the system is systemd), i.e. even when there's no error. It is a red herring.

Lone_Wolf · 2024-09-07 14:49:29

Closing this old topic.

Arch Linux

#1 2021-04-28 23:27:10

[SOLVED] Xorg fails to start under chroot after recent update

#2 2021-04-28 23:49:33

Re: [SOLVED] Xorg fails to start under chroot after recent update

#3 2021-04-29 00:31:21

Re: [SOLVED] Xorg fails to start under chroot after recent update

#4 2021-04-29 00:45:01

Re: [SOLVED] Xorg fails to start under chroot after recent update

#5 2021-04-29 06:40:33

Re: [SOLVED] Xorg fails to start under chroot after recent update

#6 2021-04-29 12:18:21

Re: [SOLVED] Xorg fails to start under chroot after recent update

#7 2021-04-29 20:42:16

Re: [SOLVED] Xorg fails to start under chroot after recent update

#8 2024-09-07 04:14:04

Re: [SOLVED] Xorg fails to start under chroot after recent update

#9 2024-09-07 14:49:29

Re: [SOLVED] Xorg fails to start under chroot after recent update

Board footer