Xorg crashed with SIGABRT in pixman_region_fini()

Bug #1507159 reported by Logan
30
This bug affects 6 people
Affects Status Importance Assigned to Milestone
xorg-server (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Crash upon booting from reboot.

ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: xserver-xorg-core 2:1.17.2-1ubuntu9
ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
Uname: Linux 4.2.0-16-generic x86_64
ApportVersion: 2.19.1-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Sun Oct 18 01:04:03 2015
ExecutablePath: /usr/bin/Xorg
InstallationDate: Installed on 2015-10-17 (0 days ago)
InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
ProcCmdline: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
ProcEnviron:

Signal: 6
SourcePackage: xorg-server
StacktraceTop:
 pixman_region_fini () from /usr/lib/x86_64-linux-gnu/libpixman-1.so.0
 ?? () from /usr/lib/xorg/modules/drivers/intel_drv.so
 ?? () from /usr/lib/xorg/modules/drivers/intel_drv.so
 ?? ()
 ?? ()
Title: Xorg crashed with SIGABRT in pixman_region_fini()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
Logan (lethal-logan) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 pixman_region_fini (region=region@entry=0x56553bd476c9) at ../../pixman/pixman-region.c:416
 __sna_damage_all (damage=0x56553bd476c1, width=1920, height=1080) at ../../../src/sna/sna_damage.c:1039
 _sna_damage_all (height=<optimized out>, width=<optimized out>, damage=<optimized out>) at ../../../src/sna/sna_damage.h:38
 apply_damage (region=0x7ffc671236b0, op=0x7ffc671236c0) at ../../../src/sna/sna_composite.c:449
 sna_composite (op=<optimized out>, src=<optimized out>, mask=0x0, dst=<optimized out>, src_x=<optimized out>, src_y=<optimized out>, mask_x=0, mask_y=0, dst_x=0, dst_y=0, width=1920, height=1080) at ../../../src/sna/sna_composite.c:767

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in xorg-server (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in xorg-server (Ubuntu):
status: New → Confirmed
Revision history for this message
Aielyn (g-o) wrote :

I'm getting the same error. Not from reboot, though - regular boot after a shutdown.

Revision history for this message
Paul White (paulw2u) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.

Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.

I'm setting the status of this bug to 'Incomplete' as it's not seen any activity for some time. If this is still an issue when using a currently maintained release of Ubuntu then please let us know which one(s) otherwise this bug report can be left to expire in approximately 60 days time.

Changed in xorg-server (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in xorg-server (Ubuntu):
status: Incomplete → Expired
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.