lightdm crashes on window open in Ubuntu 15.10 intel

Bug #1509846 reported by rubo77 on 2015-10-25
242
This bug affects 49 people
Affects Status Importance Assigned to Milestone
xorg-server (Ubuntu)
Critical
Unassigned
Nominated for Wily by Alberto Salvia Novella

Bug Description

Symptom: xorg crashes on windows creation

How to reproduce: No 100% reproducibility, however intensively using 2D/3D acceleration triggers the bug (e.g. by opening several new windows and/or menus in a Unity desktop environment)

Affected hardware: Intel HD Graphics 4400/5000 etc
Affected software:
- kernel 4.2.0-16-generic #19-Ubuntu SMP Thu Oct 8 15:35:06 UTC 2015 x86_64
- Ubuntu 15.10 with Unity (because of compiz 2D/3D acceleration)
- any other software using direct rendering (e.g. VLC)

Workaround:
- Disable window animations in Compiz reduces the frequency of the crashes.
Use compizconfig-settings-manager for this tweak (sudo apt-get install compizconfig-settings-manager)

[original description below]

I get crashes, when I open a new window in an already started application. It happens irregularely, but I can force the crash if I open several new message windows in thunderbird. But it also happens in other applilcations, for example a new terminal window.

This is the output during the crash in /var/log/Xorg.0.log
[ 253.500] (EE)
[ 253.500] (EE) Backtrace:
[ 253.500] (EE) 0: /usr/bin/X (xorg_backtrace+0x4e) [0x55f09075b62e]
[ 253.500] (EE) 1: /usr/bin/X (0x55f0905a7000+0x1b8999) [0x55f09075f999]
[ 253.500] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7f44130a8000+0x352f0) [0x7f44130dd2f0]
[ 253.500] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f440f47f000+0x24f18) [0x7f440f4a3f18]
[ 253.500] (EE) 4: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f440f47f000+0x26157) [0x7f440f4a5157]
[ 253.500] (EE) 5: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f440f47f000+0x2b4b1) [0x7f440f4aa4b1]
[ 253.500] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f440f47f000+0x804e4) [0x7f440f4ff4e4]
[ 253.501] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f440f47f000+0x80e2c) [0x7f440f4ffe2c]
[ 253.501] (EE) 8: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f440f47f000+0x82e1a) [0x7f440f501e1a]
[ 253.501] (EE) 9: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f440f47f000+0x4197c) [0x7f440f4c097c]
[ 253.501] (EE) 10: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f440f47f000+0x59906) [0x7f440f4d8906]
[ 253.501] (EE) 11: /usr/bin/X (_CallCallbacks+0x34) [0x55f090604654]
[ 253.501] (EE) 12: /usr/bin/X (WriteToClient+0x244) [0x55f09075f274]
[ 253.501] (EE) 13: /usr/bin/X (WriteEventsToClient+0x1e2) [0x55f09060a502]
[ 253.501] (EE) 14: /usr/bin/X (0x55f0905a7000+0xf495a) [0x55f09069b95a]
[ 253.501] (EE) 15: /usr/bin/X (0x55f0905a7000+0xf5ef5) [0x55f09069cef5]
[ 253.501] (EE) 16: /usr/bin/X (0x55f0905a7000+0x5818f) [0x55f0905ff18f]
[ 253.501] (EE) 17: /usr/bin/X (0x55f0905a7000+0x5c34b) [0x55f09060334b]
[ 253.501] (EE) 18: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) [0x7f44130c8a40]
[ 253.501] (EE) 19: /usr/bin/X (_start+0x29) [0x55f0905ed6c9]
[ 253.501] (EE)
[ 253.501] (EE) Segmentation fault at address 0x0
[ 253.501] (EE)
Fatal server error:
[ 253.501] (EE) Caught signal 11 (Segmentation fault). Server aborting
[ 253.501] (EE)
[ 253.501] (EE)
Please consult the The X.Org Foundation support
         at http://wiki.x.org
 for help.
