The officially official Devuan Forum!

You are not logged in.

#1 2024-01-31 19:44:43

shimarin
Member
Registered: 2024-01-31
Posts: 7  

StartX doesn't work after a fresh install (segmentation fault 0x20)

After a fresh install of devuan with sysvinit i installed xorg, xmobar, xmonad, neofetch, intel microcode, ranger and performed an apt update but i get an error every time i type startx (server not responding)

 [   341.315] 
X.Org X Server 1.21.1.7
X Protocol Version 11, Revision 0
[   341.323] Current Operating System: Linux yurucamp 6.1.0-17-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.69-1 (2023-12-30) x86_64
[   341.323] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.1.0-17-amd64 root=UUID=e8dcfe92-ab37-4051-a3ec-0f18b58ee588 ro quiet
[   341.327] xorg-server 2:21.1.7-3+deb12u2devuan1 (https://www.devuan.org/os/community) 
[   341.330] Current version of pixman: 0.42.2
[   341.334] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[   341.334] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[   341.344] (==) Log file: "/home/rin/.local/share/xorg/Xorg.0.log", Time: Wed Jan 31 20:23:31 2024
[   341.346] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[   341.346] (==) No Layout section.  Using the first Screen section.
[   341.346] (==) No screen section available. Using defaults.
[   341.347] (**) |-->Screen "Default Screen Section" (0)
[   341.347] (**) |   |-->Monitor "<default monitor>"
[   341.347] (==) No monitor specified for screen "Default Screen Section".
	Using a default monitor configuration.
[   341.347] (==) Automatically adding devices
[   341.347] (==) Automatically enabling devices
[   341.347] (==) Automatically adding GPU devices
[   341.347] (==) Automatically binding GPU devices
[   341.347] (==) Max clients allowed: 256, resource mask: 0x1fffff
[   341.347] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[   341.347] 	Entry deleted from font path.
[   341.347] (==) FontPath set to:
	/usr/share/fonts/X11/misc,
	/usr/share/fonts/X11/100dpi/:unscaled,
	/usr/share/fonts/X11/75dpi/:unscaled,
	/usr/share/fonts/X11/Type1,
	/usr/share/fonts/X11/100dpi,
	/usr/share/fonts/X11/75dpi,
	built-ins
[   341.347] (==) ModulePath set to "/usr/lib/xorg/modules"
[   341.347] (II) The server relies on udev to provide the list of input devices.
	If no devices become available, reconfigure udev or disable AutoAddDevices.
[   341.347] (II) Loader magic: 0x55baa775dea0
[   341.347] (II) Module ABI versions:
[   341.347] 	X.Org ANSI C Emulation: 0.4
[   341.347] 	X.Org Video Driver: 25.2
[   341.347] 	X.Org XInput driver : 24.4
[   341.347] 	X.Org Server Extension : 10.0
[   341.347] (++) using VT number 1

[   341.347] (II) seatd_libseat init
[   341.347] (II) [libseat/libseat.c:73] Seat opened with backend 'seatd'
[   341.347] (II) [libseat/backend/seatd.c:212] Enabling seat
[   341.347] (II) seatd_libseat enable
[   341.347] (II) seatd_libseat handled 2 events
[   341.447] (II) seatd_libseat client activated
[   341.448] (II) xfree86: Adding drm device (/dev/dri/card0)
[   341.448] (II) Platform probe for /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0
[   341.448] (II) seatd_libseat try open graphics /dev/dri/card0
[   341.448] (II) seatd_libseat opened graphics: /dev/dri/card0 (1:12)
[   341.459] (--) PCI:*(1@0:0:0) 10de:1b80:3842:6686 rev 161, Mem @ 0xee000000/16777216, 0xd0000000/268435456, 0xe0000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/131072
[   341.459] (II) LoadModule: "glx"
[   341.459] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[   341.462] (II) Module glx: vendor="X.Org Foundation"
[   341.462] 	compiled for 1.21.1.7, module version = 1.0.0
[   341.462] 	ABI class: X.Org Server Extension, version 10.0
[   341.601] (==) Matched modesetting as autoconfigured driver 0
[   341.601] (==) Matched fbdev as autoconfigured driver 1
[   341.601] (==) Matched vesa as autoconfigured driver 2
[   341.601] (==) Assigned the driver to the xf86ConfigLayout
[   341.601] (II) LoadModule: "modesetting"
[   341.602] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[   341.602] (II) Module modesetting: vendor="X.Org Foundation"
[   341.602] 	compiled for 1.21.1.7, module version = 1.21.1
[   341.602] 	Module class: X.Org Video Driver
[   341.602] 	ABI class: X.Org Video Driver, version 25.2
[   341.602] (II) LoadModule: "fbdev"
[   341.602] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[   341.602] (II) Module fbdev: vendor="X.Org Foundation"
[   341.602] 	compiled for 1.21.1.3, module version = 0.5.0
[   341.602] 	Module class: X.Org Video Driver
[   341.603] 	ABI class: X.Org Video Driver, version 25.2
[   341.603] (II) LoadModule: "vesa"
[   341.603] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[   341.603] (II) Module vesa: vendor="X.Org Foundation"
[   341.603] 	compiled for 1.21.1.3, module version = 2.5.0
[   341.603] 	Module class: X.Org Video Driver
[   341.603] 	ABI class: X.Org Video Driver, version 25.2
[   341.603] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[   341.603] (II) FBDEV: driver for framebuffer: fbdev
[   341.603] (II) VESA: driver for VESA chipsets: vesa
[   341.603] xf86EnableIO: failed to enable I/O ports 0000-03ff (Operation not permitted)
[   341.603] (II) modeset(0): using drv /dev/dri/card0
[   341.603] (WW) Falling back to old probe method for fbdev
[   341.603] (II) Loading sub module "fbdevhw"
[   341.603] (II) LoadModule: "fbdevhw"
[   341.603] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[   341.604] (II) Module fbdevhw: vendor="X.Org Foundation"
[   341.604] 	compiled for 1.21.1.7, module version = 0.0.2
[   341.604] 	ABI class: X.Org Video Driver, version 25.2
[   341.604] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[   341.604] (II) modeset(0): Creating default Display subsection in Screen section
	"Default Screen Section" for depth/fbbpp 24/32
[   341.604] (==) modeset(0): Depth 24, (==) framebuffer bpp 32
[   341.604] (==) modeset(0): RGB weight 888
[   341.604] (==) modeset(0): Default visual is TrueColor
[   341.604] (II) Loading sub module "glamoregl"
[   341.604] (II) LoadModule: "glamoregl"
[   341.605] (II) Loading /usr/lib/xorg/modules/libglamoregl.so
[   341.614] (II) Module glamoregl: vendor="X.Org Foundation"
[   341.614] 	compiled for 1.21.1.7, module version = 1.0.1
[   341.614] 	ABI class: X.Org ANSI C Emulation, version 0.4
[   341.652] (EE) 
[   341.652] (EE) Backtrace:
[   341.652] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x55baa76d21d9]
[   341.653] (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x40) [0x7f248b05b050]
[   341.653] (EE) 2: /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so (nouveau_drm_screen_create+0x4406c) [0x7f248916c2fc]
[   341.653] (EE) 3: /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so (nouveau_drm_screen_create+0x1e4c9) [0x7f2489146759]
[   341.653] (EE) 4: /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so (nouveau_drm_screen_create+0x266) [0x7f24891284f6]
[   341.653] (EE) unw_get_proc_name failed: no unwind info found [-10]
[   341.653] (EE) 5: /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so (?+0x0) [0x7f24888aaf76]
[   341.653] (EE) 6: /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so (__driDriverGetExtensions_d3d12+0x61dab4) [0x7f2488ec8ff4]
[   341.654] (EE) 7: /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so (__driDriverGetExtensions_d3d12+0x1a93) [0x7f24888acfd3]
[   341.654] (EE) 8: /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so (__driDriverGetExtensions_d3d12+0xa1a5) [0x7f24888b56e5]
[   341.654] (EE) 9: /usr/lib/x86_64-linux-gnu/libgbm.so.1 (gbm_format_get_name+0xf2e) [0x7f248a5b5eae]
[   341.654] (EE) 10: /usr/lib/x86_64-linux-gnu/libgbm.so.1 (gbm_format_get_name+0x16f8) [0x7f248a5b6678]
[   341.654] (EE) unw_get_proc_name failed: no unwind info found [-10]
[   341.654] (EE) 11: /usr/lib/x86_64-linux-gnu/libgbm.so.1 (?+0x0) [0x7f248a5b474c]
[   341.655] (EE) 12: /usr/lib/x86_64-linux-gnu/libgbm.so.1 (gbm_create_device+0x44) [0x7f248a5b4884]
[   341.655] (EE) 13: /usr/lib/xorg/modules/libglamoregl.so (glamor_egl_init+0x61) [0x7f248a5d33c1]
[   341.655] (EE) unw_get_proc_name failed: no unwind info found [-10]
[   341.655] (EE) 14: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7f248a61c733]
[   341.655] (EE) 15: /usr/lib/xorg/Xorg (InitOutput+0x95a) [0x55baa75a249a]
[   341.655] (EE) 16: /usr/lib/xorg/Xorg (InitFonts+0x1ce) [0x55baa756342e]
[   341.656] (EE) 17: /lib/x86_64-linux-gnu/libc.so.6 (__libc_init_first+0x8a) [0x7f248b04624a]
[   341.656] (EE) 18: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0x85) [0x7f248b046305]
[   341.656] (EE) 19: /usr/lib/xorg/Xorg (_start+0x21) [0x55baa754cac1]
[   341.656] (EE) 
[   341.656] (EE) Segmentation fault at address 0x20
[   341.656] (EE) 
Fatal server error:
[   341.656] (EE) Caught signal 11 (Segmentation fault). Server aborting
[   341.656] (EE) 
[   341.656] (EE) 
Please consult the The X.Org Foundation support 
	 at http://wiki.x.org
 for help. 
