Xorg crashed with SIGABRT in OsAbort()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xorg-server (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Ubuntu Bionic Beaver 18.04
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: xserver-xorg-core 2:1.19.6-1ubuntu1
Uname: Linux 4.15.0-rc8+ x86_64
ApportVersion: 2.20.8-0ubuntu8
Architecture: amd64
CompizPlugins: No value set for `/apps/
CompositorRunning: None
Date: Mon Feb 12 14:57:18 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExecutablePath: /usr/lib/xorg/Xorg
ExtraDebuggingI
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15dd] (rev c4) (prog-if 00 [VGA controller])
Subsystem: Hewlett-Packard Company Device [103c:83c6]
InstallationDate: Installed on 2017-12-30 (44 days ago)
InstallationMedia: Lubuntu-Next 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171227)
MachineType: HP HP ENVY x360 Convertible 15-bq1xx
ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/
ProcEnviron: PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=
Signal: 6
SourcePackage: xorg-server
StacktraceTop:
OsAbort ()
?? ()
FatalError ()
InitOutput ()
?? ()
Title: Xorg crashed with SIGABRT in OsAbort()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 11/10/2017
dmi.bios.vendor: AMI
dmi.bios.version: F.13
dmi.board.
dmi.board.name: 83C6
dmi.board.vendor: HP
dmi.board.version: 63.17
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.
dmi.modalias: dmi:bvnAMI:
dmi.product.family: 103C_5335KV HP Envy
dmi.product.name: HP ENVY x360 Convertible 15-bq1xx
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.89+
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 #1556418, 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.