Xwayland crashed with SIGABRT in OsAbort()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xorg-server (Ubuntu) |
Confirmed
|
Medium
|
Unassigned |
Bug Description
UI crash when using docking station with 2 external screens (DisplayLink)
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: xwayland 2:1.19.6-1ubuntu4.4
ProcVersionSign
Uname: Linux 5.3.0-45-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.13
Architecture: amd64
CompositorRunning: None
CurrentDesktop: GNOME-Greeter:GNOME
Date: Tue Mar 31 22:48:05 2020
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
evdi, 5.2.14, 5.3.0-42-generic, x86_64: installed
evdi, 5.2.14, 5.3.0-45-generic, x86_64: installed
ExecutablePath: /usr/bin/Xwayland
ExecutableTimes
ExtraDebuggingI
GraphicsCard:
Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller])
Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fa]
InstallationDate: Installed on 2020-03-13 (20 days ago)
InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1)
MachineType: LENOVO 23252F0
ProcCmdline: /usr/bin/Xwayland :1024 -rootless -terminate -accessx -core -listen 4 -listen 5 -displayfd 6
ProcCwd: /var/lib/gdm3
ProcKernelCmdLine: BOOT_IMAGE=
Signal: 6
SourcePackage: xorg-server
StacktraceTop:
OsAbort ()
?? ()
FatalError ()
?? ()
?? ()
Title: Xwayland crashed with SIGABRT in OsAbort()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 09/25/2017
dmi.bios.vendor: LENOVO
dmi.bios.version: G2ETB0WW (2.70 )
dmi.board.
dmi.board.name: 23252F0
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.family: ThinkPad X230
dmi.product.name: 23252F0
dmi.product.sku: LENOVO_MT_2325
dmi.product.
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-
version.
version.
version.
version.
version.
version.
version.
information type: | Private → Public |
This crash has the same stack trace characteristics as bug #1731911. However, the latter was already fixed in an earlier package version than the one in this report. This might be a regression or because the problem is in a dependent package.