[   341.656] (EE) Please also check the log file at "/home/rin/.local/share/xorg/Xorg.0.log" for additional information.
[   341.656] (EE) 
[   341.656] (II) seatd_libseat finish
[   341.667] (EE) Server terminated with error (1). Closing log file. 

It seems like it's a driver issue but i've never encountered that and i don't know where to start to fix this.

Last edited by shimarin (2024-02-01 15:59:14)

Offline

#2 2024-01-31 21:16:37

GlennW
Member
From: Brisbane, Australia
Registered: 2019-07-18
Posts: 527  

Re: StartX doesn't work after a fresh install (segmentation fault 0x20)

Hi, I can't see the error log you pasted...

please post it here in code tags.


pic from 1993, new guitar day.

Offline

#3 2024-01-31 21:31:19

shimarin
Member
Registered: 2024-01-31
Posts: 7  

Re: StartX doesn't work after a fresh install (segmentation fault 0x20)

I edited the post.

Offline

#4 2024-01-31 21:52:06

ralph.ronnquist
Administrator
From: Clifton Hill, Victoria, AUS
Registered: 2016-11-30
Posts: 1,096  

Re: StartX doesn't work after a fresh install (segmentation fault 0x20)

Did you install xserver-xorg-video-* package(s)?

Who is running startx; root or non-root?

