X session crash after resuming from suspend

[giacof]

Description: Ubuntu 18.04 LTS
Release: 18.04

xorg:
  Installed: 1:7.7+19ubuntu7

First I suspended my laptop, while a few applications were running (Firefox, Chrome and some others much smaller). A couple of hours later, I opened the lid and expected the Gnome session would resume.

What happened instead was a crash of the X server, then the login page was shown again and a new Gnome session started: the old session got killed!

In the Xorg.0.log.old file I found this, not sure if related:

[ 21189.337] (II) NVIDIA(GPU-0): Deleting GPU-0
[ 21189.338] (WW) xf86CloseConsole: KDSETMODE failed: Input/output error
[ 21189.338] (WW) xf86CloseConsole: VT_GETMODE failed: Input/output error
[ 21189.338] (WW) xf86CloseConsole: VT_ACTIVATE failed: Input/output error
[ 21189.338] (II) Server terminated successfully (0). Closing log file.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
Uname: Linux 4.15.0-24-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus.0000.01.00.0: Error: [Errno 21] È una directory: '/proc/driver/nvidia/gpus/0000:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.48 Thu Mar 22 00:42:57 PDT 2018
 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Jul 8 23:03:30 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 390.48, 4.15.0-23-generic, x86_64: installed
 nvidia, 390.48, 4.15.0-24-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Dell 4th Gen Core Processor Integrated Graphics Controller [1028:05cc]
 NVIDIA Corporation GK107GLM [Quadro K1100M] [10de:0ff6] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: Dell GK107GLM [Quadro K1100M] [1028:15cc]
InstallationDate: Installed on 2018-06-21 (17 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: Dell Inc. Precision M4800
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-24-generic root=/dev/mapper/vg-root ro scsi_mod.scan=sync quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/02/2014
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A06
dmi.board.name: 0T3YTY
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA06:bd01/02/2014:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn0T3YTY:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Precision M4800
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
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

[Daniel van Vugt (vanvugt)]

It sounds like some part of the system has crashed. Please:

1. Apply the workaround from bug 994921.

2. Look in /var/crash for crash files and if found run:
     ubuntu-bug YOURFILE.crash
   and tell us the ID of the newly-created bug.

3. If step 2 failed then look at https://errors.ubuntu.com/user/ID where ID is the contents of the /var/lib/whoopsie/whoopsie-id file on the machine. Do you find any links to recent problems on the machine? If so then please send them to us.

[giacof (giacof)]

Hi, I did apply the workaround, yet I can't find anything related in the /var/crash directory.
With my ID I only find a systemd crash on 2018-06-21 and other issues dated back to 2017 and older.

[giacof (giacof)]

Actually, this is the content of the /var/crash directory:

_usr_lib_virtualbox_VBoxHeadless.0.crash
_usr_lib_virtualbox_VBoxHeadless.0.upload

[giacof (giacof)]

I noticed the status is still incomplete. What additional information should be provided?
Thank you

[giacof (giacof)]

The issue is still happening when the laptop stays in standby for several hours!
This time I found something in the /var/crash directory: the new bug ID is #1788512, I'm not sure if it's related to this bug.

Please help to find the root cause and some workaround while it get fixed.
Than you

[giacof (giacof)]

Now there are errors at the bottom of the attached Xorg.1.log file:

[ 4387.635] (EE) modeset(G0): failed to set mode: No space left on device
[ 4387.635] (EE)
Fatal server error:
[ 4387.635] (EE) EnterVT failed for gpu screen 0
[ 4387.635] (EE)
[ 4387.635] (EE)
Please consult the The X.Org Foundation support
         at http://wiki.x.org
 for help.
[ 4387.635] (EE) Please also check the log file at "/var/log/Xorg.1.log" for additional information.
[ 4387.635] (EE)
[ 4387.672] (EE) Server terminated with error (1). Closing log file.

[John Pelly (jpelly)]

Was this ever resolved? This same thing is happening to me regularly. I'm about to give up on Ubuntu; I can't believe something so basic is broken.

[John Pelly (jpelly)]

For reference here are some of the tail lines in my /var/log/Xorg.0.log

[ 61070.548] (**) Option "fd" "28"
[ 61070.548] (II) event18 - Integrated Camera: Integrated C: device removed
[ 61070.548] (**) Option "fd" "46"
[ 61070.548] (II) event4 - SynPS/2 Synaptics TouchPad: device removed
[ 61070.548] (**) Option "fd" "27"
[ 61070.548] (II) event6 - ThinkPad Extra Buttons: device removed
[ 61070.548] (**) Option "fd" "44"
[ 61070.548] (II) event19 - MOSART Semi. 2.4G Keyboard Mouse: device removed
[ 61070.548] (**) Option "fd" "49"
[ 61070.548] (II) event20 - MOSART Semi. 2.4G Keyboard Mouse Mouse: device removed
[ 61070.548] (**) Option "fd" "41"
[ 61070.548] (II) event24 - John Pelly’s Keyboard: device removed
[ 61070.548] (**) Option "fd" "83"
[ 61070.548] (II) event7 - Video Bus: device removed
[ 61070.548] (**) Option "fd" "48"
[ 61070.548] (II) event5 - TPPS/2 IBM TrackPoint: device removed
[ 61070.549] (**) Option "fd" "67"
[ 61070.549] (**) Option "fd" "67"
[ 61070.549] (II) event21 - MOSART Semi. 2.4G Keyboard Mouse Consumer Control: device removed
[ 61070.549] (**) Option "fd" "69"
[ 61070.549] (II) event8 - Video Bus: device removed
[ 61070.549] (**) Option "fd" "77"
[ 61070.549] (II) event1 - Sleep Button: device removed
[ 61070.549] (**) Option "fd" "78"
[ 61070.549] (II) event2 - Power Button: device removed
[ 61070.549] (**) Option "fd" "79"
[ 61070.549] (II) event3 - AT Translated Set 2 keyboard: device removed
[ 61070.549] (**) Option "fd" "80"
[ 61070.549] (II) event22 - MOSART Semi. 2.4G Keyboard Mouse System Control: device removed
[ 61070.603] (II) UnloadModule: "libinput"
[ 61070.603] (II) systemd-logind: releasing fd for 13:86
[ 61070.632] (II) UnloadModule: "libinput"
[ 61070.632] (II) systemd-logind: releasing fd for 13:67
[ 61070.676] (II) UnloadModule: "libinput"
[ 61070.676] (II) systemd-logind: releasing fd for 13:66
[ 61070.696] (II) UnloadModule: "libinput"
[ 61070.696] (II) systemd-logind: releasing fd for 13:65
[ 61070.724] (II) UnloadModule: "libinput"
[ 61070.724] (II) systemd-logind: releasing fd for 13:72
[ 61070.753] (II) UnloadModule: "libinput"
[ 61070.753] (II) systemd-logind: not releasing fd for 13:85, still in use
[ 61070.753] (II) UnloadModule: "libinput"
[ 61070.753] (II) systemd-logind: releasing fd for 13:85
[ 61070.772] (II) UnloadModule: "libinput"
[ 61070.772] (II) systemd-logind: releasing fd for 13:69
[ 61070.804] (II) UnloadModule: "libinput"
[ 61070.804] (II) systemd-logind: releasing fd for 13:71
[ 61070.860] (II) UnloadModule: "libinput"
[ 61070.860] (II) systemd-logind: releasing fd for 13:88
[ 61070.860] (EE) systemd-logind: failed to release device: Device not taken
[ 61070.884] (II) UnloadModule: "libinput"
[ 61070.884] (II) systemd-logind: releasing fd for 13:84
[ 61070.928] (II) UnloadModule: "libinput"
[ 61070.928] (II) systemd-logind: releasing fd for 13:83
[ 61070.944] (II) UnloadModule: "libinput"
[ 61070.944] (II) systemd-logind: releasing fd for 13:70
[ 61070.968] (II) UnloadModule: "libinput"
[ 61070.968] (II) systemd-logind: releasing fd for 13:68
[ 61071.016] (II) UnloadModule: "libinput"
[ 61071.016] (II) systemd-logind: releasing fd for 13:82
[ 61071.105] (II) NV...

[Launchpad Janitor (janitor)]

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

[Abou anas (hamza-elmahjour)]

I really appreciate how this community is seriously working and I don't want to offend anyone but the importance of this bug is clearly very high because you have to imagine that after running a Matlab script for several hours or working on a long document or having a scientific flow of work then you have a pause for some time then you go back to work to discover that either the computer is suspended or your monitor is "asleep" and by pushing a key on the keyboard there is a complete weird pixelized colorful screen !!! You are forced to perform a "forced shutdown" by moving back to terminal ctrl+alt+F3 in my case then 'sudo shutdown' or by pushing the shutdown button in worst scenarios. So this bug is really annoying and even with ubuntu 20.04, I'm still having the same problem.

I hope someone will get interested to give us a solution. The screen is acting really weird after suspend or after the monitor goes off and when you try to log in you will see the picture attached to this message.

Thank you

[Sebastien Bacher (seb128)]

It would probably be useful to open new reports for problems on focal, it's not sure the problem is the same as the ones there and would be easier to tell things apart with new logs, we can duplicate the new report from this one if needed

[Michal Holeček (michalh)]

Still no fix ? I have just installed clean Ubuntu 20.04 an this exact thing is happening to me. It took me hours just to find this bug report... 🥲

[Daniel van Vugt (vanvugt)]

Judging by comment #7 this was actually bug 1897530 which is already fixed.

Anyone still experiencing problems should open a new bug by running:

  ubuntu-bug xorg