[ 253.501] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 253.502] (EE)
[ 253.502] (II) AIGLX: Suspending AIGLX clients for VT switch
[ 253.588] (EE) Server terminated with error (1). Closing log file.
---
.tmp.unity.support.test.0:

ApportVersion: 2.19.1-0ubuntu3
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
DistUpgraded: Fresh install
DistroCodename: wily
DistroRelease: Ubuntu 15.10
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.0.4, 4.2.0-11-generic, x86_64: installed
 virtualbox, 5.0.4, 4.2.0-16-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:3978]
InstallationDate: Installed on 2015-10-20 (6 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
MachineType: LENOVO 20266
Package: xorg 1:7.7+7ubuntu4
PackageArchitecture: amd64
ProcEnviron:
 TERM=screen
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic.efi.signed root=UUID=a2970568-5fac-4c99-bbdf-be6778ae16d2 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
Tags: wily ubuntu compiz-0.9
UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: '/var/log/udev'
Uname: Linux 4.2.0-16-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

_MarkForUpload: True
dmi.bios.date: 09/17/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: 76CN27WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Yoga2
dmi.board.vendor: LENOVO
dmi.board.version: 31900058STD
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo Yoga 2 Pro
dmi.modalias: dmi:bvnLENOVO:bvr76CN27WW:bd09/17/2013:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro:
dmi.product.name: 20266
dmi.product.version: Lenovo Yoga 2 Pro
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: Tue Oct 27 02:25:28 2015
xserver.configfile: default
xserver.errors:

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

rubo77 (rubo77) wrote :

some more details:

Kernel:
4.2.0-16-generic #19-Ubuntu SMP Thu Oct 8 15:35:06 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

i5 4200U, Intel HD Graphics 4400

lspci|grep Graphics
00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 09)

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in xorg (Ubuntu):
status: New → Confirmed
aldebx (aldebx) wrote :

I experience exactly the same problems as rubo77, and especially (but not limited to) when opening multiple windows or menus in Thunderbird. I also have exactly the same software/hardware configuration, except my video card is Intel(R) HD Graphics 5000.

In my case the crash log is:

[128915.663] (WW) xf86CloseConsole: KDSETMODE failed: Input/output error
[128915.663] (WW) xf86CloseConsole: VT_GETMODE failed: Input/output error
[128915.663] (EE)
Fatal server error:
[128915.663] (EE) xf86CloseConsole: VT_ACTIVATE failed: Input/output error
[128915.663] (EE)
[128915.663] (EE)
Please consult the The X.Org Foundation support
  at http://wiki.x.org
 for help.
[128915.663] (EE) Please also check the log file at "/var/log/Xorg.1.log" for additional information.
[128915.663] (EE)
[128915.663] (EE)
[128915.663] (EE) Backtrace:
[128915.665] (EE) 0: /usr/bin/X (xorg_backtrace+0x56) [0x7f5876bfb556]
[128915.665] (EE) 1: /usr/bin/X (0x7f5876a48000+0x1b7749) [0x7f5876bff749]
[128915.666] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7f587470e000+0x352f0) [0x7f58747432f0]
[128915.666] (EE) 3: /usr/bin/X (0x7f5876a48000+0x1be015) [0x7f5876c06015]
[128915.666] (EE) 4: /usr/bin/X (CloseWellKnownConnections+0x2f) [0x7f5876bfc49f]
[128915.666] (EE) 5: /usr/bin/X (0x7f5876a48000+0x1bf6f9) [0x7f5876c076f9]
[128915.666] (EE) 6: /usr/bin/X (0x7f5876a48000+0x1c051d) [0x7f5876c0851d]
[128915.666] (EE) 7: /usr/bin/X (0x7f5876a48000+0xbd801) [0x7f5876b05801]
[128915.666] (EE) 8: /usr/bin/X (xf86CloseConsole+0x153) [0x7f5876b06123]
[128915.666] (EE) 9: /usr/bin/X (ddxGiveUp+0x75) [0x7f5876ae1245]
[128915.666] (EE) 10: /usr/bin/X (0x7f5876a48000+0x5c539) [0x7f5876aa4539]
[128915.666] (EE) 11: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) [0x7f587472ea40]
[128915.666] (EE) 12: /usr/bin/X (0x7f5876a48000+0x4662e) [0x7f5876a8e62e]
[128915.666] (EE)
[128915.666] (EE) Segmentation fault at address 0x98
[128915.666] (EE)
FatalError re-entered, aborting
[128915.666] (EE) Caught signal 11 (Segmentation fault). Server aborting
[128915.666] (EE)

