You are not logged in.

Pages: 1

#1 2025-05-23 12:42:55

nostredamme
Member
Registered: 2021-04-12
Posts: 8

[SOLVED] X Server Segmentation fault in VirtualBox

Hi,

I'm running Arch Linux (xfce, X, lightdm) inside VirtualBox, everything was going fine until the yesterday's evening full-system update running pacman -Syyu. Previously, I've done update a few days back.

I get an error on startup, lighdm doesn't start at all and it gets stuck there. I have to use tty to log in and investigate.

The error I get on startup is:

[FAILED] Failed to start Light Display Manager.
See 'systemctl status lightdm.service' for details.

Here's the output of systemctl status lightdm.service:

× lightdm.service - Light Display Manager
     Loaded: loaded (/usr/lib/systemd/system/lightdm.service; enabled; preset: disabled)
     Active: failed (Result: exit-code) since Fri 2025-05-23 11:41:39 CEST; 1min 28s ago
   Duration: 241ms
 Invocation: 79e7f75037ca49f686e6cd86da04962d
       Docs: man:lightdm(1)
    Process: 724 ExecStart=/usr/bin/lightdm (code=exited, status=1/FAILURE)
   Main PID: 724 (code=exited, status=1/FAILURE)

May 23 11:41:38 arch systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
May 23 11:41:38 arch systemd[1]: lightdm.service: Failed with result 'exit-code'.
May 23 11:41:39 arch systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 5.
May 23 11:41:39 arch systemd[1]: lightdm.service: Start request repeated too quickly.
May 23 11:41:39 arch systemd[1]: lightdm.service: Failed with result 'exit-code'.
May 23 11:41:39 arch systemd[1]: Failed to start Light Display Manager.

lightdm fails on startup and after logging in via tty, I can see the following segfault in /var/log/Xorg.0.log:

[   130.767] (EE) vmware(0): Unable to map mmio BAR. Invalid argument (22)
[   130.767] (EE) vmware(0): Unable to map frame buffer BAR. Invalid argument (22)
[   130.767] (EE) 
[   130.781] (EE) Backtrace:
[   130.781] (EE) unw_get_proc_name failed: no unwind info found [-10]
[   130.781] (EE) 0: /usr/lib/Xorg (?+0x0) [0x61255eb680e4]
[   130.781] (EE) unw_get_proc_name failed: no unwind info found [-10]
[   130.781] (EE) 1: /usr/lib/libc.so.6 (?+0x0) [0x759ae4318ef0]
[   130.781] (EE) unw_get_proc_name failed: no unwind info found [-10]
[   130.781] (EE) 2: /usr/lib/libc.so.6 (?+0x0) [0x759ae44479c9]
[   130.781] (EE) unw_get_proc_name failed: no unwind info found [-10]
[   130.782] (EE) 3: /usr/lib/xorg/modules/drivers/vmware_drv.so (?+0x0) [0x759ae3b57694]
[   130.782] (EE) 4: /usr/lib/Xorg (AddScreen+0x11b) [0x61255ea815ab]
[   130.782] (EE) 5: /usr/lib/Xorg (InitOutput+0x2e5) [0x61255eb8cbc5]
[   130.782] (EE) unw_get_proc_name failed: no unwind info found [-10]
[   130.782] (EE) 6: /usr/lib/Xorg (?+0x0) [0x61255ea3a6c5]
[   130.782] (EE) unw_get_proc_name failed: no unwind info found [-10]
[   130.782] (EE) 7: /usr/lib/libc.so.6 (?+0x0) [0x759ae43026b5]
[   130.782] (EE) 8: /usr/lib/libc.so.6 (__libc_start_main+0x89) [0x759ae4302769]
[   130.782] (EE) 9: /usr/lib/Xorg (_start+0x25) [0x61255ea3bcf5]
[   130.782] (EE) 
[   130.782] (EE) Segmentation fault at address 0x0
[   130.782] (EE) 
Fatal server error:
[   130.783] (EE) Caught signal 11 (Segmentation fault). Server aborting
[   130.783] (EE) 
[   130.783] (EE) 
Please consult the The X.Org Foundation support 
         at http://wiki.x.org
 for help. 
