X server not running [SOLVED]

Shail Murtaza

New Member
Joined
Jun 13, 2022
Messages
25
Reaction score
4
Credits
202
Hi!
I'm using AntiX 19.5 Core which is debian based distro without GUI in Virtual Box. You just get tty at startup in core version of AntiX Linux

System
Code:
Host: antix1
Kernal: 4.9.0-294-antix.1-amd64-smp
Arch: x86_64
Bits: 64
console: tty1
Distro: antix-19.5_x64-core Wobblies 24 January, 2022

I installed xserver including xfce, lightdm and xinit using
Bash:
apt install xserver-xorg x11-xserver-utils xfonts-base x11-utils lightdm lightdm-gtk-greeter xfce4 xfce4-goodies xinit -y

After restart lightdm started, I logged in as normal user without root and without any problem and everything was working perfectly.
But didn't wanted to use any Login Manager as I prefer to run startx whenever I wanted to use xfce. So I removed lightdm and lightdm-gtk-greeter using apt remove.

But after reboot nothing was working when I enter startx. I was getting errors
But if i run startx as root then it works perfectly. Then I guess these errors have something to do with permissions which lightdm was doing automatically

"$ xinit" output
Capture.PNG
XORG Log File after running startx
Code:
[  2699.852]
X.Org X Server 1.20.4
X Protocol Version 11, Revision 0
[  2699.852] Build Operating System: Linux 4.9.0-294-antix.1-amd64-smp x86_64 Debian
[  2699.852] Current Operating System: Linux antix1 4.9.0-294-antix.1-amd64-smp #1 SMP PREEMPT Fri Dec 24 18:04:18 EET 2021 x86_64
[  2699.852] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.9.0-294-antix.1-amd64-smp root=UUID=371294ef-11dc-4c99-8cbc-f15d85475cda ro quiet
[  2699.854] Build Date: 05 January 2022  01:24:15PM
[  2699.854] xorg-server 2:1.20.4-1+deb10u4.0nosystemd1 (https://www.debian.org/support)
[  2699.854] Current version of pixman: 0.36.0
[  2699.854]     Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
[  2699.854] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[  2699.856] (==) Log file: "/home/shail/.local/share/xorg/Xorg.0.log", Time: Mon Jun 27 19:52:51 2022
[  2699.856] (==) Using config file: "/etc/X11/xorg.conf"
[  2699.856] (==) Using config directory: "/etc/X11/xorg.conf.d"
[  2699.856] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[  2699.856] (==) No Layout section.  Using the first Screen section.
[  2699.856] (==) No screen section available. Using defaults.
[  2699.856] (**) |-->Screen "Default Screen Section" (0)
[  2699.856] (**) |   |-->Monitor "<default monitor>"
[  2699.856] (==) No monitor specified for screen "Default Screen Section".
    Using a default monitor configuration.
[  2699.856] (==) Automatically adding devices
[  2699.856] (==) Automatically enabling devices
[  2699.856] (==) Automatically adding GPU devices
[  2699.856] (==) Max clients allowed: 256, resource mask: 0x1fffff
[  2699.856] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[  2699.856]     Entry deleted from font path.
[  2699.856] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist.
[  2699.856]     Entry deleted from font path.
[  2699.856] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
[  2699.856]     Entry deleted from font path.
[  2699.856] (WW) The directory "/usr/share/fonts/X11/Type1" does not exist.
[  2699.856]     Entry deleted from font path.
[  2699.856] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist.
[  2699.856]     Entry deleted from font path.
[  2699.856] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist.
[  2699.856]     Entry deleted from font path.
[  2699.856] (==) FontPath set to:
    /usr/share/fonts/X11/misc,
    built-ins
[  2699.856] (==) ModulePath set to "/usr/lib/xorg/modules"
[  2699.856] (II) The server relies on udev to provide the list of input devices.
    If no devices become available, reconfigure udev or disable AutoAddDevices.
[  2699.856] (II) Loader magic: 0x55a46d042d80
[  2699.856] (II) Module ABI versions:
[  2699.856]     X.Org ANSI C Emulation: 0.4
[  2699.856]     X.Org Video Driver: 24.0
[  2699.856]     X.Org XInput driver : 24.1
[  2699.856]     X.Org Server Extension : 10.0
[  2699.864] (--) PCI:*([email protected]:2:0) 15ad:0405:15ad:0405 rev 0, Mem @ 0xe0000000/16777216, 0xf0000000/2097152, I/O @ 0x0000d010/16, BIOS @ 0x????????/131072
[  2699.864] (II) LoadModule: "glx"
[  2699.864] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[  2699.865] (II) Module glx: vendor="X.Org Foundation"
[  2699.865]     compiled for 1.20.4, module version = 1.0.0
[  2699.865]     ABI class: X.Org Server Extension, version 10.0
[  2699.865] (==) Matched vmware as autoconfigured driver 0
[  2699.865] (==) Matched modesetting as autoconfigured driver 1
[  2699.865] (==) Matched fbdev as autoconfigured driver 2
[  2699.865] (==) Matched vesa as autoconfigured driver 3
[  2699.865] (==) Assigned the driver to the xf86ConfigLayout
[  2699.865] (II) LoadModule: "vmware"
[  2699.865] (II) Loading /usr/lib/xorg/modules/drivers/vmware_drv.so
[  2699.887] (II) Module vmware: vendor="X.Org Foundation"
[  2699.887]     compiled for 1.20.0, module version = 13.3.0
[  2699.887]     Module class: X.Org Video Driver
[  2699.887]     ABI class: X.Org Video Driver, version 24.0
[  2699.887] (II) LoadModule: "modesetting"
[  2699.887] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[  2699.887] (II) Module modesetting: vendor="X.Org Foundation"
[  2699.887]     compiled for 1.20.4, module version = 1.20.4
[  2699.887]     Module class: X.Org Video Driver
[  2699.887]     ABI class: X.Org Video Driver, version 24.0
[  2699.887] (II) LoadModule: "fbdev"
[  2699.888] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[  2699.888] (II) Module fbdev: vendor="X.Org Foundation"
[  2699.888]     compiled for 1.20.0, module version = 0.5.0
[  2699.888]     Module class: X.Org Video Driver
[  2699.888]     ABI class: X.Org Video Driver, version 24.0
[  2699.888] (II) LoadModule: "vesa"
[  2699.888] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[  2699.888] (II) Module vesa: vendor="X.Org Foundation"
[  2699.888]     compiled for 1.20.1, module version = 2.4.0
[  2699.888]     Module class: X.Org Video Driver
[  2699.888]     ABI class: X.Org Video Driver, version 24.0
[  2699.888] (II) vmware: driver for VMware SVGA: vmware0405, vmware0710
[  2699.888] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[  2699.888] (II) FBDEV: driver for framebuffer: fbdev
[  2699.888] (II) VESA: driver for VESA chipsets: vesa
[  2699.888] (++) using VT number 1

[  2699.897] xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)
[  2699.897] (WW) Falling back to old probe method for modesetting
[  2699.897] (EE) open /dev/dri/card0: No such file or directory
[  2699.897] (WW) Falling back to old probe method for fbdev
[  2699.897] (II) Loading sub module "fbdevhw"
[  2699.897] (II) LoadModule: "fbdevhw"
[  2699.897] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[  2699.898] (II) Module fbdevhw: vendor="X.Org Foundation"
[  2699.898]     compiled for 1.20.4, module version = 0.0.2
[  2699.898]     ABI class: X.Org Video Driver, version 24.0
[  2699.898] (EE) open /dev/fb0: No such file or directory
[  2699.898] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[  2699.898] (II) vmware(0): Creating default Display subsection in Screen section
    "Default Screen Section" for depth/fbbpp 24/32
