Xwayland crashed with SIGABRT in OsAbort()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xorg-server (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Saw the crash dialog after waking from suspend.
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: xwayland 2:1.19.6-1ubuntu3
ProcVersionSign
Uname: Linux 4.15.0-12-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CompositorRunning: None
CurrentDesktop: GNOME-Greeter:GNOME
Date: Mon Mar 19 12:03:00 2018
DistUpgraded: 2018-03-19 12:00:29,273 ERROR got error from PostInstallScript ./xorg_
DistroCodename: bionic
DistroVariant: ubuntu
ExecutablePath: /usr/bin/Xwayland
ExtraDebuggingI
GraphicsCard:
Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller])
Subsystem: Lenovo HD Graphics 620 [17aa:224b]
InstallationDate: Installed on 2017-11-10 (129 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
MachineType: LENOVO 20HF0047IX
ProcCmdline: /usr/bin/Xwayland :1024 -rootless -terminate -accessx -core -listen 4 -listen 5 -displayfd 6
ProcKernelCmdLine: BOOT_IMAGE=
Signal: 6
SourcePackage: xorg-server
StacktraceTop:
OsAbort ()
?? ()
FatalError ()
InitOutput ()
?? ()
Title: Xwayland crashed with SIGABRT in OsAbort()
UpgradeStatus: Upgraded to bionic on 2018-03-19 (0 days ago)
UserGroups:
dmi.bios.date: 10/17/2017
dmi.bios.vendor: LENOVO
dmi.bios.version: N1WET41W (1.20 )
dmi.board.
dmi.board.name: 20HF0047IX
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.family: ThinkPad T470s
dmi.product.name: 20HF0047IX
dmi.product.
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.90-1
version.
version.
version.
version.
version.
version.
version.
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1751508, so 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. Please continue to report any other bugs you may find.