Server crashes when Using X11 desktop instead of Wayland
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xorg-server (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Having trouble with the collection tools with no desktop after the crash. This is a KVM Virtual machine using QXL video.
Changed WaylandEnable=false in /etc/gdm3/
root@ubu24:
No LSB modules are available.
Description: Ubuntu 24.04 LTS
Release: 24.04
root@ubu24:
xserver-xorg:
Installed: 1:7.7+23ubuntu3
Candidate: 1:7.7+23ubuntu3
Version table:
Expected the system to boot to the greeter. Looks like GDM tried three times to start the X server and gave up. Used VT 2 to get a console login
Problem seems to be an assert in DRI initialization:
#10 __pthread_
[Error: pthread_kill.c was not found in source tree]
#11 __pthread_
[Error: pthread_kill.c was not found in source tree]
#12 __GI___pthread_kill (threadid=
[Error: pthread_kill.c was not found in source tree]
#13 0x00007f7197e4526e in __GI_raise (sig=sig@entry=6) at ../sysdeps/
[Error: raise.c was not found in source tree]
#14 0x00007f7197e288ff in __GI_abort () at ./stdlib/abort.c:79
[Error: abort.c was not found in source tree]
#15 0x00007f7197e2881b in __assert_fail_base (fmt=0x7f7197fd01e8 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=
[Error: assert.c was not found in source tree]
#16 0x00007f7197e3b507 in __assert_fail (assertion=
[Error: assert.c was not found in source tree]
#17 0x00005594ab3f33c3 in ?? ()
#18 0x00005594ab3f56a6 in DRI2Authenticate ()
#19 0x00005594ab3f6409 in ?? ()
#20 0x00005594ab2bdab4 in ?? ()
#21 0x00005594ab2c1e52 in ?? ()
#22 0x00007f7197e2a1ca in __libc_
[Error: libc_start_
#23 0x00007f7197e2a28b in __libc_
[Error: libc-start.c was not found in source tree]
#24 0x00005594ab2aa395 in _start ()
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: xserver-xorg 1:7.7+23ubuntu3
ProcVersionSign
Uname: Linux 6.8.0-35-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckR
Date: Fri Aug 23 13:59:14 2024
DistUpgraded: Fresh install
DistroCodename: noble
DistroVariant: ubuntu
ExtraDebuggingI
GraphicsCard:
Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 04) (prog-if 00 [VGA controller])
Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
InstallationDate: Installed on 2024-05-01 (114 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
Lsusb:
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU Tablet
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Lsusb-t:
/: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=uhci_hcd/2p, 12M
/: Bus 002.Port 001: Dev 001, Class=root_hub, Driver=ehci-pci/6p, 480M
|__ Port 001: Dev 002, If 0, Class=Human Interface Device, Driver=usbhid, 480M
/: Bus 003.Port 001: Dev 001, Class=root_hub, Driver=uhci_hcd/2p, 12M
/: Bus 004.Port 001: Dev 001, Class=root_hub, Driver=uhci_hcd/2p, 12M
MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=linux
XDG_RUNTIME_
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.release: 0.0
dmi.bios.vendor: SeaBIOS
dmi.bios.version: 1.15.0-1
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.
dmi.modalias: dmi:bvnSeaBIOS:
dmi.product.name: Standard PC (Q35 + ICH9, 2009)
dmi.product.
dmi.sys.vendor: QEMU
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.120-2build1
version.
version.
version.
version.
version.
version.
version.
Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1861609, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.