Ubuntu
xorg-server package

Xorg crash

Bug #1872971 reported by Bentley Oakes on 2020-04-15

This bug report is a duplicate of: Bug #1868519: [nvidia] Xorg crashed with SIGSEGV in xf86ScreenMoveCursor() from xf86MoveCursor() from miPointerMoveNoEvent() from miPointerSetPosition() from positionSprite(). Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	xorg-server (Ubuntu)	Incomplete	Undecided	Unassigned

Bug Description

lsb_release -rd
Description: Ubuntu Focal Fossa (development branch)
Release: 20.04

apt-cache policy xorg
xorg:
  Installed: 1:7.7+19ubuntu14
  Candidate: 1:7.7+19ubuntu14
  Version table:
*** 1:7.7+19ubuntu14 500
        500 http://be.archive.ubuntu.com/ubuntu focal/main amd64 Packages
        100 /var/lib/dpkg/status

I was running the game Into the Breach (https://store.steampowered.com/app/590380/Into_the_Breach/) through Steam Play (Proton 5.0-5). When I continue my game and mouse over a character which has been placed on the play field, my session crashes and I am returned to the login screen. This consistently happens every time I load my game and perform the mouseover.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus.0000.01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0000:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.82 Wed Apr 1 20:04:33 UTC 2020
GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu1)
ApportVersion: 2.20.11-0ubuntu26
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: XFCE
Date: Wed Apr 15 13:38:42 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus: nvidia, 440.82, 5.4.0-21-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller])
Subsystem: Dell UHD Graphics 630 (Mobile) [1028:0819]
Subsystem: Dell GM108M [GeForce MX130] [1028:0819]
InstallationDate: Installed on 2020-04-09 (6 days ago)
InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
MachineType: Dell Inc. Latitude 5591
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=595cdefb-5445-4df8-99e9-6a60485a8c97 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/11/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.6.1
dmi.board.name: 0DVVG1
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr1.6.1:bd01/11/2019:svnDellInc.:pnLatitude5591:pvr:rvnDellInc.:rn0DVVG1:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Latitude
dmi.product.name: Latitude 5591
dmi.product.sku: 0819
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
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

Tags:

Revision history for this message

Bentley Oakes (boakes) wrote on 2020-04-15:

.proc.driver.nvidia.params.txt Edit (690 bytes, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (78.3 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (7.2 KiB, text/plain; charset="utf-8")
DpkgLog.txt Edit (1.3 MiB, text/plain; charset="utf-8")
LightdmDisplayLog.txt Edit (4.2 KiB, text/plain; charset="utf-8")
LightdmLog.txt Edit (18.6 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (13.1 KiB, text/plain; charset="utf-8")
Lspci-vt.txt Edit (1.4 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (375 bytes, text/plain; charset="utf-8")
Lsusb-t.txt Edit (620 bytes, text/plain; charset="utf-8")
Lsusb-v.txt Edit (40.5 KiB, text/plain; charset="utf-8")
NvidiaBugReportLog.txt Edit (1.0 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (15.4 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (1.3 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (320 bytes, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (9.2 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (8.7 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (242.9 KiB, text/plain; charset="utf-8")
XorgLog.txt Edit (50.2 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (50.2 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (23.8 KiB, text/plain; charset="utf-8")
nvidia-settings.txt Edit (25.9 KiB, text/plain; charset="utf-8")
xdpyinfo.txt Edit (33.4 KiB, text/plain; charset="utf-8")

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2020-04-16:

Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself.