Xorg crash

Bug #1753658 reported by dwilches
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

Each time I turn my screen off I get logged out of my session. I have to log in again and all my apps have been forcefully closed (Chrome mentions it didn't close cleanly and offers me to restore my tabs, for example).

This happens after 5 minutes of inactivity (I have the setting for screen off at 5 minutes) and also when I turn off my screen by myself.

Some more info:

$ lsb_release -rd
Description: Ubuntu 17.10
Release: 17.10

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

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
Uname: Linux 4.13.0-36-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 5 21:57:53 2018
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] [1002:67df] (rev c7) (prog-if 00 [VGA controller])
   Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Radeon RX 480 [1002:0b37]
MachineType: MSI MS-7850
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/usr/bin/zsh
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-36-generic.efi.signed root=/dev/mapper/system-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/17/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V2.8
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: B85-G41 PC Mate(MS-7850)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.8:bd07/17/2014:svnMSI:pnMS-7850:pvr1.0:rvnMSI:rnB85-G41PCMate(MS-7850):rvr1.0:cvnMSI:ct3:cvr1.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7850
dmi.product.version: 1.0
dmi.sys.vendor: MSI
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

To diagnose this problem we still need a crash file. Please:

1. Apply the workaround from bug 994921.
2. Reboot and reproduce the crash.
3. Look in /var/crash for new crash files.
4. Run: ubuntu-bug /var/crash/YOURFILE.crash
5. Add a comment in this bug telling is the ID of the newly-created bug.

affects: xorg (Ubuntu) → gnome-shell (Ubuntu)
Changed in gnome-shell (Ubuntu):
status: New → Incomplete
Revision history for this message
dwilches (dwilches) wrote :

Tried two workarounds mentioned in that bug, none worked (the crash did not generate any files in /var/crash).

The first workaround I tried was:

    comment out line 23 ("'problem_types': ['Bug', 'Package'],") in '/etc/apport/crashdb.conf'.

I put an # at the beginning of line 20, not 23 because line 20 is the one that mentions problem_types, but after a restart and reproducing the crash I didn't get any new crash files in that folder.

Also tried adding `Crash` to the list of problem_types (as mentioned in https://bugs.launchpad.net/ubuntu/+source/apport/+bug/993450/comments/13 ) but same thing, no new files after a restart and a crash.

Something else I can try to generate the crash file?

Revision history for this message
dwilches (dwilches) wrote :

Found the issue when looking at `/var/log/apport.log`. This may be useful for other people to whom you ask to do that workaround:

RROR: apport (pid 2496) Tue Mar 6 21:33:37 2018: apport: report /var/crash/_usr_bin_gnome-shell.1000.crash already exists and unseen, doing nothing to avoid disk usage DoS

So I removed the crashes I already had in /var/crash. Will reproduce the crash now and report back in a moment.

Revision history for this message
dwilches (dwilches) wrote :

@vanvugt I followed your instructions and created the bug https://bugs.launchpad.net/bugs/1753912 with the crash file

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

Great, thanks. But I can't access that bug so it must be private. Unusual though, since as a member of ~ubuntu-bugcontrol I should be able to see it...

Please wait until that bug has finished retracing, then remove any sensitive personal information attachments from it, then change it from Private to Public (top right of the page).

Revision history for this message
dwilches (dwilches) wrote :

Went to the other bug and saw it is already public now.

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

Great, thanks. This is now a duplicate of bug 1724439.

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.