[   130.783] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[   130.783] (EE) 
[   130.791] (EE) Server terminated with error (1). Closing log file.

output from journalctl -u lightdm, but I think this one just passes on the stack trace from X (same as above):

May 23 11:19:55 arch systemd[1]: Starting Light Display Manager...
May 23 11:19:55 arch systemd[1]: Started Light Display Manager.
May 23 11:19:55 arch systemd-coredump[741]: Process 739 (Xorg) of user 0 dumped core.
                                            
                                            Stack trace of thread 739:
                                            #0  0x000074f647f1e74c n/a (libc.so.6 + 0x9774c)
                                            #1  0x000074f647ec4dc0 raise (libc.so.6 + 0x3ddc0)
                                            #2  0x000074f647eac57a abort (libc.so.6 + 0x2557a)
                                            #3  0x00005c6b9c6d8c7e OsAbort (/usr/lib/Xorg + 0x15ec7e)
                                            #4  0x00005c6b9c6e5f90 FatalError (/usr/lib/Xorg + 0x16bf90)
                                            #5  0x00005c6b9c6db143 n/a (/usr/lib/Xorg + 0x161143)
                                            #6  0x000074f647ec4ef0 n/a (libc.so.6 + 0x3def0)
                                            #7  0x000074f647ff39c9 n/a (libc.so.6 + 0x16c9c9)
                                            #8  0x000074f647703694 n/a (vmware_drv.so + 0xb694)
                                            #9  0x00005c6b9c5f45ab AddScreen (/usr/lib/Xorg + 0x7a5ab)
                                            #10 0x00005c6b9c6ffbc5 InitOutput (/usr/lib/Xorg + 0x185bc5)
                                            #11 0x00005c6b9c5ad6c5 n/a (/usr/lib/Xorg + 0x336c5)
                                            #12 0x000074f647eae6b5 n/a (libc.so.6 + 0x276b5)
                                            #13 0x000074f647eae769 __libc_start_main (libc.so.6 + 0x27769)
                                            #14 0x00005c6b9c5aecf5 _start (/usr/lib/Xorg + 0x34cf5)
                                            ELF object binary architecture: AMD x86-64
May 23 11:19:55 arch systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
May 23 11:19:55 arch systemd[1]: lightdm.service: Failed with result 'exit-code'.
May 23 11:19:55 arch systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 5.
May 23 11:19:55 arch systemd[1]: lightdm.service: Start request repeated too quickly.
May 23 11:19:55 arch systemd[1]: lightdm.service: Failed with result 'exit-code'.
May 23 11:19:55 arch systemd[1]: Failed to start Light Display Manager.

output of lspci:

00:02.0 VGA compatible controller: VMware SVGA II Adapter
        Subsystem: VMware SVGA II Adapter
        Kernel driver in use: vmwgfx
        Kernel modules: vmwgfx

  • I was experimenting with older versions of the xf86-video-vmware 13.4.0-4 package: I can see here: archlinux.org/packages/extra/x86_64/xf86-video-vmware that it has been changed yesterday, exactly before my update, it produced other error "Failed to load module "vmware"

  • Also, I'm running xorg-server-bug865 21.1.16-1, so I tried to uninstall it and install latest xorg-server from using pacman, which didn't help

  • I tried to switch to different VirtualBox Graphics Controller, each from the list available: VMSVGA (default), VBoxVGA, VBoxSVGA

  • 3D Acceleration disabled in VirtualBox Display settings

  • and last, but not least: I've done a clean install in a new VirtualBox machine and still the same error

Last edited by nostredamme (2025-05-23 14:08:30)

Offline

#2 2025-05-23 13:50:51

seth
Member
Registered: 2012-09-03
Posts: 64,527

Re: [SOLVED] X Server Segmentation fault in VirtualBox

https://bbs.archlinux.org/viewtopic.php … 3#p2242823

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#3 2025-05-23 14:08:04