summary: - lightdm crashes on window open in Ubuntu 15.10 Yoga 2 Pro
+ lightdm crashes on window open in Ubuntu 15.10 intel

rubo77, thank you for reporting this and helping make Ubuntu better.

Could you please run the following command from a terminal as it will automatically gather and attach updated debug information to this report:
apport-collect -p xorg 1509846

Please ensure you have the package xdiagnose installed, and that you click the Yes button for attaching additional debugging information.

When reporting xorg related bugs in the future, please do so via the above method. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

Changed in xorg (Ubuntu):
importance: Undecided → Low
status: Confirmed → Incomplete
rubo77 (rubo77) wrote :

I found a workaround: I installed

    apt-get install kubuntu-desktop

which runs without those problem

rubo77 (rubo77) wrote : BootLog.txt

apport information

tags: added: apport-collected compiz-0.9 ubuntu wily
description: updated

apport information

apport information

rubo77 (rubo77) wrote : DpkgLog.txt

apport information

apport information

apport information

apport information

apport information

apport information

apport information

rubo77 (rubo77) wrote : Lspci.txt

apport information

rubo77 (rubo77) wrote : Lsusb.txt

apport information

apport information

apport information

apport information

apport information

rubo77 (rubo77) wrote : UdevDb.txt

apport information

apport information

rubo77 (rubo77) wrote : XorgLog.txt

apport information

apport information

rubo77 (rubo77) wrote : Xrandr.txt

apport information

rubo77 (rubo77) wrote : xdpyinfo.txt

apport information

apport information

rubo77 (rubo77) wrote :

xfce doesn't trigger the error either, so another workaround seems to work too:

    apt-get install xubuntu-desktop

rubo77, as per http://support.lenovo.com/us/en/products/laptops-and-netbooks/yoga-series/yoga-2-pro-lenovo an update to your computer's buggy and outdated BIOS is available (76CN43WW). If you update to this following https://help.ubuntu.com/community/BIOSUpdate does it change anything?

If it doesn't, could you please both specify what happened, and provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette .

Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful. As well, you don't have to create a new bug report.

Once the BIOS is updated, if the problem is still reproducible, and the information above is provided, then please mark this report Status New. Otherwise, please mark this as Invalid.

Thank you for your understanding.

tags: added: bios-outdated-43
aldebx (aldebx) on 2015-10-29
no longer affects: xorg-server
aldebx (aldebx) wrote :

I confirm that, as reported by @rubo77, this issue does not happen using non-Compiz desktop environments such as XFCE.

In the Ubuntu session, every time xorg crashes this happens _always_ on a window/menu creation (i.e. after clicking on anything that should display a new window or a new menu). However, not all window/menu creations cause the xorg to crash.

I'm now testing a session with the "animations" plugin of Compiz disabled, and will report if this is a valid workaround.

To disable the plugin use compizconfig-settings-manager
     sudo apt-get install compizconfig-settings-manager

Thank you very much @penalvch for your guidance on collecting useful bug reports. Really appreciated.

