regular crash of X. lightdm is shown after crash

Bug #1519823 reported by Luca Frosini
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xorg (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

The crash happen randomly, but always when the user perform an action (especially when a new windows or new tab on browser is created).
I especially have this crash when I click on reply button on thunderbird

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
Uname: Linux 4.2.0-18-generic x86_64
.tmp.unity.support.test.0:

ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Wed Nov 25 14:18:45 2015
DistUpgraded: 2015-10-29 11:09:19,997 DEBUG enabling apt cron job
DistroCodename: wily
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. P8H77-I Motherboard [1043:84ca]
InstallationDate: Installed on 2015-01-05 (324 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic root=UUID=8d1438a5-df16-43eb-83f6-288e26294c57 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to wily on 2015-10-29 (27 days ago)
dmi.bios.date: 05/07/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0805
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8H77-M PRO
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0805:bd05/07/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.64-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3
xserver.bootTime: Wed Nov 25 12:42:54 2015
xserver.configfile: default
xserver.errors:

xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:

xserver.version: 2:1.17.2-1ubuntu9

Revision history for this message
Luca Frosini (lucafrosini) wrote :
penalvch (penalvch)
tags: added: bios-outdated-1505
penalvch (penalvch)
Changed in xorg (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Luca Frosini (lucafrosini) wrote :

Thanks for you answer. I'm going to update the bios now.
I'll let you know is the crash still happen in the next days.

Merry Christmas

L

Revision history for this message
Luca Frosini (lucafrosini) wrote :

I installed the latest bios available for my motherboard.

$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
1505
10/17/2014

Unfortunately the bug still happen.

Maybe this is a duplicated bug of this:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1510970

Revision history for this message
penalvch (penalvch) wrote :

Luca Frosini, to clarify, after the crash, is there a crash file in /var/crash?

tags: added: latest-bios-1505
removed: bios-outdated-1505
Changed in xorg (Ubuntu):
importance: Low → Medium
Revision history for this message
Luca Frosini (lucafrosini) wrote :

Sorry for late answer but I was out of office.
Yes, I have /var/crash/_usr_bin_Xorg.0.crash

I'm attaching the file, even I don't think is useful.

Happy new year

Revision history for this message
Luca Frosini (lucafrosini) wrote :

Actully I don't experiment the bug any more beacuse as suggest by Georgi and Mark in the bug https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1510970 I created the file /usr/share/X11/xorg.conf.d/20-intel.conf with the follwing content:
Section "Device"
        Identifier "Card0"
        Driver "Intel"
        Option "AccelMethod" "uxa"
EndSection

this switch from sna to uxa.

Revision history for this message
penalvch (penalvch) wrote :

Luca Frosini, thank you for reporting this and helping make Ubuntu better. However, your crash report is manually attached.

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/_my_crash_report.crash

If you do open this report, please feel free to subscribe me to it.

However, I'm closing this report 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

Changed in xorg (Ubuntu):
importance: Medium → Undecided
status: Incomplete → Invalid
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.