nostredamme
Member
Registered: 2021-04-12
Posts: 8

Re: [SOLVED] X Server Segmentation fault in VirtualBox

Oh thanks, that fixes the problem. I was watching that topic, but the last answer (about mesa) appeared after my post. Marking this as [SOLVED].

Offline

#4 2025-06-09 13:25:40

HansInSpace
Member
Registered: 2025-06-09
Posts: 3

Re: [SOLVED] X Server Segmentation fault in VirtualBox

I'm still seeing this error, X would Segfault in a VirtualBox VM, resulting in no GUI.

Installing xf86-video-vmware-git from AUR instead of using xf86-video-vmware solved it for me.

(No need to downgrade mesa or installing vulkan-virtio or other random packages).
My old fix (months ago) for this was also downgrading mesa, but after a full system update, the even newer mesa version was back to being broken. So the underlying problem in the mesa package seems to persist to this day, I guess.

Best Regards,

Hans

Offline

#5 2025-06-09 14:25:23

seth
Member
Registered: 2012-09-03
Posts: 64,527

Re: [SOLVED] X Server Segmentation fault in VirtualBox

My old fix (months ago) for this was also downgrading mesa

Are we sure this is is the same problem?
The current situation emerged w/ mesa v25.1 and zink falsely being used instead of llvmpipe. If you had problems w/ mesa 25.0, they're likely of different nature.

X would Segfault in a VirtualBox VM

Do you still have a corresponding xorg log?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#6 2025-06-09 16:07:31

HansInSpace
Member
Registered: 2025-06-09
Posts: 3

Re: [SOLVED] X Server Segmentation fault in VirtualBox

Hey, thanks for answering!

seth wrote:

Are we sure this is is the same problem?

Seems like i mixed things up. I had a problem with mesa on my Arch Host back in Dec. 2023. At that time i also tried the downgrade 'fix':

$ grep downgrade /var/log/pacman.log 
[2023-12-31T23:05:09+0100] [ALPM] downgraded mesa (1:23.3.2-1 -> 1:23.3.1-1)

If i remember correctly, that worked at that time, but the permanent solution were those kernel command line options:

nvidia_drm.fbdev=1 nvidia_drm.modeset=1

I think i read in the forums, that it was a 'misconfiguration' to not use those options when using the proprietary nvidia driver.
That is for the Host.

In my Arch VirtualBox Guest i never downgraded mesa, so X segfaulting here seems to be unrelated to the old error on the Host. If i revert my 'fix' on the Guest, this is the Xorg log:

[    15.488] 
X.Org X Server 1.21.1.16
X Protocol Version 11, Revision 0
[    15.488] Current Operating System: Linux vm-vpn 6.14.10-arch1-1 #1 SMP PREEMPT_DYNAMIC Wed, 04 Jun 2025 18:52:35 +0000 x86_64
[    15.488] Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=da9910f8-2230-4206-8a0e-cc14b7e6854d rw loglevel=3
[    15.488]  
[    15.488] Current version of pixman: 0.46.0
[    15.488] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[    15.488] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[    15.489] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Jun  9 17:55:48 2025
[    15.489] (==) Using config directory: "/etc/X11/xorg.conf.d"
[    15.489] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[    15.489] (==) No Layout section.  Using the first Screen section.
[    15.489] (==) No screen section available. Using defaults.
[    15.489] (**) |-->Screen "Default Screen Section" (0)
[    15.489] (**) |   |-->Monitor "<default monitor>"
[    15.489] (==) No monitor specified for screen "Default Screen Section".
	Using a default monitor configuration.
