[nvidia] X Server session crash with "No space left on device" and then "EnterVT failed for gpu screen 0"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Nvidia |
New
|
Undecided
|
Unassigned | ||
xorg-server (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Ubuntu Release: Ubuntu 18.04.1 LTS
Package version: xserver-xorg: 1:7.7+19ubuntu7.1
When my laptop resumes after suspend, the desktop session crashes and a new one is started. So each time I lose all open applications and unsaved data!
The expected behavior would be obviously to restore the suspended session.
I had a look through log files and found that Xorg.0.log ends with the following error lines:
[ 6004.019] (II) NVIDIA(0): Setting mode "NULL"
[ 6004.026] (EE) modeset(G0): failed to set mode: No space left on device
[ 6004.026] (EE)
Fatal server error:
[ 6004.026] (EE) EnterVT failed for gpu screen 0
[ 6004.027] (EE)
[ 6004.027] (EE)
Please consult the The X.Org Foundation support
at http://
for help.
[ 6004.027] (EE) Please also check the log file at "/var/log/
[ 6004.027] (EE)
[ 6004.065] (EE) Server terminated with error (1). Closing log file.
tags: | added: desktop-lts-wishlist |
tags: | added: bionic |
summary: |
- X Server session crash for "No space left on device" + X Server session crash with "No space left on device" and then "EnterVT + failed for gpu screen 0" |
summary: |
- X Server session crash with "No space left on device" and then "EnterVT - failed for gpu screen 0" + [nvidia] X Server session crash with "No space left on device" and then + "EnterVT failed for gpu screen 0" |
"No space left on device" usually means your disk is full, so check that. It can also mean that the process (X server or shell) has just leaked and exhausted some particular resource.
Since it's a crash we require a stack trace to identify it properly, since it's likely other people are reporting the same. To help us find the cause of the crash please follow these steps:
1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.
2. If step 1 failed then look at https:/ /errors. ubuntu. com/user/ ID where ID is the content of file /var/lib/ whoopsie/ whoopsie- id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us.
3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1.
Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself.