Xorg crash

[Fergus Incoronato]

1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu

$ lsb_release -rd
Description: Ubuntu 18.04.1 LTS
Release: 18.04

2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center

$ apt-cache policy xorg
xorg:
  Installed: 1:7.7+19ubuntu7.1
  Candidate: 1:7.7+19ubuntu7.1
  Version table:
 *** 1:7.7+19ubuntu7.1 500
        500 http://se.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
        100 /var/lib/dpkg/status
     1:7.7+19ubuntu7 500
        500 http://se.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

3) What you expected to happen

When I open the lid I expect the system to resume without logging me out.

4) What happened instead

When I close the lid of my laptop the system suspends (as intended), and when I open the lid the system resumes (as intended).

However, if I don't suspend manually before closing the lid, on system resume it seeems like I get logged out of my X session.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
Uname: Linux 4.15.0-29-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus.0000.02.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0000:02: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
CompositorRunning: None
Date: Wed Aug 8 07:05:10 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-29-generic, x86_64: installed
 nvidia, 390.48, 4.15.0-30-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:505e]
   Subsystem: Lenovo GM108M [GeForce 940MX] [17aa:505e]
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 005: ID 058f:9540 Alcor Micro Corp. AU9540 Smartcard Reader
 Bus 001 Device 004: ID 04f2:b5c0 Chicony Electronics Co., Ltd
 Bus 001 Device 002: ID 138a:0097 Validity Sensors, Inc.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 20J6CTO1WW
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=044a98fa-a770-435c-816f-9aab185e650a ro quiet splash resume=UUID=866bcee2-828c-41ee-a445-ed0fd5a2f921 vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/28/2017
dmi.bios.vendor: LENOVO
dmi.bios.version: R0FET37W (1.17 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20J6CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: dmi:bvnLENOVO:bvrR0FET37W(1.17):bd09/28/2017:svnLENOVO:pn20J6CTO1WW:pvrThinkPadT470p:rvnLENOVO:rn20J6CTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T470p
dmi.product.name: 20J6CTO1WW
dmi.product.version: ThinkPad T470p
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
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)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. 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.

[Fergus Incoronato (fergus.incoronato)]

================================================================================

> 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.

I was not able to find any crash file reated to the issue (as far as I can tell from the timestamp).

> 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.

I found the page related to my machine but I was not able to find any problem related to the issue I am experiencing (as far as I can tell from the timestamp)

> 3. If step 2 also failed then apply the workaround from bug 994921,
> reboot, reproduce the crash, and retry step 1.

I applied the fix and I will try as soon as possible.

================================================================================

I wrote down a little bit more details about the issue I am experiencing:

================================================================================

· The issue I am experiencing seems to be the same as the one described in these threads already:
» [1] https://askubuntu.com/questions/1000575/how-to-disable-account-logoff-when-closing-lid-of-laptop
» [2] https://askubuntu.com/questions/980891/suspending-by-closing-laptop-lid-causes-issues?rq=1
» [3] https://ubuntuforums.org/showthread.php?t=2372388
» [4] https://ubuntuforums.org/showthread.php?t=2315415

The author of the answers seems in all 3 examples to have failed to understand the problem described by the OP, however I linked the original posts anyway because they show two things:
1) other users seems to have encountered the same issue
2) the issue appears on a range of different versions (from 16.04 up as far as I can see)

================================================================================

· I have been running different versions of Ubuntu on 2 different systems myself:

   Machine | Version | DE | GPUs | Display | prop. driver
1) ThinkPad E530 - 16.04 - Unity - Intel - Xorg - no
2) ThinkPad E530 - 16.04 - Gnome - Intel - Xorg - no
3) ThinkPad T470p - 17.10 - Gnome - Intel + Nvidia - Xorg - no
4) ThinkPad T470p - 18.04 - Gnome - Intel + Nvidia - Xorg - yes

and this is the first time (configuration #4) that the problem presents itself.

================================================================================

[Fergus Incoronato (fergus.incoronato)]

> > 3. If step 2 also failed then apply the workaround from bug
> > 994921, reboot, reproduce the crash, and retry step 1.
>
> I applied the fix and I will try as soon as possible.

I applied the fix, rebooted, reproduced the crash, repeated step 1,
here is the id of the bug:

https://errors.ubuntu.com/oops/0248e064-9d7a-11e8-87ad-fa163eec78fa

However, after using the ubuntu-bug command on the crash file I found,
it redirects me to this page:

https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1663528

[Fergus Incoronato (fergus.incoronato)]

I repeated the process, now it seems to work correctly. Here is the bug:

https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1786638

[Fergus Incoronato (fergus.incoronato)]

I don't understand though: is the pulseaudio's crash the cause or the consequence of the undesired logout on lid-close?

[Launchpad Janitor (janitor)]

[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.]

[Daniel van Vugt (vanvugt)]

You were redirected to the pulseaudio crash because that is what your crash reports were from.

However, if you suspect the logout was caused by some different crash then please look for other crash files.