[  2700.210] (EE) vmware(0): Failed to open drm.
[  2700.210] (WW) vmware(0): Disabling 3D support.
[  2700.210] (WW) vmware(0): Disabling Render Acceleration.
[  2700.210] (WW) vmware(0): Disabling RandR12+ support.
[  2700.210] (--) vmware(0): VMware SVGA regs at (0xd010, 0xd011)
[  2700.210] (II) Loading sub module "vgahw"
[  2700.210] (II) LoadModule: "vgahw"
[  2700.210] (II) Loading /usr/lib/xorg/modules/libvgahw.so
[  2700.210] (II) Module vgahw: vendor="X.Org Foundation"
[  2700.210]     compiled for 1.20.4, module version = 0.1.0
[  2700.210]     ABI class: X.Org Video Driver, version 24.0
[  2700.210] (EE)
[  2700.210] (EE) Backtrace:
[  2700.211] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x55a46cfb5419]
[  2700.211] (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x50) [0x7fe5e0ff677f]
[  2700.211] (EE) 2: /lib/x86_64-linux-gnu/libpciaccess.so.0 (pci_io_write8+0x3) [0x7fe5e1ac79e3]
[  2700.212] (EE) 3: /usr/lib/xorg/modules/libvgahw.so (vgaHWSaveColormap+0x46) [0x7fe5dbfb7856]
[  2700.212] (EE) 4: /usr/lib/xorg/modules/libvgahw.so (vgaHWSave+0x2d) [0x7fe5dbfb994d]
[  2700.212] (EE) 5: /usr/lib/xorg/modules/drivers/vmware_drv.so (_init+0x2da2) [0x7fe5e0203322]
[  2700.212] (EE) 6: /usr/lib/xorg/Xorg (InitOutput+0x9b8) [0x55a46ce98618]
[  2700.212] (EE) 7: /usr/lib/xorg/Xorg (InitFonts+0x1cf) [0x55a46ce5b6cf]
[  2700.213] (EE) 8: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xeb) [0x7fe5e0e4809b]
[  2700.213] (EE) 9: /usr/lib/xorg/Xorg (_start+0x2a) [0x55a46ce4556a]
[  2700.213] (EE)
[  2700.213] (EE) Segmentation fault at address 0x8
[  2700.213] (EE)
Fatal server error:
[  2700.213] (EE) Caught signal 11 (Segmentation fault). Server aborting
[  2700.213] (EE)
[  2700.213] (EE)
Please consult the The X.Org Foundation support
     at http://wiki.x.org
 for help.