Offline

#5 2024-02-01 15:43:50

shimarin
Member
Registered: 2024-01-31
Posts: 7  

Re: StartX doesn't work after a fresh install (segmentation fault 0x20)

I didn't install the package, i assumed that it was already included in xorg like in the other distros i've used. I also tried running xorg both as root and as a user with sudo perms but it still doesn't work.

edit : i just checked again and xserver-xorg-video-nouveau is installed and up to date. I also tried booting with the other kernel (6. something) but it also didn't work

Last edited by shimarin (2024-02-01 15:57:57)

Offline

#6 2024-02-01 17:56:05

aluma
Member
Registered: 2022-10-26
Posts: 444  

Re: StartX doesn't work after a fresh install (segmentation fault 0x20)

Is seatd really necessary?
If possible, I would delete everything and run devuan_daedalus_5.0.0_amd64_desktop-live.iso.
If everything is successful, install it on your hard drive. And then I would install the frills. Xfce itself can be removed with just one command if necessary.

Offline

#7 2024-02-01 19:57:28

shimarin
Member
Registered: 2024-01-31
Posts: 7  

Re: StartX doesn't work after a fresh install (segmentation fault 0x20)

I honestly don't know if it's necessary. It came by default (i only installed the standard system utilities)

Offline

#8 2024-02-01 21:53:29

ralph.ronnquist
Administrator
From: Clifton Hill, Victoria, AUS
Registered: 2016-11-30
Posts: 1,096  

Re: StartX doesn't work after a fresh install (segmentation fault 0x20)

Could you tell what "fresh install of Devuan" means?
Which media did you use?
Which installer choices did you make?
What's your boot command line?

Would be good if I can replicate the issue; there have been similar Xorg crash reports before and possibly there's a common cause.

Offline

#9 2024-02-02 02:44:51

stultumanto
Member
Registered: 2023-12-12
Posts: 42  

Re: StartX doesn't work after a fresh install (segmentation fault 0x20)

Would be good if I can replicate the issue; there have been similar Xorg crash reports before and possibly there's a common cause.

Yes, I thought that log looked familiar. This post has an almost identical log, with X crashing out after loading the glamoregl driver. In the earlier thread, the radeon driver was next in the backtrace, but this user has the nouveau driver next. The other user seemed to be having issues with Mesa.

Offline

#10 2024-02-02 08:52:19

shimarin
Member
Registered: 2024-01-31
Posts: 7  

Re: StartX doesn't work after a fresh install (segmentation fault 0x20)

Could you tell what "fresh install of Devuan" means?
Which media did you use?
Which installer choices did you make?
What's your boot command line?

I installed nothing but the standard system utilities and the packages mentioned above. I used a USB Key booted in DD mode (it's the only one that worked) and i boot my system in legacy mode with an uefi. I also didn't encrypt my drive.

What do you mean by "boot command line"? Do you want me to send you what appears on the command line before i get asked to login?

Offline

#11 2024-02-02 10:33:15

ralph.ronnquist
Administrator
From: Clifton Hill, Victoria, AUS
Registered: 2016-11-30
Posts: 1,096  

Re: StartX doesn't work after a fresh install (segmentation fault 0x20)

1. Install media. This would be the filename of the iso file that you used to install devuan from. Perhaps even the URL you used. If you have done "installed devuan" some other way than using an installation media, then you would need to descritbe that too. Only so that I can do the same.

2. When installing with the installer ISO it takes you through a series of dialogs. I was asking that you tell me what to do so I can get the same installation done.

3. The boot command line is found in /var/log/syslog as a line with the text "Kernel command line:" in. It would tell me the specific kernel arguments used when the system starts. Presumably you would have "the default" from your manner of installation, so this point is merely a way for me to be ensured that my test system from points 1 and 2 runs in the same way as yours.

So don't worry about point 3, but please make sure you are thorough about points 1 and 2.

Offline

#12 2024-02-02 15:45:37

shimarin
Member
Registered: 2024-01-31
Posts: 7  

Re: StartX doesn't work after a fresh install (segmentation fault 0x20)

1. Install media. This would be the filename of the iso file that you used to install devuan from. Perhaps even the URL you used. If you have done "installed devuan" some other way than using an installation media, then you would need to descritbe that too. Only so that I can do the same.

2. When installing with the installer ISO it takes you through a series of dialogs. I was asking that you tell me what to do so I can get the same installation done.

https://ftp.nluug.nl/pub/os/Linux/distr … nstall.iso 

I used this exact mirror and i downloaded the latest amd64 netinstall iso. It also worked fine on my Virtual Machine.

I don't recall everything i did during the installation process, i chose the en keyboard layout, the german tier 1 mirror and i didn't encrypt the drives. I created a 256mo efi partition and a single 100Go EXT4 partition for storage.

Offline

#13 2024-02-02 17:14:42

chris2be8
Member
Registered: 2018-08-11
Posts: 255  

Re: StartX doesn't work after a fresh install (segmentation fault 0x20)

cat /proc/cmdline should also show the boot command line. On my system it matches the entry for the last boot in /var/log/syslog

Offline

#14 2024-02-02 21:37:14

ralph.ronnquist
Administrator
From: Clifton Hill, Victoria, AUS
Registered: 2016-11-30
Posts: 1,096  

Re: StartX doesn't work after a fresh install (segmentation fault 0x20)

@shimarin, thanks.

The initial step of that installer is a dialog with a menu of 8 options plus 'help'. You want me to guess that you used option '1 Install' (that's ok) and I can probably likewise guess from your outline for the handful of dialogs following; in particular that in the task selection dialog you unticked everything except the bottom one for standard utilities.

Eventually reboot into the installed system, which presents the login prompt on vt1.

So what's next? Login as root or user? And perhaps you can include the output of

grep ^Commandline /var/log/apt/history.log | grep -n ''

up to the point where you first ran into the Xorg issue.

Offline

Board footer