Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError("EnterVT failed for screen %d\n") from xf86VTEnter() from systemd_logind_vtenter()

Bug #1787332 reported by Daniel van Vugt
60
This bug affects 6 people
Affects Status Importance Assigned to Milestone
xorg-server (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

.

ProblemType: Crash
DistroRelease: Ubuntu 18.10
Package: xserver-xorg-core 2:1.19.6-1ubuntu4
ProcVersionSignature: Ubuntu 4.17.0-6.7-generic 4.17.9
Uname: Linux 4.17.0-6-generic x86_64
ApportVersion: 2.20.10-0ubuntu7
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CurrentDesktop: ubuntu:GNOME
Date: Thu Aug 16 14:15:46 2018
DistUpgraded: Fresh install
DistroCodename: cosmic
DistroVariant: ubuntu
ExecutablePath: /usr/lib/xorg/Xorg
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA controller])
   Subsystem: Lenovo HD Graphics 630 [17aa:3102]
InstallationDate: Installed on 2018-05-26 (81 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180525)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 17ef:6009 Lenovo ThinkPad Keyboard with TrackPoint
 Bus 001 Device 003: ID 045e:0047 Microsoft Corp. IntelliMouse Explorer 3.0
 Bus 001 Device 002: ID 8087:0a2b Intel Corp.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 10M7CTO1WW
ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 7 -core
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-6-generic root=UUID=d7ecc709-02c2-4413-b7e7-dfce1d2b3703 ro quiet splash vt.handoff=1
Signal: 6
SourcePackage: xorg-server
StacktraceTop:
 ()
 ()
 ()
 xf86VTEnter ()
 ()
Title: Xorg crashed with SIGABRT
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 02/06/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: M16KT47A
dmi.board.name: 3102
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN 3259627060530
dmi.chassis.type: 3
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: dmi:bvnLENOVO:bvrM16KT47A:bd02/06/2018:svnLENOVO:pn10M7CTO1WW:pvrThinkCentreM710s:rvnLENOVO:rn3102:rvrSDK0J40709WIN3259627060530:cvnLENOVO:ct3:cvrNone:
dmi.product.family: ThinkCentre M710s
dmi.product.name: 10M7CTO1WW
dmi.product.version: ThinkCentre M710s
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.93-1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.5-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

Revision history for this message
Daniel van Vugt (vanvugt) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 OsAbort () at ../../../../os/utils.c:1361
 AbortServer () at ../../../../os/log.c:877
 FatalError (f=f@entry=0x55ea826ed5d1 "EnterVT failed for screen %d\n") at ../../../../os/log.c:1015
 xf86VTEnter () at ../../../../../../hw/xfree86/common/xf86Events.c:524
 systemd_logind_vtenter () at ../../../../../../../hw/xfree86/os-support/linux/systemd-logind.c:255

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in xorg-server (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Daniel van Vugt (vanvugt) wrote : Re: Xorg crashed with SIGABRT

Looks similar to bug 1421808, but now slightly different.

summary: - Xorg crashed with SIGABRT
+ Xorg crashed with SIGABRT in OsAbort() from AbortServer() from
+ FatalError() from xf86VTEnter() from systemd_logind_vtenter()
information type: Private → Public
tags: added: bionic
Revision history for this message
Launchpad Janitor (janitor) wrote : Re: Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xf86VTEnter() from systemd_logind_vtenter()

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in xorg-server (Ubuntu):
status: New → Confirmed
Revision history for this message
Riley McDowell (lambdaman) wrote :

I've been informed that this is a duplicate of 1805873 and that further communication about this bug should happen in this thread. I am able to reproduce this bug with a specific series of steps. Here's what I know:

---

I have a laptop and docking station with 2 displays attached. I can trigger a crash of the Xorg desktop by the following series of steps.

Actual Behavior:

1. While the laptop is on the dock, put it to sleep
2. Pick up the laptop from the dock
3. Wake up the laptop while undocked
4. Use xrandr commands to adjust the laptops screen so it is the primary display
5. Put the laptop back to sleep
6. Re-dock the laptop
7. Wake up the laptop on the dock
8. Observe that Xorg has crashed, desktop state is lost, and the laptop has returned to the login screen.

Expected Behavior:

These is no combination of docking, sleeping, or xrandr display commands that can crash my X session and drop my laptop back to the login screen.

Notes on Timing of this Issue:
I've been living with this issue for many months, but it's only recently that I've realized that I can trigger it 100% of the time by running xrandr commands while undocked, then re-docking. This pattern is common if you use your laptop for work, taking it back and forth between the dock and various meeting rooms, then back to the dock again.

Revision history for this message
Riley McDowell (lambdaman) wrote :

Please let me know what I can do to help with testing/debugging/fixing/etc. I have a reliable way to reproduce the condition and am willing to participate in the process.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

This bug appears to be a little related to bug 1787337, but I can't find the official error tracker page for this one yet.

summary: Xorg crashed with SIGABRT in OsAbort() from AbortServer() from
- FatalError() from xf86VTEnter() from systemd_logind_vtenter()
+ FatalError("EnterVT failed for screen ...") from xf86VTEnter() from
+ systemd_logind_vtenter()
Revision history for this message
Riley McDowell (lambdaman) wrote : Re: Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError("EnterVT failed for screen ...") from xf86VTEnter() from systemd_logind_vtenter()

This bug seems to have stopped for me a couple of months back. Now I get black screens that have to be toggled off and back on with xrandr before they display again after undocking/redocking.

That's a minor inconvenience compared to a crashing desktop environment, so I'm quite happy. It would be good to know if anyone else has seen an improvement in this behavior.

tags: removed: cosmic
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Maybe fixed in bug 1879893?

summary: Xorg crashed with SIGABRT in OsAbort() from AbortServer() from
- FatalError("EnterVT failed for screen ...") from xf86VTEnter() from
+ FatalError("EnterVT failed for screen %d\n") from xf86VTEnter() from
systemd_logind_vtenter()
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.