[  2700.213] (EE) Please also check the log file at "/home/shail/.local/share/xorg/Xorg.0.log" for additional information.
[  2700.213] (EE)
[  2700.218] (EE) Server terminated with error (1). Closing log file.

Can anyone please help me?
 


dos2unix

Well-Known Member
Joined
May 3, 2019
Messages
1,472
Reaction score
1,074
Credits
9,160
Is this a systemd distro?

Try this as root

systemctl set-default graphical.target


I have to admit, I find it a little ironic,you are trying to run X in a distro called "anti"X! :)
 

osprey

Active Member
Joined
Apr 15, 2022
Messages
131
Reaction score
71
Credits
1,180
Can't help with the virtual box, but to start your sysVinit system in text mode, the usual way is to place a 3 in the initdefault line in /etc/inittab:
Code:
id:3:initdefault:
and reboot. Check the notes in the file.

The segmentation fault in the xorg log file is an ominous indicator. It may mean some code is accessing memory it shouldn't.
 
OP
Shail Murtaza

Shail Murtaza

New Member
Joined
Jun 13, 2022
Messages
25
Reaction score
4
Credits
202
Can't help with the virtual box, but to start your sysVinit system in text mode, the usual way is to place a 3 in the initdefault line in /etc/inittab:
Code:
id:3:initdefault:
and reboot. Check the notes in the file.
Thanks for your reply
That didn't worked
in file there was 5. I replaced it with 3. After reboot gives me same error after execution of startx.
I cannot understand. Why it was working with lightdm but not with startx(xinit)
 

osprey

Active Member
Joined
Apr 15, 2022
Messages
131
Reaction score
71
Credits
1,180
what is it with virtual box about which you can't help?
Of course if I could help, I would, but unfortunately I have so little experience with virtual box itself that I am of no real use there.

I replaced it with 3. After reboot gives me same error after execution of startx.
I gather from this statement that the virtual computer did boot to runlevel 3, and showed a text prompt, at which you ran "startx" which failed to bring up X.

I see two problems, the segmentation fault and:
cannot open /dev/tty0 (Permission denied)

I cannot say whether or not they are interacting with each other.

I'd try the permission issue first.
Here are the default permissions which work on my debian system for tty0
Code:
[[email protected] ~]$ ll /dev/tty0
crw--w---- 1 root tty 4, 0 Jun 28 08:09 /dev/tty0
You should have something at least as permissive as that. X should by default have permission to write to the tty.

To check out whether X will actually run, I would create a file: .xinitrc in my home directory with the contents:
Code:
exec xterm
If you don't have xterm on your system, replace "xterm" with any other terminal.

Then I would boot to text prompt and run the following command:
Code:
xinit /home/<username>/.xinitrc -- /usr/bin/X :0 vt1
where you insert your username for <username>.

This command instructs X to run, check out the .xinitrc file and start whatever is in there, which in this case is the terminal, xterm, and start it on the first virtual terminal.

If X runs and there's an xterm on screen, you can start up a window manager like openbox or a desktop environment from that xterm with some relevant command. If X fails, then there's a deeper problem I think.
 
OP
Shail Murtaza

Shail Murtaza

New Member
Joined
Jun 13, 2022
Messages
25
Reaction score
4
Credits
202
You should have something at least as permissive as that. X should by default have permission to write to the tty.
Code:
$ ll /dev/tty0
crw--w---- 1 root tty 4, 0 Jun 28 08:09 /dev/tty0
Permissions are same as yours


To check out whether X will actually run, I would create a file: .xinitrc in my home directory with the contents:
Code:
exec xterm
If you don't have xterm on your system, replace "xterm" with any other terminal.

Then I would boot to text prompt and run the following command:
Code:
xinit /home/<username>/.xinitrc -- /usr/bin/X :0 vt1
where you insert your username for <username>.
It is not working. But with $ sudo xinit /home/<username>/.xinitrc -- /usr/bin/X :0 vt1 it opened xterm
Even xfce is working fine with root user
 
