unity-system-compositor assert failure: unity-system-compositor: pthread_mutex_lock.c:65: __pthread_mutex_lock: Assertion `mutex->__data.__owner == 0' failed.

[zEn]

automatic apport report

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: unity-system-compositor 0.0.1+13.10.20130926.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
Uname: Linux 3.11.0-9-generic x86_64
ApportVersion: 2.12.5-0ubuntu1
Architecture: amd64
AssertionMessage: unity-system-compositor: pthread_mutex_lock.c:65: __pthread_mutex_lock: Assertion `mutex->__data.__owner == 0' failed.
Date: Tue Oct 1 03:22:48 2013
ExecutablePath: /usr/sbin/unity-system-compositor
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:21d3]
 NVIDIA Corporation GF119M [NVS 4200M] [10de:1056] (rev ff) (prog-if ff)
InstallationDate: Installed on 2012-06-07 (484 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
MarkForUpload: True
ProcCmdline: /usr/sbin/unity-system-compositor --from-dm-fd 10 --to-dm-fd 13 --vt 7
ProcEnviron:

Signal: 6
SourcePackage: unity-system-compositor
Title: unity-system-compositor assert failure: unity-system-compositor: pthread_mutex_lock.c:65: __pthread_mutex_lock: Assertion `mutex->__data.__owner == 0' failed.
UpgradeStatus: Upgraded to saucy on 2013-05-23 (134 days ago)
UserGroups:

modified.conffile..etc.lightdm.lightdm.conf.d.10.unity.system.compositor.conf:
 [SeatDefaults]
 type=unity
 #unity-compositor-command=unity-system-compositor.sleep
mtime.conffile..etc.lightdm.lightdm.conf.d.10.unity.system.compositor.conf: 2013-09-25T20:56:40
version.libdrm: libdrm2 2.4.46-1
version.lightdm: lightdm 1.7.17-0ubuntu1
version.mesa: libegl1-mesa-dev N/A

[Apport retracing service (apport)]

StacktraceTop:
 __assert_fail_base (fmt=0x7f953330d458 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x7f95340f37ef "mutex->__data.__owner == 0", file=file@entry=0x7f95340f3dfe "pthread_mutex_lock.c", line=line@entry=65, function=function@entry=0x7f95340f38c0 <__PRETTY_FUNCTION__.8369> "__pthread_mutex_lock") at assert.c:92
 __GI___assert_fail (assertion=0x7f95340f37ef "mutex->__data.__owner == 0", file=0x7f95340f3dfe "pthread_mutex_lock.c", line=65, function=0x7f95340f38c0 <__PRETTY_FUNCTION__.8369> "__pthread_mutex_lock") at assert.c:101
 __GI___pthread_mutex_lock (mutex=0xfefefefefefefeff) at pthread_mutex_lock.c:65
 ?? ()
 ?? ()

[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 1234578, 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.