[    15.489] (**) Allowing byte-swapped clients
[    15.489] (==) Automatically adding devices
[    15.489] (==) Automatically enabling devices
[    15.489] (==) Automatically adding GPU devices
[    15.489] (==) Automatically binding GPU devices
[    15.489] (==) Max clients allowed: 256, resource mask: 0x1fffff
[    15.489] (WW) The directory "/usr/share/fonts/misc" does not exist.
[    15.489] 	Entry deleted from font path.
[    15.489] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/TTF".
[    15.489] 	Entry deleted from font path.
[    15.489] 	(Run 'mkfontdir' on "/usr/share/fonts/TTF").
[    15.489] (WW) The directory "/usr/share/fonts/OTF" does not exist.
[    15.489] 	Entry deleted from font path.
[    15.489] (WW) The directory "/usr/share/fonts/Type1" does not exist.
[    15.489] 	Entry deleted from font path.
[    15.489] (WW) The directory "/usr/share/fonts/100dpi" does not exist.
[    15.489] 	Entry deleted from font path.
[    15.489] (WW) The directory "/usr/share/fonts/75dpi" does not exist.
[    15.489] 	Entry deleted from font path.
[    15.489] (==) FontPath set to:
	
[    15.489] (==) ModulePath set to "/usr/lib/xorg/modules"
[    15.489] (II) The server relies on udev to provide the list of input devices.
	If no devices become available, reconfigure udev or disable AutoAddDevices.
[    15.489] (II) Module ABI versions:
[    15.489] 	X.Org ANSI C Emulation: 0.4
[    15.489] 	X.Org Video Driver: 25.2
[    15.489] 	X.Org XInput driver : 24.4
[    15.489] 	X.Org Server Extension : 10.0
[    15.489] (++) using VT number 7

[    15.489] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[    15.490] (II) xfree86: Adding drm device (/dev/dri/card0)
[    15.490] (II) Platform probe for /sys/devices/pci0000:00/0000:00:02.0/drm/card0
[    15.492] (--) PCI:*(0@0:2:0) 15ad:0405:15ad:0405 rev 0, Mem @ 0xe0000000/134217728, 0xe8400000/2097152, I/O @ 0x0000c170/16, BIOS @ 0x????????/131072
[    15.492] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[    15.492] (II) LoadModule: "glx"
[    15.492] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[    15.493] (II) Module glx: vendor="X.Org Foundation"
[    15.493] 	compiled for 1.21.1.16, module version = 1.0.0
[    15.493] 	ABI class: X.Org Server Extension, version 10.0
[    15.493] (==) Matched vmware as autoconfigured driver 0
[    15.493] (==) Matched modesetting as autoconfigured driver 1
[    15.493] (==) Matched fbdev as autoconfigured driver 2
[    15.493] (==) Matched vesa as autoconfigured driver 3
[    15.493] (==) Assigned the driver to the xf86ConfigLayout
[    15.493] (II) LoadModule: "vmware"
[    15.493] (II) Loading /usr/lib/xorg/modules/drivers/vmware_drv.so
[    15.493] (II) Module vmware: vendor="X.Org Foundation"
[    15.493] 	compiled for 1.21.1.16, module version = 13.4.0
[    15.493] 	Module class: X.Org Video Driver
[    15.493] 	ABI class: X.Org Video Driver, version 25.2
[    15.493] (II) LoadModule: "modesetting"
[    15.493] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[    15.493] (II) Module modesetting: vendor="X.Org Foundation"
[    15.493] 	compiled for 1.21.1.16, module version = 1.21.1
[    15.493] 	Module class: X.Org Video Driver
[    15.493] 	ABI class: X.Org Video Driver, version 25.2
[    15.493] (II) LoadModule: "fbdev"
[    15.493] (WW) Warning, couldn't open module fbdev
[    15.493] (EE) Failed to load module "fbdev" (module does not exist, 0)
[    15.493] (II) LoadModule: "vesa"
[    15.493] (WW) Warning, couldn't open module vesa
[    15.493] (EE) Failed to load module "vesa" (module does not exist, 0)
[    15.493] (II) vmware: driver for VMware SVGA: vmware0405, vmware0710
[    15.493] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[    15.493] (WW) Falling back to old probe method for modesetting
[    15.493] (II) vmware(0): Driver was compiled without KMS- and 3D support.
[    15.493] (WW) vmware(0): Disabling 3D support.
[    15.493] (WW) vmware(0): Disabling Render Acceleration.
[    15.493] (WW) vmware(0): Disabling RandR12+ support.
[    15.493] (--) vmware(0): VMware SVGA regs at (0xc170, 0xc171)
[    15.493] (II) Loading sub module "vgahw"
[    15.493] (II) LoadModule: "vgahw"
[    15.493] (II) Loading /usr/lib/xorg/modules/libvgahw.so
[    15.493] (II) Module vgahw: vendor="X.Org Foundation"
[    15.493] 	compiled for 1.21.1.16, module version = 0.1.0
[    15.493] 	ABI class: X.Org Video Driver, version 25.2
[    15.493] (--) vmware(0): caps:  0x09F682E2
[    15.493] (--) vmware(0): depth: 24
[    15.493] (--) vmware(0): bpp:   32
[    15.493] (--) vmware(0): vram:  134217728
[    15.493] (--) vmware(0): pbase: 0xe0000000
[    15.493] (--) vmware(0): mwidt: 5632
[    15.493] (--) vmware(0): mheig: 5632
[    15.493] (II) vmware(0): Creating default Display subsection in Screen section
	"Default Screen Section" for depth/fbbpp 24/32