OP
Shail Murtaza

Shail Murtaza

New Member
Joined
Jun 13, 2022
Messages
25
Reaction score
4
Credits
202
parse_vt_settings: Cannot Open /dev/tty0 is usually caused by no permissions

add user to input, video and tty groups
chown user:users /dev/tty0
Thanks for your help
I ran
Code:
sudo chown user:users /dev/tty0
sudo useradd -g video user
sudo useradd -g input user

That didn't worked but now error is changed
Code:
Fatal server error:
(EE) xf86OpenConsole: Cannot open virtual console 7 (Permission denied)

I guess i have progressed lol!



After running
Code:
sudo chown user:users /dev/tty7
I think it got even worse
Now this is the error
Code:
Fatal server error:
(EE) Caught signal 11 (Segmentation fault). Server aborting
 
Last edited:

Tolkem

Well-Known Member
Joined
Jan 6, 2019
Messages
1,466
Reaction score
1,185
Credits
10,635
As others said, antiX use SysV, and for the login session it uses elogind, while systemd uses logind. https://github.com/antiX-Linux/elogind-antix/blob/master/README
Since you're using the core version, I suggest you check whether it is installed, and if it's not, install it and try again. Tho, I would recommend that you create a new VM and start over, to get everything in place. Also, it's always a good idea to create a snapshot and work on that, instead of the main image, that way, should anything go wrong, you can just delete the snapshot and start again without having to recreate the VM. :)
 
Last edited:
OP
Shail Murtaza

Shail Murtaza

New Member
Joined
Jun 13, 2022
Messages
25
Reaction score
4
Credits
202
Now try
Code:
sudo Xorg -configure
startx
After running sudo Xorg -configure
I'm getting this error again.
Code:
cannot open /dev/tty0 Permission denied
I tried to give permission user to access tty0 but after running
Code:
sudo Xorg -configure
again
I'm getting permission denied error again

I have tried many times but not working. I'm ending up on segmentation fault again and again
 

Tolkem

Well-Known Member
Joined
Jan 6, 2019
Messages
1,466
Reaction score
1,185
Credits
10,635
After running sudo Xorg -configure
I'm getting this error again.
Code:
cannot open /dev/tty0 Permission denied
I tried to give permission user to access tty0 but after running
Code:
sudo Xorg -configure
again
I'm getting permission denied error again

I have tried many times but not working. I'm ending up on segmentation fault again and again
Have you tried asking at antiX forum?
antiX's creator himself, anticapitalista, answers questions there, so with a bit a luck he might have the answer you're looking for. :)
 
OP
Shail Murtaza

Shail Murtaza

New Member
Joined
Jun 13, 2022
Messages
25
Reaction score
4
Credits
202
Have you tried asking at antiX forum?
antiX's creator himself, anticapitalista, answers questions there, so with a bit a luck he might have the answer you're looking for. :)
Well! I tried to login there but they have some issues with their website. I'm unable to create an account.
But I will try on MX Linux forum

lol! Now their forum is working fine
I will ask for help there
 
Last edited:
OP
Shail Murtaza

Shail Murtaza

New Member
Joined
Jun 13, 2022
Messages
25
Reaction score
4
Credits
202
After banging my head at google many times I finally found the solution

Code:
apt install xserver-xorg-legacy
I does not really know why installing xserver-xorg-legacy works but now startx is working without any Login Manager and root user.

Can anyone please tell me why it is working now? What it has to do with segmentation fault and permissions?
 

Fanboi

Well-Known Member
Joined
Apr 16, 2021
Messages
499
Reaction score
406
Credits
6,114
After banging my head at google many times I finally found the solution

Code:
apt install xserver-xorg-legacy
I does not really know why installing xserver-xorg-legacy works but now startx is working without any Login Manager and root user.

Can anyone please tell me why it is working now? What it has to do with segmentation fault and permissions?
Probably your VM was "emulating" a legacy/exotic video driver. "xserver-xorg-legacy" essentially lets you run whichever tty you're gonna run X on as if root was running it (setuid). This is different than simply running as root, a'la su -c, sudo, or doas (did I miss one, lol) from a security POV. Explaining it really in lay terms would be saying: instead of you acting as the boss, you're asking Ursula in accounts to do something and she is treating you as if you were the boss... That explanation was garbage. You'd be better off letting Google explain setuid...

Anyway, the "driver" is probably only designed for single user mode. The segfault is caused by this somewhere along the pipeline.
 
$100 Digital Ocean Credit
Get a free VM to test out Linux!

Linux.org Hosting Donations
Consider making a donation

Members online


Latest posts

Top