gnome-settings-daemon crashed with SIGABRT in pa_mutex_lock()

[Iikka Lehtinen]

Bug appeared after the upgrade.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-settings-daemon 3.4.0-0ubuntu7
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic-pae 3.2.14
Uname: Linux 3.2.0-23-generic-pae i686
NonfreeKernelModules: fglrx
ApportVersion: 2.0.1-0ubuntu3
Architecture: i386
Date: Mon Apr 16 18:44:01 2012
ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release i386 (20110719.3)
ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
ProcEnviron:
 PATH=(custom, no user)
 LANG=fi_FI.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: gnome-settings-daemon
StacktraceTop:
 raise () from /lib/i386-linux-gnu/libc.so.6
 abort () from /lib/i386-linux-gnu/libc.so.6
 pa_mutex_lock () from /usr/lib/i386-linux-gnu/libpulsecommon-1.1.so
 pa_once_begin () from /usr/lib/i386-linux-gnu/libpulsecommon-1.1.so
 pa_run_once () from /usr/lib/i386-linux-gnu/libpulsecommon-1.1.so
Title: gnome-settings-daemon crashed with SIGABRT in raise()
UpgradeStatus: Upgraded to precise on 2012-03-26 (21 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:
 pa_mutex_lock (m=0x91d8950) at pulsecore/mutex-posix.c:88
 pa_once_begin (control=0xae0e05d0) at pulsecore/once.c:50
 pa_run_once (control=0xae0e05d0, func=0xae0c1ed0 <current_thread_tls_init>) at pulsecore/once.c:90
 current_thread_tls_obj () at pulsecore/thread-posix.c:66
 current_thread_tls_set (p=0x91e3d00) at pulsecore/thread-posix.c:66

[Launchpad Janitor (janitor)]

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

[Lee Davis (lee-gixxer)]

I get this on 14.04. This could be a red herring, as it occurs after I upgrade and try and reboot, which has never been possible with this release for me. With the latest nvidia-updates drivers I cannot reboot without a hard reset\powerdown. Then reboot only succeeds after a few attempts. So this could be a product of the hard-reset...

Lenovo T61P
NVidia Quadra FX 570M

Please let me know if there is any additional information that would be of help.