Changed in compiz (Ubuntu):
status: New → Confirmed
aldebx (aldebx) on 2015-10-29
Changed in xserver-xorg-video-intel (Ubuntu):
status: New → Confirmed
aldebx (aldebx) wrote :

This bug is related to the intel graphics driver, which is used by compiz. However is not a compiz as I managed to crash xorg in a XFCE session as well while watching a movie with VLC.

Disabling compiz windows animations helps as workaround for this bug while opening new windows/menus, but does not fix the bug itself as any other app using accelerated graphics can make xorg to crash.

Changed in compiz (Ubuntu):
status: Confirmed → Invalid

aldebx, please stop adding bug tasks and marking things duplicate of this report.

no longer affects: compiz (Ubuntu)
no longer affects: xserver-xorg-video-intel (Ubuntu)

aldebx, it will help immensely if you filed a new report with Ubuntu via a terminal:
ubuntu-bug xorg

Please ensure you have the package xdiagnose installed, and that you click the Yes button for attaching additional debugging information.

Also, please feel free to subscribe me to it.

aldebx (aldebx) on 2015-10-30
description: updated
aldebx (aldebx) wrote :

@rubo77, after identifying the problem to be likely with the Intel graphic driver, I've been testing Kernel 4.2.5-040205-generic #201510270124 SMP Tue Oct 27 01:25:49 UTC 2015 x86_64 for the past 6 hours, and it seems not to trigger any crash despite using 2D/3D graphic acceleration in Unity/Compiz and other applications.

Kernel versions can be downloaded from http://kernel.ubuntu.com/~kernel-ppa/mainline/
Please join me in testing if this bug has been fixed upstream in kernel version 4.2.5-040205-generic and up.

aldebx (aldebx) on 2015-10-30
description: updated
aldebx (aldebx) wrote :

@penalvch, thank you for assisting.

I've flagged a few other bugs as duplicates of this one to assist developers in tracking this issue given that several other users are experiencing xorg crashes on Intel graphic cards while they open new windows or menus in various applications using unity+compiz in Ubuntu 15.10

aldebx (aldebx) wrote :

I've just experienced a xorg crash with 4.2.5-040205-generic while opening a properties window inside libreoffice (with compiz animations enabled) :/

Hw specs and logs of my case are attached to bug #1511615 . Thank you for reviewing and analyzing them.

aldebx (aldebx) on 2015-10-30
Changed in xorg (Ubuntu):
status: Incomplete → New
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in xorg (Ubuntu):
status: New → Confirmed
Robert Hrovat (robi-hipnos) wrote :

It happens also with animations disabled. Almost every time I run Thunderbird.

Davernos (davefury) wrote :

Same issue here, after clicking on print icon on LibreOffice Impress and other random events.

http://paste.ubuntu.com/12997549/

Workaround confirmed: disabling window animations fixes the problem.

aldebx, to advise, just because someone is using Intel graphics, doesn't mean they have same root cause for their crash. Hence, unless you can advise where precisely in the code each case is having the issue, and it's all in the exact same line, it's best not to mark reports duplicates of others.

Changed in xorg (Ubuntu):
status: Confirmed → Incomplete

rubo77, thank you for reporting this and helping make Ubuntu better. However, your crash report is missing.

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: Low → Undecided
status: Incomplete → Invalid
Davernos (davefury) wrote :

The workaround (disabling window animations) is NOT fixing the issue.

aldebx (aldebx) wrote :

@davefury , because this is not a bug of compiz, so disabling window animations is a workaround only to the extent it doesn't trigger the intel driver/xorg bug while opening windows/menus. Other software that use the graphic card is still capable of triggering the bug, for example I was able to crash xorg while playing a video with totem.

In your case what were you doing when the crash happened?

Davernos (davefury) wrote :

