compiz assert failure: compiz: pthread_mutex_lock.c:65: __pthread_mutex_lock: Zusicherung »mutex->__data.__owner == 0« nicht erfüllt.

[Maximilian I]

Just followed this guide: http://unity.ubuntu.com/mir/using_mir_on_pc.html. After restarting lightdm, unity won't start.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: unity 7.1.0+13.10.20130802-0ubuntu1
ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3
Uname: Linux 3.10.0-6-generic x86_64
ApportVersion: 2.12-0ubuntu2
Architecture: amd64
AssertionMessage: compiz: pthread_mutex_lock.c:65: __pthread_mutex_lock: Zusicherung »mutex->__data.__owner == 0« nicht erfüllt.
Date: Sat Aug 3 15:00:00 2013
ExecutablePath: /usr/bin/compiz
InstallationDate: Installed on 2013-08-03 (0 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130802)
MarkForUpload: True
ProcCmdline: compiz
ProcEnviron:
 LANGUAGE=de_AT:de
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=de_AT.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: unity
StacktraceTop:
 __assert_fail_base (fmt=0x7f370806fdbb <Address 0x7f370806fdbb out of bounds>, assertion=assertion@entry=0x7f370ec207ef "mutex->__data.__owner == 0", file=file@entry=0x7f370ec20dfe "pthread_mutex_lock.c", line=line@entry=65, function=function@entry=0x7f370ec208c0 <__PRETTY_FUNCTION__.8369> "__pthread_mutex_lock") at assert.c:92
 __GI___assert_fail (assertion=0x7f370ec207ef "mutex->__data.__owner == 0", file=0x7f370ec20dfe "pthread_mutex_lock.c", line=65, function=0x7f370ec208c0 <__PRETTY_FUNCTION__.8369> "__pthread_mutex_lock") at assert.c:101
 __GI___pthread_mutex_lock (mutex=0xfefefefefefefeff) at pthread_mutex_lock.c:65
 ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
 ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
Title: compiz assert failure: compiz: pthread_mutex_lock.c:65: __pthread_mutex_lock: Zusicherung »mutex->__data.__owner == 0« nicht erfüllt.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 __assert_fail_base (fmt=0x7f370806fdbb <Address 0x7f370806fdbb out of bounds>, assertion=assertion@entry=0x7f370ec207ef "mutex->__data.__owner == 0", file=file@entry=0x7f370ec20dfe "pthread_mutex_lock.c", line=line@entry=65, function=function@entry=0x7f370ec208c0 <__PRETTY_FUNCTION__.8369> "__pthread_mutex_lock") at assert.c:92
 __GI___assert_fail (assertion=0x7f370ec207ef "mutex->__data.__owner == 0", file=0x7f370ec20dfe "pthread_mutex_lock.c", line=65, function=0x7f370ec208c0 <__PRETTY_FUNCTION__.8369> "__pthread_mutex_lock") at assert.c:101
 __GI___pthread_mutex_lock (mutex=0xfefefefefefefeff) at pthread_mutex_lock.c:65
 ?? ()
 ?? ()

[Stephen M. Webb (bregma)]

Will Unity restart correctly when unity-system-compositor is disabled by commenting out the "type=unity" line in /etc/lightdm/lightdm.conf and rebooting?

[Maximilian I (maxi6594)]

No it won't.

[Stephen M. Webb (bregma)]

Added the Mir project as a bug task because it looks like it may still be an error in the mir-customized nouveau driver or something related to that.

[Robert Ancell (robert-ancell)]

Reassinging to xserver-xorg-video-nouveau as Stephen indicated it might be a driver problem, not a Mir problem.

[Maarten Lankhorst (mlankhorst)]

Sounds like an unitialized mutex. This is a problem on i386, but not really on amd64 so you won't hit it there.
Are you doing anything specific when triggering this bug?

[Maarten Lankhorst (mlankhorst)]

Unable to reproduce, is this still an issue with updates?