Xwayland crashed with SIGABRT in OsAbort()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nvidia-graphics-drivers (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Actually when I updated ubuntu yesterday, I found that there was a set of packages referring to gnome-shell 3.27.
I had tried this update before, during the past week because gnome-shell 3.27 and gnome-shell-common 2.27 were available since Wednesday (I think), however, every time I did update ubuntu lost the ability to enter the login interface (gdm), reinitializing in loop.
With the update set available yesterday, it was possible to stabilize the gdm login interface, but the system was freezing after entering user and password, before loading the gnome-shell.
Until today I was using the nouveal driver and as I had already experienced this freezing using nouveal with gnome-shell 3.26, and as I realized that the nvidia driver was more stable than the nouveal, I then decided to install again, today, the nvidea driver.
I used ubuntu-drivers autoinstall to install the nvidia driver available in graphics-
After restarting I was able to login normally and the gnome-shell interface ran normally. Then, a few seconds later, this crash message was displayed, requesting the bug report to be sent.
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: xwayland 2:1.19.6-1ubuntu2
ProcVersionSign
Uname: Linux 4.15.0-10-generic x86_64
NonfreeKernelMo
.proc.driver.
.proc.driver.
.proc.driver.
NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.25 Wed Jan 24 20:02:43 PST 2018
GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-5ubuntu1)
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CompizPlugins: No value set for `/apps/
CompositorRunning: None
CrashCounter: 1
CurrentDesktop: GNOME-Greeter:GNOME
Date: Sun Feb 25 08:52:56 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
bbswitch, 0.8, 4.15.0-10-generic, x86_64: installed
nvidia-390, 390.25, 4.15.0-10-generic, x86_64: installed
ExecutablePath: /usr/bin/Xwayland
GraphicsCard:
Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
Subsystem: Dell Device [1028:0798]
NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] [10de:1c8c] (rev a1) (prog-if 00 [VGA controller])
Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:0798]
InstallationDate: Installed on 2018-01-12 (44 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180111)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 0cf3:e007 Atheros Communications, Inc.
Bus 001 Device 003: ID 1bcf:2c01 Sunplus Innovation Technology Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Inspiron 15 7000 Gaming
ProcCmdline: /usr/bin/Xwayland :1024 -rootless -terminate -accessx -core -listen 4 -listen 5 -displayfd 6
ProcEnviron:
LANGUAGE=
PATH=(custom, no user)
XDG_RUNTIME_
LANG=pt_BR.UTF-8
SHELL=/bin/false
ProcKernelCmdLine: BOOT_IMAGE=
Renderer: Software
Signal: 6
SourcePackage: nvidia-
StacktraceTop:
OsAbort ()
?? ()
FatalError ()
?? ()
?? ()
Title: Xwayland crashed with SIGABRT in OsAbort()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 08/17/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.1.0
dmi.board.name: 0P84C9
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.
dmi.product.family: Inspiron
dmi.product.name: Inspiron 15 7000 Gaming
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.90-1
version.
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 #1731911, 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.