@albedx, it happens often, not always, when I edit items (connections) on PAC Manager (http://sourceforge.net/projects/pacmanager/). This triggers a new window.

Its also easy to reproduce when moving Libre Office windows.

aldebx (aldebx) wrote :

@davefury, could you please try using kernel 4.3? In my case I didn't run into this issue any more ever since I upgraded several days ago. Upcoming kernels can be downloaded from http://kernel.ubuntu.com/~kernel-ppa/mainline/

Davernos (davefury) wrote :

@aldebx, sure, when I have a moment. I'm currently using xfce (xubuntu desktop) to avoid problems.

Davernos (davefury) wrote :

@aldebx, I have just recreated the crash with 4.3.0-040300-generic. Same symptoms after moving Windows around on LibreOffice. Going back to xfce.

Boris Dalstein (dalboris) wrote :

I am experiencing the same issue, but on Kubuntu 15.04. I experience a crash that logs me out every few hours or so, for seemingly random actions, but it might indeed be when a new window is created. Last crash was when doing "Ctrl+T" on Google Chrome to open a new tab. Attached is the corresponding Xorg log.

Boris Dalstein (dalboris) wrote :

Sorry, I meant Kubuntu 15.10.

I also experience this problem, often it is triggered when using Chrome and opening a new tab or window.

david (david-ubuntu-e) wrote :

This bug has been affecting me for about 4 weeks now. Lightdm crashes on random window opening. Usually a thunderbird window. VERY frustrating. I used to go 6 months between restarts. Now it crashes every day a few times.

affects: xorg (Ubuntu) → lightdm (Ubuntu)
Changed in lightdm (Ubuntu):
status: Invalid → Confirmed

In my case Chrome causes the crashes, mostly when I open a new tab. Starting Chrome with parameter --disable-gpu seems to prevent them (but rendering is much slower).

I have not experienced this crash since moving from standard Ubuntu to Xubuntu.

Yesterday I did this:

https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1510970/comments/40

… and haven't experienced crashses since then. No "--disable-gpu" for Chrome required anymore (see my comment https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1509846/comments/54).

I guess this bug report duplicates https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1510970.

Changed in lightdm (Ubuntu):
importance: Undecided → Critical
david (david-ubuntu-e) wrote :

*** Hi there, I seem to have found resolution on this very frustrating bug.

I've been going on 3 days now without a single crash, and that is with trying to instigate it with all the usual things (mostly Thunderbird opening a window)

Note that I have NOT used any other workarounds (like animation disabling, GDM instead of lightdb, switch to xubuntu etc)
Switching to xubuntu/kubuntu/whatever was not an option for me.

It resolved by proceeding to follow these steps given above by Christopher M. Penalver (penalvch) wrote on 2015-10-30: #43

 (I've pasted his note below) (doing a dist-upgrade instead of just the usual upgrade seemed to do the trick):

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 lightdm:
status: New → Confirmed
Changed in lightdm (Ubuntu):
status: Confirmed → Triaged
Jan-Åke Larsson (jalar) wrote :

Going to uxa makes the mouse pointer invisible for me. The pointer is visible on the login screen but disappears after login.

david (david-ubuntu-e) wrote :

sudo apt-get dist-upgrade

give this a try. It seems to have solved my issue on Ubuntu 15.10

This stream of comments is difficult to follow. If one of the most knowledgeable people could summarize where we are, it might be useful. I am experiencing this problem also, on a Lenovo X230 under Ubuntu 15.10, since a month or so ago.

"sudo apt-get dist-upgrade" certainly is not a solution for me (indeed, you might say that's what started the problem!), and I don't actually think Christopher M. Penalver was suggesting that as a fix.

This is certainly a "critical" problem, and most frustrating a development for what was a stable machine.

As I understand it: it will still be useful if I do a "ubuntu-bug xorg" after the next time it crashes, and after logging back in? (or from a tty login, before logging back in?). I have xdiagnose installed.

affects: lightdm (Ubuntu) → xorg-server (Ubuntu)
no longer affects: lightdm
To post a comment you must log in.