[qxl] Xorg crashed with assertion failure in DRIMoveBuffersHelper

Bug #1858336 reported by Elliot
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
X.Org X server
New
Unknown
xorg-server (Ubuntu)
Triaged
High
Unassigned
xserver-xorg-video-qxl (Ubuntu)
Triaged
High
Unassigned

Bug Description

After doing a normal installation with erasing the disk in GNOME Boxes, I cannot log into the Ubuntu Xorg session. Wayland works fine, but this still isn't a workaround if the user wants to use Xorg for any given reason.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
Uname: Linux 5.3.0-24-generic x86_64
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Jan 5 10:21:36 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
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 2020-01-05 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200104)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 002: ID 08e6:4433 Gemalto (was Gemplus) GemPC433-Swap
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Lsusb-t:
 /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
 /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
 /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
     |__ Port 1: Dev 2, If 0, Class=Chip/SmartCard, Driver=, 12M
 /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=3faaad6a-d32e-4d07-877f-3ef17831e142 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: ?-20191223_100556-anatol
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-q35-4.2
dmi.modalias: dmi:bvnSeaBIOS:bvr?-20191223_100556-anatol:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:
dmi.product.name: Standard PC (Q35 + ICH9, 2009)
dmi.product.version: pc-q35-4.2
dmi.sys.vendor: QEMU
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.100-4
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.4-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

Revision history for this message
Elliot (cheese-e-boi) wrote :
Revision history for this message
Daniel van Vugt (vanvugt) wrote : Re: Xorg crashed with assertion failure in DRIMoveBuffersHelper

It looks like the recurring problem here is indeed just Xorg:

[ 604.230] (EE) Backtrace:
[ 604.230] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x5576c3d8facc]
[ 604.231] (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7f6767b6359f]
[ 604.231] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7f67679a13eb]
[ 604.232] (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) [0x7f6767980899]
[ 604.232] (EE) unw_get_proc_name failed: no unwind info found [-10]
[ 604.232] (EE) 4: /lib/x86_64-linux-gnu/libc.so.6 (?+0x0) [0x7f676798075a]
[ 604.232] (EE) 5: /lib/x86_64-linux-gnu/libc.so.6 (__assert_fail+0x46) [0x7f6767992006]
[ 604.232] (EE) 6: /usr/lib/xorg/Xorg (DRIMoveBuffersHelper+0xc15) [0x5576c3d5aaa5]
[ 604.232] (EE) 7: /usr/lib/xorg/Xorg (DRI2Authenticate+0xa2) [0x5576c3d5c0f2]
[ 604.233] (EE) 8: /usr/lib/xorg/Xorg (DRI2GetParam+0x944) [0x5576c3d5d4b4]
[ 604.233] (EE) 9: /usr/lib/xorg/Xorg (SendErrorToClient+0x354) [0x5576c3c2ef44]
[ 604.233] (EE) 10: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x5576c3c32fd4]
[ 604.233] (EE) 11: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7f67679821e3]
[ 604.233] (EE) 12: /usr/lib/xorg/Xorg (_start+0x2e) [0x5576c3c1ca1e]

summary: - Login loops with GNOME Boxes on Xorg
+ Xorg crashed with assertion failure in DRIMoveBuffersHelper
summary: - Xorg crashed with assertion failure in DRIMoveBuffersHelper
+ [qxl] Xorg crashed with assertion failure in DRIMoveBuffersHelper
affects: xorg (Ubuntu) → xserver-xorg-video-qxl (Ubuntu)
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Please report the issue to the upstream developers here:

  https://gitlab.freedesktop.org/groups/xorg/-/issues

and then tell us the new issue ID.

Revision history for this message
Elliot (cheese-e-boi) wrote :
no longer affects: xorg-server (Ubuntu)
Changed in xserver-xorg-video-qxl (Ubuntu):
importance: Undecided → High
status: New → Triaged
Changed in xorg-server (Ubuntu):
status: New → Triaged
importance: Undecided → High
Changed in xorg-server:
status: Unknown → New
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

It's possible the bug is in xorg-server and it's just failing to handle a situation which is only encountered with the qxl driver.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Actually the stack looks the same as what people see in VirtualBox so in the absence of a journal log let's assume it's the same as bug 1871752 and friends.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.