Xorg crash

Bug #1515972 reported by Hans-Christian Payer
20
This bug affects 2 people
Affects Status Importance Assigned to Milestone
xorg (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

xorg randomly and quite often (once an hour) crashes back to loginscreen, when klicking on various buttons (you can never say which button).
ProblemType: Crash
Architecture: amd64
Date: Fri Nov 13 12:20:39 2015
DistroRelease: Ubuntu 15.10
ExecutablePath: /usr/bin/Xorg
ExecutableTimestamp: 1443604291
ProcCmdline: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch

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-0ubuntu4
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
Date: Fri Nov 13 12:34:50 2015
DistUpgraded: 2015-10-20 12:22:39,151 DEBUG enabling apt cron job
DistroCodename: wily
DistroVariant: ubuntu
DkmsStatus: vboxhost, 4.3.26: added
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:21da]
InstallationDate: Installed on 2014-06-29 (501 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: LENOVO 4291QS0
ProcEnviron:
 LANGUAGE=de_AT:de
 TERM=screen
 PATH=(custom, no user)
 LANG=de_AT.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-18-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: Upgraded to wily on 2015-10-20 (24 days ago)
dmi.bios.date: 08/02/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 8DET51WW (1.21 )
dmi.board.asset.tag: Not Available
dmi.board.name: 4291QS0
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr8DET51WW(1.21):bd08/02/2011:svnLENOVO:pn4291QS0:pvrThinkPadX220:rvnLENOVO:rn4291QS0:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 4291QS0
dmi.product.version: ThinkPad X220
dmi.sys.vendor: LENOVO
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: Fri Nov 13 12:20:48 2015
xserver.configfile: default
xserver.errors:

xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 728
 vendor LGD
xserver.version: 2:1.17.2-1ubuntu9

Revision history for this message
Hans-Christian Payer (hanspayer) wrote :
penalvch (penalvch)
tags: added: bios-outdated-1.40
Changed in xorg (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Hans-Christian Payer (hanspayer) wrote :

I did update the BIOS, as recommended, but no change in crash behaviour. here is teh output of udo dmidecode -s bios-version && sudo dmidecode -s bios-release-date:
8DET70WW (1.40 )
05/14/2015

Changed in xorg (Ubuntu):
status: Incomplete → New
Revision history for this message
penalvch (penalvch) wrote :

Hans-Christian Payer, after the xorg crash, are there crash files in /var/crash ?

tags: added: latest-bios-1.40
removed: bios-outdated-1.40
Changed in xorg (Ubuntu):
status: New → Incomplete
importance: Low → Medium
Revision history for this message
Hans-Christian Payer (hanspayer) wrote :

yes, there are:
hans@dharma:~⟫ sudo ls -lah /var/crash/
insgesamt 72M
drwxrwsrwt 2 root whoopsie 4,0K Nov 17 14:11 .
drwxr-xr-x 13 root root 4,0K Apr 17 2014 ..
-rw-r----- 1 root whoopsie 72M Nov 17 08:50 _usr_bin_Xorg.0.crash
-rw-r--r-- 1 root whoopsie 0 Nov 17 08:50 _usr_bin_Xorg.0.upload
-rw------- 1 whoopsie whoopsie 0 Nov 17 08:50 _usr_bin_Xorg.0.uploaded

i try to upload them

Revision history for this message
penalvch (penalvch) wrote :

Hans-Christian Payer, to see if this is already resolved, could you please test http://cdimage.ubuntu.com/daily-live/current/and advise to the results?

Revision history for this message
Hans-Christian Payer (hanspayer) wrote :

Well, i did test with the live-cd, http://cdimage.ubuntu.com/daily-live/current/, for overall 3 hours with no crashes on both systems. I cant say, wether this issue is already resolved or not, because on 15.10 there are longer periods with no crashes and then they do. You can never say when. I think it its somekind poor Quality management to put it on the BIOS, i updated on both machines with no change. It is very annoying. I I am in the good will to help, but i see no progress. Browsing throug bug-reports i experience, that i am not the only one with sudden x.org crashes. So what now?

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in xorg (Ubuntu):
status: Incomplete → Expired
Revision history for this message
penalvch (penalvch) wrote :

Hans-Christian Payer, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1515972/comments/7 regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status.

Only if you need a backport to a release prior to Xenial, please provide a technical justification as to why you couldn't use Xenial going forward, and then mark this Fix Released.

Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

Changed in xorg (Ubuntu):
status: Expired → Invalid
Revision history for this message
Thomas Mayer (thomas303) wrote :

I've just seen this error in up-to-date ubuntu 16.04, HES Kernel 4.8.

Changed in xorg (Ubuntu):
status: Invalid → Confirmed
Revision history for this message
Thomas Mayer (thomas303) wrote :

For me, it's

sudo ls -lah /var/crash/
[sudo] Passwort für thomas:
insgesamt 189M
drwxrwsrwt 1 root whoopsie 682 Jun 9 07:52 .
drwxr-xr-x 1 root root 130 Jul 26 2015 ..
-rwxrwxrwx 1 root whoopsie 0 Jun 8 17:19 .lock
-rw-r----- 1 thomas whoopsie 155M Jun 6 12:04 _opt_phpstorm_PhpStorm-2017.1.1_jre64_bin_java.1000.crash
-rw-r----- 1 thomas whoopsie 7,9M Mai 31 12:33 _usr_bin_gedit.1000.crash
-rw-r--r-- 1 thomas whoopsie 0 Mai 31 12:33 _usr_bin_gedit.1000.upload
-rw-r----- 1 thomas whoopsie 1,3M Jun 8 22:46 _usr_bin_gnome-flashback.1000.crash
-rw-r--r-- 1 thomas whoopsie 0 Mai 31 12:35 _usr_bin_gnome-flashback.1000.upload
-rw-r----- 1 thomas whoopsie 1,9M Jun 2 08:02 _usr_bin_kactivitymanagerd.1000.crash
-rw-r----- 1 thomas whoopsie 15M Jun 9 07:19 _usr_bin_shutter.1000.crash
-rw-r--r-- 1 thomas whoopsie 0 Jun 4 06:53 _usr_bin_shutter.1000.upload
-rw-r----- 1 root whoopsie 2,9M Jun 9 07:53 _usr_lib_xorg_Xorg.0.crash
-rw-r----- 1 thomas whoopsie 5,1M Jun 2 08:21 _usr_share_apport_apport-gtk.1000.crash

Seems that shutter played a role in my case. I load shutter as a tray Icon. If shutter (or any other tiny tray-iconed program) brings down the whole desktop, that should not be (even if the program itself crashes).

Revision history for this message
penalvch (penalvch) wrote :

Thomas Mayer, this report was scoped to a bug that was fixed already. Please file a new report against the crash file.

Changed in xorg (Ubuntu):
importance: Medium → Undecided
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.