[    15.493] (--) vmware(0): depth: 24
[    15.493] (--) vmware(0): bpp:   32
[    15.493] (--) vmware(0): w.red: 8
[    15.493] (--) vmware(0): w.grn: 8
[    15.493] (--) vmware(0): w.blu: 8
[    15.493] (--) vmware(0): vis:   4
[    15.493] (==) vmware(0): Depth 24, (==) framebuffer bpp 32
[    15.493] (==) vmware(0): RGB weight 888
[    15.493] (==) vmware(0): Default visual is TrueColor
[    15.493] (==) vmware(0): Using HW cursor
[    15.493] (==) vmware(0): Will set up a driver mode with dimensions 1280x800.
[    15.493] (==) vmware(0): Using gamma correction (1.0, 1.0, 1.0)
[    15.493] (II) vmware(0): Clock range:   0.00 to 400000.00 MHz
[    15.493] (II) vmware(0): Not using default mode "320x175" (bad mode clock/interlace/doublescan)
[    15.493] (II) vmware(0): Not using default mode "320x200" (bad mode clock/interlace/doublescan)
--- Many more of these ---
[    15.493] (II) vmware(0): Not using default mode "720x405" (monitor doesn't support reduced blanking)
[    15.493] (II) vmware(0): Not using default mode "360x202" (bad mode clock/interlace/doublescan)
[    15.493] (II) vmware(0): Not using default mode "360x202" (bad mode clock/interlace/doublescan)
[    15.493] (II) vmware(0): Not using default mode "864x486" (monitor doesn't support reduced blanking)
[    15.493] (II) vmware(0): Not using default mode "432x243" (bad mode clock/interlace/doublescan)
[    15.493] (II) vmware(0): Not using default mode "432x243" (bad mode clock/interlace/doublescan)
--- Many more of these ----
[    15.493] (II) vmware(0): Virtual size is 1280x800 (pitch 5632)
[    15.493] (**) vmware(0): *Driver mode "vmwlegacy-default-1280x800": 77.2 MHz, 48.2 kHz, 60.0 Hz
[    15.493] (II) vmware(0): Modeline "vmwlegacy-default-1280x800"x60.0   77.18  1280 1281 1282 1602  800 801 802 803 (48.2 kHz ez)
[    15.493] (**) vmware(0):  Default mode "5120x2880": 1276.5 MHz, 178.9 kHz, 60.0 Hz
[    15.493] (II) vmware(0): Modeline "5120x2880"x60.0  1276.50  5120 5560 6128 7136  2880 2883 2888 2982 -hsync +vsync (178.9 kHz d)
--- Many more of these ----
[    15.493] (II) vmware(0): Modeline "1920x1080"x60.0  173.00  1920 2048 2248 2576  1080 1083 1088 1120 -hsync +vsync (67.2 kHz d)
[    15.493] (**) vmware(0):  Default mode "1600x1200": 229.5 MHz, 106.2 kHz, 85.0 Hz
--- Many more of these ----
[    15.493] (**) vmware(0):  Default mode "640x350": 31.5 MHz, 37.9 kHz, 85.1 Hz
[    15.493] (II) vmware(0): Modeline "640x350"x85.1   31.50  640 672 736 832  350 382 385 445 +hsync -vsync (37.9 kHz d)
[    15.493] (==) vmware(0): DPI set to (96, 96)
[    15.493] (II) Loading sub module "fb"
[    15.493] (II) LoadModule: "fb"
[    15.493] (II) Module "fb" already built-in
[    15.493] (II) Loading sub module "shadowfb"
[    15.493] (II) LoadModule: "shadowfb"
[    15.493] (II) Loading /usr/lib/xorg/modules/libshadowfb.so
[    15.493] (II) Module shadowfb: vendor="X.Org Foundation"
[    15.493] 	compiled for 1.21.1.16, module version = 1.0.0
[    15.493] 	ABI class: X.Org ANSI C Emulation, version 0.4
[    15.493] (II) Loading sub module "ramdac"
[    15.493] (II) LoadModule: "ramdac"
[    15.493] (II) Module "ramdac" already built-in
[    15.493] (II) UnloadModule: "modesetting"
[    15.493] (II) Unloading modesetting
[    15.493] (II) vmware(0): Initialized VMWARE_CTRL extension version 0.2
[    15.493] (II) vmware(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0
[    15.493] (EE) vmware(0): Unable to map mmio BAR. Invalid argument (22)
[    15.493] (EE) vmware(0): Unable to map frame buffer BAR. Invalid argument (22)
[    15.493] (EE) 
[    15.493] (EE) Backtrace:
[    15.493] (EE) unw_get_proc_name failed: no unwind info found [-10]
[    15.493] (EE) 0: /usr/lib/Xorg (?+0x0) [0x558ebac49f7c]
[    15.493] (EE) unw_get_proc_name failed: no unwind info found [-10]
[    15.493] (EE) 1: /usr/lib/libc.so.6 (?+0x0) [0x7f1729b94ef0]
[    15.493] (EE) unw_get_proc_name failed: no unwind info found [-10]
[    15.493] (EE) 2: /usr/lib/libc.so.6 (?+0x0) [0x7f1729cc39c9]
[    15.493] (EE) unw_get_proc_name failed: no unwind info found [-10]
[    15.493] (EE) 3: /usr/lib/xorg/modules/drivers/vmware_drv.so (?+0x0) [0x7f17293d5694]
[    15.493] (EE) 4: /usr/lib/Xorg (AddScreen+0x11b) [0x558ebab62c4b]
[    15.493] (EE) 5: /usr/lib/Xorg (InitOutput+0x3bd) [0x558ebac6715d]
[    15.493] (EE) unw_get_proc_name failed: no unwind info found [-10]
[    15.493] (EE) 6: /usr/lib/Xorg (?+0x0) [0x558ebab20c69]
[    15.493] (EE) unw_get_proc_name failed: no unwind info found [-10]
[    15.493] (EE) 7: /usr/lib/libc.so.6 (?+0x0) [0x7f1729b7e6b5]
[    15.493] (EE) 8: /usr/lib/libc.so.6 (__libc_start_main+0x89) [0x7f1729b7e769]
[    15.493] (EE) 9: /usr/lib/Xorg (_start+0x25) [0x558ebab222b5]
[    15.493] (EE) 
[    15.493] (EE) Segmentation fault at address 0x0
[    15.493] (EE) 
Fatal server error:
[    15.493] (EE) Caught signal 11 (Segmentation fault). Server aborting
[    15.493] (EE) 
[    15.493] (EE) 
Please consult the The X.Org Foundation support 
	 at http://wiki.x.org
 for help. 
[    15.493] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[    15.493] (EE) 
[    15.505] (EE) Server terminated with error (1). Closing log file.

Offline

#7 2025-06-09 16:43:25

seth
Member
Registered: 2012-09-03
Posts: 64,527

Re: [SOLVED] X Server Segmentation fault in VirtualBox

That's the OP's crash as  well - would 

export MESA_LOADER_DRIVER_OVERRIDE=llvmpipe

also prevent it?
(If not the bug is disconnected from the other crashes)

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#8 2025-06-09 17:29:23

HansInSpace
Member
Registered: 2025-06-09
Posts: 3

Re: [SOLVED] X Server Segmentation fault in VirtualBox

Unfortunately, that would not fix it.
(I put the export in /etc/profile and also /etc/environment)

No idea why aur/xf86-video-vmware-git fixed it for me, was nothing more than a shot in the dark.

Are you trying to narrow down another potential issue (also regarding the other thread you linked)?
Let me know if i could provide you with more logs or otherwise helpful input.

Offline

#9 2025-06-09 20:27:48

seth
Member
Registered: 2012-09-03
Posts: 64,527

Re: [SOLVED] X Server Segmentation fault in VirtualBox

Yup, seems this is a distinct problem - the linked post that xf86-video-vmware was also downgraded so there seems a vmware specific bug in that version, which is different from the nouveau and virtio situation.
A complete clusterbug wink

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#10 2025-06-09 21:25:06

seth
Member
Registered: 2012-09-03
Posts: 64,527

Re: [SOLVED] X Server Segmentation fault in VirtualBox

https://bbs.archlinux.org/viewtopic.php … 8#p2245508
"clusterbug"

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#11 2025-06-09 21:26:01

Toolybird
Member
Registered: 2017-09-30
Posts: 79

Re: [SOLVED] X Server Segmentation fault in VirtualBox

Yes, "xf86-video-vmware" is broken (beyond repair). More background here: https://gitlab.archlinux.org/archlinux/ … ote_275921

Offline

#12 2025-06-11 01:38:39

NuSkool
Member
Registered: 2015-03-23
Posts: 268

Re: [SOLVED] X Server Segmentation fault in VirtualBox

I have a Dec last year Arch install on USB, that I booted through vbox to update, etc...

The USB system has 'virtualbox-guest-utils' installed. Upon update and reboot via vbox, no xorg.
Troubleshooting led me to discover 'xf86-video-vmware', a formed dependency of  'virtualbox-guest-utils' was the culprit.
https://gitlab.archlinux.org/archlinux/ … aa82aadda9

Initially downgrading, then removing 'xf86-video-vmware' restored xorg, fixing the issue.

Found this thread from searching 'xf86-video-vmware', to see if this had already been figured out.
I don't think this would have been an issue if I had booted this USB system on real hardware though.

Ironically, seems the vmware_drv.so failed loading prior to the update. Maybe this is why xorg actually started?

[    21.038] (II) LoadModule: "vmware"
[    21.038] (II) Loading /usr/lib/xorg/modules/drivers/vmware_drv.so
[    21.039] (EE) Failed to load /usr/lib/xorg/modules/drivers/vmware_drv.so: libLLVM.so.18.1: cannot open shared object file: No such file or directory
[    21.039] (EE) Failed to load module "vmware" (loader failed, 0)
[    21.039] (II) LoadModule: "modesetting"
[    21.039] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[    21.040] (II) Module modesetting: vendor="X.Org Foundation"
[    21.040] 	compiled for 1.21.1.14, module version = 1.21.1
[    21.040] 	Module class: X.Org Video Driver
[    21.040] 	ABI class: X.Org Video Driver, version 25.2

Whereas after today's update, the vmware_drv.so loading seems responsible in breaking xorg?
This is all well beyond my pay grade though.... just reporting my findings.

[    21.648] (II) LoadModule: "vmware"
[    21.648] (II) Loading /usr/lib/xorg/modules/drivers/vmware_drv.so
[    21.648] (II) Module vmware: vendor="X.Org Foundation"
[    21.648] 	compiled for 1.21.1.16, module version = 13.4.0
[    21.648] 	Module class: X.Org Video Driver
[    21.648] 	ABI class: X.Org Video Driver, version 25.2
[    21.648] (II) LoadModule: "modesetting"
[    21.648] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[    21.650] (II) Module modesetting: vendor="X.Org Foundation"
[    21.650] 	compiled for 1.21.1.16, module version = 1.21.1
[    21.650] 	Module class: X.Org Video Driver
[    21.650] 	ABI class: X.Org Video Driver, version 25.2

......

[    21.650] 	ABI class: X.Org Video Driver, version 25.2
[    21.650] (EE) 
[    21.650] (EE) Backtrace:
[    21.650] (EE) unw_get_proc_name failed: no unwind info found [-10]
[    21.650] (EE) 0: /usr/lib/Xorg (?+0x0) [0x5599da163f7c]
[    21.650] (EE) unw_get_proc_name failed: no unwind info found [-10]
[    21.650] (EE) 1: /usr/lib/libc.so.6 (?+0x0) [0x7f1bcdadfef0]
[    21.652] (EE) 2: /usr/lib/libpciaccess.so.0 (pci_io_write8+0x7) [0x7f1bcdf599a7]
[    21.652] (EE) 3: /usr/lib/xorg/modules/libvgahw.so (vgaHWSaveColormap+0x50) [0x7f1bcd014cc0]
[    21.652] (EE) 4: /usr/lib/xorg/modules/libvgahw.so (vgaHWSave+0x45) [0x7f1bcd016f35]
[    21.652] (EE) unw_get_proc_name failed: no unwind info found [-10]
[    21.652] (EE) 5: /usr/lib/xorg/modules/drivers/vmware_drv.so (?+0x0) [0x7f1bcd31b77e]
[    21.652] (EE) 6: /usr/lib/Xorg (InitOutput+0x1742) [0x5599da1824e2]
[    21.652] (EE) unw_get_proc_name failed: no unwind info found [-10]
[    21.652] (EE) 7: /usr/lib/Xorg (?+0x0) [0x5599da03ac69]
[    21.652] (EE) unw_get_proc_name failed: no unwind info found [-10]
[    21.652] (EE) 8: /usr/lib/libc.so.6 (?+0x0) [0x7f1bcdac96b5]
[    21.652] (EE) 9: /usr/lib/libc.so.6 (__libc_start_main+0x89) [0x7f1bcdac9769]
[    21.652] (EE) 10: /usr/lib/Xorg (_start+0x25) [0x5599da03c2b5]
[    21.652] (EE) 
[    21.652] (EE) Segmentation fault at address 0x8
[    21.652] (EE) 
Fatal server error:
[    21.652] (EE) Caught signal 11 (Segmentation fault). Server aborting
[    21.652] (EE) 
[    21.652] (EE) 
Please consult the The X.Org Foundation support 
	 at http://wiki.x.org

Maybe someone will find this info useful.

Last edited by NuSkool (2025-06-11 01:43:51)

Scripts I Use                                                 :  https://github.com/Cody-Learner
grep -m1 'model name' /proc/cpuinfo    : AMD Ryzen 7 8745HS w/ Radeon 780M Graphics
grep -m1 'model name' /proc/cpuinfo    : Intel(R) N95
grep -m1 'model name' /proc/cpuinfo    : AMD Ryzen 5 PRO 2400GE w/ Radeon Vega Graphics

Offline

#13 2025-06-11 12:43:05

tekstryder
Member
Registered: 2013-02-14
Posts: 325

Re: [SOLVED] X Server Segmentation fault in VirtualBox

NuSkool wrote:

Whereas after today's update, the vmware_drv.so loading seems responsible in breaking xorg?

No need to me-too a known, solved issue.

If you have a new issue please open a new thread topic.

EDIT: this?

• https://gitlab.archlinux.org/archlinux/ … -/issues/3

and:

• https://bbs.archlinux.org/viewtopic.php?id=306168

Last edited by tekstryder (2025-06-11 12:52:05)

Offline

Pages: 1

Board footer

Powered by FluxBB