Bug 93875 - Random Xorg Crash when Away from Computer
Summary: Random Xorg Crash when Away from Computer
Status: RESOLVED INVALID
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/nouveau (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Nouveau Project
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-01-26 14:49 UTC by fd_mitch
Modified: 2016-02-24 04:39 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Xorg log file (1.01 MB, text/plain)
2016-01-26 14:49 UTC, fd_mitch
no flags Details
dmesg after crash (185.93 KB, text/plain)
2016-01-26 14:50 UTC, fd_mitch
no flags Details

Description fd_mitch 2016-01-26 14:49:36 UTC
Created attachment 121304 [details]
Xorg log file

I have had multiple random xorg crashes occur at different times but almost always when I am away from my computer and the lock screen is started. Sometimes it is a few minutes after I have left my computer, sometimes multiple hours. I have attached my dmesg and Xorg.0.log file.

I am using Kubuntu 15.10, with a vanilla 4.2.8 kernel.
Comment 1 fd_mitch 2016-01-26 14:50:27 UTC
Created attachment 121305 [details]
dmesg after crash
Comment 2 fd_mitch 2016-01-26 14:51:27 UTC
Here is the output of lspci for my video card:

02:00.0 VGA compatible controller: NVIDIA Corporation G96GL [Quadro FX 380] (rev a1)
Comment 3 Christopher M. Penalver 2016-02-24 04:39:19 UTC
fd_mitch@ptaff.ca, thank you for reporting this and helping make Ubuntu better. However, you are using a downstream version of the xorg stack, and kernel.

Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. First, execute at a terminal:
cd /var/crash && sudo rm * ; sudo apt-get update && sudo apt-get -y dist-upgrade && sudo service apport start force_start=1

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart. Now reproduce the crash, then open a terminal, navigate to your /var/crash directory and file your report with:
sudo ubuntu-bug /var/crash/_my_crash_report.crash

where _my_crash_report.crash is the crash you would like to report. By default, this sends the crash to the Ubuntu Error Tracker infrastructure, which is different than Launchpad. For more on this, please see https://wiki.ubuntu.com/ErrorTracker .  

However, if after doing this you would still like to have a crash report posted to Launchpad, for example to ease triage and add others to your report, one would need to open the following file via a terminal:
sudo nano /etc/apport/crashdb.conf

and comment out the line:
'problem_types': ['Bug', 'Package'],

by changing it to:
# 'problem_types': ['Bug', 'Package'],

Save, close, and file the crash report via:
sudo ubuntu-bug /var/crash/FILENAME.crash

Where FILENAME is the actual name of the file found in the folder.

However, this report is being closed since the process outlined above will deal with this issue more efficiently.

Also, please do not attach your crash report manually to this report and reopen it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.