[XMir] Too many unrefs of ScreenPixmap

[Joseph Wakeling]

Crash message appeared without any warning or apparent problem with the system.

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-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
Date: Thu Sep 12 17:10:04 2013
DistUpgraded: Fresh install
DistroCodename: saucy
DistroVariant: ubuntu
ExecutablePath: /usr/bin/Xorg
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:21ce]
InstallationDate: Installed on 2013-08-19 (24 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130819)
MachineType: LENOVO 4178CTO
MarkForUpload: True
ProcCmdline: /usr/bin/X -core :0 -auth /var/run/lightdm/root/:0 -mir 0 -mirSocket /tmp/mir_socket -nolisten tcp
ProcEnviron:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-7-generic root=UUID=0317bf16-0f96-4c2e-a5a9-10fef37c9d7e ro quiet splash vt.handoff=7
Signal: 6
SourcePackage: xorg-server
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/xorg/modules/drivers/intel_drv.so
 ?? ()
 ?? ()
 ?? ()
Title: Xorg crashed with SIGABRT
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 11/30/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: 83ET73WW (1.43 )
dmi.board.asset.tag: Not Available
dmi.board.name: 4178CTO
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:bvr83ET73WW(1.43):bd11/30/2012:svnLENOVO:pn4178CTO:pvrThinkPadT420:rvnLENOVO:rn4178CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 4178CTO
dmi.product.version: ThinkPad T420
dmi.sys.vendor: LENOVO
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: Fri Sep 13 11:08:57 2013
xserver.configfile: default
xserver.errors:

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

[Apport retracing service (apport)]

StacktraceTop:
 dixGetPrivate (key=0x7f334bf637c0 <damageScrPrivateKeyRec>, privates=0x3f0) at ../../../include/privates.h:138
 dixLookupPrivate (key=0x7f334bf637c0 <damageScrPrivateKeyRec>, privates=0x3f0) at ../../../include/privates.h:168
 damageDestroyPixmap (pPixmap=0x7f334cdc14a0) at ../../../miext/damage/damage.c:1546
 sna_early_close_screen (screen=0x7f334cd91fa0) at ../../../src/sna/sna_driver.c:762
 xf86CrtcCloseScreen (screen=0x7f334cd91fa0) at ../../../../hw/xfree86/modes/xf86Crtc.c:732

[Chris Wilson (ickle)]

That's a bug in XMir, randomly freeing the front pixmap in SetScreenPixmap.

[Launchpad Janitor (janitor)]

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

[Daniel van Vugt (vanvugt)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1224296, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.