Xorg crashed with SIGABRT in mieqMoveToNewScreen()

[أحمد المحمودي (Ahmed El-Mahmoudy)]

I was working on the virtual terminal (tty1) then this crash happened.

It doesn't happen everytime I work on the virtual terminal

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: xserver-xorg-core 2:1.14.2.901-2ubuntu4
ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0
Uname: Linux 3.11.0-7-generic x86_64
.tmp.unity.support.test.0:

ApportVersion: 2.12.1-0ubuntu4
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Sat Sep 14 10:39:38 2013
DistUpgraded: 2013-09-12 14:05:51,239 DEBUG enabling apt cron job
DistroCodename: saucy
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 4.2.16, 3.11.0-7-generic, x86_64: installed
 virtualbox, 4.2.16, 3.8.0-29-generic, x86_64: installed
ExecutablePath: /usr/bin/Xorg
GraphicsCard:
 Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:0263]
   Subsystem: Dell Device [1028:0263]
InstallationDate: Installed on 2011-07-23 (783 days ago)
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110426)
MachineType: Dell Inc. Latitude E5500
MarkForUpload: True
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdline: /usr/bin/X -core :0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
ProcEnviron:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-7-generic root=UUID=08093546-f13c-4443-9933-8cd8c8537582 ro quiet splash vt.handoff=7
Signal: 6
SourcePackage: xorg-server
StacktraceTop:
 mieqProcessDeviceEvent ()
 mieqProcessInputEvents ()
 ProcessInputEvents ()
 ?? ()
 ?? ()
Title: Xorg crashed with SIGABRT in mieqProcessDeviceEvent()
UpgradeStatus: Upgraded to saucy on 2013-09-12 (1 days ago)
UserGroups:

dmi.bios.date: 04/15/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A11
dmi.board.name: 0DW634
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA11:bd04/15/2009:svnDellInc.:pnLatitudeE5500:pvr:rvnDellInc.:rn0DW634:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Latitude E5500
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.10+13.10.20130828.2-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.46-1
version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu6
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1
xserver.bootTime: Sat Sep 14 10:39:55 2013
xserver.configfile: default
xserver.errors:

xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 21569
 vendor SEC
xserver.version: 2:1.14.2.901-2ubuntu4

[Apport retracing service (apport)]

StacktraceTop:
 mieqMoveToNewScreen (event=0x7fd913062480 <event.15501>, event=0x7fd913062480 <event.15501>, screen=0x7fd913b2c5f0, dev=0x7fd914754060) at ../../mi/mieq.c:494
 mieqProcessDeviceEvent (dev=dev@entry=0x7fd914754060, event=event@entry=0x7fd913062480 <event.15501>, screen=screen@entry=0x7fd913b2c5f0) at ../../mi/mieq.c:536
 mieqProcessInputEvents () at ../../mi/mieq.c:627
 ProcessInputEvents () at ../../../../hw/xfree86/common/xf86Events.c:165
 Dispatch () at ../../dix/dispatch.c:357

[penalvch (penalvch)]

أحمد المحمودي (Ahmed El-Mahmoudy), this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p xorg-server REPLACE-WITH-BUG-NUMBER

Please note, given that the information from the prior release is already available, doing this on a release prior to the development one would not be helpful.

Thank you for your understanding.

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

[Dmitry Shachnev (mitya57)]

Yes, this is still an issue with the latest trusty.

[penalvch (penalvch)]

Dmitry Shachnev, could you please comment regarding when you are in Trusty and your crash happens, does apport come up requesting to create a new report that funnels you here, or would it have you make a new report?

[Dmitry Shachnev (mitya57)]

Christopher, sorry, for some reason I did not run apport-collect when I got this crash (but Apport definitely popped up and said my crash is a duplicate of this bug). Also, I got it only once and can't reproduce it anymore.

[penalvch (penalvch)]

Dmitry Schanev, ok. If it continues to happen, so your hardware and problem may be tracked, could you please file a new report by executing the following in a terminal:
ubuntu-bug xorg

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

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.