Ubuntu
xorg-server package

[hybrid] Xorg crashed with SIGABRT in DamageRegister()

Bug #1194114 reported by Samuele on 2013-06-24

This bug affects 12 people

Affects		Status	Importance	Assigned to	Milestone
	xorg-server (Ubuntu)	Confirmed	Medium	Unassigned

Bug Description

Xorg crashed

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: xserver-xorg-core 2:1.13.3-0ubuntu13
Uname: Linux 3.9.7-030907-generic x86_64
.tmp.unity.support.test.0:

ApportVersion: 2.10.2-0ubuntu2
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
CrashCounter: 1
Date: Mon Jun 24 14:38:38 2013
DistUpgraded: 2013-06-15 12:02:31,293 DEBUG enabling apt cron job
DistroCodename: saucy
DistroVariant: ubuntu
ExecutablePath: /usr/bin/Xorg
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Device [1043:1457]
NVIDIA Corporation GF119M [GeForce 610M] [10de:1058] (rev a1) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Device [1043:1457]
InstallationDate: Installed on 2013-06-14 (9 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MachineType: ASUSTeK COMPUTER INC. K55VD
MarkForUpload: True
ProcCmdline: /usr/bin/X :0 -core -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch -background none
ProcEnviron:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.9.7-030907-generic root=UUID=a6036e43-2276-4f02-a312-1f90222e0f8a ro quiet splash vt.handoff=7
Signal: 6
SourcePackage: xorg-server
StacktraceTop:
DamageRegister ()
?? ()
BlockHandler ()
WaitForSomething ()
?? ()
Title: Xorg crashed with SIGABRT in DamageRegister()
UpgradeStatus: Upgraded to saucy on 2013-06-15 (9 days ago)
UserGroups:

dmi.bios.date: 03/12/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: K55VD.203
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: K55VD
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK55VD.203:bd03/12/2012:svnASUSTeKCOMPUTERINC.:pnK55VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK55VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: K55VD
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.45-2ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.3-0ubuntu4
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.3-0ubuntu4
version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu13
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.9-0ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.8-0ubuntu1
xserver.bootTime: Mon Jun 24 14:39:23 2013
xserver.configfile: default
xserver.errors:
Failed to load module "nvidia" (module does not exist, 0)
Failed to load module "nvidia" (module does not exist, 0)
NOUVEAU(G0): [XvMC] Failed to initialize extension.
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.13.3-0ubuntu13
xserver.video_driver: intel

Tags:

Revision history for this message

Samuele (samuelecleversun-deactivatedaccount-deactivatedaccount) wrote on 2013-06-24:

BootDmesg.txt Edit (84.7 KiB, text/plain; charset="utf-8")
BootLog.txt Edit (6.3 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (9.2 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (3.4 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (863 bytes, text/plain; charset="utf-8")
DpkgLog.txt Edit (3.0 MiB, text/plain; charset="utf-8")
GconfCompiz.txt Edit (43.3 KiB, text/plain; charset="utf-8")
LightdmDisplayLog.txt Edit (2.9 KiB, text/plain; charset="utf-8")
LightdmGreeterLog.txt Edit (13.4 KiB, text/plain; charset="utf-8")
LightdmGreeterLogOld.txt Edit (7.2 KiB, text/plain; charset="utf-8")
LightdmLog.txt Edit (7.2 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (33.0 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (473 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (7.5 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (3.9 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (22.4 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (4.0 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (770 bytes, text/plain; charset="utf-8")
Registers.txt Edit (767 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (1.2 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (3.2 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (138.9 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (364.2 KiB, text/plain; charset="utf-8")
UnitySupportTest.txt Edit (611 bytes, text/plain; charset="utf-8")
XorgLog.txt Edit (41.8 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (64.4 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (5.3 KiB, text/plain; charset="utf-8")
xdpyinfo.txt Edit (6.8 KiB, text/plain; charset="utf-8")
xserver.devices.txt Edit (358 bytes, text/plain; charset="utf-8")
xserver.outputs.txt Edit (832 bytes, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2013-06-24:

StacktraceTop:
DamageRegister (pDrawable=0x0, pDamage=0x7f098d25a9b0) at ../../../miext/damage/damage.c:1774
xf86RotatePrepare (pScreen=0x7f098d00ae00) at ../../../../hw/xfree86/modes/xf86Rotate.c:171
xf86RotateRedisplay (pScreen=0x7f098d00ae00) at ../../../../hw/xfree86/modes/xf86Rotate.c:192
xf86RotateBlockHandler (pScreen=0x7f098d00ae00, pTimeout=0x7fffb2d05148, pReadmask=0x7f098c971ee0 <LastSelectMask>) at ../../../../hw/xfree86/modes/xf86Rotate.c:238
BlockHandler (pTimeout=pTimeout@entry=0x7fffb2d05148, pReadmask=pReadmask@entry=0x7f098c971ee0 <LastSelectMask>) at ../../dix/dixutils.c:390

Revision history for this message

Apport retracing service (apport) wrote on 2013-06-24: Stacktrace.txt

Stacktrace.txt Edit (3.9 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2013-06-24: ThreadStacktrace.txt

ThreadStacktrace.txt Edit (8.1 KiB, text/plain)

Changed in xorg-server (Ubuntu):
importance:	Undecided → Medium
tags:	removed: need-amd64-retrace

Jamie Strandboge (jdstrand) on 2013-06-24

information type:

Private Security → Public

Revision history for this message

Launchpad Janitor (janitor) wrote on 2013-08-26: Re: Xorg crashed with SIGABRT in DamageRegister()

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

Changed in xorg-server (Ubuntu):
status:	New → Confirmed

Timo Aaltonen (tjaalton) on 2013-09-26

summary:

- Xorg crashed with SIGABRT in DamageRegister()
+ [hybrid] Xorg crashed with SIGABRT in DamageRegister()

Revision history for this message

penalvch (penalvch) wrote on 2014-01-07:

Samuele, 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

Changed in xorg-server (Ubuntu):
importance:	Medium → Low
status:	Confirmed → Incomplete

Apport retracing service (apport) on 2014-01-21

tags:

added: trusty

Karma Dorje (taaroa) on 2014-01-21

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

penalvch (penalvch) on 2014-01-21

tags:

added: bios-outdated-411
removed: trusty

penalvch (penalvch) on 2014-01-21

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

Apport retracing service (apport) on 2014-01-31

tags:

added: trusty

Revision history for this message

Bruce Pieterse (octoquad) wrote on 2014-02-01:

Looks like the GeForce 6xxM graphic cards might be the cause of this?

Revision history for this message

Chris Wilson (ickle) wrote on 2014-02-01:

The interation between -intel and -nouveau is definitely a suspect here.

Revision history for this message

penalvch (penalvch) wrote on 2014-02-02:

Despite no response from OR (Samuele), for now marking to Confirmed due to apport auto-marking duplicates, and Medium as it's reproducible in Trusty by a few others.

Changed in xorg-server (Ubuntu):
importance:	Low → Medium
status:	Incomplete → Confirmed

Apport retracing service (apport) on 2015-03-26

tags:

added: vivid

Report a bug

This report contains Public information

Everyone can see this information.

Duplicates of this bug

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

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

Ubuntuxorg-server package

[hybrid] Xorg crashed with SIGABRT in DamageRegister()

Bug Description

Duplicates of this bug

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
xorg-server package